# Teaching Project Practice for Human Teams

This guide helps an instructor run the twelve-course series. Use it with the learner courses, the Northbank case, and the course answer guides.

The aim is competent practice that another person can examine. Ask learners to explain their basis, their actions, and the consequences of relying on their work.

## Prepare the teaching group

Identify the learners' work, experience, and professional context. Include project managers, engineers, designers, coordinators, and other participants where possible.

Agree on the learning purpose. A new participant may need reliable individual practice. An experienced group may need stronger coordination or better change decisions.

Use actual discipline specialists when a discussion requires technical knowledge beyond the supplied case. The Northbank records support project reasoning. They do not provide a complete pump design.

Select a mentor for an individual learner. The mentor can act as reviewer, sponsor, or receiving party in different sessions.

## Teaching materials

Use the [series index](index.html) for learner navigation. Use the [case packet](case-study.html) for exercise inputs. Use the [glossary](glossary.html) for shared meanings.

Keep the following guides available to instructors:

| Courses | Instructor guide |
| --- | --- |
| 01 to 04 | [Professional and information foundations](instructors/01-04-foundations.html) |
| 05 to 07 | [Judgment and project definition](instructors/05-07-judgment-definition.html) |
| 08 to 10 | [Execution and delivery](instructors/08-10-execution-delivery.html) |
| 11 and 12 | [Leadership and practicum](instructors/11-12-leadership-practicum.html) |

Instructor guides contain answer guidance. Do not distribute their answers before an assessed exercise when that would defeat the exercise.

Provide accessible copies of the source records. Allow paper, a text editor, or an organization's approved document system. Assess the work's meaning and usability.

## Run a course

Use three teaching blocks. Adjust their length to the group and the work.

### Explain and examine

State the course's learning outcomes. Ask learners to identify a related problem from their experience.

Teach the lessons in order. Discuss the worked example. Ask what the source supports and what remains unestablished.

Have learners answer the knowledge check. Use the answers to identify misunderstanding. Revisit a lesson when the misunderstanding affects later work.

### Practice and review

Release the specified case records. Give learners the practice assignment and its requested outputs.

Assign a producer and a reviewer. The reviewer must have enough context to examine the work. The producer explains the basis and answers questions.

Check competence, production involvement, and interests that could impair scrutiny. Use additional scrutiny where those limits warrant it.

The reviewer identifies defects with evidence. The producer repairs confirmed defects. Ask both participants to explain what changed and why.

### Assess and continue

Use the assessed assignment and its five criteria. Examine the learner's actual output. Ask follow-up questions where the output leaves their understanding unclear.

Rate each criterion separately. Use the following meanings:

| Rating | Meaning | Next action |
| --- | --- | --- |
| Meets the criterion | The output and explanation demonstrate the required practice. | Retain the output as a portfolio contribution. |
| Needs repair | The evidence identifies a defect in the practice or result. | Identify the defect and ask for a focused repair. |
| Insufficient evidence | The available work does not establish whether the criterion is met. | Ask for the missing demonstration or explanation. |

Close the assignment when each criterion is met. Do not average away a failed criterion with unrelated strengths.

Allow different defensible solutions. Compare each solution with its actual source basis, authority, reasoning, uncertainty, and consequences.

A classroom assessment establishes the learning result demonstrated in that exercise. It does not approve an actual engineering design or grant a professional appointment.

## Use the case in stages

Release Packet A for Courses 01 to 04. It introduces the assignment, document status, conflicting sources, proposals, and unresolved applicability.

Release Packet B for Courses 05 to 07. It adds supplier pressure, a coordination problem, and incomplete interfaces.

Release Packet C for Courses 08 to 10. It adds cost and schedule forecasts, limited test observations, and incomplete operating readiness.

Release Packet D for Courses 11 and 12. It adds leadership choices, distorted incentives, weak reporting, and staged practicum events.

Packet C includes a later installation observation. It does not prove that earlier design and authority gaps were resolved. Require evidence for each claimed resolution.

In Course 12, use the event sequence in its instructor guide. Record each simulated decision as a new event. Preserve its authority, scope, conditions, and consequences.

Avoid coaching learners toward a hidden single answer. Give them sufficient inputs and a clear question. Challenge their grounds for the proposed decision.

## Prepare the requirements exercise

The offline exercise uses A06. Learners identify missing applicability inputs and the work those gaps prevent. This exercise needs no internet connection.

For an optional real-jurisdiction exercise, select one actual jurisdiction. Identify the facility classification and assignment boundary. Obtain current official instruments before the session.

Supply the adoption instrument, relevant amendments, and the applicable project or contract excerpt. Include enough context to interpret each extract.

Distinguish legislation, regulator standards, national guidance, and project requirements. A current publication date does not by itself establish adoption.

Ask learners to show the applicability chain. Ask them to state where an interpretation requires another authority or specialist.

Do not introduce invented legal clauses as real law. Do not treat the Northbank case's omission as permission to infer a jurisdiction.

## Calibrate assessment

Before assessment, examine one practice submission with another instructor or experienced reviewer. Compare your findings against the course criteria.

Discuss disagreements about the evidence and criterion. Resolve the teaching interpretation before assessing the rest of the group.

Retain enough explanation for the learner to understand a finding. A score without its grounds gives little help with repair.

Check the following recurring defects:

- A proposal appears as an approved requirement.
- A recent file appears as the governing revision without evidence.
- A survey observation supports a conclusion beyond its scope.
- A forecast appears as an amended budget or target.
- A review or test claim exceeds the examination performed.
- A document count substitutes for technical readiness.
- A concern is closed without evidence or an authorized disposition.
- A handover records file transfer but leaves responsibility unassigned.

A disposition states what a decision changes. It does not supply missing evidence of performance or conformity. Check its authority and applicable limits.

Require repairs to preserve valid evidence. A corrected submission must not conceal what the learner changed or the assumption still unresolved.

## Build a learning portfolio

The portfolio develops one connected case. Course outputs may revise or extend earlier outputs.

| Courses | Portfolio contribution |
| --- | --- |
| 01 to 04 | Responsibilities, controlled source index, evidence, applicability account |
| 05 to 07 | Decision reasoning, communication results, project basis, divided scope |
| 08 to 10 | Execution plan, forecasts, interface treatment, assurance and handover basis |
| 11 and 12 | Continuation decision, integrated result, review findings, individual defense |

Ask learners to identify the revision used by each later activity. When a source changes, follow the effect through dependent work.

Do not require a separate record for every classroom action. Keep what another learner, reviewer, or instructor needs to understand the work.

## Transfer the learning

After each course, ask learners to compare the practice with another industry or project type. Preserve the responsibility while adapting the method.

For example, an equipment configuration can become a software release configuration. A commissioning test can become a product validation scenario. Their governing conditions will differ.

Ask learners which parts of the Northbank method their workplace already provides. Identify a concrete gap before proposing another form or approval step.

Use participant experience as evidence to investigate. Check whether an earlier event supports the explanation given for it.

## Teach clear technical prose

Use short sentences and active verbs. Give one action in each instruction. Use one defined term for one meaning.

Prefer a concrete subject. Write who acts, what they do, and which condition matters.

Keep explanation with the related action. Short wording must preserve technical qualifications and uncertainty.

For example, write: "A04 identifies a 600 V connection. It does not establish spare capacity." Both sentences matter to the decision.

Use lists for separate actions. Use tables for repeated fields or comparisons. Use paragraphs to explain a relationship or reason.

The learner should understand the lesson without the presenter supplying missing connections. Read a sample lesson aloud to check that condition.