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 revisionLast revisionBoth sides next revision | ||
how_do_we_run_our_first_sprint_retrospective [2018/05/30 08:53] – hpsamios | how_do_we_run_our_first_sprint_retrospective [2020/12/16 11:03] – Terminology consistency hans | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== How Do We Run Our First Sprint (or Iteration) Retrospective? | + | ====== How Do We Run Our First Iteration |
====== Premise ====== | ====== Premise ====== | ||
- | At the end of a sprint, the Team holds a Sprint (or Iteration) Retrospective to review their work process and the way the Team worked together (the " | + | At the end of a sprint, the Team holds a Iteration |
====== Background ====== | ====== Background ====== | ||
- | When reviewing | + | When reviewing |
* What went well that we should continue to do? | * What went well that we should continue to do? | ||
Line 24: | Line 24: | ||
In addition in most cases should be an energizing (if sometimes exhausting) event. | In addition in most cases should be an energizing (if sometimes exhausting) event. | ||
- | Everyone on the Team should participate in the Retrospective. Others may be invited, but this is essentially a Team-focused activity. The Team can determine who they want to invite on a iteration-by-iteration | + | Everyone on the Team should participate in the Retrospective. Others may be invited, but this is essentially a Team-focused activity. The Team can determine who they want to invite on a Iteration-by-Iteration |
The Scrum Master' | The Scrum Master' | ||
Line 76: | Line 76: | ||
====== Sample Retrospective ====== | ====== Sample Retrospective ====== | ||
- | The following is a simple | + | The following is a simple |
* Preparation: | * Preparation: | ||
Line 137: | Line 137: | ||
As said, a Retrospective meeting is the easiest way to get this all done, ensures that the team takes time to focus on improvement, | As said, a Retrospective meeting is the easiest way to get this all done, ensures that the team takes time to focus on improvement, | ||
- | For distributed Teams, there is always an issue of " | + | For distributed Teams, there is always an issue of " |
===== " | ===== " | ||
Line 167: | Line 167: | ||
* Having a Retrospective: | * Having a Retrospective: | ||
* All the issues are not the team’s fault: For these teams, recommend that the team’s maintain two lists: 1) things that the team needs to address 2) things that the organization needs to address. Set the expectation that both lists will be populated. | * All the issues are not the team’s fault: For these teams, recommend that the team’s maintain two lists: 1) things that the team needs to address 2) things that the organization needs to address. Set the expectation that both lists will be populated. | ||
- | * Organizational issues are being dealt with: Management has responsibility to the system the team is operating in. In the early days of the team, there are typically many things identified that can and should be addressed by the team and you often see rapid improvement. Some things can only be addressed by management, and the worse thing that can happen is that the team repeatedly raises organizational issues, but nothing is done about it. Management needs to be open and transparent about working organizational issues and become very responsive to these kinds of requests. | + | * Organizational issues are not being dealt with: Management has responsibility to the system the team is operating in. In the early days of the team, there are typically many things identified that can and should be addressed by the team and you often see rapid improvement. Some things can only be addressed by management, and the worse thing that can happen is that the team repeatedly raises organizational issues, but nothing is done about it. Management needs to be open and transparent about working organizational issues and become very responsive to these kinds of requests. |
* The team does not talk about people issues: Some people think that high performing teams are smooth running teams. The opposite is true. A significant hallmark of high performing teams is “constructive dissent” where there is passionate disagreements about the things that are important to the goals of the team. To make this kind of happen, team members really need to be able to trust their team mates. Trust only develops when you have dealt (as a team) with all the inter-personal issues you have. Trust does not develop where everyone is behaving politely and where people have not worked through the difficult personal issues. | * The team does not talk about people issues: Some people think that high performing teams are smooth running teams. The opposite is true. A significant hallmark of high performing teams is “constructive dissent” where there is passionate disagreements about the things that are important to the goals of the team. To make this kind of happen, team members really need to be able to trust their team mates. Trust only develops when you have dealt (as a team) with all the inter-personal issues you have. Trust does not develop where everyone is behaving politely and where people have not worked through the difficult personal issues. | ||
* The team does not see improvement from one sprint to the next: Make sure the first part of the retrospective is focused on “what happened as a result of the last set of experiments we have run – did things get better and, if not, what have we learned.” See also the "Tears of Joy" idea above. | * The team does not see improvement from one sprint to the next: Make sure the first part of the retrospective is focused on “what happened as a result of the last set of experiments we have run – did things get better and, if not, what have we learned.” See also the "Tears of Joy" idea above. | ||
Line 179: | Line 179: | ||
====== Want to Know More? ====== | ====== Want to Know More? ====== | ||
+ | * [[what_can_we_do_to_improve_our_retrospectives|What Can We Do To Improve Our Retrospectives? | ||
* [[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