When Scrum gets big—dysfunction or constraint?
While I still prefer an Agile method such as Scrum over a traditional methodology for large projects/programs, the fact of the matter is that any effort that has 20 or more people poses a significant communications challenge. In a program with 35 Scrum teams, all of which will use Scrum the same way, a program of this size of, say, 300 people, takes a tremendous amount of coordination, communication, and organization among teams and stakeholders.
As I mentioned in a previous chapter, I once worked with a company that was creating a new gadget. The program plan called for roughly 35 teams whose focus ran the gamut from firmware, software and tablet apps, integration with conferencing systems, ...
Get The Professional ScrumMaster's Handbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
