What is whole-team approach (team-based approach)? - Definition from Whatis.com

Definition

whole-team approach (team-based approach)

The whole-team approach, also called the team-based approach, is a style of project management in which everyone on the project team is held equally responsible for the quality and success of the project. The term is often used in agile software development, lean production and creative teams in advertising and other media. 

A whole team approach recognizes that in order for the team to be successful, members cannot operate in isolation. Each team member must know and appreciate every other team member's strengths and skills.  Each team member must also be willing to switch roles when the need arises and remained focused on the success of the project, doing whatever is necessary whether or not it's technically "their job."

In agile development, this means that everyone on the development team is equally responsible for quality. In the book, “Agile Testing – A Practical Guide for Testers and Agile Teams,” by Lisa Crispin and Janet Gregory, the whole-team approach is described this way:

“ The focus of agile development is producing high-quality software in a time frame that maximizes its value to the business. This is the job of the whole team, not just testers or designated quality assurance professionals. Everyone on an agile team gets “test-infected.” Tests, from the unit level on up, drive the coding, help the team learn how the application should work, and let us know when we’re 'done' with a task or story.”

 

Contributor(s): Melanie Webb
This was last updated in November 2011
Editorial Director: Margaret Rouse

Email Alerts

Register now to receive SearchSoftwareQuality.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Dig Deeper

  • Agile development practices: Extending agility to contracts

    Outlining a variety of ideas for contracts, consultant Howard Deiner shows how Agile practices move beyond the development of code and into developing a collaborative contract.

  • Extending Agile ALM: Why Agile engineering practices matter so much

    Agile consultant Howard Deiner explains several Agile engineering practices that can be used regardless of which methodology your organization employs.

  • Agile development: Changing the way leaders lead

    “Moving towards Agile methods challenges all aspects of our traditional management and leadership approaches,” says Agile Consultant, Coach and Trainer Bob Galen. Galen will be presenting “A Test Leader’s Guide to Agile” at STAREAST 2012. In this interview, we hear more about the differences between traditional and Agile leadership and how the transition is affecting leaders and teams.

Do you have something to add to this definition? Let us know.

Send your comments to techterms@whatis.com