book
Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum
by Craig Larman, Bas Vodde
December 2008
Intermediate to advanced
368 pages
8h 23m
English
Content preview from Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,







O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
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 ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access