Scrum Won a War and Then Became an Occupation

A certified Scrum Master lays out a prosecution against how Scrum evolved: from a concise, thirteen-page framework that prescribes sprints, a handful of ceremonies, and three roles, into a global, packaged bureaucracy that occupies teams’ time without governing the technical work that actually makes software. The Agile Manifesto left an operational vacuum that Scrum, perfectly packageable, filled with hireable roles, certifiable rituals, and visible artifacts - yet the guide says nothing about code, testing, deployment or architecture. That gap produced a universal vocabulary where everyone “knows Scrum” but no shared understanding exists; different teams use the same words to mean incompatible practices, and certification rewards fluency in liturgy rather than competence in producing working systems.

The concrete cost is quantified: a seven-person team on two-week sprints typically spends eight to twelve hours per person per sprint in ceremonies - roughly three to four person-weeks per month - time taken before a line of code is written. Much of the ceremonies’ output can be obtained cheaper by continuous shipping, an up-to-date board, or ambient team communication. The most damaging artifacts are estimates and timeboxes: story-pointing reduces unfamiliar, complex tasks to a number that reflects the room’s mood, not the work, and those numbers harden into commitments and deadlines. The result is ritualized theater that consumes attention and masks real coordination failures.