Try a Practice Round
image (1)
Picture of Christian Heidemeyer

Christian Heidemeyer

Scrum Master as Manager? Role differences & tips

The role of the Scrum Master in agile teams sometimes raises questions about their position in the organization chart. The question of whether a Scrum Master should also act as a "functional manager" is also sometimes raised. In this text, I will shed light on the differences between these roles and also talk about the reasons why it is often recommended that the Scrum Master does not act as a "functional manager" at the same time. But let's start small...

Scrum Master, a management position? | Functional Development Manager

Is Scrum Master a management position?

How was it originally conceived – does the Scrum Master hold a classic management position?

To put it briefly, no, the role of a Scrum Master is not a management position in the traditional sense. Rather, the Scrum Master is responsible for ensuring that the Scrum team works effectively and follows the principles and practices of Scrum. The focus is on supporting the team to achieve optimal performance and productivity.

The main tasks of a Scrum Master include removing obstacles that hinder the team in the implementation of its tasks, promoting an agile mindset within the team, organizing and moderating Scrum meetings and supporting the continuous improvement of the team's way of working.

In contrast to a traditional manager, who often makes decisions and is responsible for the result, the Scrum Master acts more as a facilitator and coach. The decision-making power usually lies with the team itself. Scrum promotes self-organized teams that take joint responsibility for their work.

The Scrum Master as manager of the Scrum framework

Some argue that the Scrum Master is a kind of "manager of the implementation of Scrum". This designation underlines the Scrum Master's responsibility to ensure the successful implementation and application of the Scrum framework within the team and the organization. The Scrum Master then acts as a mediator between the team members and supports them in understanding and effectively implementing the principles of Scrum. Although the Scrum Master does not "manage" in a traditional hierarchical sense, they contribute to the successful implementation of Scrum by acting as a mentor and supporter for the team.

Even if some practitioners argue this way, I personally think this logic is far-fetched. A manager usually has completely different decision-making powers and also a different approach to their own work than a Scrum Master –, which is why I would not see a Scrum Master in a managerial position.

Scrum Masters are typically not in a managerial role, but still have the task of keeping chaos in check.

Scrum Master, a management position? | Functional Development Manager

Scrum Master compared to other manager positions

There are a lot of questions on the internet about the differences between Scrum Masters and various other manager roles in the agile and IT context. Next, I would like to give you a brief overview of the differences and also provide a brief thought on how these two roles can be reconciled.

First of all: In short, it is always recommended that you do the Scrum Master job full-time. And it is also recommended that the Scrum Master also has traditional decision-making power or line responsibility like a manager. Nevertheless, some companies cannot afford to hire both roles. In this respect, here are more specific explanations of what needs to be done in each case:

  1. Scrum Master and Delivery Manager:

    • Scrum Master and Delivery Manager difference: The Scrum Master focuses on implementing the Scrum principles in the team and removing obstacles. A Delivery Manager is often responsible for the efficient delivery of project results and may span multiple agile teams or processes.
    • Scrum Master and Delivery Manager Recommendation: In smaller organizations, one person could take on both roles if they have the required skills. In larger environments, however, it may make sense to separate the roles to focus on specific aspects of agility and project delivery.

  2. Scrum Master and Agile Manager:

    • Scrum Master and Agile Manager difference: The Scrum Master is focused on supporting the Scrum team and optimizing the agile process. A Agile Manager could be an overarching role that focuses on the agile transformation of the entire organization.
    • Scrum Master and Agile Manager Recommendation: It would probably be effective for the Agile Manager to manage strategic aspects of agility, while the Scrum Master addresses the specific needs of the Scrum team. Collaboration is important, but both roles can have independent focuses. Performing both roles simultaneously could also be conceivable.

  3. Scrum Master and Program Manager:

    • Scrum Master and Program Manager difference: The Scrum Master focuses on the implementation of the Scrum framework in the team, while a Program Manager is often responsible for the coordination of several teams or projects within a program (the word is primarily used in the SAFe context).
    • Scrum Master and Program Manager Recommendation: It makes sense to have both roles in order to operate at different levels of agility. The Scrum Master should focus on the day-to-day business of the team, while the Program Manager takes on a coordinating role at a higher level.

  4. Scrum Master and Release Manager:

    • Scrum Master and Release Manager difference: The Scrum Master focuses on the agile process and the performance of the team, while the Release Manager is responsible for the planning and implementation of software releases.
    • Scrum Master and Release Manager Recommendation: In smaller teams, one person could take on both roles, but in larger organizations it is of course advantageous to separate the responsibilities to enable a clear focus.

  5. Iteration Manager and Scrum Master:

    • Iteration Manager and Scrum Master difference: Both roles have similarities and might be called differently in different organizations. The Iteration Manager may focus on specific iterations or sprints, while the Scrum Master has a broader role in the agile process. This might be the typical difference between the Scrum Master and the Iteration Manager.
    • Iteration Manager and Scrum Master recommendation: In many environments, the roles could merge or have different focuses. It is important to ensure that responsibilities are clearly defined, regardless of the names used.

  6. Scrum Master and Line Manager:

    • Scrum Master and Line Manager difference: The Scrum Master promotes self-organization and collaboration within the team, while a Line Manager is more responsible for the career development and performance evaluation of team members.
    • Scrum Master and Line Manager recommendation: These roles should be separated to avoid conflicts of interest and ensure effective collaboration within the team. You can also find out more about "functional manager" below

  7. Scrum Master and QA Manager:

    • Scrum Master and QA Manager difference: The Scrum Master focuses on the agile process, while a QA Manager is responsible for quality assurance and test strategies.
    • Scrum Master and QA Manager Recommendation: It can be effective if both roles work together and ensure that quality aspects are integrated into the agile process. Clear alignment of responsibilities is important. I have also seen a QA Manager take on Scrum Master activities.

  8. Scrum Master and Engineering Manager:

    • Scrum Master and Engineering Manager difference: The Scrum Master supports the team in agile implementation, while the Engineering Manager is more responsible for technical aspects, resources and technological strategies.
    • Scrum Master and Engineering Manager Recommendation: Both roles should coexist in an agile environment, with the Scrum Master focusing on the agile process and the Engineering Manager focusing on technical aspects. In my opinion, it is also not unusual for an Engineering Manager Scrum Master to take on tasks such as moderating meetings.

  9. Scrum Master and Product Manager:

    • Scrum Master and Product Manager or PM difference: The Scrum Master supports the team in implementing the agile process, while the Product Manager or PM is responsible for defining product requirements and maximizing product value.
    • Scrum Master and Product Manager or PM recommendation: It is common for both roles to work closely together, but they have different priorities. Clear communication and collaboration are key. Product managers or PMs are also sometimes the scrum masters of their teams to a certain extent if there is no additional employee for the topic of "continuous improvement".

