The Holy Grail in Scrum: The Done Increment
summary
Claim: treating a true definition of done as the team’s North Star changes behavior. The team learns that 4 of 5 PBIs passing unit checks still crashes the demo, performance and usability tests are missing, and a critical bug takes more than a week because knowledge is siloed, so they add code reviews, exploratory and performance tests, switch hero developers into mentors, reject a manager-imposed DevOps tool that slows them, adopt feature toggles and incremental rollouts which actually work.
AI-written summary · about
chapters (6)
- 0:00Start
- 9:29Sprint Review
- 19:17Emergent Architecture
- 25:01How Can We Deliver the Done Increment at the End of every Sprint
- 26:43Using Feature Branches
- 27:12Feature Toggles
related talks
32mDefinition of Done
01h 10mSoftware Engineering Completeness
04mBack to Basics
57mFocus. Deliver. Learn. Repeat
01h 29mSoftware Engineering Completeness - Knowing When You Are Done and Why It Matters
46mScrum and Deadlines: What Holds a Team Together as It Breaks
43mEver Since We Started Doing SCRUM Everything's Great. Not!
11mDelivering imperfect software