| <?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="-MLDkI5bvaku98zEjU67Npw" |
| name="how_to_adopt_practice_config_auth,_7d3BUFGwEd2DWsgK12YtmA" guid="-MLDkI5bvaku98zEjU67Npw" |
| changeDate="2008-09-29T09:57:38.390-0700" version="7.2.0"> |
| <mainDescription><h3>
 |
| Getting started&nbsp;
 |
| </h3>
 |
| <p>
 |
| Begin by making sure the team, including the key stakeholders, understands the&nbsp;key concepts and the scenarios.
 |
| </p>
 |
| <p>
 |
| The Practice Configuration Authoring practice assumes that the method authoring environment, including&nbsp;the method
 |
| framework in which the&nbsp;<a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/practice_configuration_CC7754F2.html"
 |
| guid="_0H9aAO7EEdy9EOwDlaw7Kw">Practice Configuration</a>&nbsp;is to reside, has been set up. Make sure that all team
 |
| members can access the environment and understand how to use it.
 |
| </p>
 |
| <p>
 |
| This practice describes how to author a new practice configuration, including any needed <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/cross_practice_process_5F83B112.html"
 |
| guid="_9NcfoFJgEd2SzrMjC_svdw">cross-practice process</a>es as well as <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/navigation_view_8F89044.html"
 |
| guid="_X_hFIPAjEdyHz_B1XFOUgA">navigation view</a>s to be used to access the configuration elements. It also supports
 |
| customizing an existing practice configuration:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| To adopt the "author new practice configuration" aspects, start by identifying the practice configuration to be
 |
| authored. It is recommended that the first time you apply this practice that you apply it to author a practice
 |
| configuration where the content to be included in the configuration is well understood and where subject matter
 |
| experts&nbsp;of the practice configuration are part of the authoring team. Author the practice
 |
| configuration&nbsp;incrementally, defining the structure of the configuration first (i.e., the scope and intended
 |
| audience of the configuration, any cross-practice processes, specific navigation views that should be defined),
 |
| followed by the detailing of the practice configuration elements. See&nbsp;<a class="elementLinkWithType"
 |
| href="./../../../practice.mdev.auth.practice_config_auth.base/guidances/roadmaps/auth_new_practice_config_from_existing_practices_99B797E4.html"
 |
| guid="_zTFdki3oEd2CiunvJQy6fQ">Roadmap: Author a New Practice Configuration from Existing Practices</a>&nbsp;for
 |
| the details.
 |
| </li>
 |
| <li>
 |
| To adopt the "customize existing practice configuration" aspects, start by identifying the practice configuration
 |
| you want to customize and how you want to customize it (e.g., do you want to change a process defined in the
 |
| configuration, do you want to change the roles and/or role assignments or the standard categories used in the
 |
| configuration, or do you simply want to change the navigation views for the configuration). It is recommended that
 |
| the first time you apply this practice that you apply it to customize a practice configuration that is well
 |
| understood and where subject matter experts&nbsp;of the practice configuration (and the customization) are part of
 |
| the authoring team. See <a class="elementLinkWithType"
 |
| href="./../../../practice.mdev.auth.practice_config_auth.base/guidances/roadmaps/customize_an_existing_practice_configuration_2642DD24.html"
 |
| guid="_u5j3MFcqEd2N4vZAlUIPvw">Roadmap: Customize an Existing Practice Configuration</a>&nbsp;for the details.
 |
| </li>
 |
| </ul>
 |
| <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>
 |
| Selecting a practice configuration whose content is not well understood as the first practice configuration you
 |
| author. If this is done, more time is spent understanding the practice configuration&nbsp;itself rather than in
 |
| effectively applying the practice techniques.
 |
| </li>
 |
| <li>
 |
| Spending too much time structuring the practice configuration. If this is done, the time it takes to deliver the
 |
| practice configuration is extended as a lot of time is spent structuring as opposed to just enough to get an
 |
| initial practice configuration out to get feedback, refining the structure, as needed. Try to keep the
 |
| documentation clear and concise. Make sure that the consumers of the practice configuration documentation (the
 |
| development team) are comfortable with the format and content of the documentation. Is there more or different
 |
| information they would like see? Would they like to see less?
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
