Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Definition of Ready (XP2011)

40,345 views

Published on

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.

Published in: Technology

Definition of Ready (XP2011)

  1. 1. Defini&on  of  Ready  
  2. 2. Do something cool As a User I want to do something cool with the product So that I can benefit in some way Concept   Happy  User  ken.power@gmail.com   @ken_power  
  3. 3. Level  of  Focus  on  the  User  Story   Product   Owner   Team   Concept   Time  ken.power@gmail.com   SStart   Done   Accept   SEnd   Ship  It   @ken_power  
  4. 4. Level  of  Focus  on  the  User  Story   Done   Product   Owner   Team   Concept   Time  ken.power@gmail.com   SStart   Done   Accept   SEnd   Ship  It   @ken_power  
  5. 5. Level  of  Focus  on  the  User  Story   Done   Ready   Product   Owner   Team   Concept   Time  ken.power@gmail.com   SStart   Done   Accept   SEnd   Ship  It   @ken_power  
  6. 6. Level  of  Focus  on  the  User  Story   Done   Ready   Product   Owner   Team   Concept   Time  ken.power@gmail.com   SStart   Done   Accept   SEnd   Ship  It   @ken_power  
  7. 7. Level  of  Focus  on  the  User  Story   Done   Ready   Product   Owner   Team   Concept   Time  ken.power@gmail.com   SStart   Done   Accept   SEnd   Ship  It   @ken_power  
  8. 8. Level  of  Focus  on  the  User  Story   Done   Ready   Product   Owner   Team   Concept   Time  ken.power@gmail.com   SStart   Done   Accept   SEnd   Ship  It   @ken_power  
  9. 9. Level  of  Focus  on  the  User  Story   Done   Ready   Product   Owner   Team   Concept   Time  ken.power@gmail.com   SStart   Done   Accept   SEnd   Ship  It   @ken_power  
  10. 10. Level  of  Focus  on  the  User  Story   Done   Ready   Product   Owner   Team   Concept   Time  ken.power@gmail.com   SStart   Done   Accept   SEnd   Ship  It   @ken_power  
  11. 11. Level  of  Focus  on  the  User  Story   Done   Ready   Product   Owner   Team   Concept   Time  ken.power@gmail.com   SStart   Done   Accept   SEnd   Ship  It   @ken_power  
  12. 12. 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@gmail.com   @ken_power  
  13. 13. 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@gmail.com   @ken_power  
  14. 14. 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@gmail.com   @ken_power  

×