How To Conduct Effective Engineering Team Retrospectives

🚨 A Hard Truth: A Sprint Retrospective without action is like meal-prepping for your diet on Sunday and ordering fast food takeout all week. Too many Sprint Retrospectives turn into: ☠️ Complaint sessions with no action ☠️ Déjà vu conversations that repeat every Sprint ☠️ Endless brainstorming without narrowing down to one concrete action item ☠️ Pointing fingers instead of solving problems ☠️ A parking lot for every problem the organization will not solve ☠️ Meetings with sticky notes that vanish into the void ☠️ Feel-good chats that end in "we should…" but never "we will…" Here are some ideas to break the cycle: 💡Dot Vote → Cut through the noise to find the top priority 💡Start Small → One improvement per Sprint beats 10 forgotten ones. 💡Reserve Capacity → Plan time for improvements in Sprint Planning. 💡Make It Visible → Add an improvement idea to the Sprint Backlog. 💡Assign Ownership → Someone (or a small pair) drives the change. 💡Check Back → Inspect the outcome next Sprint Retrospective 💡Celebrate Wins → Highlight when a change sticks. Reinforcement makes continuous improvement contagious. 💡Rotate Facilitation → Let different team members lead the Sprint Retrospective so it does not feel like a Scrum Master’s ritual. 🔄 When the team feels overwhelmed by problems outside their control, try the Sphere of Influence, also known as Circles and Soup (from Diana Larsen and Esther Derby’s Agile Retrospectives): 1. Draw three concentric circles: inner = Control, middle = Influence, outer = Out of Our Control (often called Soup). 2. Sort sticky notes into each circle. 3. Focus on Control and Influence. Those are the changes the team can own. 4. Treat the Out of Our Control items as impediments the Scrum Master and leaders can work on as takeaways. This shifts the Sprint Retrospective from powerless venting to empowered problem-solving. 👉 Your Sprint Retrospective is not broken. Your follow-through is. ⚡ Improve, or stop wasting everyone’s time.

How do you run a retro that’s actually...good? We recently finished building a major new product (going live tomorrow 😉), and our design director ran one of the most effective retros I’ve ever seen. She used the Lean Coffee method (a meeting facilitation technique), and it was 𝘣𝘳𝘪𝘭𝘭𝘪𝘢𝘯𝘵𝘭𝘺 done 👌 Here’s how it worked (and why it worked so well): 📊 1. 𝐏𝐫𝐞-𝐫𝐞𝐭𝐫𝐨 𝐬𝐮𝐫𝐯𝐞𝐲: She sent out a survey asking how the project performed on key areas (e.g. alignment with company mission, clarity of product requirements, engineering execution, etc.). We rated each and explained our reasoning. 🧠 2. 𝐓𝐨𝐩𝐢𝐜 𝐧𝐨𝐦𝐢𝐧𝐚𝐭𝐢𝐨𝐧: In the second section of the survey, each person nominated up to 3 top-of-mind topics they felt were worth discussion. This ensured our biggest reflections and concerns were captured early. 🗳️ 3. 𝐕𝐨𝐭𝐢𝐧𝐠 𝐢𝐧 𝐅𝐢𝐠𝐉𝐚𝐦: She synthesized the survey feedback and dropped the topics into FigJam. We each got 3 votes to use however we wanted – all on one topic or spread across several (honor system 😛). 🗣️ 4. 𝐏𝐫𝐢𝐨𝐫𝐢𝐭𝐢𝐳𝐞𝐝 𝐝𝐢𝐬𝐜𝐮𝐬𝐬𝐢𝐨𝐧: She used FigJam to group topics by vote count (y'all this feature is so slept on...if you've never use it, I highly recommend trying!). We discussed each one for five minutes, starting with the highest-priority topics. 🙋🏻♀️ 5. 𝐒𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞𝐝 𝐩𝐚𝐫𝐭𝐢𝐜𝐢𝐩𝐚𝐭𝐢𝐨𝐧:  If you submitted a topic, you kicked off the convo. Anyone could chime in, as long as they raised their hand (either via Zoom or in-person). 🙌 6. 𝐃𝐞𝐦𝐨𝐜𝐫𝐚𝐭𝐢𝐜 𝐟𝐥𝐨𝐰: At the end of each 5-minute discussion, we voted: 👍 to keep going or 👎 to move on. Here's why this was so effective: • 𝐈𝐧𝐜𝐥𝐮𝐬𝐢𝐯𝐞 𝐨𝐟 𝐢𝐧𝐭𝐫𝐨𝐯𝐞𝐫𝐭𝐬 𝒂𝒏𝒅 𝐞𝐱𝐭𝐫𝐨𝐯𝐞𝐫𝐭𝐬: Introverts could contribute through surveys and voting, while extroverts still had space for real-time discussion. • 𝐈𝐧𝐜𝐥𝐮𝐬𝐢𝐯𝐞 𝐨𝐟 𝐭𝐨𝐩𝐢𝐜𝐬: We were able to remain democratic without devolving into pure chaos. Every voice mattered. Every topic got a fair shot. No one hijacked the hour. 👏 Huge shoutout to our design director for setting the gold standard for retro facilitation. This structure turned what could have been a chaotic debrief into a clear, inclusive, and energizing team moment. If you’ve ever been in a retro that spiraled into 30 minutes on one tangent...you’ll know how rare this is. What’s the best retro format 𝘺𝘰𝘶’𝘷𝘦 ever experienced?

