Impediment Management

This content is syndicated from Agile & Business by Joe Little. To view the original post in full, click here.

I was talking today with Martin Drapeau at, brainstorming "what do managers need"?

So, I have let the cat out of the bag: I am not one of those agile guys who thinks all managers are evil. (Yes, I have in my career seen more bad managers than I want to admit...not bad people, but "not-so-good" managers. Yes, it is a problem.) In fact, I think some managers are quite good. thing we talked about is how important it is to manage the impediments.

I say: Typically our first big impediment is a lack of focus on removing impediments. I talked about this in a recent post.

What's next? Well, I like to ask ScrumMasters..."where is your public list of impediments?" And all too often I get: "Ummm.......(long pause)" Which is usually not a good sign.

Then I like to ask somewhat experienced Scrum people in my classes: "OK, how do you prioritize impediments?" Often I get "Ummm....(pause)". [I don't give them time for a long pause.] You can guess by now: this is not a good sign.

The simple answer for impediments is: We prioritize the ones, which if improved or removed, will increase the velocity of the team the most. The more complex answer is: "The ones that give the best cost-benefit ratio." And the benefit is the improved velocity (mainly) and the cost is (mainly) the cost to reduce or remove the impediment. (Always apply the most uncommon thing: common sense.)

Do managers have a role? Yes, most assuredly, in removing impediments.

And, typically, there is a management team (or should be) whose main (only) job is removing impediments. I will call it the IRT (Impediment Removal [scrum] Team [of managers]), but other writers give it a different name. And that IRT team should see a list of all the impediments from all the teams, and try to prioritize them across the whole group. And then organize the removal of the biggest impediments for the group.

(And all the members of the 'real' teams should see all this too.)

Could a tool help here? Yes, after about two or three teams, we think a tool could help.

So, for management reporting, would it be good to relate the impediments removed with the increased velocity? Yes, rather obviously as soon as you ask the question, although exactly how might be a bit of a problem. But, if managers had this info (and teams too), would it affect behavior in a positive way? We think so, strongly.

(Yes, Virginia, it can be abused. And, perhaps far less likely, people can drink too much milk too...everything has some risks.)

Reminder: Do not do lots of management reporting. Too many numbers running around can be confusing, and NOT helpful. We only report what is useful; things that help us all make better decisions and act better, more usefully. Numbers never tell close to the whole story, but often tell us non-obvious things that can be very useful.

ScrumMasters: One of your biggest impediments is getting some managers to understand the new reporting and to use it well, operating from lean-agile-scrum values and principles. As some of you know: This can be very hard work for you.

Make sense so far?
What are the most important things I have left out? (I know there are many common questions I have not answered here).
More generally, your comments are wanted. Please comment.

I will have more to say on this topic shortly.

Leave a Reply

Your email address will not be published. Required fields are marked *

12 + 1 =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch