Scrum Masters: Be Impediment-Removing Ninjas

DZone 's Guide to

Scrum Masters: Be Impediment-Removing Ninjas

A key focus of the Scrum Master is to remove impediments and distractions that might negatively impact the team’s progress or results – by any means necessary!

· Agile Zone ·
Free Resource

ninja star

The first thing that comes to my mind when I think about a ninja is the movie “Teenage Mutant Ninja Turtles” – the 1990 version, not the 2014 reboot. Modern culture views a ninja as a sort of superhero. According to Wikipedia, a ninja (or shinobi) was a covert agent or mercenary in feudal Japan. Folklore depicts the ninja as having legendary and often supernatural abilities. Sound like any Scrum Master you know?

You may also like: What Makes a Scrum Master Successful? Insights From 30 of the Best

The Scrum Master Ninja

The Scrum Master is responsible for ensuring Scrum is understood and enacted by the team, and also helps those outside the team interact with the Scrum Team in a way that maximizes the value created by the team. Sound like a ninja yet? Well, the Scrum Master also…wait for it – facilitates Scrum ceremonies. Now does it sound like a ninja? No? OK, another key focus of the Scrum Master is to remove impediments and distractions that might negatively impact the team’s progress or results – by any means necessary! 

OK, I added the “by any means necessary” part, but that isn’t too far off from how I’d expect a good Scrum Master to behave. Impediment removal is critical to creating an environment where the team can focus on their work and deliver quality and value. Anything that gets in the way of building teams, developing backlogs, and producing working, tested software is an impediment, an enemy that needs to be obliterated! Now we’re sounding more like a ninja.

The Enemy – Impediments

The enemy (impediment) can take many forms, can morph into other forms easily, and can also remain invisible for long periods. Some more common enemies may appear in the form of team dynamics challenges, transparency issues, poor communication, and logistical or technical blockers. Sometimes they are as unassuming as poor Scrum practices or mechanics, which are often simple to repair. More often, though, the enemy is a culture or mindset impediment. This type of impediment is frequently hidden behind visible symptoms, or disguised as something else.

Destroying impediments requires different tactics that depend on the enemy’s strength, frequency of attack and other factors. The first step to defeating your enemy is to know who your enemy is. How do we find impediments that aren’t visible?

  • Take Gemba Walks. Physically walk around the team and stakeholder areas, observing actions and interactions. Dwight Eisenhower once said: “Farming looks mighty easy when your plow is a pencil and you’re 1,000 miles from the cornfield.”
  • Pay close attention to non-verbal cues during Retrospectives and other feedback loops. Watch for team members rolling their eyes at others' comments, shaking their heads, giving heavy sighs.
  • Ask lots of questions. This seems obvious, but we all get bogged down in our daily routines and our battles that we sometimes forget there are others around us being attacked.
  • Study the Burn-down chart and other lifecycle tool reports and charts. Use the intel you have at your disposal to find potential weaknesses or opportunities.

Advanced Ninja Tactics

Battle plans and a field manual are great tools, but when you come face-to-face with the enemy, the experience is what counts. Here are a few advanced tips from experience in the field:

  • Don’t just focus on removing mechanical impediments of Agile and Scrum (the practices), but also guide Agile principles that make agility more sustainable in the long run. I once began coaching a Scrum team that looked, on the surface, to have it all together. They had all the right roles in place, their ceremonies seemed to be well run, and their artifacts appeared clean and up to date.
    • When I started asking questions about how they interact with each other, I found serious distrust between business and technology people, no face-to-face communication (nearly 100% email), and very little transparency or visibility into what the team was doing. Their mindset and culture were keeping them from realizing the full benefits of agility. Teams that possess solid Agile values are less likely to need you to repeatedly remove the same impediment. Ask tough questions about interactions and thought processes.

  • Utilize good questioning methods like the “5 whys” approach. By repeatedly asking the question “why?” we peel away layers of symptoms to get to the root cause.
  • Team up with other ninjas (good Scrum Masters and other leaders) to defeat systemic or enterprise impediments, and increase the effectiveness of Scrum in the organization. Remember, the Teenage Mutant Ninja Turtles were a team, not a singular turtle.
  • A master ninja multiplies their power by teaching others to be ninjas. Don’t remove all impediments yourself. Coach the person, not just the problem, and they will learn to remove their impediments better and be able to remove similar impediments in the future. Then, you can focus on removing those impediments that the team cannot remove themselves. Agile teaches people to think, rather than to just follow instructions.

Now What?

A ninja knows their objective and does not stop until the goal is achieved, sometimes running straight into the flaming arrows flying toward them. Attacking impediments requires preparation, courage, and tact. Ninjas are known as warriors – legendary, almost supernatural beings. Start your journey today to become an impediment-removing ninja Scrum Master. Pick an impediment from your list, choose your weapon, make a plan of attack, then run full speed toward the enemy – victory is yours for the taking!

Further Reading

Dear Scrum Master: The Scrum Events Are Theirs, Not Yours

The Path to Scrum Mastery: Top 5 Common Scrum Master Traps to Avoid

A Scrum Master Works on Three Levels

agile ,agile best practices ,agile development ,agile scrum ,impediments

Published at DZone with permission of Dwight Kingdon . See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}