Skip to main content
Special announcement All BVOP™ certification programs are offered with a significant cost reduction. BVOP's mission is to support professionals worldwide. Online Certification Exam
for $ 45
Register now
Get Certified

The Scrum Master role

The Scrum Master is responsible for creating project teams, integrating them into the organization, and providing a clear vision of the product. The Scrum Master also facilitates communication and information exchange between external groups and the project team.

Scrum is a style of work that strives to maintain sustainable productivity for teams. Problems can quickly arise if the roles within the team and organization are not clearly defined and understood, and the team members do not follow the goals and purposes of the roles.

The Product Owner role represents the voice of consumers and the desires of stakeholders and businesses. The development team develops all these needs qualitatively.

The need for a Scrum Master role

However, throughout this process, there is a need for a role that takes care of all parties and strives to comply with Scrum's rules, rules, and principles. Otherwise, chaos, micro-management, and disruption to the teams would result. Such negative situations can lead to a decline in motivation, defects in the product, difficult product maintenance, divergence of plans, and potential failure.

The Scrum Master role ensures that all possible negative results do not happen.

The Scrum Master strives for teams to work according to the principles and practices of Scrum.

The Scrum Master role, like all other roles in Scrum, has no authority to manage people, work, or anything. However, it has authority over everything related to Scrum processes, events, rules, ideas.

The Scrum Master acts as a leader for the team, not as a manager. Leads the team toward their goals and product goals.

The successful Scrum Master

The successful Scrum Master is dedicated, committed, and focused on the development of others and the Scrum culture of the organization.

Key responsibilities of the Scrum Master role

Key responsibilities of the Scrum Master role include:

  • Monitor and eliminate obstacles in the workflow.
  • Protecting the team from negative outside interference.
  • Assistance with meetings and Scrum events.
  • Collaboration with the Product Owner role.
  • Coaching and guidance of all product stakeholders (Scrum team and business stakeholders) on Scrum practices and concepts.

The Scrum Master must be able to represent the significance of Scrum clearly and without complex and disturbing terminology.

Scrum Master role as a servant leader

A servant leader is a popular term used to describe the Scrum Master in two words. The traditional style of leadership is usually understood as the expression of power by one person. The understanding of the serving leader is the opposite. The needs of others are first and foremost. Teams are being helped to do their jobs well and grow.

The highest priority for the Scrum Master role is to encourage and assist the Development team in maximizing their potential and productivity, in developing their skills, and in increasing the value they create.

Collaboration with the Development Team

Protection of the team

The Scrum Master role acts as a buffer between the team and all external influences, problems, and processes.

The Scrum Master protects the Development team from the Product Owner

BVOP brings a further understanding of the protection of the team from external stakeholders and indicates the protection of the team from the Product Owner role. Although the Product Owner role is part of the Scrum team, it is assumed that he or she knows and fully understands the principles and rules of Scrum. This is not always the case. Product Owner roles in different teams and organizations can have different interests, work styles, and are driven by certain actions by many factors.

The Scrum Master protects the Development team from the Development team

BVOP focuses on an important topic regarding the protection of the Development Team, and that is precisely the protection of the Development Team by itself and specific team members.

Sometimes, in teams, some participants may wish to manage their colleagues. In the classic method of management in organizations, this would not be a problem and is even considered a positive situation.

According to Scrum rules, such management should not be accepted. Respect and equality should motivate team members and develop their creativity. Featured team leaders can often naturally lead to micro-management, individual decision making, assignment, and all Scrum principles will gradually be broken.

The Scrum Master role should be aware of such possible and potential situations of violation of the Scrum rules, have a clear mind, insight, and the skills to evaluate any possible situation.

Organizing meetings

Scrum teaching shares that the Scrum Master role supports the team. However, there are no clear rules as to who organizes team meetings. We want to focus on the fact that a very appropriate role for this is the Scrum Master role.

Only if the team needs it, the Scrum Master role organize meetings and events and invite everyone who needs to attend. Shares instructions, prepares attendees for meetings, explains discussion topics, and reminds Scrum rules.

If teams are disorganized and chaotic, the Scrum Master role restores order. For example, if a Product Owner role avoids an important meeting or provision of information, the presence or assistance needs to be sought and explained.

The Scrum Master is a Coach

Coaching is not just about the rules and principles of Scrum. The motivation, ambition, and focus of the team must be maintained.

Some team members may not understand the terminology or practices used by the rest of the team. The Scrum Master role helps everyone around to get into Scrum's atmosphere and ideas.

Removing obstacles and problems

Every team, project, and organization has problems and obstacles of any kind that can arise at any time.

The Scrum Master is actively working to resolve situations that impede the Development Team. If the Development Team is experiencing some deficiencies and is unable to do its job well and progress on the developments (technology, tools, or whatever), the Scrum Master role must have the ability and authority to fill the deficiencies immediately.

The Scrum Master does not work to remove obstacles and problems by taking self-directed decisions and actions. The options are always discussed with the team in advance to provide the best solution for them. Whenever possible, it is provided that the Development Team can solve its problem by itself in the best possible way. The Scrum Master role only supports this activity.

Interpersonal problems and team conflicts

Interpersonal problems and team conflicts are also important incidents where the Scrum Master role must be involved to solve problems in the most constructive way possible for both the team and the product.

Collaboration with the Product Owner role

