Difference between revisions of "Stable team"

From Pearl Language
Jump to navigation Jump to search
m (__SHOWFACTBOX__)
m (Goal)
Line 1: Line 1:
__SHOWFACTBOX__
{{Oyster
{{Oyster
|to=get started
|goal=get started
|stage=Sparkle
|stage=Sparkle
|theme=Agile, Scrum, Extreme Programming
|theme=Agile, Scrum, Extreme Programming
Line 25: Line 24:
|therefore=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=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}}.
|new=Make every {{p|development team}} and {{p|community of practice}} create and evolve a {{p|team charter}}.
|to=get started
}}
}}
__SHOWFACTBOX__
==Source==
==Source==
*XP?
*XP?

Revision as of 13:53, 18 May 2013

collaborative product discovery with multiple development teams.

✣  ✣  ✣

{{{wish full}}}

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.

Therefore:

{{{therefore full}}}

✣  ✣  ✣

Make every development team and community of practice create and evolve a team charter.


✣  ✣  ✣


Source