Definition of Ready (DoR) checklist

• Definition of Ready (DoR) checklist

A Story is ready for sprint when:

• The story has a self-explanatory title in the format: “As a <role>, I want <function> so that <business goal>”
• The story complies to the INVEST principle:
  • User stories must (ideally) be Independent from one another’s
  • User stories must be Negotiable in conversations between the business and the development team
  • User stories must be acknowledged by the business that their are Valuable
  • User stories must be written to be Estimable
  • User stories should be as Small as possible
  • User stories must be Testable through Acceptance Criteria
• Has a clear description including references to
  • the process description
  • the use case scenario
  • business rules that apply
  • the business objects used
  • mock-up screens and story boards when applicable
• Acceptance criteria describe all features of the story. The story is complete once the acceptance criteria have been met. Acceptance criteria are described as scenarios using the Given When Then format [1]
• The story can be completed in one sprint.
• No external dependencies prevent the story from being completed.
• The story points have been assigned by the team.
• The story has been prioritized.

[1] :We require the Given-When-Then to enable the BDD test framework. See Your Complete Guide To BDD Testing In OutSystems see this Using the Gherkin Language to Write User Stories tutorial how to use it.