The Scrum Master serves as a coach and supporting role for both the Development Team and the Product Owner role. An important aspect of working with the Product Owner is clarifying User Stories that need details and care for the Product Backlog, which needs to be prioritized and detailed for the next iteration.

Who should be the Scrum Master?

To avoid conflicts of interest, it is of particular importance that Scrum Master and Product Owner roles are not taken over by the same person in the Scrum team.

If the same Scrum team member combines Scrum Master and Product Owner roles, there may be Product Owner performing Scrum Master functions, however, which focuses solely on the product and fast work.

In another unpleasant situation, there may be a Scrum Master that also performs Product Owner functions, which, however, focuses primarily on Scrum and the team, and product progress and its value can be seriously impaired.

On the other hand, both roles require a considerable amount of time daily, and performing both roles by one Scrum team member would be particularly difficult. Organizations, teams, products, and business stakeholders may suffer losses.

Working hours of the Scrum Master role

There is much discussion as to whether the Scrum Master role is a full-time position or an hourly role. The official Scrum manuals do not answer these questions either. So we have to think logically again.

For some teams and projects, an hourly Scrum Master role might be enough. In this case, everything has been polished over time, and the problems are resolved and reduced. Everyone in the organization follows the Scrum principles. Business stakeholders look forward to the team completing the planned work at the end of the Sprint. The team is self-organized and focused on its goals.

In another case, if the team is new or Scrum is still an incomprehensible matter to everyone around, the Scrum Master role would be necessary and of particular importance, daily and throughout the working hours.

As the team cultivates respect, work, value, and collaboration, and business stakeholders become accustomed to the ideas of Scrum, then the Scrum Master role gradually becomes simply a mentor who is always available and around. The critical need to solve problems and organize events is likely to decrease.

Then, a Scrum Master can have the capacity, capability, energy, and time to serve multiple teams within the organization at a time.

Scrum Master role as part of Development Team

Another common practice in Scrum teams is to have the Scrum Master take on the role of a technical person who is part of the Development Team. In this case, every time the team needs their Scrum mentor and assistant, the developer takes on the Scrum Master role and ceases to act as a Scrum Master.

Although there are pros to the Scrum Master role being taken over by the Development role, this configuration has its logical drawbacks as well.

In addition to being distracting for a team member to change roles constantly, the Development Role is likely not fully to understand the business needs of the team and organization. Assistance to the Product Owner role may also be detrimental.

What is a Scrum Master, Roles and Responsibilities of A Scrum Master
Comments of our guests
  1. Gregory J,
    Hello again. I apologize for the massive flow of questions, but I seek urgent and professional help as the problems I face are serious. We have a brand new Scrum team formed and the project has already begun. The development team is unhappy with the Scrum Master because he lacks programming skills. Our recently selected Scrum Master has strong recommendations and a wealth of professional backgrounds, and I am sure that his assignment was not a mistake. Some members of the Development Team escalated the problem (just that Scrum Master has no experience as a developer) to senior management. I would appreciate any tips or recommendations for action. I can compensate for the advice. Kind regards
  2. Stanisław
    Hello. Can you clearly state what the real powers of the Scrum Master are? What am I authorized to and what am I not allowed to do? I have co-workers who violate the Scrum rules very much and I cannot control them. What should I do in this case? thanks
  3. Safiya Samuels
    @Stanisław, The Scrum Master role by rule has no authority over others, and no one in Scrum has authority over anyone. Scrum teaches principles and rules and, at the same time, says teams should be held accountable. In the real world, this is not always possible, as following this method of work without strict supervision is not for everyone. In the course we explain all the situations you need, as well as your role and responsibilities. In short, you are the "teacher" of the Scrum process to everyone around you, but without giving commands or orders. Why not just talk to your direct leader in your organization and talk about your authority and describe these situations and any other irregularities you notice. Ask for clarification, exactly and clearly, what your rights are regarding the work of the team. If necessary, request more formal authority. Talk to the Development Team Technical Manager, if you have one. There may be someone around you who is "responsible" for the others and the work. Ask for help from outside. Don't be alone in this.

Web site
Your Comment

The BVOP Certificates

Certified Chief Executive

The BVOP Chief Executive is the core driver of the Business Value-Oriented Principles and the most advanced figure and leads the interest of the organization.

Get Certificate $1290   $720

Certified Program Director

The BVOP Program Director manages the entire Program Management Office and possess exceptional expertise and applies strategies.

Get Certificate $720   $490

Certified Agile Director

The BVOP Director is the most advanced and important role inside Agile products and services-based organizations.

Get Certificate $440   $220

Certified Project Manager

The BVOP Project Manager is an advanced and competent business, product, and technical role and a key factor for the success of the projects.

Get Certificate $280   $130

Certified Product Manager

With the advancing design, development, technical, and business knowledge, the BVOP Product Manager is a master role and decision-maker for the products.

Get Certificate $280   $130

Certified Product Owner

Responsible and skilled BVOP Product Owners balance both business and technical needs using Agile approaches and provide business value for products.

Get Certificate $180   $90

Certified Scrum Master

The BVOP Scrum Master role combines skills, Agile thinking, and project management practices to enchant processes, teams, and stakeholders.

Get Certificate $140   $70

Certified Human Resources Manager

People are the greatest assets of any organization. Balancing the people and organization needs

Get Certificate $140   $70