Difference between revisions of "Six plus or minus one"
Jump to navigation
Jump to search
(Zeroth version.) |
m (terse/full) |
||
| Line 3: | Line 3: | ||
|theme=Agile, Scrum | |theme=Agile, Scrum | ||
|context=on a mission. | |context=on a mission. | ||
| | |goal=enjoy maximum communication bandwidth among people | ||
|wish=To optimize team performance, team size is crucial. | |wish=To optimize team performance, team size is crucial. | ||
|therefore=Foster teams of six plus or minus one so they excel in communication saturation and collective team knowledge. Amplify with {{p|few roles}}. | |so=Foster teams of six plus or minus one so they excel in communication saturation and collective team knowledge. | ||
|wish full=To optimize team performance, team size is crucial. | |||
|therefore full=Foster teams of six plus or minus one so they excel in communication saturation and collective team knowledge. Amplify with {{p|few roles}}. | |||
}} | }} | ||
See: | See: | ||
Latest revision as of 10:29, 16 June 2013
…on a mission.
✣ ✣ ✣
To optimize team performance, team size is crucial.
Therefore:
Foster teams of six plus or minus one so they excel in communication saturation and collective team knowledge. Amplify with few roles.
✣ ✣ ✣
✣ ✣ ✣
See:
- Jeff Sutherland's
- Small Teams
- Adding people to a late project makes it later (Brooks' Law)
- Borland story on Few Roles
- Performance = Communication Saturation = Collective Team Knowledge
- Daily meeting with few roles = high velocity
- Small Teams