Delivery Manager vs Scrum Master: What's the difference?

Delivery Manager and Scrum Master are often treated as interchangeable roles.

Sometimes they are. Sometimes they are very different.

The reason is that neither title exists in exactly the same way in every organisation. A role name tells you less than the actual accountabilities and responsibilities attached to it.

So rather than asking which title is "better", a more useful question is:

In Scrum, the Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and for the Scrum Team's effectiveness.

The Scrum Master serves the team, Product Owner and organisation by helping people understand Scrum, improve their practices, remove impediments and support the effective use of Scrum.

That means the Scrum Master role is strongly connected to the Scrum framework itself.

The Scrum Guide describes the Scrum Master as helping the Scrum Team with self-management and cross-functionality, helping the team focus on valuable increments, removing impediments and ensuring Scrum events are useful and timeboxed. The role also includes serving the Product Owner and the wider organisation.

In other words:

The Design for Flow course uses Delivery Manager in a broader delivery-management sense.

The focus is on improving the system through which work moves from intention to implementation and delivery.

The course identifies responsibilities such as defining the delivery process with the team, tracking progress, keeping the team focused, unblocking work, coordinating cross-team collaboration and managing delivery risks.

It also covers:

So the centre of gravity is slightly different.

A Scrum Master is accountable for helping the organisation and team get the most out of Scrum.

A Delivery Manager, the way we understand delivery management, focuses on helping the team build and improve an effective delivery system.

Quite a lot.

A strong Scrum Master may already be doing many things that look like delivery management. A strong Delivery Manager may use Scrum when Scrum is the team's chosen framework.

The biggest difference is often the scope of the system being improved.

The Scrum Master helps the team and organisation understand and use Scrum effectively. The role is grounded in the Scrum framework and its accountabilities, events and principles.

The Delivery Manager may work across a wider set of delivery concerns. That broader scope is also why our course Design for Flow does not require you to abandon Scrum.

Its principles can also be applied to different frameworks.

The biggest difference is often the scope of the system being improved.

This is another area where people often create an artificial distinction.

A Scrum Master may facilitate Scrum events and help ensure they serve their purpose.

A Delivery Manager may help design recurring meetings and ceremonies more broadly, including their purpose, participants and cadence.

We believe every meeting should earn its place.

If nobody is clearly responsible, that is as delivery problem regardless of what the org chart says.

There isn't a universal answer. The more useful distinction is about purpose and scope.

There is overlap and there can be different organisational models but neither role automatically means people management.

What matters is whether the actual responsibilities, authorities and expectations are clear.