Sprint Retrospective Insights
Analyze sprint health and generate retrospective insights. Enter values for instant results with step-by-step formulas.
Formula
Health = f(Goals, Collaboration, Process, Blockers, Quality, Velocity)
Worked Examples
Example 1: High-Performing Sprint
Problem:Sprint assessment: 90% goal achievement, collaboration 9/10, process 8/10, blocker resolution 8/10, code quality 9/10, velocity up 5%. Score this sprint.
Solution:Sprint health factors:\nGoal achievement: 90% → 90 × 0.25 = 22.5\nCollaboration: 9/10 → 9 × 2.5 = 22.5\nProcess: 8/10 → 8 × 2 = 16\nBlockers: 8/10 → 8 × 2 = 16\nQuality: 9/10 → 9 × 2.5 = 22.5\nVelocity trend: +5% → 5 × 2 = +10 (capped at +10)\n\nTotal: 22.5 + 22.5 + 16 + 16 + 22.5 + 10 = 110 → capped at 100\n\nScore: 100/100 (Excellent)\n\nThis is exemplary sprint performance:\n- High goal achievement (90%)\n- Strong collaboration\n- Process working well\n- Blockers resolved quickly\n- High code quality\n- Increasing velocity\n\nRetro discussion:\nCelebrate: what enabled this performance?\nSustain: how do we maintain this?\nMinor improvements: the 10% of goals not met—why?\n\nAction items:\n- Document what worked for this sprint\n- Share practices with other teams\n- Small process tweaks t
Result:100/100 (Excellent) | High-performing team | Focus on sustaining current practices
Example 2: Struggling Sprint
Problem:Assessment: 50% goal achievement, collaboration 4/10, process 3/10, blockers 3/10, quality 5/10, velocity down 10%. What's wrong?
Solution:Sprint health factors:\nGoal: 50% → 50 × 0.25 = 12.5\nCollab: 4 → 4 × 2.5 = 10\nProcess: 3 → 3 × 2 = 6\nBlockers: 3 → 3 × 2 = 6\nQuality: 5 → 5 × 2.5 = 12.5\nVelocity: -10% → -10 × 2 = -20 (but capped at -10)\n\nTotal: 12.5 + 10 + 6 + 6 + 12.5 - 10 = 37/100 (Poor)\n\nMultiple critical issues:\n1. Only 50% goal achievement (should be 80%+)\n2. Low collaboration (4/10)\n3. Process breakdown (3/10)\n4. Blockers not resolved (3/10)\n5. Declining velocity\n\nThis is crisis territory!\n\nRetro should focus on:\nRoot causes: What changed? New team members? Technical debt? External dependencies?\n\nImmediate actions:\n- Reduce sprint commitment (aim for 60-70% to build success)\n- Daily standup discipline (identify blockers)\n- Pair programming to improve collaboration\n- Escalate persistent block
Result:37/100 (Poor - CRISIS) | Multiple critical issues | Reduce commitment, focus on process recovery
Example 3: Moderate Performance Sprint
Problem:Assessment: 75% goals, collaboration 6/10, process 7/10, blockers 6/10, quality 7/10, velocity stable (0%). Analyze.
Solution:Sprint health factors:\nGoal: 75% → 75 × 0.25 = 18.75\nCollab: 6 → 6 × 2.5 = 15\nProcess: 7 → 7 × 2 = 14\nBlockers: 6 → 6 × 2 = 12\nQuality: 7 → 7 × 2.5 = 17.5\nVelocity: 0% → 0\n\nTotal: 18.75 + 15 + 14 + 12 + 17.5 + 0 = 77.25 ≈ 77/100 (Good)\n\nThis is solid, not exceptional:\n- 75% goal achievement (acceptable, room to improve)\n- All factors in 6-7/10 range (good but not great)\n- Stable velocity (not declining, not growing)\n\nThis team is functional but has improvement potential.\n\nRetro focus:\nPick 1-2 areas to improve (don't try to fix everything):\n\nOption 1: Improve goal achievement to 85%\n- Better estimation\n- Reduce mid-sprint disruptions\n\nOption 2: Improve collaboration to 8/10\n- More pair programming\n- Better knowledge sharing\n\nAction items:\nFocus on estimation fo
Result:77/100 (Good) | Solid functional team | Pick 1-2 areas to improve for 85+ score
Frequently Asked Questions
What is a sprint retrospective?
Retrospective (retro) is Scrum ceremony at sprint end where team reflects on: what went well, what didn't, how to improve. Format varies: Start/Stop/Continue, 4Ls (Liked/Learned/Lacked/Longed for), Mad/Sad/Glad. Goal: continuous improvement through reflection. Typically 60-90 minutes every 2 weeks.
What makes a good retrospective?
Good retros: psychological safety (people speak honestly), action items (not just complaints), variety (different formats prevent staleness), facilitation (keeps discussion productive), follow-through (action items from last retro are reviewed). Bad retros: blame, complaining without solutions, same issues repeated without action.
How do you measure sprint health?
Key metrics: goal achievement (% of committed work completed), velocity trend (increasing/stable/declining), blocker resolution time, team sentiment, code quality (bugs, technical debt), process adherence. No single metric—combination reveals health. Tools: Jira reports, team surveys, code quality tools.
What is sprint velocity?
Velocity = story points completed per sprint. Used for: forecasting capacity, tracking team performance trends. Velocity varies by team (not comparable across teams). Healthy velocity is stable, not necessarily high. Declining velocity indicates issues: technical debt, team changes, or over-commitment.