Definition of Ready

“Before everything else, getting ready is the secret of success.” ~ Henry Ford

For a ticket to be considered Ready to be added to the sprint it needs to:

1. Be written in English

2. Have been entered in our virtual ticket tracking system ⁽¹⁾

3. Have been categorized ⁽²⁾

4. Be clear which Story or Epic the ticket belongs to ⁽³⁾

5. Have been approved by the PO

6. Have been estimated by the team

7. Have a physical ticket on the Scrum board which contains the Summary, estimate and the ticket ID

8. Have all the relevant information for the developer to start working on the issue ⁽⁴⁾

9. Be understood by the development team to the extent that they are willing to commit to the task as described in the ticket

10. Dependencies are identified and no external dependencies would block the Product Backlog Item (PBI) from being completed

11. Acceptance Criteria are testable

12. Scrum team understands how to demonstrate the PBI at the Sprint review / Demo

Footnotes

1. Currently this is JIRA
2. In JIRA this means adding one of existing labels, if relevant
3. In JIRA this means having a link to an Epic or Story issue
4. See the software development protocols for details