Sprint Spillover

Sprint Spillover is the amount of work (User Stories, Tasks, Defects, Features) that was planned for a sprint but not completed by the sprint end date, causing it to move ("spill over") into the next sprint.

Simple Example

Sprint Plan:

Story A = 8 points ✅ Completed

Story B = 5 points ✅ Completed

Story C = 8 points ❌ Not completed

Sprint Commitment: 21 Story Points

Completed: 13 Story Points

Spillover: 8 Story Points

Spillover % Formula

\text{Spillover \%} = \frac{\text{Incomplete Work}}{\text{Committed Work}} \times 100

Example:

\frac{8}{21}\times100 = 38.1\%

Common Reasons for Sprint Spillover

1. Poor estimation

2. Scope changes during sprint

3. Unplanned production issues

4. Dependencies on other teams/vendors

5. Resource availability issues

6. Technical challenges discovered late

7. Excessive work in progress (WIP)

8. Incomplete requirements or acceptance criteria

Impact of High Spillover

Reduced predictability

Lower stakeholder confidence

Delayed releases

Velocity becomes unstable

Increased technical debt

SAFe Agile / Scrum Best Practices

Action Benefit

Break large stories into smaller stories Better predictability

Identify dependencies during PI Planning Fewer blockers

Maintain sprint buffer (10-15%) Handles unexpected work

Daily Scrum focus on blockers Faster issue resolution

Limit Work In Progress (WIP) Better flow

Improve estimation using Planning Poker More accurate commitments

Conduct Root Cause Analysis in Retrospective Continuous improvement

Sprint Spillover Metrics for Dashboard

An Agile Release Train Engineer (RTE) or Scrum Master typically tracks:

Metric Target

Spillover % < 10%

Sprint Predictability > 80%

Commitment Reliability > 85%

Velocity Variance < 15%

Blocked Stories < 5%

RTE / Scrum Master Questions During Retrospective

Why did the work spill over?

Was estimation accurate?

Were dependencies identified early?

Were there resource constraints?

What preventive action will be taken next sprint?

Rule of Thumb:

Occasional spillover is normal. If spillover exceeds 15-20% for 3 consecutive sprints, it indicates a planning, estimation, dependency, or capacity management issue that should be addressed at the team or ART level.

Comments

Control Chart in Lean Six Sigma

Control Chart in Lean Six Sigma Introduction In Lean Six Sigma , a control chart is a fundamental statistical tool used to monitor process performance over time and ensure that improvements are sustained . It belongs primarily to the Control phase of DMAIC , where the focus is on maintaining process stability and preventing regression after improvements have been implemented. A control chart helps distinguish between normal process variation and abnormal variation that requires investigation and corrective action. What Is a Control Chart? A control chart is a time-ordered graphical display of process data with statistically determined limits. It answers a critical question: Is the process stable and predictable, or is something unusual happening? A typical control chart consists of: Center Line (CL) – the process average or mean Upper Control Limit (UCL) – upper boundary of expected variation Lower Control Limit (LCL) – lower boundary of expected variation Plotted data points o...

Voice of the Customer (VoC) vs Voice of the Business (VoB)

Tthe differences and strategic importance of Voice of Business (VoB) and Voice of Customer (VoC) in Lean Six Sigma: Voice of Business vs Voice of Customer: Aligning Strategy with Value In the world of Lean Six Sigma , success hinges on understanding and balancing two critical perspectives: the Voice of the Customer (VoC) and the Voice of the Business (VoB) . While both are essential for driving sustainable growth and operational excellence, they represent distinct priorities that must be harmonized for optimal results. 🔊 Voice of the Customer (VoC) Definition : VoC refers to the needs, expectations, preferences, and feedback of the customer—whether internal or external. Focus Areas : Product/service quality Delivery timelines Customer experience Responsiveness and support Methods of Capturing VoC : Surveys and interviews Focus groups Customer complaints and feedback Net Promoter Score (NPS) Goal : To ensure that processes and outputs are aligned with what the customer truly ...

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics, Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...

High-Tech Yuga

Search This Blog