Differences

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

--- what_can_we_do_to_improve_our_retrospectives [2020/12/02 06:36] – [Management] hans
+++ what_can_we_do_to_improve_our_retrospectives [2021/09/10 08:37] (current) – Added ice-breaker advice hans
@@ Line 16: / Line 16: @@
 In my experience there are some simple do’s and don’ts that Scrum Masters can use to improve Retrospectives:
-  * Do understand and use a proper retrospective structure ala agile retrospectives - see below
   * Do take time to do a retrospective. General rule of thumb is that if you have a 2 week iteration, you might need a 2 hour retrospective. For a retrospective for a whole quarter you might need up to half a day (depends on depth of discussion). Do not short change the retrospective. Remind people that:
 >“Improving daily work is more important than doing daily work” - Gene Kim, The Phoenix Project
+  * Do understand and use a proper retrospective structure ala agile retrospectives - see below
+  * Do take the time to do an ice-breaker for the team, especially in these times when we are working remotely. Ice-breakers help us learn about our team mates. Pick a subject (it doesn’t have to be a lean agile subject), have people contribute to that subject, and have each person review what they provided, encouraging discussion.
   * Do review results of previous retrospective to close the feedback loop. This reminds people that we are making progress (often we forget how bad things used to be) while establishing the seriousness of the retrospective meeting. Do not sugar coat this - if nothing happened as a result of the previous retrospective (e.g. we identified an improvement area, but didn’t follow up the item with action) then report that.
   * Do spend time on what happened over the period we are reflecting on to reduce impact of [[https://www.projectmanager.com/blog/recency-bias-and-stakeholders|recency bias]]