02What PMBOK got right

It is fashionable in agile circles to treat PMBOK as an artefact of a slower age. That judgement confuses the body of knowledge with one lifecycle it was often used to support. The body of knowledge laid foundations that every serious delivery organisation still relies on.

A profession and a shared vocabulary

Before the Project Management Institute published its first PMBOK Guide in 1996, project management was mostly a craft passed on informally within industries. PMBOK made it teachable, comparable across sectors and certifiable. A construction programme director and a software delivery lead could finally use the same words for scope, baseline, risk response or earned value, and mean the same thing.

Completeness

PMBOK's ten knowledge areas map almost everything that can sink a project: integration, scope, schedule, cost, quality, resources, communications, risk, procurement and stakeholders. No agile framework attempts that coverage. Scrum, by design, addresses a fraction of it.

Disciplines that agile frameworks rarely spell out

• Risk management. Identifying risks, assessing probability and impact, planning responses and giving each risk an owner. Short iterations reduce risk, but they do not replace the explicit act of naming and tracking it.
• Integration management. One accountable person keeps the whole coherent: the plan, the changes, the dependencies and the trade-offs between them. This is the first accountability to disappear when a project manager leaves a team without a successor.
• Stakeholder and procurement management. Contracts, suppliers and stakeholders with competing interests are treated as first-class concerns. Scrum is largely silent on both.
• Integrated change control. The impact of a change is assessed before it is accepted, and decisions remain traceable. Regulated industries still depend on this, whatever the lifecycle.
• Lessons learned. Knowledge is captured for the organisation, beyond the team that produced it. A sprint retrospective improves a team; it does not, on its own, improve an organisation.
• Planning as a discipline. In the sixth edition of the Guide, 24 of the 49 processes belong to the Planning process group. Whatever one thinks of the processes themselves, the weight given to planning is a deliberate statement.

What fits poorly today

What fits poorly in many modern contexts is the predictive lifecycle applied to work with high uncertainty: defining scope upfront, baselining it, and treating every deviation as an error to correct. That lifecycle was never the whole of PMBOK, and PMI itself has moved well beyond it, as section 04 shows.

The knowledge areas have not aged in the same way. Risk, integration, stakeholders and procurement did not become less important when teams adopted Scrum. They became less visible. Teams that threw out PMBOK because of its lifecycle also threw out its checklist of everything a project must take care of.