The Complaining Retrospective
What is it?
The Sprint Retrospective becomes a recurring session of complaints and laments where problems are identified but no concrete, achievable, and trackable improvement actions are generated.
Common symptoms (how does it manifest?)
- The same complaints appear Retrospective after Retrospective.
- The team identifies problems but does not define concrete actions to address them.
- Defined actions are vague or unachievable.
- The team shows apathy or cynicism towards the Retrospective.
Impact and consequences (why is it a problem?)
- The key opportunity for continuous improvement of the team and process is lost.
- Underlying problems persist and worsen.
- Team burnout and frustration.
- The Retrospective becomes a useless event.
Frequent root causes (why does it happen?)
- Lack of an effective facilitator to guide the conversation towards solutions.
- Fear of pointing out real problems or proposing significant changes.
- Feeling of powerlessness ("nothing will change anyway").
- Not dedicating enough time to the "Decide what to do" phase.