How to fail in #agile interview Topic: Retrospective ---------------- How to Fail 😒 ---------------- 👸 Interviewer: "How do you typically run a sprint retrospective with your team?" 👨🦱 Candidate: "We usually ask what went well and what didn’t, then discuss how to improve." 👸 Interviewer: "That’s a basic format. But what if the team is disengaged, and you notice the same issues coming up in every retrospective?" 👨🦱 Candidate: "Well, I’d try to motivate them to speak up more." 👸 Interviewer: "Let’s get more specific. Suppose the team feels retrospectives aren’t useful and sees no real changes after their input. How would you handle this?" 👨🦱 Candidate: "I’d probably bring it up with the team during the next retrospective and see why they feel that way." 👸 Interviewer: "And if this lack of engagement affects continuous improvement, causing the same issues to repeat every sprint, what would you do?" 👨🦱 Candidate: "Maybe we’d focus on smaller changes to make things easier for them." ----------------- How to Pass 😊 ----------------- 👸 Interviewer: "How do you typically run a sprint retrospective with your team?" 👨🦱 Candidate: "I use different formats based on the team’s needs. Sometimes it’s ‘What went well, what didn’t,’ but I like to switch it up with activities like Start-Stop-Continue or using data-driven insights to stimulate discussions. My goal is to create an open, constructive environment where the team feels safe to discuss both successes and areas for growth." 👸 Interviewer: "What if the team is disengaged and the same issues keep surfacing?" 👨🦱 Candidate: "That signals we’re not addressing the root cause. I’d use techniques like the ‘5 Whys’ to drill deeper and focus on actionable items. If disengagement continues, I’d have one-on-one conversations to understand their concerns and re-energize retrospectives by varying the format or focusing on quick wins." 👸 Interviewer: "The team feels retrospectives aren't driving real change. How do you handle that?" 👨🦱 Candidate: "First, I’d check if we’re tracking action items and following up. If improvements aren’t visible, it’s often because we’re not holding ourselves accountable. I’d help the team create smaller, more tangible actions and make sure we review progress in the next sprint." 👸 Interviewer: "What if the same problems persist after implementing changes?" 👨🦱 Candidate: "If the issues persist, I’d revisit the changes and work with the team to measure their impact. Maybe the solution isn’t effective, or the problem was misunderstood. It’s also important to look at broader system-level challenges or external blockers and address those with the help of stakeholders." 💡 Key Takeaway: Effective #retrospectives require: ✍️ Engaging the team, ✍️ Addressing root causes, and ✍️ Ensuring actionable feedback drives change.

