Whole Team

Whole Team refers to the organization that delivers software for a project and includes any and all contributors (both direct and indirect participants) to the delivery. It creates a collaborative environment in which the “whole” team participates in setting direction, managing work efforts and delivering the solution. Successful software delivery ultimately depends on people. This dependence means that the way people work together is a critical success factor.

Background

In some approaches to software development, customers and development management tell developers what they want, when they want it and how much it can cost. Assignments are handed out and deadlines set without discussion. This environment creates resentment between developers, managers and customers. Developers also are asked or even expected to work whatever hours it takes to get the job done. In addition, barriers exist or are created between teams, causing team members to point fingers at each other or pass the problem onto someone else.

Definition

Whole Team embraces the concept that to be successful, in terms of quality, schedule and scope, resources must feel empowered to accomplish the project goals. This empowerment also means that the ultimate customer of the software must be an active and equal participant in the process. Whole Team focuses on the collaboration between all team members and the joint-decision making process that the team makes. Whole Team creates a transparent environment that ensures visibility to the teams’ work and promotes collaboration on related work items. Additionally, the active involvement of end-users, customers, and sponsors in the development process enhances the quality of the delivered product.

Some Misconceptions

Whole team does not mean that the entire team works on everything at once as the name suggests. The real goal with Whole Team is to ensure that the team collectively works to identify risks, and assign, deliver, test and review work products.

Key Aspects

Whole Team encompasses the following key ideas:

• Collaboration across team members via:
  • Daily Meetings
  • Extended Team Members
  • Cross-Functional Teams organized around components
  • Enabling Technologies
• Sustainable Pace
• Work assignments are pulled instead of pushed
• Decision making is made by people close to the decision
• Managers do not direct, but coach and lead
• Everyone participates and generates value
• Transparency of information and activities
• Open and honest communication

Business Benefits

Whole Team practice enriches the software development environment, raising overall resource productivity and improving software quality. Whole Team creates transparency to the software development process enabling all team members to be aware of all other work activities. This transparency is of direct benefit to the end-user for the software product being developed.