Definition of Ready (DoR)
- Clear Acceptance Criteria so we know what needs to be done. (elaborate no general statements)
- Create a checklist of what needs to be done on a user story before it can be implemented into next sprint
- Guideline for what needs to be done during backlog refinement
- Add and grow overtime
- Ex. The user story is understood by the team :
- Clear Business value
- all dependencies are identified
- story is small
- AC is defined
- Ex. The user story is understood by the team :
- Feature is prioritized
- Features:
- Operations SOP:
Example of how we may want to write these( Social Contracts slides):
We need the backlog owner to understand the value and context of the work being refined, to help define work for prioritization, planning, and delivery. Before refinement:
- The backlog author is prepared to clarify the requirements and context of the work
- The work item contains a value statement (who, what, why)
- The work item contains clear acceptance criteria that can be verified as pass/fail
We refuse to allow low quality requirements to impact our reliability. Before planning:
- The work item contains potential risks, blockers, unknowns, and dependencies
- The work item contains relevant guidance, information, documentation links
- Defects are clearly defined with:
- Steps to reproduce
- Expected results
- Screenshots/logs
- Test data
- The work item can be traced to its origin (Feature, Epic, OKR)
- The work item is clearly categorized by value type
- Story
- Bug/Defect
- Enabler (Spike)
- The work item is sized
- The work item is prioritized
We will only make commitments for work that meets our standards of Ready.