“What does an agile coach do at Spotify?” This is a very common question when we host study tours in our office or when we speak at conferences. It is also a very good question because it makes us think about how we work and why we have chosen that way of working. I will try to answer all of these questions in a series of blog posts, starting with this one about the Agile Coach role and then publishing one blog post every day of this week, describing how I am actually spending my days as an agile coach at Spotify.
- Agile Coach at Spotify – Monday
- Agile Coach at Spotify – Tuesday
- Agile Coach at Spotify – Wednesday
- Agile Coach at Spotify – Thursday
- Agile Coach at Spotify – Friday (not published yet)
From Scrum Master to Agile Coach
When I joined Spotify in August 2011, my position was called “Scrum Master”. The job ad was pretty similar, if not identical, to what we now have published on our web site for the agile coach position. Except for “Agile Coach” instead of “Scrum Master” of course.
The Agile Coach role at Spotify is all about coaching and enabling the Development Teams. We are building an environment where continuous improvement of the development process is in focus and where everyone’s common goal is to deliver outstanding software as fast as possible while having fun.
As an Agile Coach at Spotify you are passionate about communication, group dynamics and coaching and you are not afraid to raise issues and drive change to remove impediments from your team. You’ll be working with a world-class team of engineers who love what they do – and we expect no less from you.
You should have an insatiable appetite for learning new things and improving existing ones. If you’re the right one for us, you pay attention to details and take great pride in your work.
What attracted me with this description and with the actual work I’m doing now (yes, they match!), is the mix of coaching teams and driving organizational change, honing my coaching and people skills and working as a mentor and change agent. Also, having worked as an “lean-agile expert” consultant with several (although not exclusively) short-term engagements, I longed for the opportunity of a long-term approach backed by strong management support for agile, lean and continuous improvement.
I was hired as the third Scrum Master/Agile Coach and at the time we had about 15-20 teams or so. Several of the teams were screaming for help with working more effectively together and we tried our best to help them. After a not so successful every-team-should-work-with-Scrum-and-do-exactly-like-it-says-in-the-book approach, the CTO had spearheaded an organizational design where autonomy was a, if not the, key principle and where the teams were considered “mini-startups” and Spotify an incubator for these. An important part of this autonomy was for each team to come up with a process that fit their specific context and their current needs.
While the de facto standard still was Scrum, several teams made adjustments to the text book approach and some of them experimented with what could better be described as kanban style processes. Our work as agile coaches was to assist the teams, through coaching and mentoring, in discovering improved ways of collaborating and developing into gelled high performing teams.
At the same time we, the agile coaches, studied Lyssa Adkins’s brilliant “Coaching Agile Teams” in our book club and we liked her distinction between a Scrum Master and an Agile Coach. Lyssa describes a Scrum Master as someone who “gets a team up and running with Scrum practices and agile principles”. An agile coach is:
Someone who appreciates the depths of agile practices and principles and can help teams appreciate them, too
Someone who has faced the big dragons, organizational impediments, and has become a coach to managers and other outsiders in the course of addressing them
Someone who can help management at all levels of the organization to understand the benefits of working agile
Someone who has brought the ideas from professional facilitation, coaching, conflict management, meditation, theater, and more, to help the team become a high-performance team – the way you always imagined a high-performance team could be when you allowed yourself to dream
Adding this influence, that matched what we were actually doing, to the fact that we were no longer (if ever) a “Scrum shop”, we decided to change the title of our roles to Agile Coach.
So we don’t have Scrum Masters at Spotify anymore, but as a rule of thumb an agile coach is considered member of two teams that he or she is working with indefinitely. If the teams are new to agile practices and principles the coach will typically teach and facilitate stand-ups, planning and estimation, retrospectives, and so on, but pretty soon a lot of this will be handed over to the team members. Much like a Scrum Master, although usually not through teaching (or “implementing”) text book Scrum, but rather through helping the team decide what they need to improve and which practices to try out.
It is common for the coach to have regular coaching sessions with the individual team members, including the Product Owner, to help them on their agile journey, something that often goes on for a long time. By spending a lot of time with the teams we hope to grow a continuous improvement culture and to act as catalysts to speed up the team’s development into a high performing team.
Other agile coaches that we meet, at conferences and community events or in our recruitment process, are sometimes surprised by the amount of time we spend with the same team. They are used to go from team to team, perhaps even from organization to organization, to train teams, managers, Scrum Masters and product owners (rarely team members, at least not individually, it seems), maybe drive a change initiative or two, and then move on.
There are many reasons for our strong focus on teams at Spotify, probably at least as many reasons as there are coaches, but here’s a few of the ones I think are most important:
- In a world of autonomous squads a lot more work and decisions are being done in the teams compared to companies with more hierarchy.
- We have hired agile coaches who have experienced the power of high-performing teams first hand and who knows how effective they can be. We’re not content with average performing teams, we want to be pushing the limits.
- Spotify’s management knows this too and understands the importance of agile and coaching, that is, we have management support and we are not under staffed. Well, if my managers read this – we could always use a few more agile coaches of course! :)
- We grow fast. Extremely fast at times. 10x in the last 3 years. This means that even if we try to keep stable teams, new members are coming in all the time, teams are splitting into new teams, the organization changes, and so on, so we need to put in a lot of work to keep the teams performing in this fast-changing environment.
As with everything else at Spotify, the agile coach role is constantly evolving and changing. Back when I joined Spotify and we were only three coaches in one site, we were a small team working closely together to define our role and to decide what to look for in a new recruit. Today we are 15-20 coaches, working in three different sites and in several different departments (or “tribes” as we call them). With our emphasis on autonomy and independence there’s no wonder that the agile coach role is starting to look more and more different from tribe to tribe and from coach to coach. We are constantly experimenting with different approaches, trying different things with different teams. To share our experience and get some alignment, or at least a shared understanding of what our job is all about, we meet regularly to discuss what is happening and capture and develop the different aspects of our role.
One such meeting, a full day off-site, took place a few weeks ago at Yasuragi in Stockholm. In one of the Open Space(-ish) sessions some of the coaches produced this description of the agile coach role, beautifully illustrated by colleague Jimmy Janlén (and vectorized by Martin Wasielewski), which I guess represents our most current understanding of the topic.
At the moment we are experimenting with rating ourselves in the different areas of this poster, to understand where we want to improve, who can help us improve, and how and where to apply ourselves to be most effective in improving Spotify. But that’s a topic for another blog post.
This post has just scratched the surface of what the agile coach role is and I hope to further elaborate in future blog posts, starting with a series of daily posts describing the day-to-day work of one agile coach at Spotify – yours truly. If there’s anything else you want to know about agile coaching at Spotify or if you have something to share on the topic of the agile coach role, feel free to use the comments below.
One Response to “The Agile Coach role at Spotify”
- Agile Coach at Spotify – Monday | Joakim Sundén - [...] role at Spotify. If you haven’t done so already you may want to read the introductory post The Agile…
- Agile Coach at Spotify – Tuesday | Joakim Sundén - [...] role at Spotify. If you haven’t done so already you may want to read the introductory post The Agile…
- Agile Coach at Spotify – Wednesday | Joakim Sundén - [...] role at Spotify. If you haven’t done so already you may want to read the introductory post The Agile…
- Agile Coach at Spotify – Thursday | Joakim Sundén - [...] role at Spotify. If you haven’t done so already you may want to read the introductory post The Agile…