I'm often asked which ceremony I think is most important when running Agile. While all of the ceremonies play a key role in success of delivering outcomes, I feel that the retrospective is what makes the Agile team a team! NFL teams dedicate hours to reviewing game film after each game. This practice helps coaches and players break down their performance to identify strengths, weaknesses, and areas for improvement. Some key elements of NFL film analysis include: 1. Reviewing successful plays and strategies to reinforce positive behaviors. 2. Pinpointing errors in execution and decision-making. 3. Strategizing ways to counteract opponents and improve for the next game. Watching film allows players to visualize their actions and receive direct feedback from coaches, much like Agile retrospectives foster open discussions and learning. In Agile software development, the retrospective ceremony is a cornerstone of continuous improvement. It's a time for teams to reflect on what went well, what didn’t, and how they can improve. The main goals of a retrospective include: 1. Recognizing what went well and building on those strengths. 2. Acknowledging obstacles and areas that need improvement. 3. Collaborating on action items to enhance productivity. Teams often follow frameworks like Start-Stop-Continue or the Five Whys technique to dig deeper and create actionable takeaways. The similarities between Agile retrospectives and NFL film study demonstrate a universal truth: consistent reflection and adaptation are key to success, whether you're coding software or running plays. Here are a few ways these practices align: - Both require honest feedback, communication, and alignment on goals. - Just as developers own their contributions, players must take responsibility for their performance. - Success hinges on iterative progress—making small, consistent improvements over time. By following the below, we can have more effective Agile teams. 1. Be Honest and Open: Like NFL players facing their game tape, Agile teams should embrace transparency and feedback. 2. Focus on Actionable Change: Improvement is valuable only if followed by concrete steps. 3. Celebrate the Wins: Recognizing achievements helps maintain morale and reinforces good practices. Whether you're part of an Agile team delivering software or an NFL team chasing a championship, the retrospective process is crucial for growth and success. By embracing lessons learned and continuously striving for improvement, both Agile practitioners and athletes can achieve peak performance.

I ruined my first retrospective. By doing what I thought leadership meant. I walked in prepared. I had solutions. I knew exactly what the team needed to fix. The result? Silent nods, zero energy, and nothing changed after. Here's what I learned the hard way: Your job isn't to solve problems. Your job is to help the team solve their own. 𝗧𝗵𝗲 𝗳𝗮𝗰𝗶𝗹𝗶𝘁𝗮𝘁𝗼𝗿-𝗼𝗻𝗹𝘆 𝗿𝘂𝗹𝗲 that changed everything: 𝗚𝗮𝘁𝗵𝗲𝗿 𝘁𝗵𝗲 𝗱𝗮𝘁𝗮 → Pull sprint metrics before the meeting → Review completed/incomplete stories → Note any blockers or incidents 𝗣𝗿𝗲𝘀𝗲𝗻𝘁 𝗶𝘁 𝗼𝗯𝗷𝗲𝗰𝘁𝗶𝘃𝗲𝗹𝘆 → Show numbers, not opinions → "We completed 18 of 25 stories" not "We underperformed" → Let the team interpret what they see 𝗔𝘀𝗸, 𝗱𝗼𝗻'𝘁 𝘁𝗲𝗹𝗹 → "What patterns do you notice?" → "What's one thing we could try differently?" → Let awkward silence happen—they'll fill it 𝗦𝘁𝗲𝗽 𝗯𝗮𝗰𝗸 𝗳𝗿𝗼𝗺 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀 → Guide the discussion, don't dominate it → The team owns both problems and fixes → Your role: capture actions and owners The trap new PMs fall into: We think leadership means having all the answers. We force solutions. We rush discussions. We take responsibility that belongs to the team. Result? They tune out. They don't implement. They wait for you to fix things. When teams find their own solutions, They actually execute them. One approach gives you a checkbox retro. The other gives you actual change. 🧡 New to PM? Follow for practical leadership tips. ♻️ Repost to empower your network.

