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:

...

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​The work item is prioritized
7. Go over the specific user stories listed in the next sprint during refinement for Prioritization
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.

Features:

-The Feature has an owner 

-Clear Benefit Hypothesis

-Clear measure of success

-Write features to fit in a specific time frame when applicable so they can be closed out when completed

-Outline clearly how we will deliver on features objectives (pick up here)

-Feature has been discussed with the team during refinement

-Potentially cut features when looking at our measure of success (View as a team)

-10 min block during refinement meeting for feature owners to review and discuss their features progress or current state. 

(Any new features to review or any clarity needed on a feature)