Definition of Ready

Before assigning a story to the developers team, the story definition should be ready. This ensure fast implementation and good delivered quality.

1. The story contains a high level description in the form: As a X, I want Y, so that Z. This part should clearly describe the motivation for the feature and gives context.
   1. One or multiple demo scenario to demonstrate and test all features in the story are available in the story if the user story is not covering enough the demo scenario.
2. If screens are created or modified, mockups or graphical designs have to be provided.
3. All assets (icons, backgrounds, colors, ...) must be provided and clearly defined in the story.
4. All relevant documentation is provided (third party APIs, etc.)
5. No implementation details are present in the story (but implementation hints/suggestions from backlog grooming might be present).
6. The story has an estimation (team) and, optionally, a business value (product owner).
7. Pertinent business rules are all documented in the wiki and linked in the story.
8. Specific deadlines and hosting requirements are specified (deployment deadline, version dependencies, etc.).
   1. Contains also the impact on public APIs