Clarifies Scrum guidelines on unfinished work, explaining that items can span multiple Sprints if the Sprint Goal and Done Increment remain intact, avoiding common misconceptions.
For years I repeated a myth without questioning it: “You can’t have unfinished work in Scrum.” But the truth is, that’s not what the Scrum Guide says at all.
You must have a Done Increment by the end of the Sprint, but not every item must be finished. There’s no rule against work flowing across Sprints—so long as it doesn’t compromise the Sprint Goal or the Increment.
If you’re doing Continuous Delivery, you already have working software. You just need to make sure whatever you deliver meets the Definition of Done. That’s it.
Too many teams limit their flow by artificially cutting work to fit a two-week calendar. It’s time we stopped teaching dogma and started reading the guide.
Have you challenged this assumption in your team? You might be surprised what’s possible.
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.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
CR2
Xceptor - Process and Data Automation
NIT A/S
Schlumberger
Boxit Document Solutions
Capita Secure Information Solutions Ltd
Microsoft
Kongsberg Maritime
Qualco
Epic Games
Genus Breeding Ltd
Slicedbread
Milliman
Illumina
YearUp.org
Sage
Cognizant Microsoft Business Group (MBG)
Trayport
Washington Department of Transport
New Hampshire Supreme Court
Nottingham County Council
Ghana Police Service
Washington Department of Enterprise Services
Royal Air Force
Trayport
Deliotte
CR2
Workday
DFDS
Milliman