Difference between revisions of "Daily scrum of scrums"

From Pearl Language
Jump to navigation Jump to search
(Zeroth version.)
 
m (Agile)
Line 1: Line 1:
{{Oyster
{{Oyster
|stage=Germ
|stage=Germ
|theme=Scrum
|theme=Agile, Scrum
|context=Several teams work on the same product.
|context=Several teams work on the same product.
|wish in a single line=Need communication to flow between connected teams.
|wish in a single line=Need communication to flow between connected teams.

Revision as of 11:17, 27 August 2012

…Several teams work on the same product.

✣  ✣  ✣

{{{wish full}}}

You need to coordinate teams on a daily basis.

  • The primary means of synchronizing multiple teams during sprints
  • Ideally daily, after the individual team’s daily scrum, but 2–3 times a week is often acceptable
  • Representative from each development team—not necessarily the scrum master—the development team decides dependent on the subject matter.
  • Three main questions:
    1. What has the team done since the last meeting?
    2. What will the team do until the next meeting?
    3. What impediments does the team have that need to be escalated (i.e. that cannot be efficiently removed at the team level)?
  • Additional question:
    • Is the team about to do some that will create an impediment for another team (e.g. perform a large integration or fail to satisfy a dependency)?
  • Track results in the scrum of scrums impediment log.
  • Logs and tracks issues that have been escalated to the scrum of scrums.

Therefore:

{{{therefore full}}}

✣  ✣  ✣

One level only—avoid a ‘Scrum of Scrums of Scrums of Scrums’.


✣  ✣  ✣