Scrum Institute, Scrum Framework Episode #15

Scrum Institute, Scrum Framework Episode #15 has been proudly brought to you by International Scrum Institute, https://www.scrum-institute.org You can also listen Scrum Institute’s Podcast from Apple, Spotify, Castbox and Google Play. Listen to Scrum Institute Podcast on AppleListen to Scrum Institute Podcast on Google PlayListen to Scrum Institute Podcast on SpotifyListen to Scrum Institute Podcast on Listen NotesListen to Scrum Institute Podcast on Castbox What Is Multi-Team Coordination And Planning? This Might Surprise You! Scrum of Scrum After having seen the last chapter of this course, the next logical question in your mind could be how you do coordinate those different Scrum Teams. So they do work together efficiently. That’s a fair question, and we have attempted to cover this answer too. Scrum of Scrum Meetings Scrum of Scrum Meetings resemble Daily Scrum Meetings. And yet, here during Scrum of Scrum Meetings, the focus is not the work of individual Scrum Team members, but the Scrum Teams themselves. Scrum of Scrum Meetings do take place every day, and they are limited (timeboxed) to 15 minutes too. And yet depending on the complexity of the project, especially during its early stages while Scrum Teams are just forming, these meetings can take 30 to 60 minutes. That’s totally fine as well. Common Sprint Review Meetings Common Sprint Review Meetings with the participation of all Scrum Teams are not mandatory, but they could be very beneficial. Note that Common Sprint Review Meetings do not replace Sprint Review Meetings the Scrum Team conduct locally. What did the team do yesterday?What is the team planning to do today?Are there any impediments to hinder or slow down the progress of the team? These answers should obviously cover the user stories and interdependencies, which impact other teams too. The Chief Scrum Product Owner and the Lead Scrum Master can jointly moderate Scrum of Scrum Master meetings.Alternatively, one of them can take over the moderation duty of these meetings, or they can choose to rotate this duty among themselves as well. Common Sprint Review Meetings Common Sprint Review Meetings with the participation of all Scrum Teams are not mandatory, but they could be very beneficial. Note that Common Sprint Review Meetings do not replace Sprint Review Meetings the Scrum Team conduct locally. The participants of Common Sprint Review Meetings are the delegates from Scrum Teams and/or their respective Scrum Product Owners. The Scrum Teams can also rotate their delegates based on their preferences. The Lead (Primary) Scrum Master carries the responsibility of moderating a Common Sprint Review Meeting. Common Sprint Review Meetings enable all Scrum Teams to demonstrate their Shippable Product Increments to the Chief Scrum Product Owner and all other Scrum Product Owners. In this way, the Common Sprint Review Meetings fulfill two purposes: All Scrum Teams are now aligned about the current status of the overall project.All Scrum Teams collect feedback for their work, and they have the chance now to take this feedback into account, while they do their upcoming Sprint Planning Meetings. Common Sprint Retrospectives Similar to Common Sprint Review Meetings, Common Sprint Retrospective Meetings are not mandatory, but they could be very beneficial. Note that Common Sprint Retrospective Meetings do not replace Sprint Respective Meetings the Scrum Team conduct locally. The participants of Common Sprint Retrospective Meetings are the delegates from Scrum Teams. The Scrum Teams can choose to rotate their delegates based on their discretion. Common Sprint Retrospective Meetings are led by the Lead (Primary) Scrum Master. These meetings aim to find out and act on improvement potentials about how the larger Scrum project organization uses the Scrum Framework. All issues which require the attention and collabora