Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Scrum Guide for Leaders – Supporting the Scrum accountabilities/roles

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

We started the Scrum Guide for Leaders series with a discussion of what Scrum means for you as a Leader. Next, we discussed the conditions where Scrum’s Empiricism, Self-Management, and Continuous Improvement can thrive. We then explored some concrete examples of how adopting the Scrum Values as a Leader can help you create these conditions.

Next, We are turning to the Scrum accountabilities/roles. This article provides a concise introduction of the 3 accountabilities on the Scrum Team. We mainly focus on considerations from a Leader perspective for how to create the conditions where the people in the Scrum accountabilities can succeed in their roles.

Scrum Team

The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. 

Scrum defines some boundaries for the exercise of figuring out Scrum Teams. Scrum Teams have a certain effective size. A person should ideally be on one Scrum Team. Each Scrum Team should commit to pursuing Product Goal. 

While the Scrum Guide does not explicitly talk about anyone outside of the Scrum Team, Scrum assumes organizational leadership and support. 

Leaders have the role of leading the process of creating and nurturing a portfolio of Scrum Teams that execute the organization’s strategy. They have to courageously choose which areas to focus on and set concrete Product Goals to organize the Scrum Teams around. 

Leaders will need to bridge the gap between the current organizational capabilities and the strategic needs. They’ll need to have open conversations with the right people about the options and implications. They will have to apply some pragmatic choices while committing to working to close strategic gaps. 

They need to learn about the different accountabilities on the Scrum Team, figure out how to map them to different roles and people in the organization, and model/support the behaviors that lead to success with Scrum. 

Product Owner

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. 

Identifying the right Product Owner is a crucially important Scrum design decision that Leaders of the organization need to think through. As the Scrum Guide states “For Product Owners to succeed, the entire organization must respect their decisions”. That typically means a certain level of seniority. Can these senior people spend the necessary time with the Scrum Team? Even if these “just right” Product Owners exist in the organization, the Leader might struggle to get them to be available and interested to become a Product Owner. 

Product Owners should ideally be entrepreneurs caring deeply about the product and its customers (internal or external). If it’s hard to find a Product Owner it might be a signal to inspect whether we organized the Scrum Team around a real Product. Identifying Products (whether they are real Products or other valuable internal/external services) is a key leadership exercise. It is tempting to skip it and just organize Scrum Teams around the existing organizational structure rather than “rocking the boat”. Leaders that want to maximize the benefits they get from Scrum and Product Ownership have the courage and willingness to reflect openly on how their organizational structure aligns with their strategy and vision. They are committed to organizing their teams around products and value. 

Stakeholders

While Stakeholders aren’t an explicit accountability/role in Scrum, effectively working with Stakeholders is crucial to value creation. Stakeholders should respect the Product Owner’s accountability and the direction they’re steering the Scrum Team towards. The Leader might need to intervene as well as lead by example, being a stakeholder themselves.

Leaders can help a Product Owner identify and access Stakeholders. They can empower the Product Owner to innovate with their team. They do this by collaborating with the Product Owner and the Stakeholders to establish a clear and agreed-upon Product Goal that the Scrum Team would be committed to strive towards.

Once a Product Goal is defined, Stakeholders should respect the Product Owner’s accountability. The Leader might need to help the Product Owner shape the Stakeholder interactions.

 

Developers

Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. 

By saying Developers the Scrum Guide doesn’t necessarily mean software developers. The Scrum Guide refers to Developers as anyone responsible for developing a valuable Increment. This can include business analysts, testers, marketers, project managers, or anyone else. 

Leaders should figure out how to identify the right set of Developers that together have all the skills necessary to create and deliver valuable Increments towards the Product Goal

When identifying Developers for Scrum Teams there are a number of tensions that will become evident. These tensions include:

  • Creating a team that has enough skills to deliver value – Minimizing dependencies on people outside of the team while being small enough to have effective collaborations. 
  • Managing Specialists – Many organizations encourage and reward people who are specialists in a particular skill set or domain. A Scrum Team needs to be focused and include all the necessary skills to deliver value. Deciding where to put specialists is a key decision made by leaders. 
  • Managing ‘Resources’ – Scrum encourages organizations to think of people as people rather than resources and encourages stable teams. However many organizations apply the mindset of resource optimization and treat people as interchangeable parts. A Leader will have to spend time managing this disconnect. 
  • Dependency Management – There is never an ideal Scrum Team and it will always require help and support from other teams or service departments. The Leader’s job is to ensure that the right compromises are made and when presented with opportunities for improvement as the Scrum Team operates to be able to make changes. 

