The Definition of Ready (DoR) specifies the criteria that must be met before a backlog item (such as a user story, feature, or capability) can be considered ready for implementation. 

It helps ensure that the team has all the necessary information and clarity before starting work on a backlog item.

Here’s an example of what a Definition of Ready might include:

Example Definition of Ready

1. Clear Description:

   • The backlog item has a clear and concise description that outlines what needs to be done.

2. Acceptance Criteria:

   • Acceptance criteria are defined and agreed upon, detailing what success looks like.

3. Dependencies Identified:

   • Any dependencies on other teams, systems, or components are identified and documented.

4. Estimation:

   • The item has been estimated by the team, ensuring that the effort required is understood.

5. Stakeholder Input:

   • Relevant stakeholder input has been gathered, ensuring that the item aligns with business needs.

6. Technical Feasibility:

   • The technical feasibility of the item has been assessed, and any potential risks are identified.

7. Prioritization:

   • The item is prioritized in the backlog, ensuring it is ready to be pulled into the next iteration or Program Increment (PI).