A Sh!tshow: The regrettably relatable retrospective.

To err is human, to learn, divine. Each and every one of us can think of a project that should have earned us a feature on our local firefighters calendar. But how are we meant to learn and grow if everything goes swimmingly? Luckily, one of the cornerstones of the Agile Manifesto gives us some guidance on learning from mistakes: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." While it's not quite a hot-girl-September, there are so many lessons from crash-and-burn projects that we can reflect on together and commit to improving on the things within our control. Forget the February spread, put your 20-20 hindsight goggles on and come along for a cathartic retrospective to reflect on working in difficult projects and what we can learn from our collective experiences: - What anti-patterns did we notice? - What fixes did we try? - How impactful were they? - Did we consider best practice vs best fit?