post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Career

Buiding the Kimolian Academy: How Eleni Lialiamou is helping women break into product

Product Management

Sunday Rewind: Metrics don’t have all the answers: a human-centered approach to business strategy by Samihah Azim

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Why great product managers think like therapists

When your product is not THE product by Emily Tate at #mtpcon London 2025

Spotify invests in non-English audiobooks, new product chief at Trainline: This week’s news round-up

What AI can’t—and shouldn’t—do for product managers

How and when to sunset features – Roni Ben Aharon (CPO, Craft.io, Booking.com, Wix)

Ketaki Vaidya

<p><em>Software Teams generally follow the practice of Agile methodology to promote continuous iteration of development and testing throughout the software development lifecycle of the project.</em></p>
<p><em>After every iteration, these teams conduct a Retrospective meeting.</em></p>
<p><em>However, a Retrospective meeting can benefit any team, irrespective of whether you follow Agile or not.</em></p>
<p><em>This guest post by <a href="https://www.linkedin.com/in/ketaki-vaidya08/?originalSubdomain=in" target="_blank" rel="noopener"><span class="il">Ketaki</span> <span class="il">Vaidya</span></a> gives an overview of conducting retrospectives efficiently. This can also be applied to our personal lives.</em></p>
<hr />
<h2>What is a Retrospective?</h2>
<p>When we say <span style="font-style: italic;">retrospective,</span> here’s what we have in mind: a special meeting where the team gathers after completing an increment of work to inspect and adapt their methods and teamwork.</p>
<p>The goal is simple: Reflect on the previous work increment and come up with a plan to improve the next one.</p>
<p>The duration of a retrospective is around 30 mins-1 hour. Each team member is supposed to answer 3 questions:</p>
<ol>
<li>What went well?</li>
<li>What did not go well?</li>
<li>What can be improved?</li>
</ol>
<figure style="width: 830px" class="wp-caption alignnone"><img loading="lazy" decoding="async" src="https://www.mindtheproduct.com/wp-content/uploads/2022/12/4a0d1e6d-04d8-4bf5-9cf4-e5c0b25be575_Untitled.png" alt="A picture containing text Description automatically generated" width="830" height="438" /><figcaption class="wp-caption-text">Image credit: https://guide.quickscrum.com/</figcaption></figure>
<p>As the team reflects on the previous work increment with respect to these 3 questions, they discuss not only work-process-related issues (technical aspects of work) but also team-related issues.</p>
<p>The outcome of the Retrospective meeting: Meeting notes and Improvement action plan for the next work increment.</p>
<h2>Why should you have a Retrospective?</h2>
<p>Any team (usually with a size of up to 10 members), with interdependent work, need to focus on problems that affect their capability to contribute as a team. Only the team members should attend a retrospective. During retrospectives, teams discover real solutions that they can implement without waiting for management’s permission. Since experiments and changes are chosen, not imposed from above, people are more invested in their success.</p>
<p>Even if your team isn’t using Agile, having a retrospective after every project milestone can lead to substantial improvements in the productivity of the individuals and the team.</p>
<h2>Conducting a Retrospective:</h2>
<p>By now, you have understood what a retrospective is and why your team should have it. Let’s now look at the key to conducting an effective retrospective. We will split up the meeting into three sections:</p>
<p>Before, During, and After the Retrospective.</p>
<h3>Before the Retrospective:</h3>
<ol>
<li><span style="font-weight: bold; font-style: italic;">Working Agreement</span><span style="font-weight: bold;">:</span> Every team is different and there is a set of characteristics that work for one team which might not work for another. Consequently, it is important for every team to have a working agreement. If your team does not have one, schedule a separate meeting to jot down the working principles that all the team members agree to. The working agreement can then be adjusted or revisited based on the discussion during the retrospective (if required). For example, a simple agreement like “Mobile phones on silent during meetings” can go a long way in setting the stage for the meeting and helping everyone focus on its agenda.</li>
<li><span style="font-weight: bold; font-style: italic;">Gathering Relevant Data</span><span style="font-weight: bold;">:</span> It may seem silly to gather data for every work increment (or project milestone). But when someone misses even one day of work (due to any reason), they’ve essentially missed a significant share of the events and interactions. Even when people are present, they don’t see everything, and different people have different perspectives on the same event. Gathering data creates a shared picture of what happened. Without a common picture, individuals tend to verify their own opinions and beliefs. The person who drives the Retrospective can collect the following data (or delegate it to someone) before the meeting:</li>
</ol>
<ul>
<li>Event-related Data: Meetings, decision points, changes in team membership, milestones, celebrations, adopting new tools, or work processes.</li>
<li>Metrics: Deliverables completed vs. Deliverables committed, Burndown charts (a visual measurement tool that shows the completed work per day against the projected rate of completion for the current project release), the velocity of the team</li>
<li>Other Artifacts: Team calendars, etc.</li>
</ul>
<h3>During the Retrospective:</h3>
<p>The person driving the retrospective can do a quick review of the above data with the entire team and ask the team to scan the data and comment on patterns, shifts, and surprises. Generating insights allows the team to step back, see the big picture, and delve into the root cause of various issues.</p>
<p>The nature of a retrospective demands meeting notes. One team member should be assigned to take notes and share them with the team after the meeting (The notes of each retrospective can be maintained in one place).</p>
<p>All team members should be given an opportunity to speak and voice their perspectives. There are always some team members who are more willing to voice their opinions and experiences than others. The person who drives the retrospective should prompt those who might not speak up easily. Ask the member about the deliverables that they were involved in and how they went. Help them think through each point and draw insights from it. Everyone’s experience helps shape the improvement action plan of the team. A successful retrospective empowers every team member, to be honest, and vocal about their experience of the previous work increment.</p>
<p>Three questions can be used to drive the retrospective session:</p>
<ol>
<li><span style="font-weight: bold;">What went well?</span><br />
Set the session off on a positive note by talking about the team’s successes during the last sprint. Celebrate accomplishments (and why they were successful), positive interactions, efficient techniques, etc. that you have experienced during the sprint. Ask why that specific event/process was successful, what about it is reproducible in similar future situations. It is imperative to note these for future reference so that you can make sure to continue doing the same thing going forward and replicate that success.</li>
<li><span style="font-weight: bold;">What didn’t go well?</span><br />
Next, start getting into the more difficult topic of what didn’t go so well. Most importantly, discuss why that event/process didn’t go well. Different team members might have different perspectives on the same event as to what in their mind was the cause of the issue. Collecting these different perspectives is a great way to really see a problem from as many angles as possible. The more “inconvenient truths” that the team can uncover together is a sign of the team’s strength and maturity. Team members should, of course, be respectful of one another and practice empathy while discussing what didn’t go well. Embrace a mindset of improvement, stay away from blame. At the same time, this is a good opportunity to take constructive criticism from team members. Don’t take feedback personally. It’s important to understand if something you’re doing is negatively affecting the team so that you can work towards correcting it, going forward. These points will feed into the next question about what can be improved?</li>
<li><span style="font-weight: bold;">What can be improved?</span><br />
Once the team has discussed the various aspects that they think did not go so well, it’s time to start thinking about how to make sure not to run into the same situation in the future. Brainstorm some steps the team can take (that are under their control) which can help mitigate the issues. These steps together constitute the improvement action plan. For instance, the team members might point out that only one person on the team knows how to integrate client data with the corporate database which overburdens that person. The action plan might be something like the team setting up a pairing schedule that enables other team members to learn about the database and can eliminate the bottleneck. The plan should be specific, and the team members should all be committed to enacting the plan going forward.</li>
</ol>
<p>After the above questions are answered, the person who is driving the retrospective can revisit the points of the last retrospective and track whether they were resolved in the improvement action plan of the previous work increment. If some of the issues are still open, they should be prioritized and added to the current improvement action plan</p>
<h3>After the Retrospective:</h3>
<p>At this point, the team has a list of potential experiments and improvements. Now is the time to pick the top items (usually no more than one or two for an iteration) and plan what to do.</p>
<ul>
<li>Help your team choose items that they can commit to. If your team is recovering from a change that was stressful, help them choose something less complex this time. Holding your retrospective right before the planning of the next work increment (or project milestone) is ideal so that the action plan can be implemented in right away</li>
<li>Decide how to document the experience and plan for follow-up</li>
<li>Help your team decide how they’ll retain what they’ve learned from the retrospective</li>
<li>Adjust the working agreements of the Retrospective (if required)</li>
</ul>
<h2>Benefits of Retrospective:</h2>
<ol>
<li>Helps the team to inspect and adapt their methods and teamwork</li>
</ol>
<p>2. Retrospectives enable whole-team learning, act as catalysts for change, and generate action</p>
<p>3. Increasing empowerment and enjoyment for teams</p>
<p>4. Increased team productivity</p>
<h2>Your Personal Retrospective:</h2>
<p>Usually, Procrastination is the thief of our time. We often want to do a lot, but “can never find the time”. Define a personal task increment for yourself. This can be a day, a week, or 2 weeks (whatever suits you). Take 5 minutes at the end of every increment. Lock yourself in a room and reflect on what you did well and need to continue (You need to focus only on yourself when you do it). Make a note of what did not go well and could have been improved. It is implicit that these points need to be documented. The improvement action plan of your retrospective can translate to your to-do list for the next task increment.</p>
<p>For instance, I do my personal retrospective every day and jot down my improvement action plan in Google Keep. The practice of daily retrospectives helps me prioritize and track my personal goals. Somedays, there is a lot to do. In such a scenario, it is crucial to pick the most important thing and do only that. There might be days when you take a break and don’t want to do anything. That is totally fine. In the end, it is important that we are consistent in this practice so that we are aware of what we want in our life. A few days here and there don’t make a difference. What creates an impact is the will to constantly reflect and improve.</p>
<h3>There&#8217;s more where that came from! Access more insights below</h3>
<ul>
<li><a href="https://www.amazon.in/gp/product/B00B03SRJW/ref=as_li_tl?ie=UTF8&amp;camp=3638&amp;creative=24630&amp;creativeASIN=B00B03SRJW&amp;linkCode=as2&amp;tag=ketakiv-21&amp;linkId=b56df33ee3594fab6652eca2981f1d54" target="_blank" rel="noopener">Agile Retrospectives by Esther Derby, Diana Larsen</a><span style="text-decoration: underline;"><a href="https://amzn.to/3tL5Siv"><br />
</a></span></li>
<li><a href="https://guide.quickscrum.com/scrum-retrospective-meeting/" target="_blank" rel="noopener">About Retrospective meetings</a></li>
<li><a href="https://www.mindtheproduct.com/three-hidden-problems-that-can-ruin-your-agile-retrospectives/" target="_blank" rel="noopener">Three Hidden Problems That can Ruin Your Agile Retrospectives<br />
</a></li>
</ul>
<div></div>

Running your retrospective meetings, the right way

Ketaki Vaidya

Read more

Comments