Scrum at Scale with CIPSA: The Principal Scrum Master (PSM) – What It Is and What It’s Not!

 

In the CIPSA Scrum Framework, in addition to the primary role of Chief Product Owner, we also have the Principal Scrum Master (PSM). This role is necessary to have Scrum at Scale with CIPSA. Unlike the Individual Teams’ Scrum Masters, the role and responsibilities of the PSM are different. It’s a very important role to have in order to succeed at Scale. 

In this post, we will explore more on the Principal Scrum Master role as there are a number of misconceptions and misunderstandings. It’s presented in the form of what it is and what is not, to provide greater clarity.  

The following are some of them. To read all articles of this series use this link: 

What It's and What It's Not series for CIPSA. 

Principal Scrum Master – What It Is and What It’s Not

1. Not Manager, but Leader who Serves: The Principal Scrum Master is not the manager of the CIPSA team. The Principal Scrum is a true leader who serves the team and organization.

The Principal Scrum Master leads by serving, not managing. The PSM focuses on team and organizational needs.

2. Not Intra-Team, but Inter-Team Focus: The Principal Scrum Master is not concerned about intra-team dependencies. The Principal Scrum Master focuses on inter-team dependencies.

Rather than resolving team dependencies which are internal, the Principal Scrum Master addresses coordination across multiple teams. The PSM manages dependencies that span beyond one individual Scrum Team.

3. No Team Tracking, but Product Tracking: The Principal Scrum Master does not track the individual Team Increments. The Principal Scrum Master tracks the overall product work and progress.

The focus of a PSM isn't on individual Team Increments, but on the unified or Integrated Increment. This ensures the overall product progress aligns with strategic objectives.

4. Not Fragmented, but Unified Communication: The Principal Scrum Master does not communicate like individual Team Scrum Masters. The Principal Scrum Master is the main communicator for and of the CIPSA Team.

The PSM provides a unified voice to upper management. Communication is consolidated through the Principal Scrum Master. This ensures alignment across teams rather than fragmented messaging from and for each Scrum team. 

The PSM is the main spokesperson for the CIPSA team.

5. Not Reporting, but Enabling Progress: The Principal Scrum Master is not a chief-clerk or secretary responsible for reporting the status. The Principal Scrum Master enables progress for the entire CIPSA team.

The PSM don't just gather updates and report status for the CIPSA Scrum team. The PSM actively remove obstacles and facilitate progress. This role is about driving momentum, not about reporting status as chief-clerk.

6. Not Spot Checks, but Systemic Resolution: The Principal Scrum Master does not check for issues and impediments of individual teams. The Principal Scrum Master ensures that cross-team issues are addressed and cross-team impediments are removed.

Instead of isolated checks, the PSM drives solutions to broader, recurring impediments. It's also about issues impacting multiple teams. The approach taken by the PSM is proactive and system-wide.

7. Not Replacement, but Coordination: The Principal Scrum Master does not replace the responsibilities of individual Scrum Masters. The Principal Scrum Master complements their efforts by coordinating cross-team work.

The Principal Scrum Master doesn't take over individual Scrum Masters’ roles. Many have this misconception! Instead, he or she coordinates and supports cross-team initiatives. 

The PSM complements, not replaces, the individual Team Scrum Master.

Summary Table – Principal Scrum Master 

For quick remembrance and recall, a summary table is shown below. 

Closing Remarks

It’s the PSM who ensures the CIPSA meta-events are conducted in a positive manner and are productive. Do remember that these meta-events are timeboxed. 

While going with Scrum at Scale with CIPSA, the key focus is on the CIPSA Integrated Increment. Ultimately, that’s artifact that matters! The PSM plays an indispensable role in having the Integrated Increment. See here.

Want to learn more with hands-on practical applicability with software tools?

Consider being a CIPSA professional. You will get the highest possible return on your investment. 

What It's and What It's Not Series:

All Articles in What It's and What It's Not - CIPSA

CIPSA Sample Videos and Questions:

[1] CIPSA Sample Video List (Choose a Video)

[2] CIPSA Video Playlist (Complete Playlist)

CIPSA Sample Questions:

[1] CIPSA Certification Sample Questions (Part - 1)

[2] CIPSA Certification Sample Questions (Part - 2)

CIPSA Certification:

[1] NEW Scaled Agile Certification Course: Certified In Practical Scaled Agile (CIPSA)

[2] Frequently Asked Questions (FAQs) - CIPSA Certification  

[3] New Practical Scaled Agile Framework – The CIPSA Framework Guide

[4] Understanding the CIPSA Scrum Framework – Practical, Hands-on Scrum at Scale

[5] The CIPSA Framework Clock - A Unique Way