| name | scrum-event-sprint-review |
| description | Verify Definition of Done and acceptance criteria for Sprint increments. Use when completing sprints, running verification commands, or preparing for acceptance. |
AI Sprint Review facilitator verifying increments and determining acceptance.
Single Source of Truth: `scrum.ts` in project root. Use `scrum-dashboard` skill for maintenance.
Show the Increment above all else - Working software, not slides
NEVER present incomplete work - Creates false expectations
NEVER skip even with no completed Increment - Discuss the situation
Sprint Review is NOT just a demo - It is a collaborative working session
Transparency: Show only completed Increments (meeting DoD)
Inspection: Examine product, gather feedback
Adaptation: Adjust Product Backlog based on feedback
| Achievement (Present) | Activity (Do NOT Present) |
|----------------------|---------------------------|
| "Users can now reset passwords" | "We worked on password reset" |
| "API response time: 500ms → 100ms" | "We did performance work" |
| "Mobile checkout is complete" | "Mobile checkout is 80% done" |
Run Definition of Done checks from scrum.ts:
```bash
npm test
npm run lint
deno check scrum.ts
```
Each acceptance criterion has an executable command - run them all.
- All pass → Move PBI to `completed`
- Any fail → Return with details
Minor Fix Possible:
```yaml
# Keep sprint.status = "in_progress"
# Add fix subtask:
subtasks:
- test: "Fix [specific issue]"
implementation: "Resolve the failure"
type: behavioral
status: pending
# Re-run Review after fix
```
Sprint Goal Unachievable:
1. Report to Product Owner
2. Choose:
- Scope reduction: Split PBI, complete achievable part
- Sprint cancellation: Set `sprint.status = "cancelled"`, return PBI
3. Always run Retrospective to analyze root cause
Sprint Review STILL happens:
- Acknowledge openly no Increment met DoD
- Discuss why items weren't completed
- Continue with environmental updates
- Gather stakeholder input on priorities
- Assess Product Goal impact
<best_practices>
Guide discussion: How does this Sprint contribute to Product Goal?
Is Product Goal still achievable at current pace?
What is planned next toward the Goal?
</best_practices>
<related_skills>
PBI completion status, acceptance decision
Demo preparation, DoD verification
Facilitation, impediment identification
Outputs Review outcomes for reflection
</related_skills>
Sprint Review is a collaborative working session for inspecting the product and adapting based on feedback. Transparency is paramount - show only what is truly complete.
