A Scrum Master/Agile Coach job description

I’m often asked for help putting together a job description for a Scrum Master, so I thought I would post an extract of one we’ve used recently.

We are a product team of developers, QA experts, user experience and visual designers and product owners who are looking for someone to help us get better at what we do. We’re pretty good at the basics of agile software development but can always use new ideas about how and where to improve. We’re less concerned about what it’s called (Scrum/Kanban) and much more excited about results, whether that means moving towards continuous deployment, using ATDD, or seeing our active users grow.

You are someone who leads by example rather than by dictate and you know how to bring out the best in people. You’re not afraid to deal with conflicts. You know when it’s good to say “No” and when to push for more results.

In addition, we’re looking for someone to act as a galvanizing force for our whole wider team in terms of sharing Agile knowledge across the company. Whether it be organizing 1-day open spaces for our agile community, or organizing cross-team workshops, the goal is for you to establish an Agile center of gravity around our team.

Your main responsibilities will be:

  1. Act as Scrum master for 1-2 scrum teams with a focus on guiding the teams towards improving the way they work.
  2. Facilitate sprint planning, retrospective and sprint demos
  3. Assist the product owner with keeping the backlog groomed
  4. Ensure cross-team coordination
  5. Reach out to the larger company network for impediment removal
  6. Maintain relevant metrics that help the team see how they are doing
  7. Coach and mentor other scrum masters in our product team. Ensure that our ways of working are consistent across the teams.
  8. Liaise between the developers and User Experience/Visual Designers. Foster better communication between the disciplines.
  9. Act as a project manager when necessary. Take responsibility for managing dependencies between our team and third parties or between our team and other scrum teams.
  10. Strengthen the presence of our team as an Agile centre of excellence. Actively contribute to the company’s Agile and Lean Community. Keep the rest of the company network aware of our activities.


  1. Knowledge of the software development life cycle
  2. Certified scrum master/scrum practitioner
  3. Knowledge and/or experience of Kanban
  4. Excellent communication skills in English in written and spoken form
  5. At least 3 years experience working in an agile environment, preferably in a variety of situations

Feel free to use this, re-use it and copy it. I hope it’s helpful!

What would you add to make a better Scrum Master job description? Share your tips in the comments.

7 thoughts on “A Scrum Master/Agile Coach job description

  1. Will, thanks for posting this. I was tasked to come up with job descriptions for a Scrum Master and Agile Coach. You provided me with a great starting point that I can refine or add to.

    Having said that can I get up on my soapbox for a minute? I only took umbrage with one small phrase in Responsibilities, item #9. I try to avoid at all costs the inclusion of the words ‘Project Manager.’ I’m not an Agile purist but I have found that using this term when (key word) transitioning groups can lead to not only a lot of confusion but sows the seeds of ‘Worst Practices.’ for a variety of reasons. It invites a whole host of hanging on to traditional practices and mind sets.

    That is just my 1 cent – it’s not even worth 2.

    Thanks again.

    • Hi Steven,
      thanks for the feedback.

      I get your point about using the word “project manager”. This term, and this role, has very different connotations to different people. What I mean with the term is that sometimes the scrum master just needs to roll the sleeves up and coordinate people and teams to get a specific thing done. I see this as being in contrast to the normal role where a more facilitative approach is best.

      In other words, I expect the normal focus to be on helping the team learn how to be better at helping themselves. But sometimes, to get things done (especially in large organisations where the scrum team is one part of a much larger system), the “traditional project manager”-type job of coordinating and organising comes into play.

      Very good point about the connotations though… could easily lead to the wrong perception.


      • Will, completely agree with the need for someone to just “roll up their sleeves” sometimes. Some people vehemently oppose this notion, but I’ve seen too many bad implementations of Scrum as a result of this passive mindset. Thanks for the great list!!

    • This is a nice example too.

      I think the thing I don’t necessarily agree with in this job description is the assertion that a good scrum master is a development manager, or at least someone with a development background. The two best scrum masters with whom I’ve ever worked had no development background at all. What they did have, however, was an ability to understand people and systems, and an ability to know what questions to ask to guide someone through solving a problem (without knowing the subject matter themselves).

      What’s your view on scrum master as a development manager?

Leave a Reply

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