The purpose of this meeting is to better reflect on your remote agile team’s last sprint cycle.
Sprints get their name for the simple fact that they are fast experiences, they go by in a blur. And just like a sprinter, it’s important to take your time and review your performance afterwards - instead of repeating flawed techniques cycle after cycle, your work is iterative in nature and so too should be its operations.
How should you retro your sprint?
It’s important to get your whole team’s candid feedback, and not just the limited POVs of management. This means you need to create a fun environment with a clear forum for the team to open up and be candid with their issues and advice. Make things comfortable, this should feel like a group reflection, not a review of all individual’s performance.
What should you retro?
You won’t be able to review everything that’s happened in two weeks in one meeting, so it’s key to create a structured meeting with strategic, planned out discussions. Typical topics to cover in a sprint are: demos of new deliverables, recognition of individual’s work, and collectively commenting and brainstorming on the team’s performance!
Why retro?
Just like sprinters, if you do not continually review and adjust your performance, you will almost definitely fall victim to inefficiency, unsustainability, or worse (fatal bugs, employee turnover..). It is best practice to make sprint retro’s a ritual for your team, at the end of each retro - showcase, celebrate, and improve your craft.