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
SprintTotal StoriesCompletedCarried OverCarryover %Main Reason
Sprint 150351530%Underestimated complexity
Sprint 248361225%Underestimated complexity
Sprint 34537818%External dependencies
Sprint 450401020%External dependencies
Sprint 55347611%Technical blockers
Sprint 64944510%Technical blockers