User Tools

Site Tools


how_do_we_run_our_first_sprint_retrospective

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
how_do_we_run_our_first_sprint_retrospective [2018/05/24 11:12] – [Meeting Outline] hpsamioshow_do_we_run_our_first_sprint_retrospective [2019/08/14 05:42] – [Want to Know More?] added liberating structures hpsamios
Line 7: Line 7:
 ====== Background ====== ====== Background ======
  
-The Team can consider potential improvement topics, such as the following areas:+When reviewing retrospective materials you will often see that the retrospective is about:
  
-  * Quality: How to reduce defects which escape from the Sprints?+  * What went well that we should continue to do? 
 +  * What did not go well that we should perhaps improve? 
 +  * What ideas do we have to improve? 
 + 
 +But then they offer little advice about how to make this happen. The result is that Teams will often set up a meeting, put these headings on the board and then discuss. While this can produce results, most Teams that do it this way will find the results superficial, that they feel that it is boring, and they feel that no progress is being made. 
 + 
 +The first thing we need to ask ourselves is "what areas do we need to look at to focus on our improvements?". In general, Teams can consider potential improvement topics, such as the following areas: 
 + 
 +  * Quality: How to reduce defects which escape from the Sprints / Iteration?
   * Predictability: How to bring committed velocity close to actual velocity?   * Predictability: How to bring committed velocity close to actual velocity?
-  * Throughput: How to increase the value of work delivered each Sprint?+  * Throughput: How to increase the value of work delivered each Sprint / Iteration?
   * Team health: How are we working as a team?   * Team health: How are we working as a team?
  
Line 20: Line 28:
 The Scrum Master's role during the Retrospective is to facilitate the Team's discussion about improving their delivery process. It may be helpful, and a beneficial change of pace, to have someone else facilitate the meeting so the Scrum Master can participate as a “normal” Team member during the Retrospective. For example, another Team's Scrum Master could serve as facilitator. The Scrum Master's role during the Retrospective is to facilitate the Team's discussion about improving their delivery process. It may be helpful, and a beneficial change of pace, to have someone else facilitate the meeting so the Scrum Master can participate as a “normal” Team member during the Retrospective. For example, another Team's Scrum Master could serve as facilitator.
  
-The result of a Retrospective is a prioritized list of potential improvements with a few selected to be worked on during the next Iteration. Often these improvements are defined as backlog items, to ensure that they are worked on in the Iteration. Like any backlog item these are estimated, prioritized and, when they become part of the Iteration, are detailed just like any other backlog item.+The result of a Retrospective is a prioritized list of potential improvements with a few selected items to be worked on during the next Sprint / Iteration. Often these improvements are defined as backlog items, to ensure that they are worked on in the Sprint / Iteration. Like any backlog item these are estimated, prioritized and, when they become part of the Sprint / Iteration, are detailed just like any other backlog item.
  
-During the next Iteration's Retrospective, prior improvement items should be reviewed for progress made in achieving the expected result or to understand what happened, whether the improvement was (or still shows potential to be) successful, or whether something else needs to be tried.+During the next Sprint / Iteration's Retrospective, prior improvement items should be reviewed for progress made in achieving the expected result or to understand what happened, whether the improvement was (or still shows potential to be) successful, or whether something else needs to be tried.
  
 As much as possible try to treat these improvements as “experiments.” In other words, we want to set up an experiment with an expected result, we understand how we are going to track the experiment (metrics) as we run it, and we then run the experiment in the next Iteration to see if the expected result occurs. There are a couple of reasons for doing it this way: As much as possible try to treat these improvements as “experiments.” In other words, we want to set up an experiment with an expected result, we understand how we are going to track the experiment (metrics) as we run it, and we then run the experiment in the next Iteration to see if the expected result occurs. There are a couple of reasons for doing it this way:
Line 33: Line 41:
 ====== Structure ====== ====== Structure ======
  
-**Duration**: Maximum 1.5 hours for a 2 week sprint (10 working days).+**Duration**: Maximum 1.5 hours for a 2 week Sprint / Iteration (10 working days) - 1/2 that for 1 week Sprint / Iteration.
  
 **Who**: The Team and others invited by the team. **Who**: The Team and others invited by the team.
