Scrum Team Organization – Part 2

One approach is to set up a common sprint backlog for all teams to pull work from. As part of the sprint planning process each team will have selected its own set of user stories, and done its own task-level planning. Every team has its own scrum master and runs its own daily stand-ups. To synchronize dependencies between teams, a scrum-of-scrums session is also held daily (or perhaps 3 times per week) with the team scrum masters and architects participating. The output of each team is rolled up into one overall burndown chart for the sprint.



If the teams are geographically distributed then good tooling is necessary to provide a coherent picture of progress. The individual teams can use whiteboards and post-its to track progress, but that does not really scale in a truly reliable way. Rather than burden the teams with the overhead of tool-based record keeping, the local scrum masters can help out here by capturing the results of the teams daily progress in a tool that is shared by the entire project. The integrated view of total iteration progress can then be shared at the scrum-of-scrums via GoToMeeting, Webex, Skype or other equivalent application.

Print Friendly

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>