Skip to main content

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

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more