Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

The Definition of Ready ensures that the product backlog items are well-prepared, understood, and have enough information for the development team to start working on them. The criteria in the DoR may vary from team to team.

To consider the Story ready for a developer we should have this criterion already defined:

  • Title: a clear user story title is defined and give a well visibility of the problem to be solved
  • Description/Problem statement: a clear and concise statement that describes a specific problem to be solved or a gap to be filled.
  • Acceptance Criteria: specific conditions or requirements that a product or feature must meet to be considered acceptable or "done" from the perspective of the stakeholders or users.
  • Dependencies: mapped all dependencies from other teams/applications
  • Estimates: use the specific measure to estimate the story on the macro vision
  • Wireframes: mockups provided by the UI/UX designer
  • Testability: comprehensive test plan created to guide the developers in executing the required tests
  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.