Every team member has a unique spark that might light up the entire team if aimed in the proper direction, and the ScrumMaster can ignite this spark. ScrumMastering can be visualized as an art that requires a good amount of investment to master and excel. It comes with experience working with teams on the ground and being present in the moment. It cannot be acquired simply by reading books.
The ScrumMaster is a constantly evolving role, which metamorphoses from a coach, facilitator, and servant leader to a change enabler/influential cheerleader and an evangelist. My personal experience is that the ScrumMaster continually switches these hats, and many others, based on the need of the hour.
The saying goes that a smooth sea never made a skilled sailor. A ScrumMaster would not be able to experience the richness of this role unless he or she gets an opportunity to wear these different hats and live the role and experience the turbulence of change.
Here are a few arts that the ScrumMaster must master for the ship to sail through turbulent seas!
- Art of mastering Scrum knowledge. The ScrumMaster is considered a “master of Scrum,” one who understands and can articulate Scrum from the value perspective. One of the prime responsibilities is to ensure that teams understand and enact Scrum well.
- Art of keeping a neutral mindset. A ScrumMaster is empathetic, approachable, and unbiased while talking to team members so that he or she understands the different perspectives.
- Art of asking powerful questions. The ScrumMaster uses powerful, open-ended questions to enable the team to think through their current state by asking: “Who can do this? Who is interested? How can we solve this?” and “What are the available options?”
- Art of facilitating constructive disagreements. The ScrumMaster facilitates discussion among team members that helps them assess the situation, generate options, and determine a right course of action.
- Art of igniting the need for reflection. The ScrumMaster coaches the team on the benefits of continuous improvement cycles and strives to lead the retrospectives using various innovative and creative techniques to make them interesting and lively.
- Art of driving self-realization. The ScrumMaster helps teams self-reflect and come up with what works, given the situation and context of the teams.
- Art of shielding the team. The ScrumMaster shields the team from external and internal distractions to make sure that the team can focus on the current sprint goal. The ScrumMaster protects the team like a sheep dog from outside interference and serves the team by removing impediments so that the team can focus on the sprint goal.
- Art of facilitation. The ScrumMaster facilitates the Scrum implementation across teams, keeping in mind the purpose of each event to ensure that the goal is realized. The ScrumMaster also strives to keep them effective and engaging by using effective facilitation techniques like timeboxing, focus, engagement, and visualization.
- Art of interpreting team behaviors. The ScrumMaster masters the art of understanding team dynamics, is approachable, and coaches members one-on-one to transform them into a high-performing team.
- Art of communicating. The ScrumMaster is an excellent communicator, often acts as a liaison between the team and the product owner, and is great at articulating and communicating the right things in a timely manner.
- Art of listening. The ScrumMaster is a patient and persistent listener who understands an individual’s emotions and concerns, including those of the people who don’t speak up.
- Art of nurturing an environment for celebration. The ScrumMaster fosters an environment in which team efforts are rightfully rewarded, thereby ensuring that the team stays focused and motivated throughout.
- Art of radiating information. The ScrumMaster understands the importance of radiating as much information as possible and guides the team to effectively use the information radiators.
- Art of building trust within the team. The ScrumMaster strives to build trust within the team so that its members are eventually courageous enough to voice their opinions, willing to share their work, and thus collectively focus on the team goal.
- Art of role modeling. The ScrumMaster, while coaching other ScrumMasters, behaves as a role model and becomes an embedded ScrumMaster so that others learn by observing!
- Art of influencing and enabling organizational changes. The ScrumMaster is able to influence and drive organizational changes to ease the ecosystem into the Scrum journey. He or she looks out for systemic impediments in the organization, thus enabling their timely resolution. The ScrumMaster has mastered the art of influencing and bringing about effective changes that are conducive to the Agile culture working, such as changing the way team members are appraised.
- Art of exhibiting situational leadership. Team formation typically follows the stages of forming, storming, norming, and performing. The ScrumMaster works with teams in each of the stages as per Blanchard and Hersey’s delegating leadership style. This kind of leadership model is called situational leadership.All teams do not necessarily go through all four stages in a sequential manner; they wobble back and forth between stages, particularly when new team members are added or existing ones leave the team. The ScrumMaster is aware of these different stages, looks for signs in each of the stages, and coaches the teams accordingly. An effective ScrumMaster can actually reduce the journey time from the forming to the performing stage.
Tips for easing the ScrumMaster’s Agile journey
- Detect the team dysfunctions, as described in Patrick Lencioni’s book The Five Dysfunctions of a Team. For example, if you notice there is absence of trust in the team, focus on promoting constructive disagreements and try to foster an open culture. If one notices there is lack of accountability, focus on coming up with team-working agreements.
- Watch out for team behavioral problems, such as individual silos, heroism, resistance to change, inhibitions, waiting for task assignments, looking up to the ScrumMaster as a problem solver, and management asking for status reports.
- Watch out for team-practice issues, such as
- Never-ending meetings
- Team waiting for input from the product owners during sprints
- Team experiencing many quality issues after sprints
- Same patterns of problems arising within the teams
- Too much work-in-progress during sprints
- Many interdependencies cropping up; managing dependencies becomes a nightmare
- Dedicated hardening sprints
- Sprint planning meetings always ending in surprise
- Occasional system crashes during sprint reviews
- Check the health of the Agile adoption by holding regular checks-ups.
- Check the team’s cross-skills health and promote cross-learning so that team members can swarm to complete what had already been started instead of starting with new items.
A ScrumMaster is more than a leadership role, as he or she leads the team by example and is adaptive to the changing environment, like a chameleon responds to changes. The ScrumMaster thrives on the philosophy of, “Don’t catch me a fish, but teach me to catch one.”
There are five levels of Agile leadership, according to Leadership Agility: Five Levels of Mastery for Anticipating and Initiating Change: Expert, Achiever, Catalyst, Co-Creator, and Synergist, by William Joiner and Stephen Josephs. Research shows that most of the crowd is at the Achiever level, whereas the need for today’s environment is to transcend to the Catalyst and Co-creator levels. The ScrumMaster must be able to operate beyond the Expert and the Achiever levels to be instrumental as a servant leader and a change agent.
A ScrumMastership is a journey, and it could take years to reach to a stage of a leadership role! The sooner the ScrumMaster gets the teams self-organizing, the better he or she can watch out for things beyond the team level, thus helping the organization and business units with their Agile journey.
ScrumMasters can potentially coach organizations as they navigate through the organizational turbulence of change and become versatile enough over time to handle any kind of turbulence with ease. However, it takes time to get to this stage, but the investment is totally worth it!
Originally Posted by Madhavi Ledalla @ Scrum Alliance on 19 January 2017