Difference between revisions of "Stable team"
Jump to navigation
Jump to search
m (__SHOWFACTBOX__) |
m (No __SHOWFACTBOX__) |
||
| Line 1: | Line 1: | ||
{{Oyster | {{Oyster | ||
|goal=get started | |goal=get started | ||
| Line 27: | Line 26: | ||
|to=get started | |to=get started | ||
}} | }} | ||
==Source== | ==Source== | ||
*XP? | *XP? | ||
Revision as of 14:59, 18 May 2013
…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.
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
- XP?
- Organizational Pattern Language?
- http://www.infoq.com/news/2013/04/stable-teams