What is ready and what is done? Oh, crazy agile world!
👉 A common question from Software Developers and Agile practitioners is how do I know if my story is ready, and is it done yet?
After reviewing multiple times, both tables below are the conclusion to that question, of course, still in refining, however, close to perfection(not) 😅.
Being SCRUM Master and Software Development Manager for quite a long time, helped me to share my vision on what is Ready to be picked up and worked and also what is what we call, done. Simple, but efficient and well understood by the team.
⚠️DoR — Definition of Ready
A set of agreements that let you know when a user story is really done, and all the essential activities are complete is the Definition of Done. But the Definition of Ready is a different concept. It is a set of agreements that tells you when something is ready to begin. More correctly, “if something is good to begin”.
E.g., when a user story is ready to be taken into a sprint, or when all the conditions are right for a team to begin a sprint.
- The story should be written exactly in the ‘user story’ format.
- Acceptance criteria must be understood by the team.
- A-Team needs to estimate the story. We use 1,3,5,8, meaning S,M,L,XL
- The team should understand how to provide a demo of the features.
- Performance criteria should be understood by the team.
✅DoD — Definition of Done
- The code should be peer-reviewed
- Code is deployed to the PPE/TEST environment
- Regression testing should be passed by feature/code
- The code should have a unit test, integration test, smoke test and e2e test
- Documentation up to date in Wiki(Github) and OpenAPI spec
- Observability, what is the impact on observability?
- Help/Run documentation is updated