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.
To read all articles of this series use this link: What It's and What It's Not series for CIPSA.
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.
.png)
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.
CIPSA – 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:
CIPSA Sample Questions:
CIPSA Certification:
No comments:
Post a Comment
Sign- or Log-in and put your name while asking queries in comments. Any comment is welcome - comments, review or criticism. But off-topic, abusive, defamatory comments will be moderated or may be removed.