In the intricate world of SAFe 6.0, understanding roles, ceremonies, and their interplay is vital. Among these, a question that often emerges is about the Scrum Master’s participation.
Where should they be, and what role should they play?
Setting the Stage:
The Question at Hand When we discuss the Scrum Master’s attendance, four key ceremonies come to mind:
- A. Iteration Review
- B. Scrum of Scrums
- C. Daily Stand-Up
- D. PO sync
So, which meeting should the Scrum Master attend, but not facilitate?
The answer: Scrum of Scrums.
The Scrum of Scrums Explained:
To illustrate this, imagine the world of aviation. Each aircraft (or team) has its pilot (Scrum Master) guiding it.
Now, when pilots fly in formation, they need to be in sync, communicate seamlessly, and be aware of each other’s movements. The Scrum of Scrums is akin to the control tower where pilots (Scrum Masters) gather to discuss the broader flight plan, air traffic, potential hazards, and strategies to ensure all planes reach their destination safely and on time.
Here, the Scrum Master is not the controller but rather one of the pilots, sharing insights, challenges, and seeking solutions collectively.
Why Only Attend and Not Facilitate?
The Scrum Master leads team ceremonies, but the Scrum of Scrums is for Scrum Masters to collaborate and coordinate. It’s a platform for them to be team members, sharing their challenges and learning from peers. Facilitation in this meeting is often rotated or handled by a designated individual, ensuring that every Scrum Master can participate fully without the added responsibility of guiding the session.
In Conclusion, The SAFe 6.0 framework offers clear delineation of roles and responsibilities. For Scrum Masters, while they are the guiding force within their teams, they are also learners and contributors in the larger ART ecosystem. The Scrum of Scrums stands as a testament to this dual role, reminding us of the collaborative spirit of Agile.