Updated
What is process theater in Scrum?
Process theater is what I call it when a team has the Scrum roles, events and Sprints, but the decisions that should follow them never happen. The meetings take place and nothing changes. The Scrum Guide does not use the term. It does warn that failing to operate the events as prescribed "results in lost opportunities to inspect and adapt."
What the Scrum Guide says
"Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts."
"Failure to operate any events as prescribed results in lost opportunities to inspect and adapt."
"The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation." Read the Scrum Events section of the Interactive Scrum Guide.
Go deeper
If your events all run and delivery has not improved, read Scrum Events Running, Delivery Flat: What Leaders Do. It covers the five things leaders should check first. This page is only the definition.
What I see in practice
As I wrote in that article, it’s when “the roles, the rituals and the Sprints are present, and the decision-making that is supposed to follow them is missing.”
It creeps in quietly. In Kill Zombies I described teams that “start operating on auto-pilot, blindly following processes without remembering why they do them.” That’s how a Daily Scrum can “devolve from a collaborative planning session into a mindless status report.”
The habits are easy to spot. In Lipstick On A Pig I listed a few: “Renaming your daily status meeting a ‘Daily Scrum’ and calling it good,” and a Sprint Review that shows “all the work / effort your team has accomplished” without “actual valuable working software.”
Common mistakes
- Renaming old meetings with Scrum words and changing nothing else.
- Replacing conversations about Product Backlog items with tickets that have no context.
- Using the Sprint Review to show effort instead of working product.
- Dropping the Retrospective because the list of improvements keeps growing.
What to do this week
- Pick the event that feels emptiest. Ask the team what decision it led to last Sprint.
- Find the meeting with “no heartbeat” and change it or end it.
- If the decisions you need belong to someone above the team, take the five checks in the article above to that leader.
FAQ
How can I tell if my team is doing process theater?
Ask what each event produced. The Scrum Guide says the Daily Scrum "produces an actionable plan for the next day of work." My take: if an event ends with no plan, no decision and no change, it was theater. See Is the Daily Scrum a status meeting?
Is process theater the team's fault?
In the article above I wrote that "the cause is usually not the teams." It can sit above them, with priorities, shared people and leaders who never see the work. Start with How can an executive tell if Scrum is working in their organization? and What should executives stop doing to help their Scrum teams?
Should we drop the event that feels pointless?
My take: fix it, don't drop it. The Scrum Guide says failing to operate an event as prescribed means lost chances to inspect and adapt. In [Reflect Often](https://www.linkedin.com/pulse/reflect-often-michael-vizdos) I wrote that the Retrospective is "usually the first event that gets dropped" and that improving is the only way to get more done by doing less.