Writing
Scrum Is Not Agile
Read the manifesto. None of the ceremonies are in it.
The Agile Manifesto is four values and twelve principles. Nothing in it mentions sprints, story points, retrospectives, or daily standups. All of that came later, from Scrum.
Scrum first showed up in 1995. Seventeen people wrote the Agile Manifesto in 2001. The two overlap, but most teams that say “we are agile” really mean “we do Scrum.”
None of the Scrum rituals are bad in principle. Short iterations give work a boundary. The standup gives the team a daily check-in. They all work, for a while.
Words matter, and they set a tone. “Sprint” is the wrong word. A sprint is something you cannot sustain. Runners sprint the last hundred meters of a race, not the whole race. Short iterations are a good idea. Calling them sprints sets an expectation nobody can actually meet for long.
Then they become performance. The standup turns into a status report for the manager. The retro hits the same three complaints every two weeks, and nothing changes. The sprint ends, half the work slides to the next one, and it gets called “carryover” as if that makes it fine.
Planning drifts the most. The original pitch was “commit to a small batch and adjust next sprint.” After a few quarters it becomes three hours every other Monday, full of estimate negotiation and subtask breakdowns. The whole thing starts to look a lot like design up front, just repeated every two weeks. Knowing where you are going is useful. When the planning meeting becomes the deliverable, you have reinvented what Agile was a reaction to.
The fix is to audit the rituals. Look at each one and ask whether it is still producing a different output than a month ago. The retro that produces the same list of grievances every time is a ritual that has run its course. Kill it and schedule a conversation when something worth talking about actually comes up.
Read the Manifesto once a year. It puts four things above four other things. Individuals and interactions. Working software. Customer collaboration. Responding to change. A team that has not read those in a year is not agile. It is doing Scrum.