Sprint monitoring for teams that want fewer surprises.

Use sprint monitors to keep blockers, scope growth, capacity pressure, and unresolved retro actions visible before they become end-of-sprint surprises.

When to create a monitor

Create a sprint monitor after capacity planning or sprint planning. Link it to a capacity plan when possible so the monitor can compare planned work against actual progress and risk signals.

What to snapshot

Take snapshots at predictable moments: after planning, mid-sprint, before review, and before the retro. Each snapshot captures planned work, completed work, blocked items, scope changes, estimates, owner allocation, and unresolved action items.

How to use risk cards

Risk cards are facilitation inputs, not blame. Use them to ask concrete questions: What changed? Which blocker needs escalation? Which action item is stale? Which owner is overloaded?

Open Sprint Monitoring