View source for Stable team

{{Oyster
|goal=sustain maximum results of human assets
|stage=Sparkle
|theme=Scrum, Extreme Programming, Jumpstart, Team
|context={{p|collaborative product discovery}} with multiple {{p|development team}}s.
|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:
*stable;
*predictable;
*co-located ({{p|obeya}});
*sustainable paced;
*{{p|t-shaped}}—both the team and its members;
*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.

As with all good teams, everyone is !rst accountable for the teams gear, followed by their teammates gear, and !nally their personal gear. This assures that no-one stands around waiting for the team to get ready, or for the team to clean and stow their gear after the session.
|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}} or {{p|guild}} create and evolve a {{p|team charter}}. Cultivate the {{p|stable team}} in an {{p|obeya}}. Use a {{usage|unity of purpose}}.
|to=get started
}}
The book {{book|The Wisdom of Teams||Jon Katzenbach, Douglas Smith}} identifies six basic requirements for good teamwork:
#{{p|six plus or minus one}} team members.
#{{p|diverse skills}} to create resilience and completeness.
#{{p|big hairy audacious goal}}, shared, to align all forces.
#{{usage|team charter}}.
#{{p|disciplined autonomy}} to foster mutual accountability.
#{{usage|unity of purpose}}.

==New==
About {{p|ask for help}} when working in teams: 
{{quote|Being great means not accepting the old way of doing things. Being great requires that you intentionally change your behavior after thinking about the ideal way to behave, and then following through with courage.|Jim and Michele McCarthy}}

==Sources==
*XP?
*Organizational Pattern Language?
*http://www.infoq.com/news/2013/04/stable-teams
*http://blogs.hbr.org/hmu/2013/08/how-to-reward-your-stellar-tea.html
*http://blogs.hbr.org/2013/11/taking-over-from-an-incompetent-team-leader/
{{WebSourceListItem
|url=http://www.infoq.com/articles/what-are-self-organising-teams
|site=InfoQ
|person=Sigi Kaltenecker, Peter Hundermark
|title=What Are Self-Organising Teams?
}}
{{Source
|author=Martien van Steenbergen
|coder={{mvs}}
}}