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.

Achieving Ready Ready User Stories

1,909 views

Published on

How to get Ready-Ready user stories in agile? Software requirements made easy

Published in: Education

Achieving Ready Ready User Stories

  1. 1. Achieving ready-ready stories<br />Gil Nahmias, csp<br />
  2. 2. Consider an organization<br />PO (BA)<br />Team<br />Chief PO<br />PO (BA)<br />Team<br />
  3. 3. And a team Story Board<br />A<br />B<br />C<br />D<br />E<br />F<br />G<br />H<br />
  4. 4. Who’s usually engaged?<br />A<br />B<br />C<br />D<br />E<br />F<br />G<br />H<br />
  5. 5. And a team Story Board<br />A<br />B<br />C<br />D<br />E<br />F<br />G<br />H<br />
  6. 6. And a team Story Board<br />“customer” of the column = team<br />A<br />B<br />C<br />D<br />E<br />F<br />G<br />H<br />
  7. 7. After a while…<br />Ready Ready Story<br />Epic<br />Ready Ready Story<br />Ready Ready Story<br />Ready Ready Story<br />Ready Ready Story<br />
  8. 8. Definition of ready<br />Quantity<br />Ready Ready Story<br />Are there just enough stories waiting on the team to develop?<br />Quality<br />Do the stories form a good viable software?<br />
  9. 9. Definition of ready<br />Quantity<br />Ready Ready Story<br />Relevance<br />Is the story aligned with the epic / business goal?<br />Quality<br />Achievability<br />What are the chances of completing the story in time?<br />
  10. 10. Ideas for “Ready-ready” process<br />1-2 sprints worth ahead<br />Quantity<br />Ready Ready Story<br /><ul><li>Approve by Chief PO
  11. 11. Prioritize</li></ul>Relevance<br />Quality<br /><ul><li>INVEST + “As a..” syntax
  12. 12. Can be estimated by team in < 15min
  13. 13. Estimated in < 5 days
  14. 14. Lead time < 5 days
  15. 15. Tests & AT defined
  16. 16. Approve API / UI mockups
  17. 17. Approve by Team
  18. 18. Measure % time story was actually worked on</li></ul>Achievability<br />
  19. 19. Defect analysis<br />
  20. 20. Defect analysis<br />Requirement <br />Defect?<br />Design <br />Defect?<br />Implementation Defect?<br />Other Defect?<br />
  21. 21. Defect analysis<br />Retrospect to improve <br />“Ready-Ready”<br />Requirement <br />Defect?<br />Communication<br />Design <br />Defect?<br />Knowledge<br />Implementation Defect?<br />Availability<br />.<br />.<br />.<br />Other Defect?<br />
  22. 22. ?<br />Now, when we know what we want to do,<br />how to present it to the organization?<br />
  23. 23. Presenting to the org - format <br />Org support<br />KPI<br />
  24. 24. Presenting to the org<br />To provide <br />direction<br />Org support<br />KPI<br />To help them achieve the goal<br />
  25. 25. Presenting to the org<br />For example:<br />PO gets time to learn the needs better<br />Story can be estimated by team in 15 mins<br />Tech guru avail in planning<br />Practice “Sniffing Era”<br />
  26. 26. Presenting to the org<br />Another example:<br />More PO Availability<br />Lead time<br />Lab time<br />Protect team when reviewing DoD<br />
  27. 27. That’s just a starting point<br />Start experimenting...<br />NOW!<br />
  28. 28. Drop me a line<br />gil@agilesparks.com<br />myagile.co.il<br />

×