Scaling Scrum with Feature Teams

room: Regency D — time: Wednesday 11:00-11:45, Wednesday 11:45-12:30
Level: Practicing

How do you scale Scrum to hundreds of people? This presentation will explain a way of organizing your development so that it scales up well. It involves breaking the link between architecture and organization, breaking code ownership and organize the development in a more customer centric way. This has its drawbacks too! These are explained and some techniques for overcoming these drawbacks are discussed. This talk is based on the “feature teams” and “requirement areas” chapters in the recently published “Scaling Agile & Lean Development” by Bas Vodde and Craig Larman.

Process/Mechanics

This is a talk. The agenda is:

  • Component team structures and their drawbacks
  • Feature teams structures
  • Drawbacks of feature teams and ways of overcoming these
  • Requirement areas

This presentation is similar than the one at Agile2008 (then called “The Trouble with Component Teams”)

Learning outcomes
  • Problems with scaling Scrum using component teams
  • Traditional work-around to component team problems
  • Feature team concepts
  • Typical problems with feature teams
  • Ways of overcoming feature team problems
  • Requirement Areas and scaling over 100 people
Featured participants
Primary target persona
Reviews

No reviews

Subscribe to an RSS feed of reviews of this proposal Syndicate content