Carryover Analysis Dashboard
Monitor work rolled into future sprints to identify planning and capacity issues
Current Sprint Carryover
10%
5 of 49 stories
6-Sprint Average
19%
Improving trend
Target Carryover
<15%
Organization goal
Teams Over Target
1
DevOps at 25%
Carryover Trend
Percentage of work carried over to next sprint
Team Carryover
Current sprint carryover by team
Carryover Reasons
Why work items are being carried over
Improvement Actions
Recommended actions to reduce carryover
Better Estimation
Implement story point poker and historical velocity analysis to improve estimation accuracy.
Dependency Management
Identify and track external dependencies earlier in the planning process.
Scope Control
Implement stricter change control processes to prevent mid-sprint scope changes.
Technical Debt
Allocate 20% of sprint capacity to technical debt and infrastructure improvements.
Sprint-by-Sprint Analysis
Detailed breakdown of carryover items and reasons
| Sprint | Total Stories | Completed | Carried Over | Carryover % | Main Reason |
|---|---|---|---|---|---|
| Sprint 1 | 50 | 35 | 15 | 30% | Underestimated complexity |
| Sprint 2 | 48 | 36 | 12 | 25% | Underestimated complexity |
| Sprint 3 | 45 | 37 | 8 | 18% | External dependencies |
| Sprint 4 | 50 | 40 | 10 | 20% | External dependencies |
| Sprint 5 | 53 | 47 | 6 | 11% | Technical blockers |
| Sprint 6 | 49 | 44 | 5 | 10% | Technical blockers |