Now we have a better idea of how we can differentiate between the various manager roles of the Scrum Master. But what about the question of whether Scrum Masters can or should also be functional managers?

Scrum Master, a management position? | Functional Development Manager

Can a Scrum Master be a functional manager?

Normally, a Scrum Master is not a "functional manager" in the traditional sense. A functional manager is usually a person in an organization who has direct authority and responsibility over a specific functional group or department. This type of manager often makes decisions, is responsible for the performance of the group and has clear line authority.

In contrast, the Scrum Master is more of a coach, mentor and facilitator for the Scrum team. The Scrum Master normally has no direct authority over the team members and does not act as a supervisor in the traditional sense. Instead, the Scrum Master promotes self-organization and teamwork.

It is important to note that the role of a Scrum Master in agile environments is deliberately designed to challenge the traditional hierarchy and command structure in order to support self-organized and autonomous teams. In this respect, a dual role is more likely to lead to conflict. 

Speaking of which, what if your organization doesn't want to hire a full-time Scrum Master for financial reasons, for example, and plans to use managers instead?

Phew, that would definitely not be ideal. Nevertheless, I know that some companies actually handle it in exactly the same way. So if you're faced with this situation, how can you possibly argue against it? Here are a few thoughts.

Scrum Master, a management position? | Functional Development Manager

Scrum Master is a functional manager: What to do?

It is usually recommended that the Scrum Master does not also act as a "functional manager". The reasons for this lie in the principles and values of agile methods, including Scrum.

Here are some concrete thoughts:

  1. Conflicts of interest: The Scrum Master is there to support the team and ensure that it works effectively according to agile principles. If the same person also has formal authoritative power over the team, conflicts of interest may arise. The Scrum Master's focus is on removing impediments and empowering the team, not on giving direct orders.

  2. Promote self-organization: Agile methods emphasize the self-organization of teams. If the Scrum Master also acts as a manager, this could impair the self-organization of the team, as team members may wait for instructions from above instead of proactively making decisions.

  3. Independent view from the outside: A Scrum Master should often have an independent view from the outside and be able to objectively assess the team and the development process. If the Scrum Master also has line responsibility for the department, this could affect the ability to make an objective assessment.

In agile environments, it is therefore more common for the Scrum Master and the management position to be separate roles in order to effectively implement the agile principles and values.

"Many team members are afraid to speak up!"

Solve this challenge

"We discover too many unexpected issues & bugs at a late stage!"

Solve this challenge

"Why does it sometimes take me hours to prepare a simple retrospective?"

Solve this challenge
Woman_pm
You lead an agile team and...
📊... want to impress with clear metrics on your teams agiliity?
⏱️... lack the time to prepare great agile retrospectives?
You should try Echometer.
Learn more & Get Started

Scrum Master, a management position? | Functional Development Manager

Tips for the dual role

Your company has not been able to ensure that the Scrum Master role is not available full-time and dedicated to each team? Then Echometer could be of interest to you. In such situations, it enables a continuous improvement process that focuses on the employees. For example, agile retrospectives can be conducted anonymously to increase the likelihood of open feedback.

Echometer is a digital tool that helps agile team leads with agile retrospectives and team Health Checks. Whether remote, hybrid or on-site: it makes team coaching measurable and professionalizes your work while saving you a lot of work. Just take a look at our website to find out more: www.echometerapp.com.

"Scrum masters should not see themselves in a traditional management position, but should at best be in close contact with the decision-makers in order to understand their perspective."

Christian Heidemeyer, Psychologist & Scrum Master

Scrum Master, a management position? | Functional Development Manager

Conclusion - Scrum Master as a management position

In agile environments, the separation of the roles of scrum master and functional manager is crucial. The agile principles, such as self-organization and team empowerment, are better supported when the Scrum Master focuses on promoting agile methods without exercising formal authoritarian power over the team. This helps to promote an effective, self-organized and agile way of working.

Finally, another quick hint: If you would like to know how it feels to develop your team with our tool: You can start an agile retrospective below without logging in, in this case the "Keep, Stop, Start" workshop. 

Alternatively, simply forward our website to the responsible colleagues: www.echometerapp.com.

Open Feedback Questions

Continue: What should we keep?

Stop: What should we stop doing?

Start: What should we start doing?

Open this retro now
Customize...

Share this article in your network

Need a team boost? Do this: The Spotify Health Check Retrospective!

First Health question: "😍 We love going to work, and have great fun working together."

Sounds good? Try our retro tool for free below.

Open this retro now

Articles you may also be interested in

View all

Echometer Newsletter

Don't miss updates on Echometer & get inspiration for agile working