Page History

We expect the Product Manager to use strategic vision to guide prioritization, planning, and delivery:

1. (Suggest: The vision for all features are presented to the team)
2. (Suggest: The Product Manager will be fully available to the feature owner)
3. Work Defined at the Feature level will be prioritized

We expect all team members backlog owner(suggest: team) to understand the value and context of the all work being included in each iteration: refined:

1. The Feature Owner understands the vision and the expected outcomes of the feature
2. The Feature Owner The backlog author is prepared to clarify the requirements and context of the work in refinement and/or planning​
3. The work item defined contains a value a value statement (who, what, why) (benefit hypothesis or use story statement)​
4. The work item defined contains clear acceptance criteria that can be verified as pass/fail
5. (Suggest: The Feature Owner understands the vision and the expected outcomes of the feature)

We expect the Product Manager to use strategic vision to guide prioritization, planning, and delivery:

1. (success or acceptance criteria)
2. The work defined will fit into the appropriate timebox
3. (Suggest: The vision for all features are presented to the team)
4. (Suggest: The Product Manager will prioritize availability to the feature owner)

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

For each work item, before commitment:

1. The work item contains potential risks, blockers, unknowns, and dependencies​is prioritized
2. The correct issue type is used
3. The value is clear and understood
4. If necessary or beneficial to cross-functionality, Mob/Pair team members are identified
5. All team members delivering will added to a role
6. Binary criteria are present
7. There is an estimate
8. Labels are accurate
9. Links are accurate (clones, features, dependencies, etc)
10. Relevant The work item contains relevant guidance, information, and documentation links ​are included
11. Potential risks, blockers, unknowns, and dependencies​ are noted
12. Defects are clearly defined with:
    1. Steps to reproduce​
    2. Expected results​
    3. Screenshots/logs​
    4. Test data
13. The work item can be traced to its origin (Feature, Epic, OKR)​
14. The work item is clearly categorized by value type
    1. Story​
    2. Bug/Defect​
    3. Enabler (Spike)
15. The work item is sized​
16. The work is refined in priority order
17. 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 

-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

Extra notes :

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

...