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

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)

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...

4 T's - Technology, Time, Teamwork, Transparency

1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished. 3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...

High-Tech Yuga

Search This Blog