01 · 1950s–2000s
Modern project disciplines
Large engineering, defence, technology and change programmes developed formal planning, control and governance practices.
ASSURANCE DNA · PROJECT MANAGEMENT
Guidance for governing and managing projects across predictive, iterative, adaptive and hybrid delivery approaches.
How will a promise become governed work, accepted outputs, realised outcomes and retained learning?
It is method-neutral guidance. It cannot make an unviable bid deliverable or replace sector-specific engineering, commercial and legal controls. Source-bounded interpretation: no certification, protected text reproduction or award prediction.
LIVING EXPERIMENT · BRIDGE
Bid commitments occupy one bank and delivery controls the other. Each span needs an owner, baseline, dependency and acceptance route before handover.
ORIGIN × EVOLUTION × CURRENT PRACTICE
Public and private project organisations, professional services, infrastructure, technology, transformation and consortium delivery teams.
01 · 1950s–2000s
Large engineering, defence, technology and change programmes developed formal planning, control and governance practices.
02 · 2012
ISO published a common high-level project-management reference across sectors and methods.
03 · 2020
The current guidance expanded governance, benefits, outcomes, change and multiple delivery approaches.
04 · 2025–2026
ISO records the 2020 edition in formal review while it remains the published reference.
Project-management guidance cannot rescue an unviable commercial promise. Bid design must preserve realistic resources, dependencies, authority and acceptance.
OFFICIAL SOURCE FRESHNESS MONITOR
Monthly official-source reachability and change review.
The check records source reachability and a content fingerprint. It does not silently change the page or claim that an edition changed.
PUBLICLY DESCRIBABLE ANATOMY
These are navigational interpretations, not substitute clauses. Use the official publication for normative wording.
Place the proposed project inside organisational strategy, constraints and delivery environment.
Define sponsor, governance, direction, assurance and escalation across buyer and suppliers.
Integrate plans so scope, schedule, cost, resources, risk and change remain mutually coherent.
Control scope and change around outcomes, products, acceptance and benefits.
Make resource, schedule, cost and risk assumptions explicit and testable.
Govern stakeholders, communication, procurement and supplier work as delivery systems.
Transfer outputs, close obligations, measure outcomes and retain lessons.
BEFORE × INTERVENTION × AFTER
A fictional project deploys one service to 36 organisations through data migration, training and local change.
A worked project baseline, not evidence that rollout has occurred.
The bid has 420 activities but no product acceptance map, benefits owner or resource test across overlapping waves.
The team rebuilds around products, outcomes, governance, acceptance, integrated resources and controlled local variations.
The plan exposes ten stage decisions, 47 accepted products, constrained resources and a transition path from bid promise to operational ownership.
PROPORTIONATE IMPLEMENTATION
It is method-neutral guidance. It cannot make an unviable bid deliverable or replace sector-specific engineering, commercial and legal controls.
Decision note, milestone plan, acceptance record
Integrated plan, estimate basis, change route
Portfolio decisions, benefits data, closure learning
SOURCE TRAIL · REVIEWED 21 AUG 2026
Publication status can change. Exact conformity questions belong with the current licensed publication and competent assurance.
Published guidance, delivery approaches and review status
Open primary source ↗ISORelated organisational context
Open primary source ↗UK GovernmentPublic major-project context
Open primary source ↗