Stable team

…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.

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:

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
• 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/

---