Retrospectives – between making and breaking teams
<yellow>Introduction</yellow>
In Agile, retrospectives are an essential element that creates cohesion and promotes team collaboration. This is a space solely meant for the members of the team, and for them alone – no project pressure, no judgment, no pointing fingers. The theory is clear and aims to create an environment where issues and ideas are discussed and dissected freely, so that every participant can ultimately identify their proverbial ‘comfort zone’ within the team’s ecosystem.
All of this sounds great and leaves little room for error; however, in practice, a retrospective meeting requires work from all sides to make the team feel like a cohesive unit. Nothing will come easy or even naturally, and it is important for the moderator of the meeting to encourage active participation, mediate discussions, and ensure that previously established rules are respected.
Having experienced both sides of the coin and participating in multiple variations of retrospectives, I managed to compile a series of patterns that, when paired with tough discussions, can only lead to dissent and discord:
<yellow>Obstacles</yellow>
These behaviors are just a few examples of the most common blockers that stunt growth and can seriously affect collaboration and, indirectly, project delivery.
So, what is to be done in order to overcome the obstacles that threaten to break the equilibrium of the team? Below are some useful tactics that can be employed to deal with the concerns above and can support a healthy work environment overall:
<yellow>Solutions</yellow>