Contracting for Success, Establishing Clear Agile Coaching Outcomes | Richard

Thu Apr 17 2025

Richard Brenner: Contracting for Success, Establishing Clear Agile Coaching Outcomes Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: . ...

Summary

Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches

Episode: Contracting for Success, Establishing Clear Agile Coaching Outcomes
Host: Vasco Duarte
Guest: Richard Brenner
Release Date: April 17, 2025

Introduction

In this insightful episode of the Scrum Master Toolbox Podcast, host Vasco Duarte engages in a profound conversation with Agile Coach Richard Brenner. The discussion centers around establishing clear outcomes in Agile coaching and defining success metrics that resonate with both teams and management. Skipping the promotional segments, the episode delves deep into practical strategies and philosophical shifts necessary for effective Agile coaching.

Favorite Agile Retrospective Format: Solution Focused Retrospective

Richard Brenner begins by sharing his preferred format for Agile retrospectives, drawing inspiration from his favorite book, Solution Focused Coaching of Agile Teams. He explains:

“The Solution Focused Retrospective is powerful because it shifts the focus from dissecting problems to modeling the desired future state” (01:25).

Unlike traditional retrospectives that often delve into root causes of issues, the Solution Focused approach encourages teams to envision what they want to achieve. Richard emphasizes the positive impact of this method:

“Instead of opening up about problems and potentially fostering finger-pointing, we concentrate on what we want to create moving forward” (02:15).

This approach not only fosters a more constructive environment but also helps teams generate actionable steps towards their goals without getting bogged down by past obstacles.

Handling Conflicts with a Solution Focused Approach

Building on the Solution Focused mindset, Vasco and Richard discuss conflict resolution within Agile teams. Richard advocates for understanding conflicts from multiple perspectives and collaboratively designing a future state that accommodates diverse viewpoints. He notes:

“By focusing on actions and future states, we can navigate conflicts that might otherwise seem unsolvable” (04:40).

This method contrasts with traditional root cause analysis, which assumes that identifying and addressing the underlying cause will resolve the conflict. Richard points out that especially in interpersonal conflicts, creating a new approach can be more effective than merely solving the problem.

Defining Success as an Agile Coach

Transitioning to the core theme of the episode, Richard Brenner reflects on his evolving understanding of success in Agile coaching. Initially, Richard equated his success with the success of the teams he coached. However, he realized the necessity of broader metrics:

“If my team is successful, then I'm successful” was my initial thought, but it wasn’t comprehensive enough (05:21).

Richard explains the importance of establishing tangible Key Performance Indicators (KPIs) through a coaching agreement with both management and teams. These KPIs often encompass:

Flow Metrics: Measuring the speed and efficiency of work.
Outcome Metrics: Assessing the quality of products and feedback loops.

He elaborates:

“By defining these metrics with the teams and management, we create a clear and measurable path to success” (06:40).

This structured approach ensures that success is not only team-centric but also aligned with the organization's broader objectives.

Contracting and Mutual Accountability

A significant portion of the discussion focuses on the necessity of contracting—establishing agreements that define how success will be measured and who is accountable. Richard advocates for a two-sided accountability model:

“Management is accountable for the change process, and I am accountable for supporting that change” (10:28).

Vasco highlights the importance of this mutual accountability, stating:

“It's not just accountability for us; it's also accountability for them” (09:34).

This ensures that all stakeholders are engaged in defining what success looks like and are responsible for their roles in achieving it. Richard reinforces the idea that ongoing conversations are crucial to maintain alignment and adjust goals as necessary:

“Ongoing conversations help us stay on track and ensure that everyone remains committed to the defined goals” (11:52).

Conclusion

The episode concludes with an emphasis on the dynamic and conversational nature of defining success in Agile coaching. Richard Brenner underscores that success metrics should evolve through continuous dialogue and collaboration between coaches, teams, and management. This approach not only fosters a sense of ownership among all parties but also ensures that the Agile transformation remains aligned with the organization's needs and aspirations.

Key Takeaways

Solution Focused Retrospective: A positive approach that emphasizes desired future states over problem analysis.
Defining Success: Move beyond team success to include tangible KPIs agreed upon with management and teams.
Contracting: Establish mutual accountability through clear coaching agreements.
Continuous Dialogue: Maintain ongoing conversations to adapt and stay aligned with goals.

Notable Quotes

Richard Brenner:
“The Solution Focused Retrospective is powerful because it shifts the focus from dissecting problems to modeling the desired future state.” (01:25)
“If my team is successful, then I'm successful” was my initial thought, but it wasn’t comprehensive enough.” (05:21)
“Management is accountable for the change process, and I am accountable for supporting that change.” (10:28)
Vasco Duarte:
“It's not just accountability for us; it's also accountability for them.” (09:34)

This episode serves as a valuable resource for Scrum Masters and Agile Coaches seeking to refine their approach to coaching, establish clear success metrics, and foster a collaborative environment that promotes continuous improvement and accountability.

Transcript

Vasco (0:06)

Have you ever wondered what it really.

Unknown Host (0:08)

Takes to make Agile work well? At the Global Agile Summit, we're bringing you real life first person stories of Agile succeeding out there in the real world that will inspire you to take action. Whether you're a leader, a product innovator, a developer, you'll hear practical insights from those who've done it. They'll be telling their own stories from the stage. I'll tell you more about this at the end of this episode. So stay back and listen to the full detailed description of what we have in store for you at the Global Agile Summit. But if you can't wait, you can go right now to globalagilesummit.com and check out our full schedule for now onto the episode. But I'll see you at the end of this episode with more details on the Global Agile Summit. Talk to you soon.

Vasco (1:03)

Hello everybody.

Unknown Host (1:04)

Welcome to our Success Thursday. The big question of the week this.

Vasco (1:08)

Week with Richard Brenner. Hey Richard, welcome back.

Richard Brenner (1:12)

Hi Vasco.

Vasco (1:14)

So Richard, Thursday is success day, but we always start with what is your favorite Agile retrospective format and why?

Richard Brenner (1:25)

Yeah, coming from my favorite book that I mentioned, the Solution Focused Coaching of Agile Teams is also my favorite retrospective format, which is called Solution Focused Retrospective. And I like it because what I learned in the classical retrospective is like this set the stage, gather data, derive insights, generate actions, and so on is that you usually open up a topic and then you dig deeper into the root cause of the problem. And this format changed the perspective of my retros completely because I said, look, don't dive into the problem space too much because you open bad things and you talk about bad things and you might end up with finger pointing someone and so on. So stop this and try to model your desired future state, which is I think far more powerful to say, okay, don't talk about the too much about of course don't avoid talking about problems, but let's not try to dive deeper into why do we have this problem. But let's think about what do we would what would you like to have? And then if you model that desired future state, you think about, okay, from a scale from 1 to 10, where are we now? And when you say okay, you end up in let's step four or five. Then you have conversations with the people who, who stand there on a line, usually say, why are you here on four? Why are you already on four? What do you need to come a step forward further? And so on. And from that point you think about, okay, how do we get from this scale Just a step further. And from that you get the actions derived. And I think this is a very positive approach to retrospective because you think about something good that will happen that you want to achieve and not something bad that happened and how to avoid it.