Addressing these tensions will require some tough choices as well as the investment of time/money with a mid/long-term perspective. 

Scrum Master

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.

“Scrum Masters are true leaders who serve the Scrum Team and the larger organization” 

The effective Scrum Master combines a facilitator, coach, teacher, mentor, change agent, and impediment remover. Helping everyone means also being available to Leaders and Stakeholders.  

In reality, we more often find Scrum Masters that act as scribes/secretaries/clerks for their teams, admins, project or people managers, heroes taking all the burden of delivery on their shoulders, or the Scrum police. They struggle to coach the organization and its leaders/stakeholders whether because of their abilities/experience or how they are perceived/positioned. 

The Scrum Master role is a unique one that doesn’t map easily to current organizational structures or areas of expertise. Most environments and cultures struggle to cultivate effective Scrum Mastery or leaders who serve in general. 

Leaders have the role of identifying effective Scrum Masters for their teams that would be respected and listened to at the team and organizational level as trusted advisors/partners.

The Scrum Master is accountable for the success of Scrum within the Scrum Team. That success relies on the right culture/environment which requires partnership with Leadership. 

Leaders need to be open to feedback/coaching from about their behavior and their organizational choices. They need to commit to working with the Scrum Master on addressing systemic impediments that limit the team’s potential. 

Leaders should consider the following when working with Scrum Masters:

  • Career path – Scrum Master isn’t necessarily a career path. It’s an accountability that requires certain competency. Having said that, Leaders looking to find great Scrum Masters for their teams need to figure out as well as provide transparency to how being a Scrum Master would support people’s career growth. 
  • Reporting Structure – Setting the Scrum Master up for success means figuring out a reporting structure that enables the Scrum Master to be honest and open with minimal risk of repercussion. For example, If the Scrum Master reports to the Product Owner it might make it hard for them to be honest and open about their challenges. If they report to the same people as the Developers there might be a lack of understanding for their role. A Scrum Master that’s outside of the Scrum Team’s reporting structure coming in as either an internal or external “consultant” provides certain benefits but carries certain disadvantages as well. Finding the right reporting structure is difficult and depends on both the situation and the people in the role. Leaders apply empiricism to figure out this complex problem. This means trying out a certain pattern, inspecting its impact, and amplifying or pivoting away as needed. The fact that these “experiments” involve human beings makes them even more complex and sensitive. 
  • Measurement – By putting in place the right measures a leader can clearly define what outcomes they are looking for, but deciding the right measures is often difficult and can become political. 
  • Title – There is much debate in the industry as to what job title is held by a Scrum Master. The Scrum Guide describes Scrum Master as an accountability highlighting that the job title will depend on the organization. For many organizations, Agile Coach may be the right job title. Deciding on the job title helps set the scene for the role and helps with recruiting. But more important to the actual title is the reasoning for the title.
  • Teams Supported – Depending on the maturity of the teams, the complexity of the problems they are solving or the constraints of the situation the Leader must decide on how many Scrum Teams the Scrum Master supports. Leaders in many cases face the tradeoff between having a few passionate and effective Scrum Masters covering multiple teams, versus having a Scrum Master for each team that is also a Developer on that team and sees Scrum Mastery as their secondary accountability. Again, no clear choices here, but aim to have Scrum Masters who are passionate about Scrum Mastery and see it a key part of their career journey. 
  • Employment Status – Each situation is different but making decisions about if the Scrum Master is better served as an external contractor, or an internal employee requires some level of thought and choice. Both approaches have merit. Think of the courage the Scrum Master might have to “speak to power”. The openness people in the organization and team would have to listen to their ideas. The commitment the Scrum Master would have to the team and the organization. The respect they would garner from the Product Owner, Developers, Leaders, Stakeholders. And how much they will be able to focus on helping the Team. 
  • Where Scrum Masters come from – Often organizations naturally think that Project Managers should be the place Scrum Masters are recruited from. Project Management is a different, somewhat overlapping set of skills that may or may not house good Scrum Masters. Leaders should understand the Scrum Master accountability and open a wide aperture to find the right people for the role wherever they are in the organization. Sometimes, the right Scrum Master for the job is found by looking at the mirror…

Whether the Leader chooses to be a Scrum Master or not, they should draw upon the accountabilities, skills, and stances of the Scrum Master. By doing this they can better serve the team and the larger organization.

In Summary

As we’ve seen, the Leader has many considerations and intervention opportunities when it comes to choosing the right structure and people for Scrum to succeed and for agility to be unlocked.

While the Leader isn’t mentioned explicitly as a role/accountability in the Scrum Guide, Scrum will not succeed without Leaders taking on themselves the accountability to set up Scrum Teams for success and continuously inspecting and adapting the structure based on transparency Scrum generates.

