Cultivating the Positive Effects of Agile Retrospectives
19 December, 2018
An agile retrospective is a meeting held at the end of an iteration or at a scheduled interval. In a retrospective, team members get a chance to voice their opinions on things that worked well and items that need improvement. Participants write their concerns and praises on post-it notes that are stuck to opposite ends of a wall. We read and review each topic one by one, take notes, and create action items on things that deserve more attention. Action items are assigned as stories and chores and sent out to all participants. Sounds good, but how do you ensure its proper implementation?
- Make sure all team members understand the purpose of the retrospective.
- Review previous retrospectives action items quickly before you begin, if you have any.
- Keep participants focused and any one individual from hogging the mic or going on lengthy tangents.
- Keep the meeting to one hour max.
- Have a moderator and a separate note-taker. We rotate these responsibilities at Doximity amongst team members.
- Include remote participants and make sure they have local representation for posting post-its on the whiteboard.
- Walk away with clear action items and assign them as stories and chores.
- Send out retrospective notes to all participants as soon as possible. We began with a team-wide retrospective that included the entire engineering team, QA team, and a few of the product managers. We now have team-wide retrospectives every two months rather than every six. Sub-teams within the engineering department also have smaller retrospectives slightly more often. They use these to discuss items pertaining more closely to their specific work and focus.
- I would certainly recommend you follow all Agile principles when first adopting the methodology. This will help you learn what works best for you.
- As we focus on improving based on constructive feedback, negative items are soon replaced by positive feedback and praise.
- It has led us to a place where everyone is happy with the process, and the outcome has been nothing but positive.
Deepak Paramanand, Product Lead at Hitachi, explains how his early efforts in stand-up comedy and experience of interaction between a performer and audience helped him better understand his colleagues and customers.
Product Lead at Hitachi
Peter Berg, Founder and CTO at Forward, recounts how he introduced processes for continuous improvement and thus creating a more psychologically safe working environment.
Founder / CTO at Forward
Peter Berg, Founder and CTO at Forward, describes how he helped ramp up a slow-moving team by applying his simple, yet expert approach.
Founder / CTO at Forward
Caroline Parnell, previously managed product teams at O2 and Vodafone, shares some of the techniques she applied with her team to ensure diversity of thinking during product discovery workshops.
Most recently Head of New Product Innovation at Previously O2 and Vodafone
Justin Potts, VP of Engineering at MoneyLion, tackles the ever-intriguing problem of simplifying the architecture and thus reducing the overall complexity of the systems.
Head of Engineering at MoneyLion
You're a great engineer.
Become a great engineering leader.
Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.