Page History

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 
• 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:

1. The backlog author is prepared to clarify the requirements and context of the work ​
2. The work item contains a value statement (who, what, why)​
3. 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:

1. The work item contains potential risks, blockers, unknowns, and dependencies​
2. The work item contains relevant guidance, information, documentation links​
3. Defects are clearly defined with:
   1. Steps to reproduce​
   2. Expected results​
   3. Screenshots/logs​
   4. Test data
4. The work item can be traced to its origin (Feature, Epic, OKR)​
5. The work item is clearly categorized by value type
   1. Story​
   2. Bug/Defect​
   3. Enabler (Spike)
6. The work item is sized​
7. The work item is prioritized

We will only make commitments for work that meets our standards of Ready.

Image Added