
Sprint Retrospective Analyzer
Analyze sprint data to surface root causes and generate data-backed retrospective briefs
What You Can Do
You can rapidly analyze sprint data to uncover actual performance drivers—distinguishing between real blockers and perceived issues. The skill generates structured retrospective briefs with quantified impact assessments, helping you run data-driven retrospectives that reduce circular discussions and produce measurable improvement outcomes. You'll surface hidden patterns in 15 minutes that typically require hours of manual analysis, enabling objective stakeholder communication about sprint misses.
Features
Separates actual blockers from assumptions by analyzing sprint velocity data, dependency issues, and capacity constraints
Detects patterns across multiple sprints to diagnose whether declines stem from scope creep, technical debt, skill gaps, or external factors
Assigns measurable impact to recurring issues so teams can prioritize which problems actually matter
Produces structured discussion frameworks with pre-identified topics and time allocations
Generates specific, testable improvement suggestions with success metrics and tracking mechanisms
Translates sprint data into objective narratives explaining performance variance to non-technical stakeholders
Provides realistic velocity baselines for sprint planning by accounting for identified constraints
Tracks improvement outcomes across multiple sprints to validate which process changes actually work
Example Output
Input: Sprint 23 velocity data, list of blockers, scope changes, and team capacity
Output Example 1 — Root Cause Brief:
- Velocity dropped 18% from Sprint 22
- Primary driver: 3 critical production incidents consuming 32 hours (28% of capacity)
- Secondary driver: 2 external API dependencies added 6-day delay to 2 stories
- Process gap: No incident response protocol led to reactive work without backlog update
- Recommendation: Establish incident reserve capacity (15%) starting Sprint 24
Output Example 2 — Blocker Impact Analysis:
| Blocker | Frequency | Stories Affected | Hours Lost | Impact % |
|---|---|---|---|---|
| Infrastructure access delays | 3 sprints | 7 | 18 | 12% |
| Design review bottleneck | 4 sprints | 11 | 24 | 16% |
| Missing acceptance criteria | 5 sprints | 14 | 12 | 8% |
Output Example 3 — Retrospective Agenda:
- Celebrate: 2 features shipped with zero bugs (10 min)
- Incident handling: Formalize response protocol (15 min)
- Dependency management: Pre-sprint coordination with API team (15 min)
- Process test: Implement acceptance criteria checklist (10 min)
What's Included
- SKILL.md instruction file with skill configuration and usage guidelines:
- Sprint Data Analysis Template: Structured worksheet for gathering velocity, blocker, and capacity data
- Retrospective Brief Generator Framework: Pre-built format for surfacing root causes and improvement proposals
- Blocker Impact Quantification Checklist: Methodology for assigning measurable impact to recurring issues
- Improvement Tracking Worksheet: Cross-sprint comparison matrix to validate whether process changes produce results
Who It's For
- Scrum Masters — Run retrospectives with data instead of opinion, reducing circular debates
- Engineering managers — Objectively explain velocity variance to stakeholders and executive leadership
- Tech leads — Diagnose technical debt impact and justify refactoring time allocation
- Product owners — Understand realistic capacity for release planning and commitment forecasting
- Agile coaches — Help teams identify and fix systemic process problems with evidence-based interventions
Best For
- Sprint retrospective planning when velocity has declined or sprint goals were missed
- Root cause analysis when the same blockers appear in multiple consecutive sprints
- Stakeholder communication when explaining sprint performance variance to leadership
- Capacity forecasting for upcoming sprint planning based on realistic constraint analysis
- Process improvement validation to confirm which team changes actually drive better outcomes
- Onboarding conversations with new team members to highlight chronic pain points
- Release timeline estimation by establishing reliable velocity baselines







