What is the difference between a Scrum Master and Agile Delivery Manager and how can I bridge the gaps.
Perhaps you could recommend books, courses or podcasts.
Project Management Stack Exchange is a question and answer site for project managers. It only takes a minute to sign up.Sign up to join this community
The "Agile delivery manager" seems to be an undefined/undocumented role, and from what I read in the job openings is mostly a combination of a Project Manager, a Product Owner and a Scrum Master. Sounds like utter bullshit to me. A made up title to map existing roles to a probably fake-Agile implementation, while using a lot of buzzwords.
According to Jeff Sutherland, the Scrum Master and Scrum of Scrum Master is responsible for delivery:
"Because why would you have a group of Scrum Masters if they can't deliver? Not only deliver, but actually make delivery go faster and faster. That is their job right." -- Jeff Sutherland
So, there is not real factual definition of the "Agile delivery manager", except for open vacancies (13k open jobs). The Scrum Master is responsible for making sure the team delivers working software Sprint after sprint, as working software is the primary measure in Agile.
Leading me to think that the Agile delivery manager is not something that should exist and should be covered by the Scrum Master if you're doing Scrum. Maybe if you're not doing Scrum, it could be alternative title for the same.
Maybe someone can prove me wrong and point us to documented proof of the "Agile delivery manager", hopefully showing it is truly Agile, but from my research it seems to be a sort of Scrum Master or a something which would fit in an Agile anti-pattern book.
I second Niels opinion on "there is not real factual definition of the Agile delivery manager" (+1!), however it doesn't mean that some companies haven't faced a need to name a delivery manager role for Agile projects.
Long story short: That's likely to be a managerial role, responsible for aligning different agile teams (not necessarily scrum).
Aspects to be considered:
Bottomline: Understand the context where this role is required. If that's a job offer, see what's being expected. It's likely to change from place to place, anyways.
What I like about the “Delivery Manager” title is that there’s little question about the purpose – getting stuff delivered. The role is not about discovery, and it’s not about coaching on process; it’s all about getting stuff pushed live. ( https://svpg.com/the-delivery-manager-role/ )
Reading the above quote tells me that companies who have no idea what it means to be agile and who just jump on the agile band wagon because they like the idea of shorter delivery cycles but without any of the values, principles, behaviours, and practices. Just deliver what you promised right on the deadline.
The Scrum Master and the Agile Delivery Manager (ADM) are quite different (According to SAFe) For example:
These are some examples; hope they help. We are in our 7th year of our agile journey applying SAFe.
I’ve found that the Scrum Master role and the ADM role create conflict within the Scrum Team. Roles clearly need to be defined otherwise the Scrum Master position is compromised. The Scrum Master is task with protecting the team from outside and inside distraction. To me the ADM as I mentioned above can falls into this. Not a fan of this role.