At regular intervals, the team reflects on how to become more effective, then tunes & adjusts its behaviour accordingly – Agile Manifesto
We all know that at the end of each iteration, we gather and discuss on the agile retrospectives; come up with one retrospective which is worth sharing and implementing, discuss tricks and practices and experiment ways to improve. During Ekipa’s retrospective sessions, we share ideas to experiment, repeat those working well, analyse the less performing ones and neglect those aren’t.
Iteration retrospectives are crucial for the success of software teams. In the agile retrospective meetings at the end of the project or process, teams will be reflecting on both quantitative and qualitative actions. Quantitative aspects are the metrics team uses to review the performance and the qualitative part focusses on the challenges during the iterations and practices to move forward.
Sometimes, too many retrospectives might lead to ineffective meetings and the reasons are;
- lack of understanding
- No focus
- Poor participation & insights
- Inconsistent follow-up
Yes, it’s very hard to get the right retrospective! David Horowitz, the CEO and Co-Founder of Retrium, gathered 21 hand-picked agile experts to share their tips to become a retrospective rockstar. It is now released as a wonderful ebook. Source: Retrium
Our CEO, Hugo Messer is honored to be listed as one of the experts in this ebook. These are contributors of the ebook;
21 Experts Of The Retrium Ebook
The compilation of these ideas straight from the horse’s mouth into this ebook can be the perfect guide to many software teams. Take time to go through each expert tip and leverage it to accelerate your iteration process. Remember, it’s good to experiment with one tip first and see how well you can drive your process.
Read Next >> Join Me Virtually For The Mobile World Congress?