DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
The Latest "Software Integration: The Intersection of APIs, Microservices, and Cloud-Based Systems" Trend Report
Get the report
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Leadership Lessons for Creating High-Performing Scrum Teams

Leadership Lessons for Creating High-Performing Scrum Teams

After analyzing the traits that make a great team captain, we take a look at how these qualities apply to Scrum leadership.

Ron Eringa user avatar by
Ron Eringa
·
Sep. 28, 18 · Opinion
Like (2)
Save
Tweet
Share
6.51K Views

Join the DZone community and get the full member experience.

Join For Free

This is the last in a series of 3 blogs presenting the result of an interesting research study from Sam Walker.
Walker discovered that the most successful sports teams that ever existed all shared one single element: they all had a team captain with 7 overlapping traits that made them extremely successful. In this blog, we will explore what Agile Leaders can learn from these extremely successful team captains.

6 Lessons to Learn from Elite Team Captains

The Scrum Master role has a lot of overlap with the team captains from Walker's research.
Another overlap with Walker's research is the role of the sports coach: the Agile Leader, responsible for the Scrum Teams.

So, what lessons can Agile Leaders or Scrum Masters learn from these sports teams?

Lesson 1: Scrum Masters Make the Difference Between Good and Great Teams

Walker's research proves that having an inside Leader (or team captain) is the most important factor in making a team successful.
It wasn't strategy, management, money, or superstar talent that made the difference: 106 Teams had similar characteristics but all ended second place (the so-called Tier 2 teams). It was the presence of a Leader, fighting on the battlefield with the team, who made the difference between good and great.

In Scrum, it is the Scrum Master role who has most overlap with the captains from Walker's research.

In times of high pressure and when things get rough, the Scrum Master is the leader, working with the team from the trenches. For this reason, he will have the most impact on the teams' performance. No coach, manager or process can help a team better in these circumstances than the Scrum Master.

Lesson 2: Agile Leaders Enable Scrum Masters to Lead

Many Scrum Masters I encounter, only take up day-to-day routine tasks (such as hosting Scrum events and planning meetings), because their manager handles all leadership-related work.

The Tier 1 captains in Walker's research proved that their Leadership was most effective because they were part of the team. The duty of their coach was to create an environment that allowed this to happen.

An Agile Leader should help Scrum Masters to develop the character traits of a Tier 1 captain, so Scrum Masters can also become Agile Leaders. While some Scrum Masters might have a natural talent to lead, some will develop these talents along the way. The challenge for the Agile Leader is to understand when to delegate these responsibilities, once the Scrum Master becomes more mature.

Alex Ferguson, the legendary coach of Manchester United once said: "As hard as I worked on my own leadership skills, and as much as I tried to influence every aspect of United's success on the field, at kickoff on match day things moved beyond my control."

Lesson 3: Scrum Masters are Servant Leaders

We have come to expect that the best leaders are often those with:

  • Exceptional talent
  • Mesmerizing characters
  • High market-value
  • Superstar egos

The evidence Walker presents (the best team captains are Servant Leaders), proves that this is a distorted picture.

Many Scrum implementations I have seen reflect that same distortion. We often think that Scrum Masters are highly technical superheroes that follow orders from an even greater hero-leader. As a result Scrum Masters are often selected for their technical skills and their superhero status.
The most effective Scrum Masters I encountered had the character traits that Walker found in his research.

Walker's research proves that Scrum Masters do not have to be superstar heroes with deep technical skills. Instead, they should be humble, have a relentless drive to learn and play to win. While doing this, they should support team members in growing and becoming technical experts.

Lesson 4: Agile Leaders Are Also Servant Leaders

Walker could not find any evidence that the sports coaches (the equivalent of the Agile Leader) of the Tier 1 teams had a direct impact on their success. With regard to the contribution of the coach, his research led Walker to a number of conclusions:

  • The coaches were not prizewinning strategists
  • Most were not inspirational figures
  • The coaches did not have a big impact on a player's performance
  • Changing coaches had either no or a low impact (many of the Tier 1 teams coaches came and left during the bursts of success)
  • There were no real unifying principles/character traits like with the teams' captains

What these coaches did have in common:

  • They gave their captains the room to be a leader for their team
  • They all enjoyed close and contentious relationships with their captains
  • They all had been decorated captains before moving to their management position

This allowed them to understand what makes a good captain and identify the perfect person to lead the players.

All coaches of the Tier 1 teams understood that to achieve great success, they needed a player on the field who could serve as their proxy.

The consequence of delegating Leadership to a Scrum Master is that the role of the traditional manager will change. The focus of an Agile Leader might be different, but the roles and required skills/character traits have a lot of similarities.

True Agile Leaders are also Servant Leaders. They work closely together with the Scrum Masters and dare to step aside, once the game is on.

Lesson 5: Agile Leaders Create a Learning Environment

Walker's research shows us that being a great leader is not (always) genetically determined, it can be learned. All Tier 1 captains started off with having early struggles in their captaincy. These struggles lead to a breakthrough moment that left no doubt about their desire to win. As a result they focused, worked hard and pushed themselves and others to keep learning.

Coaches and managers of Agile teams need to create an environment where it's safe to fail and where people get enough opportunity to learn from their mistakes.

It is the Scrum Master's job to show the team how to be persistent in reaching their goals and learn from their mistakes.

Lesson 6: Positive Dissent Is Essential

Scrum uses closed feedback loops as a mechanism to continuously improve, eliminate waste and create incremental value. All Tier 1 captains from Walker's research understood that their teams needed positive dissent in order to make such a feedback loop work.

Like the captains in Tier 1, a Scrum Master needs to create an atmosphere in his team where conflicts are not driven by egos, but by the will to win.
To achieve such an atmosphere, a Scrum Master needs to act on the edge of the status quo.

To be excellent, it is sometimes necessary to challenge existing processes, bad decisions, or test the limits of existing rules.

Conclusion

One of the biggest struggles in becoming a true Agile Leader is to delegate responsibility. Walker's research shows that Leaders who are able to delegate these responsibilities to their Scrum Masters, create the most successful teams. If the Agile Leader and the Scrum Master work closely together, they can achieve amazing things!

Did you become curious about the role of the Agile leader? Come and experience it in my Professional Agile Leadership (PAL-E) training!

scrum agile

Published at DZone with permission of Ron Eringa, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • DevOps for Developers: Continuous Integration, GitHub Actions, and Sonar Cloud
  • How To Choose the Right Streaming Database
  • Solving the Kubernetes Security Puzzle
  • A Gentle Introduction to Kubernetes

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: