Difference between revisions of "Stable team"
(Theme::Jumpstart) |
m (--Theme::Agile) |
||
| Line 2: | Line 2: | ||
|goal=sustain maximum results of human assets | |goal=sustain maximum results of human assets | ||
|stage=Sparkle | |stage=Sparkle | ||
|theme= | |theme=Scrum, Extreme Programming, Jumpstart | ||
|context={{p|collaborative product discovery}} with multiple {{p|development team}}s. | |context={{p|collaborative product discovery}} with multiple {{p|development team}}s. | ||
|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. | ||
Revision as of 14:28, 12 July 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