Page History

Definition of Ready (DoR)

We need expect the backlog owner to understand the value and context of the work being refined, to help define work for prioritization, planning, and delivery. Before refinementbeing refined:

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 expect the backlog owner to use strategic vision to guide prioritization, planning, and delivery:

We refuse to allow low quality requirements to impact our reliability. Before planningcommitment:

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 is refined in priority order
8. Develop Clear Acceptance Criteria so we know what needs to be done

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

DoR for Features:

-The Feature has an owner 

...