Course 12 — Integrated Project Practicum

Series · Northbank case · Glossary · References

This practicum brings the series together. Your team must establish a common basis, produce connected work, examine it, and defend its recommendation.

The project changes during the exercise. New information will challenge the scope, forecast, technical basis, and delivery claim.

Your work product is an examined project decision package. Its conclusions must fit the evidence and authority available at each event.

Prerequisites and working arrangements

Complete Courses 01 to 11. Bring the earlier portfolio as working material. Check its revision and source basis before reuse.

Use six participants and one facilitator. Four participants can combine compatible roles. Arrange an independent reviewer for each assessed output.

The facilitator represents the sponsor and the relevant technical authorities. The facilitator records simulated decisions under the limits in A01.

Read the role cards before starting. Use Packets A to D from the case. The facilitator releases events in D03 order.

Participants may already know the case. At each event, use only the released record set for that decision. Identify later evidence separately.

Allow twelve working hours. Hold several sessions if necessary. Preserve the working revision when a session ends.

Learning outcomes

After this practicum, you can:

• Establish and maintain a shared decision basis.
• Coordinate project management and project engineering contributions.
• Assess changes without creating unsupported approvals.
• Produce and independently examine an integrated recommendation.
• Explain your own reasoning, limits, and responsibility.

Lesson — Work from evidence to a combined result

A team's result needs more than several competent documents. Their requirements, configuration, assumptions, forecasts, and conclusions must agree where they interact.

Allocate each output to a producer. Give that producer its inputs, intended use, boundaries, and examination conditions.

State dependencies as conditions. “Procurement needs engineering” is incomplete. Procurement needs an identified, technically reviewed purchase package and expenditure authority.

Keep decisions specific. Approval of an investigation permits that investigation. It does not approve the future design or operating result.

A later event can invalidate a conclusion or expose an omitted condition. Identify the affected outputs before repairing them.

Retain valid work. Repeat examination when a change affects its grounds. Record the new decision without silently replacing the earlier decision basis.

The reviewer examines an identified revision for a stated purpose. The reviewer must have suitable competence and independence from its production.

Consider shared interests, assumptions, and relationships that could impair the review. Nonparticipation in production alone does not establish suitable scrutiny.

Examine consequences for operators, site personnel, other affected people, and the environment. State where evidence is needed to assess those effects.

Report readiness truthfully. Identify incentive conflicts and the grounds of dissent. Apply assigned information-sharing conditions when providing evidence to reviewers.

Northbank supplies no confidentiality clause or legal determination. Identify any needed condition without inventing it. Use an appropriate route for significant concerns.

Review findings belong with the claim they affect. The producer repairs the work. The reviewer confirms the affected repair.

If the reviewer previously produced the affected item, obtain another reviewer. The facilitator can arrange a mentor or a reviewer from another team.

Role cards

The cards describe exercise responsibilities. Use A01 for decision rights. Each participant must question unsupported conclusions, including those outside their current card.

Project manager

Coordinate the undertaking's scope, resources, expenditure, schedule, contracts, and forecast. Prepare sponsor decisions when commitments need amendment.

Maintain the integrated action plan. Explain the difference between the authorized budget and the current forecast.

Do not treat schedule pressure as technical approval. Give technical and operating conditions a visible place in the plan.

Project engineer

Coordinate the technical basis, requirements, operating cases, discipline inputs, and interfaces. Identify the conditions that dependent work needs.

Prepare technical decision requests within the assigned remits. Explain the effect of proposed changes on the combined result.

Keep legal applicability visible under A06. Identify which design or release decisions require that missing basis.

Discipline representative

Examine the mechanical, electrical, civil, or controls question assigned in the phase. State your competence limits within the simulation.

Use the supplied facts to identify missing inputs and necessary checks. Prepare an interface or examination plan for the assigned contribution.

Do not invent calculations, selected equipment data, field observations, or technical approval. Identify the competent examination that a real project would need.

Procurement and contracts coordinator

Identify the purchase package, proposed configuration, price basis, delivery conditions, and required authorizations.

Check whether the proposed supplier response supports a commitment. Record exclusions and conditions that affect other team members.

Return technical substitutions to the relevant technical authority. Separate a supplier proposal from an accepted project requirement.

Operations representative

Explain the need behind the requested capacity and changeover function. Identify operating, maintenance, training, and receiving conditions.

Examine the proposed result from its intended use. Prepare a bounded receiving recommendation with remaining obligations.

Do not treat an operating preference as an approved scope amendment. Ask the sponsor to decide any proposed departure from A02.

Independent reviewer and information controller

Maintain the source and decision index. Preserve output identity, revision, status, and the source set used in each phase.

Independently examine assigned outputs that you did not produce. Record findings against specific claims and requirements.

