The team met every week.
Sprint planning. Daily standup. Backlog refinement. Sprint review. Retrospective. All of it. On the calendar, every time, nobody missing.
And somehow nothing was getting better.
The backlog had stories that hadn't moved in four months. The sprint reviews were a slideshow. The retrospectives ended with the same action items as the one before. Everyone showed up to the ceremonies. Nobody was doing the ceremonies.
When the calendar becomes the product
I've watched this happen in a lot of Agile teams, and at scale on Agile Release Trains. The calendar becomes the product. Check the boxes, close the week, repeat.
PI Planning gets booked. The room fills up. Objectives get written. Two weeks later the team is doing exactly what it was doing before the event. Because the meeting happened. Job done.
This isn't laziness. Most of the people in those rooms work hard. It is something more subtle: the ceremony gets mistaken for the outcome it was designed to produce. Attendance becomes the evidence of agility. And attendance is easy to measure, so it is what gets measured.
Ceremonies are containers
The ceremonies are a container. The work is what you put inside them.
That distinction matters because an empty container looks exactly like a full one from the outside. Same calendar invite. Same duration. Same attendee list. You only find out what was in it by looking at what changed afterward.
Here is how I think about the difference for each event.
Refinement. Real refinement surfaces blockers, dependencies, and uncomfortable questions before they become sprint problems. Refinement that doesn't do that is just a reading group. If every story comes out of refinement looking the same as it went in, the meeting isn't refining anything.
Iteration or sprint review. A real review is a working session with stakeholders about what was built and whether it was the right thing. A slideshow of completed tickets is a status report with a nicer name. The tell: does anything in the backlog change because of what was said in the room?
Retrospective. A retro where nobody says anything uncomfortable is a standing meeting with sticky notes. If the same action item shows up three retros in a row, the retro isn't the problem. The problem is that nobody owns the follow-through, or the issue sits outside the team's control and nobody has said that out loud.
PI Planning. PI Planning with no one willing to push back on capacity is an elaborate scheduling exercise. The value of the event is the tension: business owners hearing what is realistic, teams hearing what matters, and both sides adjusting. If the draft plans and the final plans look identical, the negotiation didn't happen.
Why it drifts this way
A few patterns I've seen push teams toward empty ceremonies:
- Psychological safety is lower than anyone admits. People don't raise the real issue because the last person who did got labeled negative.
- The ceremony is owned, the outcome isn't. Someone is responsible for booking the retro. Nobody is responsible for the retro producing change.
- Leadership measures presence. When the question from above is "are the teams doing the events?" the answer will always be yes.
- Fatigue. After enough cycles of nothing changing, people stop trying. Showing up becomes the rational minimum.
What actually helps
You don't fix this by adding more structure. You fix it by changing what you look at.
- End every ceremony with one question: what is different now because we met? If the answer is nothing, say so.
- Track retro actions to closure, and review them at the start of the next retro before generating new ones.
- In reviews, ask stakeholders to make a decision, not just watch a demo.
- In PI Planning, treat pushback as a feature. The confidence vote is only meaningful if a low vote is a real option.
None of this is new. It's all in the framework already.
SAFe gave us the structure. We still have to show up for the substance.
Has this happened on your team? You do all the meetings and none of the work changes?
