Skip to main content

metrics.sprint-review

Type: commands | Track: Enterprise

Sprint review ceremony. Showcases working product with demo items, completion metrics, DORA actuals, and feedback capture. Distinct from sprint retro (what shipped vs how the team performed). Delegates to observability-engineer. Exempt from PO+CA coordination.

Quick Start​

# Run sprint review
/metrics:sprint-review

# Override sprint
/metrics:sprint-review --sprint CloudOps-S1

Output Sections​

SectionContent
Demo itemsCompleted stories with evidence links (CSV + JSON)
Completion metricsStories completed, BV delivered, sprint velocity
DORA actualsDF, LT, CFR, MTTR — actual vs target
Stakeholder feedbackCapture format for HITL to fill in
Next sprint previewTop 3 backlog items ranked by WSJF

Benefits​

  1. Reads from stories.csv and dora.csv — no manual aggregation
  2. Demo items link to evidence files in tmp/ — stakeholders can inspect actual deliverables
  3. Clearly distinguishes sprint review (WHAT shipped) from retro (HOW team performed)
  4. Exempt from PO+CA coordination — ceremony reads existing data only

When to Use​

AttributeDetail
PersonaHITL / Engineering Manager
TriggerSprint end (bi-weekly) — the last day of the sprint, before the retrospective, when the team needs to demonstrate completed work to stakeholders
Business ValueDemo items with completion metrics and DORA actuals — gives stakeholders an objective view of what was delivered, with evidence links, rather than relying on verbal summary
FrequencyBi-weekly

Example: As an Engineering Manager (HITL), I need the sprint review output before the stakeholder meeting because I need to present completed stories with evidence and DORA metrics to the CTO. I run /metrics:sprint-review which reads stories.csv and dora.csv to produce demo items with evidence links, completion velocity, DORA actuals vs targets, and a next-sprint preview ranked by business value.

Coordination-exempt command. Reads existing data only — no architecture decisions.