Definition of Ready (DoR)

The Definition of Ready (DoR) is a set of criteria a user story or backlog item must meet before the development team can begin working on it. It ensures the user story is well-prepared and all necessary information and prerequisites are in place, helping the team avoid delays and uncertainties during the sprint.

Key Components of the Definition of Ready

1. Clear and Understandable: The user story should be clearly written and understandable by all team members.
2. Acceptance Criteria Defined: Specific conditions must be met for the story to be considered complete, and these conditions should be clearly defined.
3. Estimate Provided: The story should have an estimated effort in story points or time.
4. Dependencies Identified: Any dependencies on other tasks, stories, or external factors should be identified and addressed.
5. Testable: The story should have clear, testable conditions that allow for verification of completion.
6. User Perspective: The story should describe the feature from the user’s perspective, outlining the value or benefit to the user.
7. Prioritized: The Product Owner should prioritize the story in the backlog.
8. Acceptance by Team: The development team should agree that the story is ready to be worked on and can be completed within a sprint.
9. Design and UI/UX Elements: Any necessary design, wireframes, or UI/UX elements should be attached or available.
10. No Major Blockers: No significant impediments or blockers should prevent the story from being started.

Example of Definition of Ready

Here’s an example of how a Definition of Ready might look for a development team:

1. User Story is Well-Defined: “As a user, I want to be able to log in using my email and password so that I can access my account.”
2. Acceptance Criteria Specified:
   • Users can enter their email and password.
   • Users can click a ‘Login’ button to authenticate.
   • Error messages are displayed for invalid credentials.
   • Successful log in redirects to the user dashboard.
3. Story Point Estimate: The story is estimated at five story points.
4. Dependencies: The authentication API must be available.
5. Testable Conditions: Test cases are written for valid and invalid login attempts.
6. User Perspective Clearly Outlined: The story describes the benefit to the user (accessing their account).
7. Prioritization: The story is prioritized by the Product Owner and scheduled for the upcoming sprint.
8. Team Agreement: The development team has reviewed the story and agrees that it is ready to be worked on.
9. Design Elements Provided: Mockups or wireframes of the login page are available.
10. No Blockers: No major impediments are preventing the start of this story.

Benefits of Definition of Ready

1. Reduces Ambiguity: Ensures that user stories are clear and understandable, reducing misunderstandings.
2. Improves Planning: Helps in accurate sprint planning and estimation.
3. Increases Efficiency: Reduces delays and blockers during the sprint by meeting all prerequisites.
4. Enhances Quality: Ensures that stories are testable and meet predefined acceptance criteria, leading to higher-quality deliverables.
5. Facilitates Better Collaboration: Encourages collaboration between the Product Owner and the development team to refine and prepare stories.

By having a clear Definition of Ready, teams can ensure that they start working on well-prepared user stories and that they can complete them efficiently within the sprint.