how_do_we_run_our_first_sprint_retrospective
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
how_do_we_run_our_first_sprint_retrospective [2018/05/24 11:12] – [Meeting Outline] hpsamios | how_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 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, | ||
+ | |||
+ | The first thing we need to ask ourselves is "what areas do we need to look at to focus on our improvements?" | ||
+ | |||
+ | | ||
* Predictability: | * Predictability: | ||
- | * Throughput: How to increase the value of work delivered each Sprint? | + | * Throughput: How to increase the value of work delivered each Sprint |
* 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' | The Scrum Master' | ||
- | 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 |
- | During the next Iteration' | + | During the next Sprint / Iteration' |
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**: | + | **Duration**: |
**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:// | * [[http:// | ||
- | * [[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:// | + | * [[http:// |
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// | ||
* [[http:// | * [[http:// | ||
- | * [[http:// | + | * [[http:// |
+ | * [[http:// | ||
{{tag> | {{tag> | ||
- |
/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