Episode 7 : Definition of Ready (DOR) in Agile

In software we come across common patterns like teams start the sprint with the Sprint backlog and soon we get to hear that they cannot move on with certain stories for different reasons like Story not understood properly or we have dependencies on other teams and so on.

How do we get over these kinds of problems? The answer to these questions is “Definition of Ready (#DOR)”

In this episode, we will try to understand what DOR is and as a team how do we come up with DOR for our team.

Definition of Ready (DOR), as the name suggests, is making the User Story ready before it can be taken into the Sprint. This is the criteria or the check list the User Story must meet. When we have this criterion defined then it becomes a common understanding to all team members and the stakeholders what it means when teams say User Story is READY. This will help the teams to plan the sprint better and achieve the goals they are planning to achieve in the Sprint.

How to define Definition of Ready (DOR)

As a coach I would recommend that the whole team should participate and contribute to setting the Definition of Ready criteria. This DOR could be different for different teams based on the environment, the context and other factors which will have an impact on their work. Scrum Master should organize a workshop where every team member participates and gives their input. They can choose the format for the workshop they are comfortable with.

Below are some factors teams can consider for DOR.

1.??????Story described by Product Owner and understood by everyone in the team.

2.??????If required, the story is further sliced so that it can be completed within one Sprint.

3.??????Dependencies have been identified and possibly resolved.

4.??????In scope and Out of Scope been described and understood by the team

5.??????The story has been estimated using Relative estimation techniques.

6.??????Acceptance criteria defined and understood by team.

7.??????Performance criteria identified.

8.??????Any criteria specific to the Organization

9.??????Criteria specific to teams

The above list is only an example and is in no way comprehensive. Once the team has DOR, they should make sure that they follow this for all the stories before they can take them into the Sprint. Scrum Master should coach in case teams are taking exceptions or shortcuts. It is the refinement meeting where teams should go through all the Stories and make them READY. The recommended practice is that the teams should keep enough Stories ready which are good enough for at least next two sprints.

Once the team has DOR, does that mean it is frozen and teams do not have an option to change it? The answer to this question is “NO”.

They will have an opportunity to revisit their DOR in retrospective and if they feel they must change it they can do it but not during the Sprint.

Anti Pattern: ?Teams have DOR but hidden somewhere and teams, stakeholders do not have access to it. Teams only understand the stories from Product Owner during refinement meetings and not making Stories READY as per DOR or not following DOR for all User Stories.