Chapter 9 Requirement Areas
To be stupid, selfish, and have good health are three requirements for happiness, though if stupidity is lacking, all is lost.
—Gustave Flaubert
Chapter
• Try...One Product Owner and one Product Backlog 217
• Try...Requirements Areas 218
• Try...Moving whole teams between areas 223
• Try...An all-at-once transition to requirement areas 224
• Avoid...Development areas 224
A product with more than five or ten feature teams is difficult for
• teams...to work on the whole product
• the Product Owner...to work with so many teams
Therefore, feature teams are scaled up by grouping related teams in a requirement area. Like a feature team, a requirement area is customer centric; it is not an architectural ...
Get Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale 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.
