The origin of my Retrospectives Antipatterns book

Overview
The article recounts the process behind creating the "Retrospectives Antipatterns" book. The author explains the motivation, research, writing challenges, and the key insights gained while documenting common pitfalls in agile retrospectives.

Key Takeaways

• Identify common antipatterns early to prevent wasted effort.
• Structure retrospectives with clear goals and actionable outcomes.
• Embrace iteration not only in software but also in the way you improve team processes.
• Learn from personal mistakes to produce a more useful guide for others.

Who Would Benefit

• Engineering managers looking to improve team retrospectives.
• Agile coaches and Scrum Masters seeking practical examples of pitfalls.
• Technical leaders interested in fostering a culture of continuous improvement.
• Anyone planning to write a technical book or guide.

Frameworks and Methodologies

• Agile retrospectives
• Continuous improvement (Kaizen)
• Lean thinking
• Technical writing best practices