Differences

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

--- how_do_we_run_our_first_sprint_retrospective [2020/06/02 14:22] – external edit 127.0.0.1
+++ how_do_we_run_our_first_sprint_retrospective [2021/10/06 13:14] (current) – [Want to Know More?] hans
@@ Line 1: / Line 1: @@
-====== How Do We Run Our First Sprint (or Iteration) Retrospective? ======
+====== How Do We Run Our First Iteration (Sprint) Retrospective? ======
 ====== 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 "inspect and adapt" cycle for the process and people). This information can help the Team determine how to improve performance in the next Sprint / Iteration. Typically, the Retrospective is held after the Review / Demo.
+At the end of a sprint, the Team holds a Iteration (Sprint) Retrospective to review their work process and the way the Team worked together (the "inspect and adapt" cycle for the process and people). This information can help the Team determine how to improve performance in the next Sprint / Iteration. Typically, the Retrospective is held after the Review / Demo.
 ====== Background ======
@@ 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, and helps with team dynamics by having the team work complex issues. You will want to have a very good reason for not doing a Retrospective meeting before deciding on some other approach. And, if you don't do this through a meeting, you will need to ensure that you take the time to focus on continuous improvement and that the equivalent results are part of your team documentation.
-For distributed Teams, there is always an issue of "communication" and so you may want to consider this subject as a standard subject for every Retrospective the Team has or, in some cases, establish a single subject Retrospective to address a specific issue. Many people make the mistake of treating "communication" as a tool issue. In reality it is often an issue of working agreements a Team has (see [[blog:how_can_we_work_more_effectively_with_remote_people|How Can We Work More Effectively with Remote People?]] for more information).
+For distributed Teams, there is always an issue of "communication" and so you may want to consider this subject as a standard subject for every Retrospective the Team has or, in some cases, establish a single subject Retrospective to address a specific issue. Many people make the mistake of treating "communication" as a tool issue. In reality it is often an issue of working agreements a Team has (see [[how_can_we_work_more_effectively_with_remote_people|How Can We Work More Effectively with Remote People?]] for more information).
 ===== "Running" Retrospective =====
@@ Line 188: / Line 188: @@
   * [[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.
+  * [[https://www.thevirtualagilecoach.co.uk/|Fun Retrospectives by the Virtual Agile Coach]]. Pretty much ready to be dropped into Mural or Miro.
 {{tag>Consultant Tools Team Retrospective Ceremony FirstSprint FAQ}}