![]() Scrum of Scrums is widely used and a key way to scale scrum. A representative of each team or the product owner should discuss team impediments, risks to achieving the sprint goal or dependencies on other teams followed by discovered improvements that can be leveraged by other teams. These new roles use the 15 minutes scaled daily scrum as a key meet-up align, improve and tackle impediments. This role doesn't need to be performed by a dedicated person and the role should have the same responsibilities as a product owner, just at scale.Īnother new role is the Scrum of Scrum Master, who should focus on progress and impediment backlogs visible to other teams, facilitating prioritization or removal of impediments and continuously improving the effectiveness of the Scrum of Scrums. The chief product owner is responsible for overseeing the product owner team and helping to guide the overarching product vision. To deliver an integrated, potentially shippable product at the end of every sprint, additional roles might be required, like architects or quality assurance leaders.įor instance, there is the Chief Product Owner role. That said, if it is working, please don’t stop doing it… yet don’t feel you must do it because of adopting LeSS.The newly formed Scrum of Scrums team applies nearly the same practices, participates in the same events, and has the same roles as a Scrum team. Scrum of Scrums isn’t a part of LeSS and as a more formal centralized coordination technique, it is also not recommended. Typically held two or three times per week. This is how LeSS (Large-Scale Scrum) puts it:Ī Scrum of Scrums meeting is a Daily-Scrum-like meeting between teams, ![]() Other scaling frameworks have a slightly different view, but I think it still focused on sync and impediment removal. So, it is also about keep delivering the product! Why have a meeting of Scrum Masters if they cannot deliver, faster and faster, that is their job, not? In this video Jeff Sutherland suggest (at 34:39) another responsibility of the Scrum of Scrums, namely: "Responsible for deployments of all teams together". Next it suggests a Scrum Master Cycle and a Product Owner Cycle, which would facilitate the organisational improvement cycles. The SDS event mirrors theĭaily Scrum in that it optimizes the collaboration and performance of The SoS holds a Scaled Daily Scrum (SDS). ![]() But I've seen everything ranging from one consistent representative to even all team members attending.Īccording to the guide it is more about sync and impediment removement: (Not that the Scrum Master can't attend, they just shouldn't be substituted for a dev team member) The approach I liked the most was actually that each team sent two representatives and those representatives rotated. The focus was usually how each team's work may be technically impacting other teams or what dependencies may be emerging or resolving.Īs to who attends, the Scrum Master is rarely the best person to attend, since they are not one of the people doing the work. In the most successful Scrum of Scrums implementations I've been a part of, these were short, 15-minute meetings held every few days where representatives from the teams would synchronize on needs between teams and plan how to move forward together. However, given the fact that the Daily Scrum is not a status meeting, but rather a chance for team members to synchronize and plan their day, I would treat the Scrum of Scrums the same, but at a broader scale. Everywhere I've worked that uses a Scrum of Scrums, it has always been selected as a lightweight approach for teams to synchronize without putting a more robust scaling framework into place. I'm not aware of any authoritative answer to this question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |