Skip to content

XP Practice: Whole Team

September 27, 2007 by Artem Marchenko

Whole team practice recommends including on the team people with all skills and functionalities needed for creating the product: developers, testers, designers, technical writers and especially customers. It is a known fact that in software development a lot of information is lost or misinterpreted whenever the distant handover occurs. Even if everybody is doing his best and 90% of information is handed over correctly when the request goes over 4-5 handovers from customer to analyst to architect to developer to tester the information loss already reaches about 40%.

Agile software development methods fight with this information degradation with the help of the feedback loops, by making it easy for people to clarify things and verify if they got the idea correctly. Whole team practice is an extension of this idea to the extreme level - include everybody on the team and during the iteration they will be able to collaborate in order to produce a shippable increment of the software. Such a permanent collaboration and frequent commitment to the iteration plan also helps people to actually develop a feeling of a team - a feeling of belonging together, common responsibility, a feeling of "we are in this together".

Whole team practice does not necessarily dictate to having the same team during the whole project. While it is definitely good to have the team core stay on the project extra team members can be added on the need basis. For example, in the beginning of the project there might be a bigger need for the subject domain experts, database administrator or user interface designers.


This page is a part of the Extreme Programming overview

About the Author: As the Editor-in-Chief for, Artem is charged with overseeing the direction for content, advertising, and the overall management of the site. Nowadays in his day life, Artem is a product manager in a global telecommunication company where he leads the development of a product developed in extremely distributed environment. Artem has been applying Agile and researching Agile since 2005. Contact Artem


Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <b> <i> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <br> <blockquote>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>. Beside the tag style "<foo>" it is also possible to use "[foo]".

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.

Best of