Over a million developers have joined DZone.

Becoming an Agile Leader, Part 3: How to Create Allies

DZone's Guide to

Becoming an Agile Leader, Part 3: How to Create Allies

In this post, Agile consultant Johanna Rothman explores the nuances of Agile coaching, and how to broach the subject with your peers or bosses.

· Agile Zone
Free Resource

Reduce testing time & get feedback faster through automation. Read the Benefits of Parallel Testing, brought to you in partnership with Sauce Labs.

To summarize: your Agile transformation is stuck. You’ve thought about your why, as in Becoming an Agile Leader, Part 1: Define Your Why. You’ve started to measure possibilities. You have an idea of who you might talk with, as in Becoming an Agile Leader, Part 2: Who to Approach. Now, how do you create allies so you can un-wedge your Agile transformation?

First, here’s a big question: do you have a relationship with this person? If so, terrific. You have options. as I discuss below. If you don’t have a relationship yet, it’s time to build a relationship.

Let’s assume you have some sort of relationship with this person. In that case, you might ask for coaching.

You might say, “Hey, wait a minute, Johanna. I’m the coach (or leader in some way). Why would I ask for coaching?”

When you ask for help, as in coaching, you offer the other person (often called a client) a gift. You offer explicit permission to explore options with the other person’s support. This is especially helpful if the other person is your peer or is senior to you in the hierarchy.

I know, this is turning the normal definition of coaching around. Many people think that if they are one of the Agile transformation leaders, they have to have all the answers. No, you don’t. You might not know what the smallest possible change is. You might not be aware of the forces that prevent change (I’m assuming good intentions on everyone’s part). You might not know what this person might gain or lose with an Agile transformation.

Asking for help is a sign of strength, not weakness. Asking for help shows transparency and a willingness to consider other options.

You might “lead” the coaching conversation by saying something like this: “Here’s what I’m seeing. We’ve done this and that and gotten these results. Do you see the same things?” If the person has different data, wow, that’s great to learn. If you have the same data, you might continue, “I’m concerned we’re stuck. I see these options to solve these problems. Do you see something else?”

When you ask for other options, you open the conversation (and your brain) to possibilities you might not have seen before.

This coaching conversation is very different from, “I’m the Agile expert and I’m here to help.” You might be the Agile expert. You are definitely there to help. And, you need to enter the other person’s context to understand what’s going on for that person.

You might be thinking, “Oh, this is going to take time.” Well, it will. These are one-on-one conversations. You might have to wait a week to get on someone’s calendar. And, what have you got to lose? What’s the worst thing that can happen?

If you want to experience this kind and other kinds of coaching conversations in the context of helping your Agile transformation continue, join us at the next Influential Agile Leader, May 9-10, 2017 in Toronto.

My next post is about exploring how you use influence aside from coaching to achieve win-win scenarios.

The Agile Zone is brought to you in partnership with Sauce Labs. Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure.

agile ,agile coaching ,team building

Published at DZone with permission of Johanna Rothman, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}