a·gen·tic a·gil·i·ty

Work can flow across the Sprint boundary

Work Can Flow Across the Sprint Boundary

Explains how Scrum teams can strategically allow unfinished work to flow across Sprint boundaries, enhancing throughput, responsiveness, and continuous delivery without compromising goals.

Published on
4 minute read
Image
https://nkdagility.com/resources/a7UMLdZeVYq
Loading the Elevenlabs Text to Speech AudioNative Player...

There is nothing in the Scrum Guide that explicitly prevents work from flowing across the Sprint boundary. In fact, allowing flow across Sprints—without compromising the Sprint Goal—is a pragmatic strategy that enhances delivery, throughput, and responsiveness to customer feedback.

For practical guidance, explore the Kanban Guide for Scrum Teams , and consider attending a Professional Scrum with Kanban class.

TL;DR

The Definition of Done ensures transparency and quality and is non-negotiable. The Sprint Goal must articulate clear, measurable business outcomes or customer benefits. Effective flow requires reducing batch sizes, allowing unfinished work to cross Sprint boundaries strategically. Professional Scrum Teams adept at consistently delivering Done increments significantly enhance their throughput by embracing flow principles and rapid feedback cycles.

Work can flow across the Sprint boundary

A Sprint serves primarily as a container for planning, not always for delivery. Just as Continuous Delivery integrates seamlessly with Scrum, incorporating flow through Kanban complements and strengthens Scrum practices. All teams can benefit from this approach, provided they consistently achieve clear, outcome-focused Sprint Goals and maintain transparent, Done increments.

Managing Work Across Sprint Boundaries

Allowing work to flow across Sprint boundaries is an advanced yet beneficial technique. Initially, many teams struggle as they rarely achieve truly Working Software or fully meet their Sprint Goals by Sprint’s end. Transitioning to a mindset of flow and continuous validation is crucial for agile maturity.

My early scepticism around flowing work across Sprints shifted through deeper discussions with colleagues like Steve and Daniel. The critical insight was distinguishing the necessity of a Done Increment from the expectation that all Product Backlog Items (PBIs) must be completed by Sprint’s end.

Teams practicing Continuous Delivery (CD) inherently create working software incrementally and continuously. Such teams typically automate every aspect of their Definition of Done . Thus, by the Sprint Review , presenting completed increments is straightforward and predictable.

For a professional Scrum Team, adopting CD is foundational—not optional.

Strategic Sprint Goals and Continuous Value

Good Sprint Goals clearly articulate measurable outcomes or customer benefits rather than listing features or technical tasks. These goals act as strategic stepping stones toward your broader product or business roadmap, enhancing the clarity and alignment of your team’s efforts. Poorly constructed Sprint Goals, focused merely on delivering bundles of functionality or technology, often fail to communicate explicit and measurable benefits.

Aim to deliver multiple increments within a single Sprint, frequently gathering user feedback to continuously inspect and adapt progress toward your Sprint Goal. Regular increments and rapid feedback loops foster empirical control, allowing the team to pivot swiftly based on emerging insights or market changes.

Minimal Sunk Costs and Strategic Investment

Organisations invest in products or services one Sprint at a time. Each Sprint represents a potential decision point: assessing product-market fit and deciding whether continued investment is justified. The ultimate aim is to minimize sunk costs, banking created value incrementally and evaluating whether the product should continue development, transition to maintenance, or be marked end-of-life. Effective Sprint Goals and transparent increments support informed strategic decisions, ensuring resources align with business outcomes.

Shipping Software with Unfinished PBIs

Flow necessitates disciplined engineering practices ensuring early, frequent validation through automation. Key practices significantly enhancing CD include:

While complementary, these practices are fundamental to robust CD frameworks. Experimentation and iterative improvements tailor their application effectively to your context.

Aligning Flow with Scrum Principles

The Scrum Guide mandates a Done increment each Sprint for transparency . Without transparent increments, empirical control suffers, undermining Scrum itself.

Unfinished Backlog Items differ fundamentally from incomplete (“undone”) work.

Flowing work between Sprints is permissible within Scrum if aligned with clear Sprint Goals and delivering usable increments:

Regularly revisiting the Scrum Guide, emphasizing empirical control, and maintaining Scrum Values ensures successful flow integration within Scrum. Consistently verify increments against the Definition of Done and fulfil measurable Sprint Goals.

For further insights, review the Kanban Guide for Scrum Teams and consider participating in a Professional Scrum with Kanban course.

Engineering Practices Software Development Pragmatic Thinking Product Delivery Agile Frameworks … 10 more Value Delivery Operational Practices Professional Scrum Agile Planning Throughput Flow Efficiency Market Adaptability Team Performance Agile Product Management Organisational Agility
Subscribe

Related Blog

Related videos

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Brandes Investment Partners L.P. Logo

Brandes Investment Partners L.P.

Illumina Logo

Illumina

SuperControl Logo

SuperControl

Slaughter and May Logo

Slaughter and May

Slicedbread Logo

Slicedbread

ALS Life Sciences Logo

ALS Life Sciences

Alignment Healthcare Logo

Alignment Healthcare

Teleplan Logo

Teleplan

Lean SA Logo

Lean SA

CR2

Hubtel Ghana Logo

Hubtel Ghana

Xceptor - Process and Data Automation Logo

Xceptor - Process and Data Automation

Big Data for Humans Logo

Big Data for Humans

Emerson Process Management Logo

Emerson Process Management

Deliotte Logo

Deliotte

Bistech Logo

Bistech

Cognizant Microsoft Business Group (MBG) Logo

Cognizant Microsoft Business Group (MBG)

Capita Secure Information Solutions Ltd Logo

Capita Secure Information Solutions Ltd

New Hampshire Supreme Court Logo

New Hampshire Supreme Court

Ghana Police Service Logo

Ghana Police Service

Washington Department of Enterprise Services Logo

Washington Department of Enterprise Services

Royal Air Force Logo

Royal Air Force

Department of Work and Pensions (UK) Logo

Department of Work and Pensions (UK)

Nottingham County Council Logo

Nottingham County Council

Alignment Healthcare Logo

Alignment Healthcare

Milliman Logo

Milliman

Bistech Logo

Bistech

YearUp.org Logo

YearUp.org

Boxit Document Solutions Logo

Boxit Document Solutions

New Signature Logo

New Signature