Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

The Sprint Increment Is Dead

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

The Sprint Increment Got Us Here

If you’re a veteran of the software industry, you probably remember those days when we released to production/GA every couple of months. Heck, many of the companies I meet these days still work that way.

If you’re also an experienced Scrum practitioner, you probably associate the time you started to use Scrum with the time you started to release more frequently. The Sprint Increment that had to be potentially releasable caused you a lot of pain as you were trying to improve your processes and capabilities, implement Continuous Integration, and finally gain the ability to actually have a releasable Increment each Sprint. You were pretty proud.

Transcending Scrum and the Sprint Increment?

But these days, as people talk more and more about DevOps and Continuous Deployment, you might be thinking that since Scrum is focused on Sprints, You need to transcend Scrum in order to keep up with the industry and the need to release more often. You start to look at approaches such as Flow and Kanban that are continuous in nature.

Before you recycle your copies of the Scrum Guide – can I ask you a couple of questions though?

The Need For Continuous Deployment

The first question is why do you need Continuous Deployment? Does your Product Owner really see a business need to deploy more often than every Sprint (which is always up to 30 days and more frequently these days more along the lines of 14 days)? If you are like most of the Scrum practitioners I’m working with, the answer to that is “Not Really”. Even cloud/SaaS/internet-based companies typically don’t see a need for releasing new features to market more frequently than every 15 days.

So, why the need for Continuous Deployment?

Scrum Theory helps us out here. The reason is empiricism. In contexts of growing business and technical uncertainty, those with the fastest feedback loop win. And the feedback loop should provide REAL transparency to the usefulness of the products we build so that our inspection and adaptation is based on what users really think of the product we’re building. When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. We also don’t mean just “It is working and we demonstrated it to internal and even external stakeholders and got their feedback”. These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desiredץ

What we REALLY mean when we say Working Software

They aren’t as good us “It is working, we actually turned it on for some users and they’ve been using it as part of their real flow of work, and we can inspect how useful it really is for them.” The last one is what real transparency is about. And classic teams only get to that level of “working” pretty infrequently. Their REAL feedback loop takes weeks if not months to close. Their level of empiricism leaves much to be desired.

The real reason for moving toward Continuous Deployment is actually to address this issue. To enable much more frequent transparency of how our product is REALLY doing, and enabling inspection and adaptation on a daily and maybe even hourly basis by those developing the software/product.

Continuous Deployment with Scrum and Kanban

In Scrum terms, Continuous Deployment happens during the Sprint, where we can have as many mini-increments as we want deployed throughout the Sprint, with the purpose of helping the Scrum Team optimize the value it delivers with its Sprint Increment. Yes, they could also release some of those mini-increments for the purpose of actually delivering customer value, but most of the time the purpose would be to inspect and adapt, in service of empiricism.

Moving to multiple mini-increments inside the Sprint doesn’t change Scrum in any way. This is actually just a more professional instance of Scrum that more and more Scrum practitioners should strive for. The Sprint-level events are still as valuable as ever for inspecting and adapting the Product and the Process. The roles are still as valuable as ever. If anything, it might be even more important to have a Product Owner that focuses the Development Team on the mission/goal, being open about the fact that there are some hypothesis-level assumptions that need to be validated by building some product and running some experiments, and respecting the developers and trusting them to figure out how to achieve that mission/goal by running fast feedback loops that include actual experimentation, inspection, and adaptation. In order to scale, the Product Owner needs to have the courage to let the Development Team run some of those experiments on their own. They can all review these experiments and the resulting Sprint Increment as part of the Sprint Review. The review will not be just a demonstration of working software but also inspection of analytics from real usage.

Where Kanban/flow comes handy is not in replacing Scrum but in managing the flow of these intra-Sprint feedback loops more explicitly and helping the Scrum Team identify bottlenecks, constraints, and impediments on their way towards this type of flow.

So, yes, the Sprint Increment is dead. Long live the REAL Sprint Increment as well as all the mini Increments during the Sprint.

To learn more about how professional Scrum teams think about flow and Continuous Deployment, join an upcoming Scrum with Kanban workshop.