Line 48: Line 56:
   * Is there anything we want to raise to management that would help?   * Is there anything we want to raise to management that would help?
  
-**Result**: A couple of improvement experiments to try in the next Iterations, publish to a public place (team site).+**Result**: A couple of improvement experiments to try in the next Sprint / Iteration, publish to a public place (team site).
  
 ====== Meeting Outline ====== ====== Meeting Outline ======
Line 72: Line 80:
   * Preparation:   * Preparation:
     * Have team metrics (actual throughput / velocity, committed vs actual throughput / velocity, cycle time, and others such as % unplanned work) displayed in the room     * Have team metrics (actual throughput / velocity, committed vs actual throughput / velocity, cycle time, and others such as % unplanned work) displayed in the room
-    * Have “retrospective prime directive” displayed in the room - see below +    * Have “Retrospective Prime Directive” displayed in the room - see below 
-    * Have “timeline” drawn up in the room - see below “running retrospective” for image+    * Have “timeline” drawn up in the room - see below “Running Retrospective” for image
     * Have “liked, didn’t like, kudos, idea” grid drawn up in the room     * Have “liked, didn’t like, kudos, idea” grid drawn up in the room
     * Food in the room, perhaps something to celebrate with as well     * Food in the room, perhaps something to celebrate with as well
Line 172: Line 180:
  
   * [[http://www.amazon.com/Agile-Retrospectives-Making-Pragmatic-Programmers-ebook/dp/B00B03SRJW/ref=tmm_kin_swatch_0?_encoding=UTF8&qid=&sr=|Agile Retrospectives]] - the Bible!   * [[http://www.amazon.com/Agile-Retrospectives-Making-Pragmatic-Programmers-ebook/dp/B00B03SRJW/ref=tmm_kin_swatch_0?_encoding=UTF8&qid=&sr=|Agile Retrospectives]] - the Bible!
-  * [[collaboration_at_scale_-_keeping_retrospectives_fresh_by_ben_linders|Keeping Retrospectives Fresh]] - report of a webinar. Idea is to vary goal, exercises and environment to keep retrospective engaging +  * [[collaboration_at_scale_-_keeping_retrospectives_fresh_by_ben_linders|Keeping Retrospectives Fresh]] - report of a webinar. Idea is to vary goal, exercises and environment to keep retrospective engaging. 
-  * [[http://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki|Retrospective Wiki]] - resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives+  * [[http://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki|Retrospective Wiki]] - resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives.
   * [[https://www.benlinders.com/exercises/|A retrospective toolbox from Ben Linders]] - Exercises to keep things interesting   * [[https://www.benlinders.com/exercises/|A retrospective toolbox from Ben Linders]] - Exercises to keep things interesting
   * [[https://plans-for-retrospectives.com/|"Dial-a-retrospective" or "Ret-ro-mat"]] - Uses the structure defined by Agile Retrospectives, and a suite of games / exercises to dial up a new retrospective.   * [[https://plans-for-retrospectives.com/|"Dial-a-retrospective" or "Ret-ro-mat"]] - Uses the structure defined by Agile Retrospectives, and a suite of games / exercises to dial up a new retrospective.
   * [[http://tastycupcakes.org|Tasty Cupcakes Tools for Innovation and Learning]] - Not just retrospectives, but exercises and games for all kinds of situations.   * [[http://tastycupcakes.org|Tasty Cupcakes Tools for Innovation and Learning]] - Not just retrospectives, but exercises and games for all kinds of situations.
-  * [[http://www.funretrospectives.com/|Fun Retrospectives]]+  * [[http://www.funretrospectives.com/|Fun Retrospectives]]. Site with, no surprise, fun retrospectives. 
 +  * [[http://www.liberatingstructures.com/|Liberating Structures]]. Great site for collaborative, inclusive facilitation techniques. Again, great for retrospectives but also useful in other situations.
  
 {{tag>Consultant Tools Team Retrospective Ceremony FirstSprint FAQ}} {{tag>Consultant Tools Team Retrospective Ceremony FirstSprint FAQ}}
- 
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/how_do_we_run_our_first_sprint_retrospective.txt · Last modified: 2021/10/06 13:14 by hans