| <?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="--dByCrR1PiKA-JrdNIjebw" name="how_to_adopt_doc_training,_2OLFEKBGEeCRzIAAKeJxvA" guid="--dByCrR1PiKA-JrdNIjebw" changeDate="2011-07-30T13:25:06.810-0700" version="7.2.0"> |
| <mainDescription><h3>
 |
| Getting started
 |
| </h3>
 |
| <p>
 |
| The goal of the Documentation and Training practice is to ensure that end users of a product receive quality
 |
| information about the product (in comprehensive documentation) and have been adequately trained regarding how to use
 |
| the product.
 |
| </p>
 |
| <h3>
 |
| Common pitfalls
 |
| </h3>
 |
| <ul>
 |
| <li>
 |
| <strong>Inadequate documentation:</strong> No one likes to rigorously document a product, least of all the team
 |
| members who developed it. Historically, product documentation often has been an afterthought, if given thought at
 |
| all. In the Agile world, because the goal is to deliver high quality, working software to end users more quickly,
 |
| realize that part of the quality component is adequate documentation that enables end users to use the product more
 |
| effectively.
 |
| </li>
 |
| <li>
 |
| <strong>Non-existent or inadequate training:</strong> Like documentation, training often is an afterthought. When
 |
| product budgets are reduced, training often is the first line item to be eliminated. However, in fairness to the
 |
| end user community, proper training about how to use the product is critical to the overall success of product
 |
| deployment in terms of enabling end users do their jobs effectively.
 |
| </li>
 |
| </ul>
 |
| <h3>
 |
| Considerations
 |
| </h3>
 |
| <p>
 |
| The following is a list of points to consider when adopting this practice:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>Training depends on documentation:</strong> The better the documentation, the easier it is to develop
 |
| training materials. If your team skimps on the quality and quantity of product documentation, the cost of training
 |
| materials development will significantly increase.
 |
| </li>
 |
| <li>
 |
| <strong>Documentation can be developed in many ways:</strong> The more varied the documentation media (e.g., Help
 |
| files, Wizards, PowerPoint presentations, video vignettes, etc.), the easier it will be to use those forms of
 |
| documentation and convert them into robust training modules. Also, multiple forms of documentation will appeal to a
 |
| broader audience because people internalize information differently: what works for one person might not resonate
 |
| with another.
 |
| </li>
 |
| <li>
 |
| <strong>Training can be delivered in many ways:</strong> Like documentation, training delivery media should be
 |
| varied to appeal to different audiences. Not only can training be delivered by a live instructor in a classroom,
 |
| other options include:
 |
| </li>
 |
| <li style="LIST-STYLE-TYPE: none">
 |
| <ul>
 |
| <li>
 |
| Computer-based training where users complete modules on their own time
 |
| </li>
 |
| <li>
 |
| On-line instructor-led modules delivered over the Internet at scheduled times
 |
| </li>
 |
| <li>
 |
| Just-in-time training modules (either live or on-line instructor-led) for incremental learning
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
