Updated
How can an executive tell if Scrum is working in their organization?
Look at the work, not the calendar. According to the Scrum Guide, a Scrum Team produces a usable Increment that meets the Definition of Done and inspects it with stakeholders at the Sprint Review. My take: if you can attend and see something real each Sprint, Scrum is working. If you can't, the events are just meetings.
What the Scrum Guide says
"In order to provide value, the Increment must be usable."
"Work cannot be considered part of an Increment unless it meets the Definition of Done."
"The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations." Read the Increment section of the Interactive Scrum Guide.
What I see in practice
Here’s the trap. Every event happens, the boards look busy, and nothing improves. I call it process theater, and I wrote about it in Scrum Events Running, Delivery Flat.
The tell is the Sprint Review. When leaders and stakeholders skip it, it “turns into a check-the-box exercise.”
So stop measuring activity. In Synthetic Speed I put it in one line: “start measuring how quickly working software reaches real users.” And ask the question from Output Outcomes: “What are the REAL outcomes you are producing with all that output?” (Yes, you.)
Common mistakes
- Counting Scrum activity (events held, boards updated) instead of looking at the Increment.
- Taking the team’s word for it instead of attending a Sprint Review.
- Rewarding busy-ness. In Output Outcomes I wrote that people “might get rewarded for staying busy and producing lots of stuff.”
- Letting Sprints run past a month. The Scrum Guide says they are “fixed length events of one month or less to create consistency.”
- Measuring how fast the team generates drafts or code, instead of how fast working software reaches users.
What to do this week
- Attend one Sprint Review. Ask to see the Increment working (not slides), and say out loud what you would change.
- Check whether the last Sprint ended with something usable that meets the Definition of Done. If it did not, ask the Scrum Team what got in the way.
- Ask the Product Owner one question: what did the last Increment change for a customer or user? If nobody can answer, start there.
FAQ
How often should an executive see something working?
Every Sprint. The Scrum Guide says Sprints are "fixed length events of one month or less," and that the sum of the Increments is presented at the Sprint Review. It also says an Increment may be delivered to stakeholders before the end of the Sprint.
Is the Sprint Review just a demo?
The Scrum Guide says: "The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation." My take: if you attend, come ready to react to the work and say what you would change.
Every Scrum event runs, but nothing is improving. What now?
In Scrum Events Running, Delivery Flat, I wrote that the cause is usually above the team: priorities, shared people, the Product Owner role, and whether leaders look at working results. Start with the five checks on that page.