| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.2.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.2.0" xmi:id="_K-e8IKX4EdmvhNXG0Oc2uA" |
| name="status_assessment,_0bA2EMlgEdmt3adZL5Dmdw" guid="_K-e8IKX4EdmvhNXG0Oc2uA" |
| changeDate="2006-11-01T15:32:14.824-0800" version="1.0.0"> |
| <purpose><p>
 |
| Capture and communicate whether the project is on track, requires corrective actions, and whether there are
 |
| opportunities for improvement.
 |
| </p></purpose> |
| <impactOfNotHaving>The team may not understand whether they are on track or not, and whether established iteration objectives and evaluation
 |
| criteria are met. The team may not be able to improve the way they develop software.</impactOfNotHaving> |
| <representationOptions><p>
 |
| The format of the status assessment varies from one&nbsp;project to another. It can be the minutes of an assessment
 |
| meeting, an update to a web site, or just an email. The important thing&nbsp;is to effectively communicate&nbsp;to all
 |
| involved parties whether iteration objectives and evaluation criteria were addressed, and what improvements are
 |
| needed&nbsp;to the way the team is working.
 |
| </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
