Teamwork is at the heart of every agile process. The Agile Manifesto proclaims
that we are to favor “individuals and interactions over process and tools” (Beck et
al. 2001), meaning great software comes from great teams. Scrum itself derives its
name from the view that a product development team should behave much like a
rugby team—a group of individuals moving the ball down field as a unit. Considering
the central importance of teams to successful agile development, it should
be no surprise to encounter a chapter called “Teamwork.”
Chapter Contents
- Embrace Whole-Team Resposibility
- Nurture Whole-Team Commitment
- Rely On Specialists But Sparingly
- Do A Little Bit Of Everything All The Time
- Don’t Wait Until the End of the Sprint to Finish Everything
- Mix the Sizes of the Product Backlog Items You Commit To
- Foster Team Learning
- Ensure Learning Conditions Exist
- Eliminate Knowledge Waste
- Encourage Collaboration Through Commitment
- All Together Now
- Additional Reading