Lean-Agile
Coaching and Training
Other
-
- Also some Useful Tools
Note that we have some Incomplete Pages That Require Work on this site:-)
Note that we have some Incomplete Pages That Require Work on this site:-)
When you get started, Retrospectives seem like a great idea. Many organizations use the basic “what went well, what didn’t go well, what ideas do we have” but, let’s face it, this is not a great format for a retrospective and so it is not surprising that it doesn’t produce results. As time goes on questions arise as to why we should bother with Retrospectives at all. After all, nothing really changes …
In many organizations:
“Inertia is our enemy” - Claudio Perrone (developer of POPCORN flow)
In my experience there are some simple do’s and don’ts that Scrum Masters can use to improve Retrospectives:
“Improving daily work is more important than doing daily work” - Gene Kim, The Phoenix Project
“If I had an hour to solve a problem I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.” - Albert Einstein
“Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.” - Norm Kerth
A couple of additional ideas for distributed Teams: