Difference between revisions of "Stable team"
m (No __SHOWFACTBOX__) |
(Content++) |
||
| Line 4: | Line 4: | ||
|theme=Agile, Scrum, Extreme Programming | |theme=Agile, Scrum, Extreme Programming | ||
|context={{p|collaborative product discovery}} with multiple {{p|development team}}s. | |context={{p|collaborative product discovery}} with multiple {{p|development team}}s. | ||
| | |goal=sustain maximum results of human assets | ||
|wish=Quality, predictability and sustainability are highly valued by clients and the market. | |wish=Quality, predictability and sustainability are highly valued by clients and the market. | ||
|so=Evolve stable, resilient, co-located, and multi-disciplinary development teams and let no one touch it. | |||
|wish full=Quality, predictability and sustainability are highly valued by clients and the market. | |||
|background=Any {{p|product owner}} wants sharp and focused {{p|development team}}s that are: | |background=Any {{p|product owner}} wants sharp and focused {{p|development team}}s that are: | ||
*stable; | *stable; | ||
| Line 22: | Line 23: | ||
* customer satisfaction | * customer satisfaction | ||
Customer delight drives profitability and gives reason for existence. | 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 full=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}}. Cultivate the {{p|stable team}} in an {{p|obeya}}. | ||
|to=get started | |to=get started | ||
}} | }} | ||
Revision as of 10:36, 16 June 2013
…collaborative product discovery with multiple development teams.
✣ ✣ ✣
Quality, predictability and sustainability are highly valued by clients and the market.
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:
Evolve stable, resilient, co-located, and multi-disciplinary development teams. Don't let anyone touch it. In scrum, the product owner and scrum master will aggressively push back on anything that can potentially disrupt the team dynamic and high communication bandwidth in hyperproductive teams.
✣ ✣ ✣
Make every development team and community of practice create and evolve a team charter. Cultivate the stable team in an obeya.
✣ ✣ ✣
Source
- XP?
- Organizational Pattern Language?
- http://www.infoq.com/news/2013/04/stable-teams