Stable team

From Pearl Language
Jump to: navigation, search

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:

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.


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 or guild create and evolve a team charter. Cultivate the stable team in an obeya. Use a unity of purpose to give direction, align forces, and pursue meaningful work.

✣  ✣  ✣

The book The Wisdom of Teams by Jon Katzenbach, Douglas Smith identifies six basic requirements for good teamwork:

  1. six plus or minus one team members.
  2. diverse skills to create resilience and completeness.
  3. big hairy audacious goal, shared, to align all forces.
  4. team charter to create a container that facilitates self-organization.
  5. disciplined autonomy to foster mutual accountability.
  6. unity of purpose to give direction, align forces, and pursue meaningful work.


About ask for help when working in teams:

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

From HBR » What New Team Leaders Should Do First (see reference below):

  1. Get to know each other
  2. Show what you stand for
  3. Explain how you want the team to work
  4. Set or clarify goals
  5. Keep your door open
  6. Score an “early win”

Principles for Team Leads


  • Be clear about what goes into your decision making and how you’ll evaluate the team’s progress
  • Encourage team members to connect — better communication early on will help avoid misunderstandings and poor results later
  • Look for roadblocks or grievances you can fix — it will earn you capital and inspire the team

Do not:

  • Jump into trying to accomplish the work without building relationships with the team
  • Assume that new team members understand how you or others work ­— take the time to explain processes and expectations.
  • Be afraid to communicate often early on — you can always pull back when the team is working well


Facts about "Stable team"
AuthorJon Katzenbach +, Douglas Smith + and Martien van Steenbergen +
Goalsustain maximum results of human assets +
PearlCollaborative product discovery +, Development team +, Product owner +, Obeya +, T-shaped +, Moderate truck number +, Stable team +, Scrum +, Scrum master +, Community of practice +, Guild +, Team charter +, Unity of purpose +, Six plus or minus one +, Diverse skills +, Big hairy audacious goal +, Disciplined autonomy + and Ask for help +
SoEvolve stable, resilient, co-located, and multi-disciplinary development teams and let no one touch it. +
ThemeScrum +, Extreme Programming +, Jumpstart + and Team +
WishQuality, predictability and sustainability are highly valued by clients and the market. +