With an objective to enable continuous learning and progression for our learners, PremierAgile curated several learning articles in the areas of Agile, Scrum, Product Ownership, Scaling, Agile Leadership, Tools & Frameworks, latest market trends, new innovations etc...
In the Scrum framework, a Scrum Master needs to wear several hats in different situations. While team coach and facilitator are some of the primary roles of a Scrum Master that come into mind, the overall purpose goes way beyond just setting up Scrum events, removing impediments, and encouraging the Developers.
While the books state the Scrum Master role as a "Servant Leader", the most crucial factor that determines the success of a Scrum Master is how much they are able to transform the Scrum Team as well as the organization.
Servant Leadership means leading the Scrum Team by serving them. Serving is about removing high-priority blockers. Leadership is no longer a given authority but provided as a service.
Servant leadership is a leadership philosophy in which the leader serves. Unlike traditional leadership, where the primary goal of the leader is to focus only on the success of the organization, a servant leader shares power, decision making, the needs and requirements of the employees, and helps them perform as a high-productive team.
A Scrum Master role is not performed as 'command and control' leadership but by 'empowering and enabling' teams. Scrum Master role is to improve the efficiency of Developers, Product Owner and, in fact the entire organization. The main focus of a Scrum Master is to enable an open mindset among various roles, units and leaders, in order to make Scrum create value for all the stakeholders.
Let's take a look at various hats that a Scrum Master wears.
A Scrum Master helps Scrum Teams and leaders in decision making. Thus, Facilitator is the hat you wear, well almost every day. Facilitation includes several responsibilities such as:
1. Sprint Planning
2. Sprint Review
3. Sprint Retrospective
Yes, a Daily Scrum is not facilitated by a Scrum Master unless the Development asks to. Instead, the Scrum Master should focus on making the Developers self-organized so that they can conduct their own Daily Scrum, in order to make a plan on how to execute the work in the reminder of the Sprint.
It is possible that a Developers or a Product Owner or a stakeholder do have conflicting opinions, and it is challenging to arrive at a decision. A Scrum Master facilitates in such a situation, helps to arrive at a decision. A facilitator takes a neutral stance viz. doesn't take either of the sides, helps the participants to discover new ideas, different paths of problem solving and channelizes the discussions towards a decision. A facilitator may ask critical questions to ignite the thought process within the participants.
This hat reflects the "Servant" facet of the Scrum Master role. Since Scrum Master responsibilities includes eliminating impediments that paves way for faster delivery, it will be one of the top responsibilities for the Scrum Master.
The Scrum Team can run into various impediments. For example, lack of skills, knowledge gap, unstable test environment, unavailability of Product Owner or a stakeholder, and various other factors. In such instances, the Scrum Team members will look up to you for resolving the impediment as soon as possible. Serving and supporting the team helps you establish a great teamwork atmosphere and promote faster delivery.
As per Wikipedia, Coaching is a form of development in which the coach supports a learner or client in achieving a specific personal or professional goal by providing guidance. The learner is sometimes called a coaches.
The coach unlocks the coachee's potential to maximise the coachee's performance. It is helping them to learn rather than teaching them to do.
A Scrum Master acts as a coach at times. Rather than providing decisions to the Scrum Team or the organization, the Scrum Master helps to decide what is the best course of action to be taken in each situation. To help people grow and improve, you don't have to do their work but enable them to find the ideal, most suitable way of working. This work is more oriented towards people where the ultimate goal is to help people and organizations grow and become better. A Scrum Master needs to guide people without being bossy or authoritative, which is considered as one of the most challenging facets of the job. To perform this responsibility better, a Scrum Master should have good analytical skills, good negotiation skills, good communication skills. But more importantly, the Scrum Master should have great listening skills.
A Developers is 'self-organizing' and 'cross-functional'. For organizations going through a transformation, technical expertise may be required until Developers become cross-functional. There is a need to introduce engineering practices that help to develop high quality products. Therefore, a Scrum Master with technical expertise would readily need to wear the corresponding hat to introduce technical practices, coach Developers hands-on until they become more independent.
Some examples where technical coaching will be useful are (but not limited to):
A Scrum Master acts as a mentor at times, based on the experience gathered over the years. During a difficult situation, the Developers may look up to Scrum Master as a mentor to resolve their impediments. Or the Product Owner may need help about various techniques available in the industry to prioritize the Product Backlog.
These are situations, where the Scrum Master can utilize their experience to solve a problem and help the Scrum Team.
The Scrum Master wears the hat of a teacher at times. You may have to teach the Scrum Team, the organization, stakeholders about the following:
The Scrum Master also helps the organization to plan and adopt Scrum in the organization.
Besides focusing on continuous improvement, a Scrum Master also needs to focus on people and their emotions, personalities, and experiences. One should also ensure a sustainable development, so that the Scrum Team as well as the organization sustain over a longer period of time. A Scrum Master needs to always ask - Do you want to go faster, or do you want to go longer?
Large organizations are looking for Scrum Masters who can be change agents and not just coordinators. They are looking to leverage the Agile way to working to build awesome products & services, in evolving market conditions and changing customer preferences. While you need to wear different hats as a Scrum Master, it is improbable for someone to excel in all these aspects right away. Like for the teams and organizations, it is also a continuous learning journey for the Scrum Masters too.
The key to becoming a successful Scrum Master is to be Agile yourself and ready to wear different hats as per the situation.