Skip to main content

Scrum Masters & Agile Coaches, Stop Team Coaching!

November 16, 2018

Why do I think team coaching is a bad idea? Don't get me wrong, I believe team coaching can have a great amount of added value. It’s just that I often find that teams receive coaching while they should not even be a team. The Agile way of working is all about being in control in a complex environment. We get control by learning from feedback on the value delivered as quickly as possible. So we deliver Done Increments regularly in short iterations.

“Does a Done Increment always deliver customer value?”

I’d like to answer that question through a metaphor. The hamburger.

Imagine: you order a Hamburger at a local hamburger joint. They tell you preparing that hamburger will take 60 minutes. (they make everything from scratch, fresh!) Recently, the kitchen made a transition to Agile delivery, so they will deliver your order in 10-minute increments. Interesting! The delivery can be in two possible ways: first the bottom bun, then the burger, then the pickles, etc. Building your Burger layer for layer. Or, you get a small bite after the first 10 minutes, but with all the ingredients in it, and then a second etc. In this second scenario, you can immediately tell the clerk that you dislike pickles. The next delivery they can leave those out. In the first scenario a result is delivered every iteration. But does a single bottom bun deliver customer value? I’d prefer a full, juicy, crispy, tasty bite. Without pickles. Please ;)

flipover with a schematic hamburger and two highlights - vertical indicating feature (agile) teams - horiztontal indicating component teams

When we return from the metaphor (well-fed, hopefully) and look at the way most businesses are organized, we will discover business units similar to the components of the hamburger. When such a business unit ‘implements Agile’, they will start creating Agile Teams within those units (components). Those teams need lots of help to become truly agile, so Scrum Masters & Agile Coaches are hired to coach those teams. And so we end up passionately coaching team bottom bun.

And while coaching this team bottom bun may have some benefits, for instance honest feedback during Retrospectives aimed to improve as a team, this is not what Agile should primarily be about. Agile is about delivering a real working product to customers, so you can validate your assumptions and adapt your course as needed. Remember? The goal of Agile is being in control in a complex environment. So long as the output delivered by team bottom bun is just a small part of the actual total output needed to deliver customer value, this goal is not achieved. There is no actual feedback (just more assumptions). Because of that we will not be able to learn what is needed to stay on course to keep delivering maximum value. We are actually just creating a false sense of control that is potentially steering us into the Bermuda triangle of lost hope. This means we are missing the point of Agile, giving control in a complex environment.

So, dear Scrum Masters and Agile Coaches, are YOU coaching a team bottom bun? Are you avoiding the conversation about continuously moving the organization to create full bite, full flavor, full value teams? Then you are not helping the organization and the team use Agile as intended and potentially harming the organization by playing Agile theater. So should we simply refuse to help teams and organizations that are only able to start creating component teams (delivering bottom buns)? No way, this is sometimes the only place to start helping. But please don’t stop there and use all impediments and dependencies you and the team will surface to push the organization and its teams towards delivering a full bite of value, helping them to increase their control and effectiveness using Agile.

So before you start coaching a team, please be aware of the full hamburger and the components needed to deliver value. So looking beyond the team you’ve been asked to coach, which other ingredients are needed to deliver customer value? It’s truly rare to start in a perfect Agile situation, and that is OK. But never forget that it’s your duty as Agile Coach or Scrum Master to help the organization to improve their way to true agility, to start delivering customer value with each iteration. To get the whole hamburger front and center and make it better with each delivery.

The hamburger is a playful, lightweight metaphor to start discussing true agility in your organization, to keep in mind what is really important: delivering customer value and being in control by inviting feedback and learning from it. Good luck and enjoy your burger! 

This article was originally conceived in dutch by Guido Boskaljon and collaboratively developed by Guido & Sjoerd Kranendonk. Find the original dutch article here.


What did you think about this post?

Comments (10)


Evan T. Cook
10:31 pm November 16, 2018

Love the metaphor and nicely articulated!


Thomas Ferris Nicolaisen
11:36 am November 17, 2018

Thanks for writing, translating and sharing! I came at this from a different angle, but also arrived at the same metaphor :-) maybe you'll find it interesting: https://blog.tfnico.com/201...


Jon
06:40 pm November 17, 2018

But you can’t create just a slice of pickle to go on your bite sized burger. You need to pickle an entire cucumber and cut a slice off. Likewise I find your metaphor is fine for building websites with an established technology pattern. But with innovative builds that require new technology stacks, it’s not that easy to build just a bite at a time.


Filipe Nascimento
03:28 pm November 18, 2018

Tell this to an Enterprise Application organisation... with multiple roles around the world.


Tim Ottinger
04:40 pm November 19, 2018

This is odd. The title and presumed focus was about coaching teams v. <something> but then the content is about building in disconnected layers instead of walking skeleton/evolutionary/slicing. It kind of felt bait-n-switch. Nothing about "team" naturally says "component layer teams" - and I didn't see any reason to not coach teams, so I'm confused what the author feels this post is about.


Bianca State
03:39 pm November 20, 2018

I agree, I was somewhat confused as well! On reading the title I was expecting something like an anti-coaching article saying why coaching is deprecated and then suggesting something other than that.. Ideally the title would incorporate the component aspect, to make the message and article focus topic clearer.


Karin Dames
07:34 am November 23, 2018

I agree. It gives team coaching a bad wrap when in actual fact it is the definition of done or definition of a MVP that is at fault. Team coaching (when done properly) would actually have pointed this out and resolved it rather than impede it.


Claire
08:41 pm November 27, 2018

This is a great article to help switch the thinking from developing for one layer to developing for actual value! I completely understand the title as it reinforces that in Agile you should not coach a team (such as an API team or a Client Side team) but rather build and coach a team that delivers something at each layer in order, again, to provide real value! Love the hamburger analogy and will use it!


Vasilij Savin
06:12 pm January 24, 2019

The metaphor is off. Hamburger production is a manufacturing process where iterative approach is not necessary. It is operations, better organised with Kanban approach.

Also, the whole article underappreciates complexity of modern companies and need to slowly expand Agile coverage. Not always ACs and SMs have enough clout to work on the whole value stream from the get go.


Peter Barica
05:11 pm August 12, 2019

In my understanding, there is a difference between the Scrum Master and Professional Team Coach, but I don't see any relation to the product delivery. The main difference is in contracting a role in relation to the (development) team, where Scrum Master role is defined in Scrum Guide, but the Team Coach must contract his/her role for the team and the organization. But the particular implementation of those roles can be indistinguishable to an observer, if the coach/scrum master truly addresses the needs of the team and the organization.