Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace:
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/30 08:53] – hpsamioshow_do_we_run_our_first_sprint_retrospective [2019/09/16 06:55] – [Challenges of a Retrospective] Updated organizational issues hpsamios
Line 167: Line 167:
   * Having a Retrospective: After a while team’s begin to feel they have all the improvements under control and so think they don’t need a retrospective. After all, they are perfect. To be clear – there is always room to get better, and so always a need for something like a retrospective.   * Having a Retrospective: After a while team’s begin to feel they have all the improvements under control and so think they don’t need a retrospective. After all, they are perfect. To be clear – there is always room to get better, and so always a need for something like 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 180: 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