Most refinement sessions are structured around a false assumption: that the goal of the meeting is to walk through the stories on the board.
It isn’t. The goal of refinement is to make sure every engineer understands the problem well enough to solve it independently — without needing to ask for approval on their approach, without needing to come back to a meeting for clarification, without needing the scrum master to tell them what the story means.
That is a fundamentally different goal than walking through stories. And running toward it requires a fundamentally different structure than most teams use.
This post is the playbook I use. Three sessions per sprint, specific roles, specific moves for the hardest moments, and the one thing that matters more than any of it.
This is the opening of a paid subscriber post at danielholt.substack.com. The full playbook — three-session structure, the silence problem, what the scrum master's job actually is, and the one thing that matters more than all of it — is available to paid subscribers.
Use code JULY20 for 20% off a paid subscription through July 31.
danielholt.substack.com
Top comments (0)