| <?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-8HIJRiG1VwF8mwvxuZ0c2Q" name="new_roadmap,_z093UOQVEdyy8NdG6HqqRA" guid="-8HIJRiG1VwF8mwvxuZ0c2Q" changeDate="2010-08-31T08:37:16.000-0700" version="7.5.0"> |
| <mainDescription><h3> |
| <em>Getting Started</em> |
| </h3> |
| <p> |
| Understand&nbsp;the basic building blocks of methods and how to define and customize them.&nbsp; Implement your method |
| assets and publish a method configuration that can be reviewed by your stakeholders. |
| </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> |
| <em>Common Pitfalls</em> |
| </h3> |
| <p> |
| Following are some common pitfalls when adopting this practice: |
| </p> |
| <ul> |
| <li> |
| Spending too much time developing method assets to get them "perfect" before trying them out with real project |
| work. Define just enough to get started and then gather feedback for improvement from teams as they use the assets. |
| </li> |
| <li> |
| Creating too many method assets at too fine-grained a level can overwhelm and confuse teams. Confirm that you |
| understand the requirements for each asset and how it will help project teams before investing a lot of time in |
| development.<br /> |
| <br /> |
| </li> |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |