Definition of Ready in Agile

Definition of Ready AgileAgile teams use product backlogs to manage their requirements. Product owners prioritize the user stories. To enable delivering products with sufficient quality agile teams need to have user stories that are ready at the start of an iteration.

Agile teams treat requirements as being stable during an iteration. Ready means that the quality of the user stories is sufficient so that teams can start developing the software.

Teams can use a Definition of Ready (DoR) to check the user stories. A DoR states the criteria that a user story should meet be accepted into an iteration.

Defining your own Definition of Ready

Some useful resources to make your own Definition of Ready are:

Having prioritized user stories with sufficient quality ready at the start of an iteration helps to increase commitment from the stakeholders and the development team and to keep requirements stable during the iteration, resulting in higher product quality.

Share this Experience
  • 31
    Shares

Ben Linders

I help organizations with effective software development and management practices. Active member of several networks on Agile, Lean and Quality, and a frequent speaker and writer.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.