Understanding the need for scaling

So far, in this book, we have labored under the assumption that we are working on product development and delivery with only one Scrum Team. Although this is often the case, there are occasions when the product complexity requires multiple Scrum Teams working on the same product. This is usually pertinent when the product functionality crosses multiple technical platforms, for instance, when the product has website-specific usage and phone or tablet-specific usage. In such a case, it may make sense to have a Scrum Team working on the website functionality and another Scrum Team working on the portable devices’ functionality. Both teams will be working off the same Product Backlog, as there can only be one Product Backlog per product. However, some of the work undertaken by the teams will be cross-cutting, such as the web team working on a feature that requires changes to the device’s user interface, or the other way around.

The number...