sprint-review

Sprint Review

Scrum Guide grounding

The Sprint Review is a working session, not a presentation. The Scrum Team and stakeholders inspect what was accomplished and how the environment has changed. The output is an adapted Product Backlog that reflects the current best opportunity going forward.

Key rules:

• Time-boxed to four hours for a one-month Sprint (proportionally shorter for shorter Sprints).
• The increment is inspected — not just described. Stakeholders ask questions and give input.
• The Product Backlog may be adjusted based on what was learned.
• Velocity and burn-down metrics are inputs, not the focus.

---

Tool detection

Identify which project management tool is available:

1. Check for active mcp__azure-devops__* tools → set $PM_TOOL to ado
2. Otherwise check for active mcp__jira__* tools → set $PM_TOOL to jira
3. If both → ask: "I see both ADO and Jira connected — which should I use?"
4. If neither → set $PM_TOOL to manual

---

Step 1 — Fetch Sprint data

Retrieve the completed Sprint's items:

• ADO: use wit_get_work_items_for_iteration for the sprint just completed; filter for Done/Closed state
• Jira: use the sprint report or issue listing tool for the closed sprint
• Manual: ask the team to share what was completed, what wasn't, and the Sprint Goal

Identify:

• $SPRINT_GOAL — the goal set at Sprint Planning
• $DONE_ITEMS — work items that meet the Definition of Done
• $NOT_DONE_ITEMS — work items that were planned but not completed
• $PRODUCT_GOAL — the longer-horizon objective the team is working toward (if known)

---

Step 2 — Assess the Sprint Goal

State clearly whether the Sprint Goal was met, partially met, or not met — and why.

• Met: The increment delivered the intended outcome.
• Partially met: Some committed scope was not done, but the core outcome was achieved.
• Not met: The team did not deliver the outcome. Name the cause without assigning blame.

A missing Sprint Goal is a team health signal worth naming: "The team didn't have a Sprint Goal this Sprint — that makes it hard to assess whether the Sprint was successful. Worth raising in the Retrospective."