Definition of Ready & Done - Achieving Predictability
summary
Defines concrete Definition of Ready checks (no unanswered questions, dependencies identified, acceptance criteria reviewed) and a Definition of Done checklist (unit/integration tests, peer-reviewed PR, UAT, release notes, deployed) and pushes left: quick pre-implementation design reviews, grooming ahead of sprint, and split stories to under one week to make sizing accurate. Recommends measuring sprint planning time (target 30–60 minutes), running prod tests, and deploy every story to production as part of the sprint to reduce risk and stabilize velocity.
AI-written summary · about
chapters (9)
- 0:00Introduction and overview
- 3:11What is predictability
- 6:45Why predictability matters
- 12:08Definition of Ready explained
- 22:26Common Definition of Ready problems
- 31:28Remote team challenges
- 38:57Definition of Done explained
- 47:49Deploying to production
- 51:03Summary and Q&A
related talks
01h 10mSoftware Engineering Completeness
01h 17mSoftware Engineering Completeness
01h 29mSoftware Engineering Completeness - Knowing When You Are Done and Why It Matters
33mThe Holy Grail in Scrum: The Done Increment
01h 01mSoftware Engineering Completeness
29mAm I ready to be a Senior Engineer?
33mContinuous Delivery - What does good really look like?
43mPredictable Delivery