Embedded Files
Overview
Overview
Retrospectives are literally that - a reflection on the last few weeks of you working as a team. These are a great opportunity to talk about what’s going well, what could be improved on and any other general topics to discuss. Regardless of whether you do Scrum or Kanban, we’d highly recommend a regular Retrospective meeting for your team to adopt, adapt and improve and increase/improve delivery.
Introduction
Introduction
Retrospectives (Retros) are a place to learn from any challenges encountered since the last meeting and take action where possible to improve. The team should reflect and then decide what changes they want to make next. It’s a meeting that should be driven by the team and all actions agreed upon by those who attend, ensuring accountability is had by all.
Running Your First Retro
Running Your First Retro
The best place to start is to sit with your team and ask three key questions:
- What went well?
- What could have gone better?
- What else could we try to improve?
The key thing is to really challenge each other and dig into each point that gets raised to ensure you get to the root cause of the issue and create the right actions. In terms of format, there are loads of great tools out there which you can read about on our Retros We Love page which are suitable for all levels (whether you’re co-located or fully remote).
Our Self-Serving Retro is also a great place to start if you're new to facilitating them - it has lots of open questions and helps show the kinds of prompts an Agile Coach would use.
Retros are a great morale booster for teams; they are a celebration of a great achievement or a chance to blow off some steam and have a good chat about the challenges and frustrations the team have faced. Remember though, the main point is to make positive changes and improvements as a result of the conversations, so driving relevant and timely actions is vital to the success of these meetings and of teams as a whole.
Summary
Summary
Inspect. Adapt. Improve. Retrospectives are a really key part of the Agile process so regardless of whether you do Scrum, Kanban or just abide by the general principles, Retros are a great way to understand the challenges you’re facing as a team as well as celebrating successes.
Report abuse