"Lessons learned" meetings: why they’re like 'new year’s resolutions' (and how to fix them)   We’ve all been to that project retrospective:   The one where someone earnestly suggests "better communication" (for the 9th time)   Where the pm writes down "document processes" in the exact same doc that will never be opened again   Where everyone leaves feeling vaguely productive…but nothing actually changes   Let’s be honest: most lessons learned sessions are like gym memberships in january , full of good intentions but doomed by february.   Why our good intentions fail   The idea is noble:   ✅ reflect on what worked ✅ improve for next time ✅ become better professionals   The reality is:   -we identify the same 3 generic "improvements" every time -no one gets assigned actual ownership -the only thing we learn is that we're great at repeating lessons   A smarter (and actually fun) approach   Instead of another forgettable meeting, try this:   1. The "one regret" lightning round "if you could undo one decision from this project, what would it be , and what espresso drink would you buy the team as apology?"   (pro tip: the caffeine bribe makes people surprisingly honest)   2. The "fix it or ticket" rule Every identified issue gets either: -A named owner who fixes it now -A ticket with a deadline   A ceremonial burning of the complaint (kidding...mostly)   3. The "before/after" bet Have each team member predict: -"which 'lesson' will we pretend to care about next project?" Vs "which one will we actually implement?" (winner gets to choose the next meeting snack)   Why this actually works The humor disarms defensiveness Specific bets create accountability The snack stakes ensure follow-through (never underestimate engineers and free food)   🍿 hot take: if your lessons learned doc has survived more than 2 projects without causing actual change, it belongs in a museum of good intentions.   What's your favorite retro hack? Share your best (or most hilariously failed) lessons learned story below! 👇 #projectmanagement  

Today’s Joy Notes is focused on the power of THE DEBRIEF. As a child my mother would always tell me that it was essential to examine your wins and losses equally, in order to be able to understand your strengths and weaknesses. I became a believer of the power of the debrief. Whether you win or lose, one of the most powerful tools for sustaining momentum and building a culture of continuous improvement is the debrief. It’s not just for failure recovery, it’s a celebration of learning. By making the debrief a standard post-project ritual, teams strengthen alignment, accountability, and agility. The process hinges on three foundational questions: What worked? What didn’t? What’s next? Here’s your guide to an effective debrief: 1. Create a Safe Space – Encourage honest reflection. Make it clear this isn’t about blame: it’s about building better. 2. Start with Wins – Celebrate what went well. Highlight individual and team contributions to reinforce positive behaviors. 3. Address Challenges Openly – Analyze what didn’t work without defensiveness. Focus on systems, gaps, and decision-making: not personalities. 4. Invite Every Voice – Ensure all roles are heard. Diverse insights often reveal hidden patterns or overlooked wins. 5. Extract Lessons – Identify transferable knowledge that can be applied to future projects. 6. Action the Insights – Don’t let insights die in a document. Assign ownership to changes, and integrate improvements into future workflows. 7. Document & Share – Capture the outcomes in a concise, shareable format to build institutional memory. Debriefs turn moments into momentum. When you regularly pause to reflect, you don’t just improve projects—you develop people, processes, and culture. In a world that moves fast, reflection is your competitive edge. #TheDebrief #Awareness #ActionableSteps #Accountability #Acknowledgement #Dotherightthing #Document #Reflections #Learn #JoyNotes Today’s Playlist “Lessons Learned” – Alicia Keys “After the Storm” – Kali Uchis ft. Tyler, The Creator & Bootsy Collin’s “Learn from the Mistakes” – Slick Rick “Back to the Drawing Board” – EPMD “Fix You” – Coldplay

