Lacking Necessary Skills
Scrum doesn’t prescribe how development teams should be constructed. It simply requires that teams deliver a done increment of software at the end of every sprint. (See Chapter 13, Deconstructing the Done Product Increment for more about what “done” means.) So how should you construct development teams?
In the scenario we just described, the teams were organized by area of expertise. (These are called competency-based teams or component teams.) This way of arranging things fits into traditional organizational management structures, so it’s common for companies that are new to Scrum to organize their dev teams this way. In waterfall projects, for example, these competency areas are phase gates: Competency teams hand ...
Get Fixing Your Scrum 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.
