The Certified In Practical Scaled Agile (CIPSA) courseworld’s only Practical Scaled Agile certification, where you learn scaling with your own hands. It’s also highly economical.
The below second trailer (1m: 4s) informs more. For the best experience, go full-screen HD mode and plug-in your headphones. For the earlier one, see here.
A tabular differentiation is shown below. Do note that CIPSA supports both Scrum at Scale and Kanban at Scale. There are many differences compared to other Scaled Agile certifications; I've outlined a few.
For example, cadence management for Kanban at Scale is complicated, but with CIPSA, you'll learn it in-depth. Similarly, you'll have visualizations with Cumulative Flow Diagrams (CFD), determining WIPs, among others.
To know more about the CIPSA certification course, see here.
For this course, many FAQs have been answered. See here.
In the CIPSA Kanban (not Scrum!) Framework, one key primary role is that of the Principal Flow Master (PFM). Very few Scaled Agile frameworks, if any, support team-level Kanban. CIPSA is unique not only in its practical, hands-on, tool-driven approach but also in its support of Kanban.
As the PFM role is new and not available in most Scaled Agile approaches, it is often misunderstood. Note that this role is unique to CIPSA certification.
In this post, we will learn more about the PFM role and how it differs from the individual team-level Flow Master. In addition, we will explore what this person actually does. This post explains “what it is and what it is not” to bring more clarity.
Principal Flow Master – What It Is and What It’s Not
1. Not a Manager, but an Enabler: The Principal Flow Master is not the manager of flow for the CIPSA team. The Principal Flow Master enables the flow for the CIPSA team.
This role of the PFM is not about command and control, but about creating the conditions for flow to happen naturally for the CIPSA Kanban team.
2. Not Intra-, but Inter-team: The Principal Flow Master is not concerned about intra-team bottlenecks. The Principal Flow Master is focused on inter-team bottlenecks (in flow).
The focus of the PFM is on how teams interact, not how they operate individually. The PFM looks for inter-team bottlenecks and works to remove them.
3. Not Team Metrics, but Product Flow: The Principal Flow Master does not track the individual Kanban team Increments. The Principal Flow Master tracks the overall product work and progress.
The PFM does not micro-manage team Increment or team-metrics, and indeed, he or she plays no role in that! The goal is to maintain visibility into the flow of value at the product or system level.
4. Not Local Fixes, but Systemic Resolution: The Principal Flow Master does not check for the issues and impediments within individual teams. The Principal Flow Master ensures resolutions of cross-team issues and removal of cross-team impediments.
It’s well-known in management that local issues are best handled by the team itself. The Principal Flow Master, on the other hand, focuses on complex, multi-team issues that block the CIPSA Team’s overall flow.
5. Not Individual Team Risks, but Cross-team Risks: The Principal Flow Master is not concerned about individual risks arising within individual teams. The Principal Flow Master is focused on cross-team risks.
Cross-cutting risks can impact multiple areas and jeopardize delivery. It’s the job of the PFM to manage the. By managing them, the CIPSA Team can have smoother coordination and predictability.
6. Not Setter, but Facilitator of WIP Limits: The Principal Flow Master does not set the work in progress (WIP) limits. The Principal Flow Master supports the team in deciding the WIP.
WIP can be set for the workflow states in the CIPSA Kanban Board. The CIPSA Team is trusted to self-regulate their capacity. The PFM’s role is to facilitate, not impose it.
Principal Flow Master – Summary Table
The following table contrasts common misconceptions with the true nature of the role of PFM, highlighting key differences in focus and approach.
Live Video Explanation
For the PFM role, I've prepared the below video [duration - 13m: 30s]. I've also explained the false pride in having "branded" certification. A certification should be useful to you. Watch the video alongside this article for a better learning experience. Plug-in your headphones and go full-screen HD.
Conclusion
The Principal Flow Master (PFM) plays a facilitative and enabling role, rather than a directive or managerial one. The PFM’s focus is not on managing individual teams or resolving team-specific issues, but on fostering cross-team alignment, enabling flow, and removing bottlenecks that hinder the CIPSA team’s ability to deliver.
Just as the Principal Scrum Master (PSM) is a key role in CIPSA Scrum (see here), the PFM is also a vital and indispensable role in CIPSA Kanban. Like the PSM, the PFM is a leader who servers the CIPSA Kanban team. However, unlike the Scruma@Scale+CIPSA mindset for the PSM, the thinking here for the PFM must be rooted in Kanban@Scale+CIPSA mindset.
The above list of “what it’s and what it’s not” is a partial and brief one.
Want to learn more with hands-on practical software tools?
Want to know how the PFM is assigned and part of the Flow Master group?
Want to visualize the workflow across the Integrated Kanban Board at Scale?
Want to build the Cumulative Flow Diagram (CFD) at Scale?
Want to resolve overallocations for Kanban at Scale?
Want to determine the Work in Progress Limit (WIP) at Scale?
To gain in-depth knowledge on all the above and more, consider being a CIPSA! You’ll learn Kanban at Scale in a hands-on manner with direct usage of software tool. The course is thoroughly practical and highly economical.
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:
Principal Scrum Master – What It Is and What It’s Not
1. Not Manager, but Leader: 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: 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. Not 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: 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: 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 a Replacement, but a Complement: 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.
Live Video Explanation
The below video [duration - 10m: 08s] will further consolidate your understanding. Watch the video alongside this article for a better learning experience. Don't forget to plug-in your headphones and go full-screen HD.
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 software tools?
Want to know how the PSM and CPO are assigned?
Want to visualize cross-team dependencies for the entire CIPSA team?
Want to assign resources for Scrum at scale?
Want to resolve overallocations for Scrum at scale?
Consider being a CIPSA professional. You will get the highest possible return on your investment.
The Certified In Practical Scaled Agile (CIPSA) courseis highly practical and economical. It's world's only Practical Scaled Agile certification, where you learn scaling with your own hands.
Complex concepts are explained with simple lessons, and you will get an unforgettable certification. The below trailer (1m: 1s) informs more. For the best experience, go full-screen HD mode and plug-in your headphones.
A brief tabular differentiation is shown below.
To know more about the CIPSA certification course, see here.
To have the complete course breakdown, check here.
For this course, many FAQs have been answered. See here.
If you have any other questions or clarifications, please send an email to managementyogi@gmail.com.