Pre-mortems for agile teams — failure modes captured before the sprint clock starts.
Agile coaches who run pre-mortems before sprints or projects produce more honest risk conversations than those who run traditional risk registers. BoardSnap captures the pre-mortem output in a structured format ready for action.
Why agile coaches love this workflow
The pre-mortem technique — imagining the sprint has already failed and asking why — is one of the most effective risk surfacing tools an agile coach has. Teams are more honest about failure modes in this framing than in a traditional 'what are the risks?' conversation. The physical whiteboard amplifies this effect: writing 'we failed because the API wasn't ready' on a board feels more concrete than saying it.
BoardSnap captures the pre-mortem board while the honesty is still fresh. Snap the failure mode list with probability markers and mitigation owners and you have a sprint risk register that the team actually owns — not a compliance document the coach filled in.
The exact flow
- Set the pre-mortem premise clearly
Write on the board: 'The sprint ended. We failed to deliver the sprint goal. Why?' Make the failure specific and real — not abstract. The specificity is what unlocks honest responses.
- Silent brainstorm of failure modes
Each team member writes failure modes on sticky notes independently. Silent writing before discussion is critical — it prevents anchoring on the first idea someone says.
- Cluster and name the failure themes
Cluster related sticky notes. Name the failure theme for each cluster. Team velocity issues, dependency failures, scope creep, technical unknowns — name the pattern.
- Vote on highest-probability failure modes
Each person gets three dot votes. The top three to five failure modes are the real risks. Write them in a 'Top Risks' column with their vote counts.
- Assign mitigation owners for each top risk
For each top failure mode, write a specific mitigation action and an owner. Snap the board — this is the sprint risk register.
What you'll get out of it
- Team-generated failure modes more honest than coach-assigned risks
- Cluster themes reveal systemic team vulnerabilities
- Priority failure modes identified by team vote — not coach judgment alone
- Mitigation owners assigned by the team — higher accountability
- Sprint risk register built from real team intelligence in 45 minutes
Frequently asked
When is the best time to run a sprint pre-mortem?
At the end of sprint planning, before the sprint starts. The team has the sprint goal and the plan in mind — the pre-mortem asks them to imagine that plan failing, which is easiest to do while the plan is fresh.
How does a sprint pre-mortem differ from a project pre-mortem?
Sprint pre-mortems are faster (30-45 minutes) and focused on near-term execution risks. Project pre-mortems cover a longer horizon and include strategic and external risks. Both work well on whiteboards with BoardSnap capture.
Should I run a pre-mortem every sprint?
Not necessarily. Run one at the start of a project, after any major process change, or when the team is facing an unusually risky sprint. Over-running them reduces the honest engagement that makes them valuable.
Agile Coaches: try this on your next pre-mortem.
Three taps. Action items in your hand before the room clears.