Difference between revisions of "Stable team"
Jump to navigation
Jump to search
(Zeroth version.) |
m (Typo.) |
||
| Line 2: | Line 2: | ||
|stage=Sparkle | |stage=Sparkle | ||
|theme=Agile, Scrum, Extreme Programming | |theme=Agile, Scrum, Extreme Programming | ||
|context={{p|collaborative product | |context={{p|collaborative product discovery}} with multiple {{p|development team}}s. | ||
|wish in a single line=Quality, predictability and sustainability are highly valued by clients and the market. | |wish in a single line=Quality, predictability and sustainability are highly valued by clients and the market. | ||
|therefore in a single line=Evolve stable, resilient, co-located, and multi-disciplinary development teams and let no one touch it. | |therefore in a single line=Evolve stable, resilient, co-located, and multi-disciplinary development teams and let no one touch it. | ||
| Line 20: | Line 20: | ||
*Organizational Pattern Language? | *Organizational Pattern Language? | ||
{{Source | {{Source | ||
|author=Martien van Steenbergen, | |author=Martien van Steenbergen, | ||
|coder={{mvs}} | |coder={{mvs}} | ||
}} | }} | ||
Revision as of 08:44, 10 September 2012
…collaborative product discovery with multiple development teams.
✣ ✣ ✣
{{{wish full}}}
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.
Therefore:
{{{therefore full}}}
✣ ✣ ✣
Make every development team and community of practice create and evolve a team charter.
✣ ✣ ✣
Source
- XP?
- Organizational Pattern Language?