SOS Scrum of Scrums

1. Purpose

1.1. Focus on areas of overlap and integration

1.2. Maintain backlog of issues

1.3. Capture and remove impediments for the larger project

2. Assumptions

2.1. Should be development team focused

2.2. Not a status or scrum master coordination meeting

2.3. SoS does not: 1. Develop backlog (though will maintain  an "issues log" and can agree on a story that should be added to the backlog 2. Coordinate Epics 3. Plan releases 4. Manage releases

2.4. Individual scrum teams are self-organizing.  The SoS will not dictate ways of working/prioritization within the teams

2.5. individual scrum masters report on

2.5.1. velocity

3. Reporting & Admin

3.1. What type of reporting?

3.1.1. SoS risk/issue/impediments log

3.2. Frequency

3.3. Format

3.4. Manage SOW/contractors

4. Other meetings/responsibilities

4.1. Meta Scrum

4.1.1. The Meta Scrum is a virtual team made up of Product Owners that coordinate Epics, product releases and product lines.

4.1.2. Facilitated by the Chief Product Owner

4.2. SoS backlog grooming (for coordination purposes only) - 3 sprint rolling view

4.3. SoS Retrospective

5. Participants

5.1. Technical Participant (active)  - can vary per meeting based upon the relevant stage of the project

5.1.1. Tester

5.1.2. Programmer

5.1.3. Developer

5.2. Scrum Master (observer)

5.3. SoS Master/Chief Scrum Master (facilitator)

5.4. Chief Product Owner (representing Meta Scrum team)

6. Frequency & Timing

6.1. Option 1: As a daily 15 minute scrum

6.2. Option 2: 2-3 times/week for 30-60 minutes

7. Agenda

7.1. 1. What has your team done since we last met? 2. What will your team do before we meet again? 3. Is anything slowing your team down or getting in their way? 4. Are you about to put something in another team’s way?

7.2. For Option 2 only

7.2.1. Resolve problems and discuss issues on the SoS backlog

7.2.2. update SoS backlog

8. Misc

8.1. At team or project level?

8.1.1. Support/Operations Owner

8.1.2. SEM

8.1.3. SDLC

9. Release Management