One key point here is to avoid analysis paralysis. While the complexity of setting Scrum the right way seems daunting, the right move is to start, see, adapt rather than spending many hours or weeks on perfecting a roles and responsibilities plan or waiting for the perfect people for the role. You’ll learn much more by just starting – both about what surprisingly works better than expected as well as what doesn’t.

In the next article in the series, we will turn our attention to the Scrum Events and how the Leader can best interact with them and support the Scrum Team in using them.

Subscribe for Email Updates:

Categories:

Tags:

AgileSparks
Applying Agile Methodology
Portfolio for Jira
Kaizen Workshop
Lean Agile Organization
What Is Kanban
Agile Release Planning
Agile Testing Practices
Team Flow
Slides
BDD
Scrum Master Role
Enterprise DevOps
Elastic Leadership
Spotify
Planning
Self-organization
Achieve Business Agility
Built-In Quality
chatgpt
Kanban Game
Kanban
Scrum Master
Jira Plans
Lean Risk Management
Development Value Streams
Agile Basics
Agile Exercises
Agile Marketing
agileisrael
LPM
Managing Risk on Agile Projects
Daily Scrum
Sprint Planning
lean agile change management
Value Streams
Agile Israel Events
Product Management
Large Scale Scrum
Business Agility
Kanban Basics
SAFe DevOps
Webinar
Legacy Code
Artificial Intelligence
Nexus and SAFe
RSA
POPM
Code
NIT
Software Development Estimation
ART Success
PI Planning
Implementing SAFe
Coaching Agile Teams
Agile
Risk Management on Agile Projects
RTE Role
Pomodoro Technique
ALM Tools
Games and Exercises
Lean and Agile Principles and Practices
Lean-Agile Software Development
GanttBan
Lean Agile Basics
The Kanban Method
Agile Product Ownership
SAFe
System Integration Environments
Legacy Enterprise
Video
Agility
Scrum
Story Slicing
Agile Delivery
Principles of Lean-Agile Leadership
Operational Value Stream
Lean Agile Management
Limiting Work in Progress
Keith Sawyer
ATDD
PI Objectives
Agile Project Management
Agile Israel
Jira admin
Scrum.org
LeSS
Agile Product Development
Agile Outsourcing
Continuous Integration
Agile Games
Hybrid Work
Rapid RTC
The Agile Coach
Agile Development
AI Artificial Intelligence
Scrum Values
Agile Assembly Architecture
Jira Cloud
System Team
Continuous Delivery
Agile India
Frameworks
System Archetypes
Sprint Iteration
User stories
Lean Budgeting
Systems Thinking
Presentation
TDD
Agile Release Management
Release Train Engineer
Lean Agile Leadership
predictability
Nexus Integration Team
Lean Startup
Kanban 101
Manage Budget Creation
ScrumMaster Tales
WIP
SA
Test Driven Development
ATDD vs. BDD
Advanced Roadmaps
Professional Scrum Product Owner
EOS®
RTE
SPC
Releases Using Lean
Certification
Agile Risk Management
Introduction to ATDD
Agile and DevOps Journey
Scrum and XP
Agile Contracts Best Practices
SAFe Release Planning
Continuous Improvement
Agile in the Enterprise
Agile Project
Engineering Practices
Scaled Agile Framework
Accelerate Value Delivery At Scale
Software Development
speed at scale
Change Management
AI
Lean-Agile Budgeting
Reading List
Kaizen
Jira
Continuous Planning
Lean and Agile Techniques
A Kanban System for Software Engineering
Process Improvement
Scrum Primer
Amdocs
Tips
Scrum With Kanban
ARTs
An Appreciative Retrospective
Professional Scrum with Kanban
Atlaassian
Agile Mindset
Lean Agile
Covid19
Program Increment
Agile Community
LAB
Acceptance Test-Driven Development
Perfection Game
Continuous Deployment
Risk Management in Kanban
Entrepreneurial Operating System®
Sprint Retrospectives
Professional Scrum Master
Scrum Guide
Certified SAFe
Iterative Incremental Development
Nexus and Kanban
DevOps
QA
Risk-aware Product Development
Product Ownership
speed @ scale
IT Operations
Atlassian
Nexus
Kanban Kickstart Example
Tools
Agile Games and Exercises
Nexus vs SAFe
ROI
Introduction to Test Driven Development
Quality Assurance
Agile Program
Managing Projects
Effective Agile Retrospectives
Agile Techniques
Implementation of Lean and Agile
Agile for Embedded Systems
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart