| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\openup_basic\workproducts\status_assessment.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: status_assessment.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_0bA2EMlgEdmt3adZL5Dmdw CRC: 4196749033 -->Status Assessment<!-- END:presentationName,_0bA2EMlgEdmt3adZL5Dmdw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_0bA2EMlgEdmt3adZL5Dmdw CRC: 1799779189 -->Capture and communicate results and actions from assessments. This is typically done at the end of each iteration.<!-- END:briefDescription,_0bA2EMlgEdmt3adZL5Dmdw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: purpose<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:purpose,_K-e8IKX4EdmvhNXG0Oc2uA CRC: 1427235238 --><p> |
| Capture and communicate whether the project is on track, requires corrective actions, and whether there are |
| opportunities for improvement. |
| </p><!-- END:purpose,_K-e8IKX4EdmvhNXG0Oc2uA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: impactOfNotHaving<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:impactOfNotHaving,_K-e8IKX4EdmvhNXG0Oc2uA CRC: 4179707242 -->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.<!-- END:impactOfNotHaving,_K-e8IKX4EdmvhNXG0Oc2uA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: representationOptions<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:representationOptions,_K-e8IKX4EdmvhNXG0Oc2uA CRC: 227428847 --><p> |
| The format of the status assessment varies from one 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 is to effectively communicate to all |
| involved parties whether iteration objectives and evaluation criteria were addressed, and what improvements are |
| needed to the way the team is working. |
| </p><!-- END:representationOptions,_K-e8IKX4EdmvhNXG0Oc2uA --> |
| </body> |
| </html> |