Difference between revisions of "Stable team"
Jump to navigation
Jump to search
m (Typo.) |
(Background++) |
||
| Line 13: | Line 13: | ||
*{{p|t-shaped}}—both the team and its members; | *{{p|t-shaped}}—both the team and its members; | ||
*resilient, i.e. having a {{p|moderate truck number}}. | *resilient, i.e. having a {{p|moderate truck number}}. | ||
Productivity differences of {{p|stable team}}s are huge and increase: | |||
*quality of work; | |||
*satisfaction; | |||
*joy in work stuff; | |||
*customer delight; | |||
* customer satisfaction | |||
Customer delight drives profitability and gives reason for existence. | |||
|therefore=Evolve stable, resilient, co-located, and multi-disciplinary {{p|development team}}s. Don't let anyone touch it. In {{p|scrum}}, the {{p|product owner}} and {{p|scrum master}} will aggressively push back on anything that can potentially disrupt the team dynamic and high communication bandwidth in hyperproductive teams. | |therefore=Evolve stable, resilient, co-located, and multi-disciplinary {{p|development team}}s. Don't let anyone touch it. In {{p|scrum}}, the {{p|product owner}} and {{p|scrum master}} will aggressively push back on anything that can potentially disrupt the team dynamic and high communication bandwidth in hyperproductive teams. | ||
|new=Make every {{p|development team}} and {{p|community of practice}} create and evolve a {{p|team charter}}. | |new=Make every {{p|development team}} and {{p|community of practice}} create and evolve a {{p|team charter}}. | ||
Revision as of 12:53, 15 January 2013
…collaborative product discovery with multiple development teams.
✣ ✣ ✣
{{{wish full}}}
Any product owner wants sharp and focused development teams that are:
- stable;
- predictable;
- co-located (obeya;
- sustainable paced;
- t-shaped—both the team and its members;
- resilient, i.e. having a moderate truck number.
Productivity differences of stable teams are huge and increase:
- quality of work;
- satisfaction;
- joy in work stuff;
- customer delight;
- customer satisfaction
Customer delight drives profitability and gives reason for existence.
Therefore:
{{{therefore full}}}
✣ ✣ ✣
Make every development team and community of practice create and evolve a team charter.
✣ ✣ ✣
Source
- XP?
- Organizational Pattern Language?