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.

3. Armine - retrospective and grooming

768 views

Published on

Agile Tour by Macadamian - 04 Oct 2014

Published in: Education
  • Be the first to comment

3. Armine - retrospective and grooming

  1. 1. AGILE TOUR YEREVAN 04, October, 2014 Sprint Retrospective and Backlog Refinement Armine Amiryan Confidential 10/6/2014 1
  2. 2. Agenda  Sprint Retrospective Meeting  Backlog Refinement Meeting / Grooming 2
  3. 3. Sprint Retrospective 3 Daily Scrum Sprint Planning Sprint Retrospective Sprint Review The last event in scrum circle – empirical feedback Sprint
  4. 4. The Purpose Sprint Retrospective is to:  Inspect how the last Sprint passed regarding people, relationships, processes, and tools  Identify what went well, and what can be improved  Create a plan for implementing the improvements 4
  5. 5. Description The Sprint Retrospective is  time-boxed to 3-hours and is attended by:  the Scrum Team,  the Scrum Master,  the Product Owner (optional)  intended to answer 2 fundamental questions:  What went well during the last Sprint that we continue doing?  What could we do differently to improve?  usually facilitated by the SM who is also taking notes. 5
  6. 6. Process  Ideas on “how”:  SM asks the team to share their ideas within a discussion, writes down the results and shares with the team  Team-members write down the improvements on the Sticky notes, stick them on the board and group the ideas  What’s important  Timeline approach – make it clear when the problem was noticed during the Sprint (at the beginning, at the end, in the middle, etc.)  Come up with an action plan  Sometimes they do:  Safety Check 6
  7. 7. Result The meeting must end with a list of action items that have been agreed upon and will be implemented. 7
  8. 8. Sprint Retrospective Practice  What went well during the last Sprint that we continue doing?  What could we do differently to improve? Also  What did we learn?  What still puzzles us? 8
  9. 9. Backlog Refinement A K A  Product Backlog Grooming  Backlog Estimation  Backlog Maintenance  Story Time 9
  10. 10. Participants: The Scrum Team  Product Owner  Development Team  Scrum Master 10
  11. 11. Why & When 11
  12. 12. Create INVEST PBIs 12
  13. 13. The Refinement Process  Prioritizing by the PO  Focus on top item (Epic)  Estimation by the Dev Team  Splitting the Epics to User Stories  Estimation of User Stories 13
  14. 14. Purpose & Result  Estimation of efforts  Clarification of requirements  Decomposition of large PBIs into smaller ones  Help the PO to get the top PBIs ready for next Sprint Planning 14
  15. 15. Questions 15
  16. 16. Thank You! 16

×