Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches
Episode: Six Thinking Hats, An Agile Retrospective for Balanced Discussions | Mike Bowler
Host: Vasco Duarte
Release Date: November 14, 2024
Introduction
In this insightful episode, host Vasco Duarte, a seasoned Agile Coach and Certified Scrum Master, engages in a deep conversation with Mike Bowler, an experienced Scrum Master and Agile Coach. The discussion centers around effective retrospective formats, defining success within Scrum roles, and leveraging data to drive team improvement. This episode offers practical advice and real-world examples aimed at enhancing the craft of Scrum Masters worldwide.
1. Mike Bowler's Favorite Retrospective Formats
Mike delves into two of his preferred retrospective techniques: LEGO Serious Play and Six Thinking Hats.
a. LEGO Serious Play
Mike, a trained LEGO Serious Play facilitator, highlights the transformative power of this hands-on technique:
"In one case ... we filled two huge whiteboards ... People had things they wanted to say, but for reasons they weren't saying them. As soon as we got things into a playful approach using the LEGO board bricks, we were able to get everybody just talking about all of those things."
[02:00]
Key Insights:
- Engagement Through Playfulness: LEGO Serious Play breaks down communication barriers, encouraging even the most reserved team members to share their thoughts.
- Deep Unconscious Interaction: The tactile nature of LEGO bricks facilitates subconscious expression, leading to richer discussions and insights.
b. Six Thinking Hats
Inspired by Edward de Bono’s method, Six Thinking Hats provides a structured approach to managing complex or conflict-laden retrospectives:
"The six Thinking hats is also great ... Because we do that, it pulls all of the deep emotion out of it and we're able to look at things logically and rationally."
[04:35]
Key Insights:
- Structured Dialogue: By segregating discussions into different thinking modes (data, emotions, alternatives), teams can navigate conflicts more effectively.
- Emotional Management: This technique helps in reducing negative emotions, fostering a respectful and productive conversation environment.
2. Dealing with Skeptics in Playful Formats
Vasco raises a pertinent concern about team members who may not take playful retrospective formats seriously. Mike counters this by emphasizing the scientific underpinnings of these techniques:
"I want you to learn more effectively, because I want you to be thinking at your most creative."
[05:00]
Strategies Discussed:
- Educational Approach: Introducing neuroscience and psychology to explain the benefits of playful methods.
- Dopamine Release for Learning: Highlighting how novelty, humor, and creativity trigger dopamine, enhancing memory and learning.
- Building Trust: Demonstrating the intentionality behind playful formats to gain team buy-in.
Mike observes that skeptics often become the most engaged participants once they decide to give the methods a try:
"My own experience is that some of the most skeptics are those that enjoy it the most because they actually decide to give it a try."
[05:22]
3. Defining Success for Scrum Masters
At the core of Mike's philosophy is the principle that the team's success inherently defines the Scrum Master's success:
"If the team is successful, the Scrum Master is successful."
[06:22]
Key Metrics for Success:
- Effectiveness: Measuring whether the team is delivering meaningful outcomes versus merely staying busy.
- Continuous Improvement: Ensuring the team shows measurable improvement over time in their processes and outputs.
Mike emphasizes that the Scrum Master acts as a catalyst, fostering an environment where the team can thrive and evolve continuously.
4. Accountability Through Metrics and Data
To maintain accountability and objectively assess team performance, Mike leverages both qualitative and quantitative data:
"The data actually tells us a story ... It could be an experience talking to a customer. Yes, I'm much happier today than I was last month."
[07:36]
Approaches to Data Utilization:
- Ticketing Systems: Extracting data from tools like Jira to identify delivery patterns and bottlenecks.
- DORA Metrics: Utilizing DevOps Research and Assessment metrics to gauge performance.
- Customer Feedback: Incorporating qualitative insights to complement quantitative data.
Mike underscores the necessity of data in validating progress and identifying areas for improvement:
"If we don't have some kind of data, then it's impossible to say whether we're better or worse."
[08:51]
5. Real-Life Examples and Insights
Mike shares practical examples that illustrate the profound impact of data-driven coaching:
a. Identifying Delivery Patterns
By analyzing delivery data, Mike helps teams recognize and address recurring issues rather than attributing them to isolated incidents. This pattern recognition is crucial for sustainable improvement.
b. Enhancing Control Over Workflow
Mike recounts a scenario where a team’s workflow was hindered by dependencies outside their control. By presenting data on their lack of control and encouraging proactive measures, the team shifted to a more autonomous and effective workflow:
"I said, hey, I'm noticing the last time I was in, everything was out of your control and today everything's in your control. What's different?"
[13:01]
Outcome:
- Proactive Behavior: The team began chasing dependencies and making proactive efforts to take ownership.
- Improved Control: This led to a transformation from having little control over their work to managing their workflow effectively.
Conclusion
This episode offers a comprehensive exploration of advanced retrospective techniques and the pivotal role of data in Scrum Mastery. Mike Bowler’s experiences and methodologies provide valuable lessons for Scrum Masters aiming to enhance team dynamics, foster continuous improvement, and achieve measurable success. By integrating playful yet scientifically-backed techniques and emphasizing data-driven accountability, Scrum Masters can significantly elevate their coaching effectiveness and drive their teams toward sustained excellence.
Upcoming Episode Teaser:
Part of a successful Scrum Master’s role is to assist the Product Owner. In the next episode, we'll delve into the critical responsibilities of the Product Owner in Scrum, exploring common anti-patterns, actionable support strategies, and real-life examples of exemplary Product Owners. Tune in tomorrow for our Friday Product Owner episode!
If you found this summary helpful, please rate the podcast on Stitcher or iTunes, and share it with fellow Scrum Masters to spread valuable Agile insights.