Definition of Ready (DoR): Gaining Clarity Before Work Begins

The Definition of Ready (DoR) is a central element in agile development processes, ensuring that all requirements for a work package or User Story are clarified before the development team begins work. It serves as a quality standard and ensures that all stakeholders have a common understanding of what is expected.

What is the Definition of Ready (DoR)?

The DoR is a checklist or a set of criteria that must be met before a User Story or work package can be moved into a sprint or workflow. It ensures that the team has all the necessary information to start work and that no major questions remain open.

Example Criteria for a DoR

1. The User Story is clearly formulated and understandable.
2. Acceptance criteria are defined and understandable.
3. All dependencies and prerequisites are clarified.
4. The User Story is technically feasible.
5. There are no open questions that could block implementation.
6. The necessary resources (e.g., data, tools, access) are available.

Practical Example

A product team wants to develop a new login function for an app. Before this User Story is brought into the next sprint, the team checks the DoR criteria. They discover that not all dependencies on external services have been clarified yet. The User Story is put on hold until these questions are resolved.

Important Notes

• The DoR should be reviewed regularly and adjusted as needed.
• It serves as a guideline, not a rigid rule. In some cases, it may make sense to deviate from the DoR if the team deems it necessary.
• A clear DoR helps to accelerate the workflow and prevent blockers.

Conclusion

The Definition of Ready is a powerful tool to ensure that all stakeholders are on the same page and that work can be carried out efficiently and purposefully. A common understanding and clear criteria are key to successful agile work.