Chapter 4 recap

Managing the work

The key takeaways from this chapter’s 6 lessons.

Projects in one page

Scope (what), time (when), cost (how much) and quality (how good) pull against each other; changing one moves the others.
The project manager (or project director) is accountable for the whole; discipline leads for their parts.
Information delivery is one of the project's work streams, with milestones that must fit the programme.
A good coordinator speaks the PM's language: impact on scope, time, cost, quality and risk.

A risk is an uncertain event that would affect the project's objectives; an issue is a risk that has happened.
Each risk is described, scored (likelihood × impact), owned, and given a response: avoid, reduce, transfer or accept.
Information risks belong on the register: late or missing deliverables, poor data, interoperability, skills, security.
ISO 19650 asks the delivery team to assess information delivery risks in its tender response and keep them up to date.

Quality assurance (QA) is the planned system that prevents defects; quality control (QC) is the checking that finds them.
Many firms run a quality management system (often to ISO 9001) with procedures, checks, records and audits.
Model checks, IDS checks and naming validation are QC for information; templates, training and procedures are QA.
Non-conformances are recorded, fixed, and analysed so the cause is removed.

A change request describes the change, its reason and who asked for it.
It's assessed for impact on scope, time, cost, quality and risk (design, programme, information).
The person with authority approves or rejects it, and the decision is recorded.
Model comparison between revisions shows what actually changed, which keeps change records honest.

Stakeholders are everyone affected by or able to affect the project: client, users, designers, contractors, authorities, neighbours.
Map them by interest and influence, and decide what each needs to know, when and how.
Coordination reports should be short and tailored: status and risk for the PM, actions for discipline leads, decisions for the client.
Use the same source for every view so the numbers never disagree.

Capture lessons at each stage, not just at the end, while people still remember.
Write each as what happened, why, and what to change; give it an owner.
Turn lessons into changes: templates, BEP, information standard, requirements, training.
Close-out archives the project record (final models, documents, decisions) so it can be found later.