definition of ready (xp2011)
DESCRIPTION
Many agile teams are familiar with Definition of Done as a set of agreements that let everyone know when a user story (or a sprint or a release) is really done, and all necessary activities are complete. Definition of Ready is a set of agreements that lets everyone know when something is ready to begin, e.g., when a user story is ready to be taken into a sprint, or when all necessary conditions are right for a team to start a sprint. These are the slides from a talk I gave at XP2011 in Madrid, Spain.TRANSCRIPT
![Page 1: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/1.jpg)
Defini&on of Ready
![Page 2: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/2.jpg)
@ken_power [email protected]
Concept Happy User
Do something cool
As a User I want to do something cool with the product So that I can benefit in some way
![Page 3: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/3.jpg)
Product Owner
Team
Level of Focus on the User Story
Concept SStart SEnd Ship It Done Accept Time @ken_power [email protected]
![Page 4: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/4.jpg)
Product Owner
Team
Level of Focus on the User Story
Concept SStart SEnd Ship It Done Accept
Done
Time @ken_power [email protected]
![Page 5: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/5.jpg)
Product Owner
Team
Level of Focus on the User Story
Concept SStart SEnd Ship It Done Accept
Ready
Done
Time @ken_power [email protected]
![Page 6: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/6.jpg)
Product Owner
Team
Level of Focus on the User Story
Concept SStart SEnd Ship It Done Accept
Ready
Done
Time @ken_power [email protected]
![Page 7: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/7.jpg)
Product Owner
Team
Level of Focus on the User Story
Concept SStart SEnd Ship It Done Accept
Ready
Done
Time @ken_power [email protected]
![Page 8: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/8.jpg)
Product Owner
Team
Level of Focus on the User Story
Concept SStart SEnd Ship It Done Accept
Ready
Done
Time @ken_power [email protected]
![Page 9: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/9.jpg)
Product Owner
Team
Level of Focus on the User Story
Concept SStart SEnd Ship It Done Accept
Ready
Done
Time @ken_power [email protected]
![Page 10: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/10.jpg)
Product Owner
Team
Level of Focus on the User Story
Concept SStart SEnd Ship It Done Accept
Ready
Done
Time @ken_power [email protected]
![Page 11: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/11.jpg)
Product Owner
Team
Level of Focus on the User Story
Time Concept SStart SEnd Ship It Done Accept
Ready
Done
@ken_power [email protected]
![Page 12: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/12.jpg)
Why have a Defini&on of Ready?
• So everyone knows when a User Story is really ready to be taken into a Sprint – It does not need to be “100% defined” with all acceptance criteria, etc.
– It does need to be “ready enough” so that the team is confident they can successfully deliver
@ken_power [email protected]
![Page 13: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/13.jpg)
Defini&on of Ready for a User Story
• User Story defined • User Story Acceptance Criteria defined • User Story dependencies iden&fied • User Story sized by Delivery Team • Scrum Team accepts UE artefacts • Performance criteria iden&fied, where appropriate • Person who will accept the User Story is iden&fied • Team has a good idea what it will mean to Demo the User Story
@ken_power [email protected]
![Page 14: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/14.jpg)
Defini&on of Ready for a Sprint
• The Sprint Backlog is priori&zed • The Spring Backlog contains all defects, User Stories and other work that the team is commiUng to – No hidden work – Examples of ‘other work’ might include lab setup, build environment maintenance, crea&ng a test app
• All team members have calculated their capacity for the Sprint – Full&me on project = X hours per day
• All User Stories meet Defini&on of Ready
@ken_power [email protected]
![Page 15: Definition of Ready (XP2011)](https://reader033.vdocument.in/reader033/viewer/2022051612/54c24c0f4a7959f43c8b45a5/html5/thumbnails/15.jpg)