Retrospectives Antipatterns
Fleeting- External reference: https://martinfowler.com/articles/retrospective-antipatterns.html
Retrospectives Antipatterns
how easily a retrospective can be inefficient. If you don’t follow the idea of a retrospective and only go through the motions, you will waste time.
— https://martinfowler.com/articles/retrospective-antipatterns.html
5 stages of a retrospective
Setting the Stage Intro, theme, follow up on previous action points
Gather Data Collect data about how the team is working together
Generate Insights Find the causes behind the issues, understand and learn
Decide what to do Find a few action points or experiments to try in the near future
Close the Retrospective Make sure there is a concrete plan for the action points, outro
— https://martinfowler.com/articles/retrospective-antipatterns.html
refactored solution is to use an activity called In the Soup, where you ask the team to divide the things they are discussing into things they can do something about, things they can influence, and things that are in the soup.
— https://martinfowler.com/articles/retrospective-antipatterns.html
When things are in the soup, they are a part of life that you cannot change. Your time is better spent accepting and finding a way to adapt to the situation. Or changing your situation by removing yourself from the soup
— https://martinfowler.com/articles/retrospective-antipatterns.html