Check whether the revised outputs address the findings. Record closure on evidence or a decision within the decision owner's authority. Identify any factual claim that remains unestablished.

Rotate responsibilities

Number participants 1 to 6. Assign the six cards in the order above during Phase 0.

Move each participant to the next card at each phase from Phase 1 to Phase 5. Move the sixth card to the first.

For Phase 6, assign roles to preserve independent examination of the final package. Record each person's production and review contributions.

Transfer the current revision, open findings, decisions, and next action at each rotation. The next participant must inspect the actual output.

For a four-person team, combine project engineering with discipline representation. Combine procurement with information control. Keep production and independent examination separate.

Use the facilitator or another team for conflicted reviews. Role rotation alone does not establish independence or technical competence.

Phase 0 — Establish the working basis

Use A01 to A07 and B03. Treat B03 as an initial coordination input. Preserve its missing owners and dates as open matters.

1. Establish a source index.
2. Identify the approved scope and commitments.
3. Identify the authority for each decision type.
4. Assign owners to the unresolved interfaces.
5. Define the conditions for the next dependent activity.
6. Select a reviewer for the first purchase-package recommendation.

Produce a one-page project basis, a source index, and an interface table. Include the missing hydraulic and legal basis.

Record proposed owners and timing as your team's planning decisions. Do not report them as original source facts.

Phase 1 — Respond to the supplier

Event prompt: The supplier requests acceptance of B01 within two working days. It wants to preserve its proposed delivery slot.

Release B01 and B02. The supplied motors are rated for 480 V. A04 records a 600 V site observation.

1. Compare the submission with the governing project basis.
2. Identify the unresolved technical and procurement conditions.
3. Prepare a purchase-package recommendation.
4. Request the applicable technical disposition from the facilitator.
5. Examine the recommendation independently.
6. Record the facilitator's decision.

Produce a supplier response, interface actions, and a decision request. Identify the evidence needed for any later equipment acceptance.

Give procurement a usable instruction. State which commitment, if any, the decision authorizes. Preserve the decision's conditions in the current working basis.

Phase 2 — Respond to the requested scope change

Event prompt: Operations asks the team to adopt 22 litres per second and automatic changeover under A05.

Release A05 as the current request. A02 still requires 18 litres per second. The sponsor has requested an impact assessment.

1. Explain the operational need stated in A05.
2. Assess the affected requirements and interfaces.
3. Identify missing evidence for the impact assessment.
4. Compare the proposed change with retaining the approved scope.
5. Prepare a sponsor decision request.
6. Record the facilitator's disposition.

Produce a change assessment and revised action plan. Distinguish automatic changeover from the changeover function that A02 requires the project to confirm.

Identify any forecast exclusions. Carry the earlier voltage issue into the revised interface account.

Phase 3 — Respond to the forecast

Event prompt: C03 arrives for the existing 18 litres per second scope. The sponsor asks whether the original commitments remain credible.

Release C01 to C03. Treat cost and duration values as exercise assumptions. Use the sequential calculation before considering alternatives.

1. Calculate the difference between the forecast and budget.
2. Calculate the sequential delivery and handover weeks.
3. Identify the technical limits of the forecast.
4. Prepare options for the commitment decision.
5. Request the sponsor's disposition.
6. Update the forecast without silently changing the approved commitments.

Produce a cost comparison, schedule calculation, and commitment decision request. Explain the conditions needed before proposed recovery could become credible.

Do not add recorded actual expenditure to C03 again. Its item totals already include that expenditure.

Phase 4 — Respond to the acceptance claim

Event prompt: The simulation moves to a later installation scenario. C04 arrives with a cover sheet claiming complete acceptance.

Release C04 and C05. This time change supplies the reported observations. It does not establish that earlier design gaps were resolved.

The reported test observed 18 litres per second during one normal condition. It leaves several scenarios unexercised and lacks complete configuration information.

Establish intended behavior and examination coverage before calling a specific test mandatory. Distinguish untested behavior from observed failure.

1. Compare each acceptance claim with its evidence.
2. Identify the unresolved configuration and readiness conditions.
3. Prepare an assurance finding.
4. Define the additional examination needed for proposed reliance.
5. Request the applicable technical and receiving decisions.
6. Prepare a bounded handover recommendation.

Produce a claim-to-evidence table, examination plan, and handover recommendation. Identify the responsible recipients for continuing obligations.

Keep the observed result available. Correct any broader conclusion that the observation cannot support.

Phase 5 — Respond to incentives and adverse evidence

Event prompt: D02 reveals the handover bonus, document-count reporting, and closure of the junior engineer's changeover concern.

Release D01 and D02. The sponsor requests a credible continuation decision. None of the recovery proposals has confirmed supporting conditions.