Subscribe for Email Updates:

Categories:

Tags:

Agile Games
Scrum With Kanban
PI Objectives
Planning
AgileSparks
Development Value Streams
Large Scale Scrum
Release Train Engineer
TDD
Jira
Agile Games and Exercises
Scrum.org
Webinar
Business Agility
Entrepreneurial Operating System®
RTE
Risk Management on Agile Projects
Agile Contracts Best Practices
Story Slicing
Legacy Enterprise
SPC
ALM Tools
Lean Software Development
Risk-aware Product Development
Agile Project
Agile and DevOps Journey
Agile Exercises
Retrospectives
A Kanban System for Software Engineering
LPM
Test Driven Development
Professional Scrum Master
chatgpt
An Appreciative Retrospective
RTE Role
Legacy Code
Process Improvement
Scrum Master Role
SAFe DevOps
LeSS
DevOps
Agile Basics
Agile Development
Tips
Kanban Kickstart Example
What Is Kanban
NIT
ATDD
Agile Delivery
Product Management
Lean Risk Management
Agility
Agile Product Development
Atlassian
Advanced Roadmaps
PI Planning
POPM
The Kanban Method
Code
Agile for Embedded Systems
Lean Agile Basics
Kanban Game
Kaizen Workshop
Managing Projects
Lean and Agile Techniques
BDD
Agile Israel
Self-organization
Certification
agileisrael
Kanban
Jira Plans
Sprint Iteration
Principles of Lean-Agile Leadership
GanttBan
Scrum and XP
Agile Israel Events
Change Management
lean agile change management
Elastic Leadership
Lean Budgeting
Continuous Integration
speed @ scale
Nexus vs SAFe
Jira Cloud
Professional Scrum Product Owner
Daily Scrum
Agile Testing Practices
System Integration Environments
Implementation of Lean and Agile
EOS®
Perfection Game
Accelerate Value Delivery At Scale
Lean Agile Leadership
Kanban Basics
Quality Assurance
QA
Portfolio for Jira
Professional Scrum with Kanban
Agile in the Enterprise
Frameworks
Lean Agile Management
transformation
Scrum Guide
Manage Budget Creation
Continuous Planning
LAB
Hybrid Work
Agile Assembly Architecture
Spotify
Introduction to Test Driven Development
Engineering Practices
Agile Techniques
Agile Program
Games and Exercises
Nexus Integration Team
Implementing SAFe
Iterative Incremental Development
Releases Using Lean
Applying Agile Methodology
Scrum Values
Presentation
System Archetypes
Rovo
Artificial Intelligence
Agile Release Management
Kanban 101
Nexus
Acceptance Test-Driven Development
Software Development Estimation
Rapid RTC
Agile Mindset
Program Increment
Sprint Retrospectives
Scrum Primer
Agile Project Management
Team Flow
Lean-Agile Software Development
Coaching Agile Teams
Enterprise DevOps
Covid19
Continuous Delivery
Lean and Agile Principles and Practices
Lean Agile Organization
Pomodoro Technique
Agile India
Systems Thinking
ROI
The Agile Coach
Amdocs
Operational Value Stream
WIP
Tools
Product Ownership
RSA
Managing Risk on Agile Projects
Agile Outsourcing
speed at scale
Value Streams
Scrum Master
Agile Release Planning
AI Artificial Intelligence
Software Development
ATDD vs. BDD
Limiting Work in Progress
Risk Management in Kanban
Certified SAFe
ScrumMaster Tales
ARTs
Agile
Agile Marketing
Jira admin
Nexus and SAFe
SAFe Release Planning
Built-In Quality
Achieve Business Agility
Video
Reading List
AI
User stories
Lean Agile
Agile Community
Scaled Agile Framework
IT Operations
Nexus and Kanban
Scrum
Kaizen
Effective Agile Retrospectives
ART Success
Lean Startup
Keith Sawyer
predictability
System Team
SAFe
Agile Product Ownership
Confluence
Atlaassian
Continuous Improvement
Introduction to ATDD
SA
Sprint Planning
Lean-Agile Budgeting
Continuous Deployment
Slides
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart