| <?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:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-umGbPWvT56IZ_9eN4zN4XQ" |
| name="how_to_adopt_team_based_method_auth_env,__IsVACv4Ed2HiavZWDwUwQ" guid="-umGbPWvT56IZ_9eN4zN4XQ" |
| changeDate="2008-09-30T18:55:57.906-0700" version="7.2.0"> |
| <mainDescription><h3>
 |
| Getting started&nbsp;
 |
| </h3>
 |
| <p>
 |
| Make sure that the users of the environment (the process engineers) are comfortable with the&nbsp;environment
 |
| </p>
 |
| <p>
 |
| As you apply the recommendations described in the practice, capture what you have learned, what worked for your team
 |
| and what didn't so that you can continually fine-tune how your team applies the practice.
 |
| </p>
 |
| <h3>
 |
| Common pitfalls
 |
| </h3>
 |
| <p>
 |
| The following are some common pitfalls when adopting this practice.
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Spending too much time making sure the environment is perfect. Define just enough environment to get started.&nbsp;
 |
| Then gather feedback on how the environment is working, refining, as needed.&nbsp;
 |
| </li>
 |
| <li>
 |
| Having a team that is unfamiliar with the environment and is therefore hesitant to "jump right in" and start
 |
| working.
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