1. Examine the recorded closure of the concern.
2. Compare the reported progress with the readiness evidence.
3. Draw one evidence-based feedback explanation.
4. Prepare a corrected project status.
5. Compare continuation, reduction, and suspension.
6. Submit the recommended direction for the appropriate decisions.

Produce a leadership memorandum and revised decision table. Include conditions for supplier alternatives, activity overlap, and any proposed temporary use.

Explain who could be affected by premature reliance. Identify the consequences that require further examination and the responsible reporting route.

Address the reporting arrangement without assuming personal motives. Preserve the concern's technical basis and route it to competent examination.

Decision requests and adverse findings

Use one table for each consequential request. Name the decision question, authority, options, evidence, uncertainties, recommendation, conditions, and affected outputs.

The facilitator can grant, qualify, or reject the request. A decision becomes a new simulated case event with an identity and exact scope.

An unanswered request remains open. A conditional decision authorizes only the work within its stated conditions.

Identify each adverse finding by the affected claim, source evidence, consequence, responsible producer, and required closure evidence.

The producer must either repair the defect or defend the original account with adequate evidence. Record the reviewer’s confirmed disposition.

Worked example — Separate an observation from acceptance

A team receives a witnessed test from another project. It establishes one performance result under stated conditions.

The team lists the result as evidence for that condition. It then compares the proposed acceptance claim with the full examination requirements.

A required failure response has no test evidence. The team records a finding and prepares the missing examination plan.

The relevant authority can consider a bounded decision where the applicable requirements permit it. The team preserves the unexamined condition and its consequences.

The report therefore remains useful without carrying an unsupported claim of complete acceptance.

Transfer example

A transport project receives a bridge inspection report. The report covers visible surfaces during one inspection.

The receiving team identifies what the inspection establishes and which proposed uses need other evidence. It preserves those distinctions in its recommendation.

The same practice applies to software tests, factory inspections, training records, and supplier certificates.

Practice — Rehearse an event response

Before the timed phases, use A03, A04, and a blank supplier-response page. One participant presents the legacy schedule as current evidence.

1. Ask which source establishes the current condition.
2. Explain the source's limits.
3. Identify the required next contribution.
4. State the authority needed for the proposed decision.

Change roles. Repeat the exchange with a different claim. Use the same source set without inventing a new approval.

Knowledge check

1. What must an incoming participant inspect during role rotation?
2. What makes a reviewer independent for an assigned output?
3. How must the team treat a facilitator's conditional decision?
4. What does the Phase 4 time change establish about earlier technical gaps?
5. Why must C03 remain separate from the 22 litres per second proposal?
6. How can the team finish this practicum while project acceptance remains unsupported?

Assessed assignment — Integrated package and defense

Assemble one coherent decision package. Use the repaired phase outputs and their decision history.

Include the project basis, source index, interface account, purchase recommendation, change assessment, forecast, assurance findings, handover recommendation, and continuation memorandum.

Use links or record identifiers to avoid unnecessary duplication. Include a short cover that states the requested decisions and proposed reliance.

During Phase 6, present a twenty-minute team defense. The facilitator and reviewer question the evidence, authority, consequences, and connected outputs.

Complete the required repairs within the remaining phase time. If required evidence remains unavailable, state its effect on the recommendation.

During Phase 7, each participant writes a two-page individual explanation. Identify one personal contribution, one changed judgment, and one unresolved consequential condition.

Each participant then receives a ten-minute examination. Explain a decision outside your final role and respond to one adverse finding.

The assessment uses five observable criteria:

1. The basis identifies source revisions, statuses, governing commitments, and simulated decisions without unsupported authority.
2. The integrated plan gives usable owners, interfaces, prerequisites, forecasts, and consequences of change.
3. The decision requests distinguish sponsor, technical, procurement, and operating authority with explicit conditions.
4. The assurance and handover conclusions match the evidence and preserve unresolved obligations.
5. Each participant defends the reasoning, addresses findings and ethical consequences, and shows the affected repairs within the team's integrated result.

Meet all five criteria. A team result does not establish each participant's understanding. An unsupported individual explanation requires individual repair.

Individual-study adaptation

Use a mentor as facilitator, sponsor, technical authority, and reviewer. Keep separate output pages for each role you perform.

Complete the phases in order. Before each event, give the mentor the current source set and working revision.

Ask the mentor to roleplay the requesting party. Prepare your response before reading the instructor guidance.

Use a fresh output revision for each repaired conclusion. Ask the mentor to examine independence limits when you occupy several producer roles.

Complete the same written package and individual defense. Label the result as a facilitated individual practicum in your portfolio.

Portfolio and references

Keep the final package, phase decisions, review findings, repaired versions, and individual explanation. Keep an index that makes their relationships retrievable.

Use the references for further study. Compare the source manuals' basis, dependency, examination, and integration principles with your experience.

Identify one practice to improve on your next project. State the evidence that would show whether it helps the intended result.