The Liberating Structure “What, So What, Now What” breaks experiences down into three steps: 1️⃣ “What do we notice?” 2️⃣ “So, what does this mean?” 3️⃣ “Now, where do we go from here?”. It takes inspiration from the Ladder of Inference by Chris Argyris, an expert on learning in organizations, and it offers a perfect structure for Sprint Retrospectives. By doing this with others, you are encouraged to discover the gaps in your understanding by learning from their perspectives. Being a relatively simple structure, you can quickly adapt it to suit the situation's needs. And the more you do it, the more natural this structured approach to sense-making becomes. ## Round 1 Invite your team to consider what they noticed and/or what facts or observations stood out in the previous Sprint. ❌ “We didn’t finish three backlog items” ❌ “Item X got stuck for almost the entire Sprint because we needed to wait for another team.” ❌ “We managed to release only twice, although we agreed to do it daily.” ✅ “Our most important stakeholders validated an important item during the Sprint” ✅ “Our Sprint Review was visited by all our stakeholders!” ## Round 2 Invite your team to reflect on the observations individually. Why are those observations important? What patterns do you see? What conclusions can we draw? 🤔 “We seem to have too many dependencies on other teams.” 🤔 “Somehow, we aren’t able to release daily.” 🤔 “Our collaboration with stakeholders is going smoothly.” ## Round 3 Invite people to reflect on the previous round individually. Based on the conclusions, what are the next steps that make sense? What should we invest in as a team based on what we know now? 📌 “Let’s map all our dependencies to find bottlenecks and identify at least one improvement to remove it.” 📌 “ Let’s visit a team that has automated something we haven’t yet, and let’s take one idea from them that we will implement next Sprint as well.” 📌 “Let’s share our good experiences with our stakeholders, with team XYZ, because they seem to struggle with their stakeholders.” Collect the key ideas in a shared workspace, turn them into concrete improvements, and realize them in the next Sprint. Optionally, use “What, So What, Now What” again during the next Sprint Retrospective. Repetition is also a form of learning.

Leaders don’t build strong teams by accident. They build systems that support feedback, safety, and accountability. Retrospectives are one of those systems. They’re short, structured meetings where teams reflect on how they worked—so they can work better next time. When done well, retrospectives build: ↳ Psychological Safety – People feel safe to speak up ↳ Organizational Learning – Teams retain and apply lessons ↳ Engagement & Ownership – Promotes accountability and shared success Start with a simple structure. Keep your retrospectives predictable to invite engagement. Use this 4-question agenda: ↳ What went well? ↳ What didn’t go well? ↳ What do we need to change or keep doing? ↳ What actions do we need to take? Once your foundation is in place, here are four best practices to make your retrospectives more effective: ✅ Best Practice #1 – Create Psychological Safety ↳ Open with intent: “We’re here to learn. This is a safe space and there’s no judgment.” ↳ Thank people for their input—even if you disagree ↳ Make it a closed meeting with only the execution team ↳ Use sticky notes or digital whiteboards to gather input ↳ Timebox each agenda item ↳ Ask: “Is there anything here we should explore further?” ✅ Best Practice #2 – Ask Great Questions Great retros are driven by great questions. Use open-ended prompts like: ↳ “Can you share an example?” ↳ “What made that challenging?” ↳ “What is the action?” ↳ Avoid yes/no questions—explore context and nuance. ✅ Best Practice #3 – The Leader’s Role in a Retrospective Leaders set the tone—intentionally or not. ↳ Use active listening ↳ Hold back opinions until others share ↳ Thank input, don’t evaluate it ↳ Coach leaders ahead of time: “You’ll be prompted to respond at the end.” ↳ Encourage reflection, not resolution ✅ Best Practice #4 – Commit to Action ↳ Choose one improvement to implement next sprint ↳ Assign ownership and next steps ↳ Report back: “Here’s what we changed because of your feedback.” Retrospectives build trust, encourage ongoing feedback, and enable small, consistent improvements over time. When teams learn consistently, they grow consistently. Do you do retrospectives in your team and how have they helped you? ♻️ Repost to help more teams make reflection part of their rhythm. ➕ Follow Morgan Davis, PMP, PROSCI, MBA for frameworks that drive operational excellence.