SoS terminology confusion

[scrumatscale]

SoS terminology confusion

[FischbachP]

While translating the guide to German, we had the same thoughts. So we thought about paraphrasing this section to this:

A set of the teams that have a need to coordinate comprise a “Scrum of Scrums” (SoS). This team is a Scrum Team unto itself which is responsible for a fully integrated set of potentially shippable increments of product at the end of every Sprint from all participating teams. A SoS functions as a Release Team and must be able to directly deliver value to customers. To do so effectively, it needs to be consistent with the Scrum Guide; that is, have its own roles, artifacts, and events:

Roles:

• It needs to have all of the skills necessary to deliver a fully integrated potentially shippable product at the end of every Sprint. (It may need experienced architects, QA Leaders, and other operational skill sets.) Since the SoS needs to be responsive in real-time to impediments raised by participating teams, the Scrum Masters of the participating teams need to be on the Scrum of Scrums.
• It has Product Owner representation to resolve prioritization issues.
• The Scrum Master of the Scrum of Scrums is called the Scrum of Scrums Master (SoSM).

Events:

• A Backlog Refinement event wherein they decide what impediments are “ready” to be removed, how best to remove them, and how the team will know it is “done.”
• Particular attention should be paid to the SoS Retrospective in which the teams’ representatives share any learnings or process improvements that their individual teams have succeeded with, in order to standardize those practices across the teams within the SoS. 

• The SoS hold a Scaled Daily Scrum (SDS). The SDS event mirrors the Daily Scrum in that it optimizes the collaboration and performance of the network of teams. Beside the Scrum Masters, any person or number of people from participating teams may attend.

Additionally, the SDS:

• is time-boxed to 15 minutes or less.
• is a forum where team representatives may address 3 simple questions:
  What impediments does my team have that will prevent them from accomplishing their Sprint Goal (or impact the upcoming release)? 

  Is my team doing anything that will prevent another team from accomplishing their Sprint Goal (or impact their upcoming release)? 

  Have we discovered any new dependencies between the teams or discovered a way to resolve an existing dependency? 


[jeffsutherland]

Peters solution is a good one. For the next couple of weeks I will update the Scrum@Scale Guide to Version 1.1 and incorporate these and other comments from the Train the Trainer session last week. Any good language would be helpful.

[davidjuan01]

Something to also consider for this, is that the MetaScrum is an organizational structure, but the term is sometimes also used to refer to the scaled version of Backlog Prioritization/Refinement. I think that the Scrum@Scale guide could use some clarity around the Scaled Backlog Refinement being an event (unless I am missing where that is covered).

[jeffsutherland]

I have updated the Guide to respond to all issues above and recommended changes from the May TtT group. A pull request has been created. Alex, please merge after review. Thanks, Jeff

[scrumatscale]

I'm going to close this issue, please comment on the related pull request if you feel there is a need to address it further, or open a new issue.

PR is here: #17

Thanks for addressing this Jeff!