<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore"
    xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf"
    epf:version="1.5.0" xmi:id="-pXI3ZcdGOOyWtDdzIg2E7w"
    name="building_effective_teams,_zLlDwEk5Ed2JToD8KCVSGA" guid="-pXI3ZcdGOOyWtDdzIg2E7w"
    changeDate="2008-07-09T10:10:35.172-0700" version="7.5.0">
  <mainDescription>&lt;h3>&#xD;
    Whole Team&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Whole Team refers to the organization that delivers software for a project and includes any and all contributors (both&#xD;
    direct and indirect participants) to the delivery. It creates a collaborative environment in which the “whole” team&#xD;
    participates in setting direction, managing work efforts and delivering the solution. Successful software delivery&#xD;
    ultimately depends on people. This dependence means that the way people work together is a critical success factor.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Background&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    In some approaches to software development, customers and development management tell developers what they want, when&#xD;
    they want it and how much it can cost. Assignments are handed out and deadlines set without discussion. This&#xD;
    environment creates resentment between developers, managers and customers. Developers also are asked or even expected&#xD;
    to work whatever hours it takes to get the job done. In addition, barriers exist or are created between teams, causing&#xD;
    team members to point fingers at each other or pass the problem onto someone else.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Definition&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Whole Team embraces the concept that to be successful, in terms of quality, schedule and scope, resources must feel&#xD;
    empowered to accomplish the project goals. This empowerment also means that the ultimate customer of the software must&#xD;
    be an active and equal participant in the process. Whole Team focuses on the collaboration between all team members and&#xD;
    the joint-decision making process that the team makes. Whole Team creates a transparent environment that ensures&#xD;
    visibility to the teams’ work and promotes collaboration on related work items. Additionally, the active involvement of&#xD;
    end-users, customers, and sponsors in the development process enhances the quality of the delivered product.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Some Misconceptions&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Whole team does not mean that the entire team works on everything at once as the name suggests. The real goal with&#xD;
    Whole Team is to ensure that the team collectively works to identify risks, and assign, deliver, test and review work&#xD;
    products.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Key Aspects&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Whole Team encompasses the following key ideas:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Collaboration across team members via: &#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                Daily Meetings&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Extended Team Members&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Cross-Functional Teams organized around components&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Enabling Technologies&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Sustainable Pace&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Work assignments are pulled instead of pushed&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Decision making is made by people close to the decision&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Managers do not direct, but coach and lead&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Everyone participates and generates value&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Transparency of information and activities&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Open and honest communication&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Business Benefits&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Whole Team practice enriches the software development environment, raising overall resource productivity and improving&#xD;
    software quality. Whole Team creates transparency to the software development process enabling all team members to be&#xD;
    aware of all other work activities. This transparency is of direct benefit to the end-user for the software product&#xD;
    being developed.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
