Small Teams

Large agile teams are composed of small agile sub-teams

The communication overhead in large teams can often be a stumbling block. To maintain agility, a large team can be composed of small sub-teams that collaborate with the project community. Sub-teams are usually of two natures:

permanent, identified at the start of the project based on core competency (e.g. QA, Database, Programming, Mainframe, etc.)
transient, identified at the start of an iteration, based on the collaboration needed for a story

Note that the above natures of sub-teams are not mutually exclusive. It is important to preserve a permanent team for members to harness knowledge and create expertise, just as it is important to move beyond individual competency boundaries when collaboration is necessary.

·	Values
·	Readiness Assessment
·	Continuous Risk Management
·	Project Chartering
·	Project Community
·	Test-Driven Management
·	Sustainable Pace
·	Planning Game
·	Storytelling
·	Storytesting
·	Frequent Releases
·	Small Teams
·	Sitting Together
·	Continuous Learning
·	Iterative Usability
·	Evolutionary Design
·	Story Test-Driven Development
·	Refactoring
·	Domain-Driven Design
·	Pairing
·	Continuous Integration
·	Collective Ownership
·	Coding Standard
·	Retrospectives

Small Teams

Further Reading