| <?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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-IwJHnU8hFzICUIbJ3tygeg" name="release_iteration,_IAHg1uB-EeC1y_NExchKwQ" guid="-IwJHnU8hFzICUIbJ3tygeg" changeDate="2012-10-23T14:20:29.872-0700" version="7.5.1"> |
| <mainDescription><p>
 |
| Typical activities that occur during a Release Sprint/Iteration include:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Removing accrued technical debt
 |
| </li>
 |
| <li>
 |
| Fixing critical and major defects
 |
| </li>
 |
| <li>
 |
| Finalizing integrations to other systems
 |
| </li>
 |
| <li>
 |
| Documenting various aspects of the product, including support and user documentation
 |
| </li>
 |
| <li>
 |
| Significant functional, performance, load, system,&nbsp;user acceptance, and integration testing
 |
| </li>
 |
| <li>
 |
| Training support personnel and end users
 |
| </li>
 |
| <li>
 |
| Drafting an Implementation Plan and/or Deployment Plan
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Sometimes development teams will split into two - one subteam works on release hardening activities, while the other
 |
| works in parallel using a separate stream, developing new features for a follow-on release.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
