How to run an effective retrospective

How to run an effective retrospective

Really nice article about effective retrospectives: https://www.notonlycode.org/effective-retrospective/

The accompanying YouTube video also adds more insight: https://youtu.be/ZbAIkWCfBuc

He focuses on the point of retros: Without improvement, the retrospective is a waste of time.

• keep it simple
  • what went well, what to improve
• implement improvements
• start with problems
• clarify
• then discuss solutions
  • this is why starting with “keep doing/stop doing” is bad because it jumps to solutions

Follow the links - his other articles and videos look equally interesting.