01The misreading: Scrum as anti-PMBOK

Every drift starts from an interpretation. The one behind most Scrum-in-name-only teams is simple and attractive: Scrum is what you do once you have freed yourself from traditional project management.

The caricature is familiar. The project manager is a controller who imposes deadlines. The Gantt chart is a cage. Change requests are bureaucracy. Scrum arrives as the liberation: no more project manager, no more plan, no more documents nobody reads. The team organises itself and delivers value every two weeks.

There is a grain of truth in it. Heavy plan-driven methods did produce expensive failures, especially in software, where requirements change faster than any baseline can be updated. The Agile Manifesto of 2001 was a reaction to real problems.

The misreading lies elsewhere. The Scrum Guide defines no project manager role. It defines three accountabilities, the Product Owner, the Scrum Master and the Developers, and gives them, together, everything a project needs: deciding what to build, ordering the work, maintaining quality, managing stakeholders, removing impediments and adapting the plan. Removing a role does not remove the work that role used to do.

When a team celebrates the departure of the project manager without asking who now owns the timeline, the risks, the integration of the parts and the expectations of stakeholders, that work does not disappear. It becomes unowned. Each item then decays at its own pace, and the decay is easy to mistake for the normal friction of agile delivery.

Reading Scrum through a PMBOK lens is therefore not a step backwards. It is a way to trace where each piece of project management work went, and to check whether anyone picked it up.