Scaling and Time Synchronisation

This page shows all challenges and their respective Best Practices related to (global) scaling of the Scrum team and resulting time synchronisation issues

Index Challenge Best Practice
(42) Team members are only part-time available, are working on other projects or work remotely [16, p. 163, 4, p. 86 | 91, 2, p. 2, 37, p. 275] Meet twice a week on fixed dates as a substitute for daily meetings [37, p. 276]
Combine Sprint Review, Retrospective and Sprint Planning into a single event [37, p. 276]
Establish rules about communication with remote team members [9, 10]
(43) The team is distributed over multiple locations [38, p. 1532, 39, p. 108] Utilise the daily meeting of all Developers [38, p. 1532]
Product Owners should meet daily [38, p. 1532]
Builds can be automatically generated hourly [38, p. 1532]
Integrate XP practices into the Scrum method [38, p. 1532]
Use Scrum-of-Scrums [39, p. 109]
(44) Scaling Scrum to higher levels (e.g. global) or synchronising teams [16, pp. 162-163, 5, p. 692, 21, p. 4, 36, p. 148, 39, p. 108] Use Scrum-of-Scrums [39, p. 109]
Find a common timeslot for the daily Scrum meeting within the workday of each team [36, p. 148]
Have the maximum team size so that the team “can be fed by two large pizzas” [5, p. 692]
Use tools of communication that allow for videoconferences [13, p. 83]
Establish rules about communication with remote team members [9]
Augment Scrum practices with best practices of Global Software Engineering [40, p. 1137]