Definition of Ready

Before a development story is added to a sprint, it must be "ready," which we define as meaning that all of the following have been addressed to the satisfaction of the team:

• Testable acceptance criteria are in the story and cover all the case(s) that the story must implement in order to be acceptable to the Product Owner. All relevant stakeholders help shape the acceptance criteria.
• Any UI designs needed by the developers are available and the story links to them.
• The scope boundaries of the story are clear to the team and any explicit exclusions are documented in a list of work being handled by other stories or work that is simply out of scope.
• Known dependencies and prerequisites are documented in the story. They don't necessarily have to be addressed prior to the sprint start.