Difference between revisions of "Stable team"

From Pearl Language
Jump to navigation Jump to search
(HBR » How to Reward Your Stellar Team)
(Quote from the Unbeatable Mind.)
Line 22: Line 22:
* customer satisfaction
* customer satisfaction
Customer delight drives profitability and gives reason for existence.
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.
|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.
|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}}. Cultivate the {{p|stable team}} in an {{p|obeya}}.
|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}}.

Revision as of 16:32, 29 August 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:

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.

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