Sprint planning through a coaching lens — the session and the signals captured.
An agile coach observing sprint planning sees different things than the team does. BoardSnap captures what you write on your coaching board — the process observations, anti-patterns, and interventions — alongside the planning output.
Why agile coaches love this workflow
Agile coaches who observe sprint planning sessions are watching for specific behaviors: does the team pull from the backlog or get pushed by the PM, are estimates happening through discussion or dictation, does the team set a sprint goal before pulling stories or after. These observations are the coaching value — but they disappear if they're not captured.
BoardSnap gives coaches a second board to maintain during the planning session: your observation board, separate from the team's planning board. Write what you see. Snap it. The coaching report is built from real observation data, not post-hoc recollection.
The exact flow
- Set up a coach's observation board separately from the team's board
Your observation board has different sections than the team's board: Anti-patterns Observed, Positive Behaviors, Coaching Interventions Made, Follow-up Topics. Don't mix them.
- Write observations in real time during the session
As you observe the planning session, write specific behavioral observations on your board. 'PM pushed story to top of sprint without team vote. Nobody pushed back.'
- Note coaching interventions you made
When you intervened — redirected a conversation, asked a coaching question, highlighted an anti-pattern — write what you did and what happened. This is your coaching log.
- Snap both boards
Snap the team's planning board and your observation board separately. Two captures, one project.
- Use the summary to structure your coaching report
The observation board summary is your coaching report. The planning board summary shows what the team produced — the two together tell the full story of the session.
What you'll get out of it
- Coaching observations captured in real time — not reconstructed from memory
- Specific behavioral examples documented for coaching feedback conversations
- Coaching interventions logged with outcomes — builds your coaching portfolio
- Anti-patterns documented with frequency for trend tracking across sprints
- Coaching report structured from real observation data, not impressions
Frequently asked
Is it appropriate to keep a separate coaching observation board visible to the team?
This is a coaching philosophy question. Transparent coaching (observations visible to the team) builds team self-awareness but may inhibit some behaviors. Confidential observation boards (visible only to the coach/sponsor) produce more candid data. Choose based on your coaching contract.
How does BoardSnap help me as a coach working with multiple teams?
Create a project per team in BoardSnap. Each team's sprint planning and retro boards are in their own project. Use the AI chat to compare patterns across teams — 'what planning anti-patterns appeared in more than one team this quarter.'
Can I use BoardSnap to build a coaching case study from a team's progress over time?
Yes. A team's BoardSnap project becomes a longitudinal record of their agile maturity journey — from early sprint boards to mature ones. The AI chat can summarize the arc of improvement for a coaching case study.
Agile Coaches: try this on your next sprint planning.
Three taps. Action items in your hand before the room clears.