| <?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\tasks\manage_iteration.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: manage_iteration.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_8S2aICbYEdqh1LYUOGRh2A CRC: 475284402 -->Manage Iteration<!-- END:presentationName,_8S2aICbYEdqh1LYUOGRh2A --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_8S2aICbYEdqh1LYUOGRh2A CRC: 3426038205 -->Assess project status and identify any blocking issues and/or opportunities. Identify and manage exceptions, problems and risks. Communicate project status.<!-- END:briefDescription,_8S2aICbYEdqh1LYUOGRh2A --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: purpose<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:purpose,-PbfqVxB_j9KN-Jx39_pEUA CRC: 615557520 --><p> |
| Identify blocking issues and/or opportunities early to take action and keep the project on track. |
| </p><!-- END:purpose,-PbfqVxB_j9KN-Jx39_pEUA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_OE65ICuxEdqTIKp3l5PtzQ CRC: 116850368 -->Capture status<!-- END:name,_OE65ICuxEdqTIKp3l5PtzQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_OE65ICuxEdqTIKp3l5PtzQ CRC: 2351524981 --><p> |
| The project manager needs to continuously monitor the project to ensure its appropriate progress, and to enable the |
| team to react as soon as possible to any change. Many alternative means may be used to track the status: |
| </p> |
| <ul> |
| <li> |
| Quick, daily meetings with the entire project team, also called "scrum meetings” are useful to understand what team |
| members have accomplished since the last meeting, and what they plan to accomplish before the next meeting. It |
| also allows the team to identify any blocking issues. See <a class="elementLinkWithUserText" href="./../../openup_basic/guidances/supportingmaterials/references,_9ToeIB83Edqsvps02rpOOg.html" guid="_9ToeIB83Edqsvps02rpOOg">[SCH04]</a> for guidance on scrum meetings. |
| </li> |
| <li> |
| Basic metrics, ideally automatically generated from the tools at hand, or manually assembled. The <a class="elementLinkWithType" href="./../../openup_basic/workproducts/project_plan,_0a6vcMlgEdmt3adZL5Dmdw.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Artifact: Project Plan</a> should outline which metrics the project should use. |
| Examples of such metrics include <a class="elementLinkWithType" href="./../../openup_basic/guidances/reports/iteration_burndown,_uAzgkDg3Edu4E8ZdmlYjtA.html" guid="_uAzgkDg3Edu4E8ZdmlYjtA">Report: Iteration Burndown</a> and <a class="elementLinkWithType" href="./../../openup_basic/guidances/reports/project_burndown,_ePrt8Dj3EduxovfWMDsntw.html" guid="_ePrt8Dj3EduxovfWMDsntw">Report: Project Burndown</a> charts, which are reports on the <a class="elementLinkWithType" href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>. See also <a class="elementLinkWithType" href="./../../openup_basic/guidances/concepts/metrics,_0mYYkMlgEdmt3adZL5Dmdw.html" guid="_0mYYkMlgEdmt3adZL5Dmdw">Concept: Metrics</a> for more information. |
| </li> |
| </ul> |
| <br /><!-- END:sectionDescription,_OE65ICuxEdqTIKp3l5PtzQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_ztF0UCuxEdqTIKp3l5PtzQ CRC: 3829857704 -->Communicate status<!-- END:name,_ztF0UCuxEdqTIKp3l5PtzQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_ztF0UCuxEdqTIKp3l5PtzQ CRC: 3040873295 --><p> |
| Communicating project status is as important as gathering it. Communication is usually done at two levels: the task |
| level and project level. |
| </p> |
| <ul> |
| <li> |
| <strong>Task Level – Communicated within the project team:</strong> status can be communicated through quick, daily |
| meetings. This allows you to combine the status capturing with the status communications. |
| </li> |
| <li> |
| <strong>Project Level – Communicated to the stakeholders and the project team:</strong> status is usually |
| communicated through core metrics rather than detailed information. This can be done through meetings, e-mail, or |
| Web publishing. |
| </li> |
| </ul><!-- END:sectionDescription,_ztF0UCuxEdqTIKp3l5PtzQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_oIZdkCbZEdqh1LYUOGRh2A CRC: 395784438 -->Handle exceptions and problems<!-- END:name,_oIZdkCbZEdqh1LYUOGRh2A --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_oIZdkCbZEdqh1LYUOGRh2A CRC: 687981015 --><p> |
| One of the project manager's key responsibilities is to know about the project team's problems and issues. The manager |
| needs to focus on problems that are blocking progress. A quick, daily meeting is usually a good way to monitor those |
| problems and issues. |
| </p> |
| <p> |
| Identify the cause and impact of problems and exceptions as they arise. Identify possible solutions for problems that |
| have an immediate impact on the short-term goals and objectives and identify who needs to be involved in implementing |
| the solution. Then, define the corrective actions and implement them. <br /> |
| </p><!-- END:sectionDescription,_oIZdkCbZEdqh1LYUOGRh2A --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_xiFJwCbZEdqh1LYUOGRh2A CRC: 509729981 -->Identify and manage risks<!-- END:name,_xiFJwCbZEdqh1LYUOGRh2A --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_xiFJwCbZEdqh1LYUOGRh2A CRC: 179667628 --><p> |
| Identify risks as soon as the project starts and continue identifying and managing risks throughout the project. The |
| risk list should be revisited weekly, or as a minimum once per iteration, see <a class="elementLinkWithType" href="./../../openup_basic/guidances/concepts/risk,_0bsLgMlgEdmt3adZL5Dmdw.html" guid="_0bsLgMlgEdmt3adZL5Dmdw">Concept: Risk</a> and <a class="elementLinkWithType" href="./../../openup_basic/workproducts/risk_list,_Ckay8Cc_EduIsqH1Q6ZuqA.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Artifact: Risk List</a> for more details. The entire team should be involved in |
| identifying and mitigating risk. |
| </p><!-- END:sectionDescription,_xiFJwCbZEdqh1LYUOGRh2A --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_Br6VECuxEdqTIKp3l5PtzQ CRC: 479485767 -->Reprioritize work as needed<!-- END:name,_Br6VECuxEdqTIKp3l5PtzQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_Br6VECuxEdqTIKp3l5PtzQ CRC: 3611697103 -->When a team is falling significantly behind, or critical problems occur, it may be necessary to reprioritize tasks to |
| ensure that the team delivers a useful product increment by the end of the iteration, while maximizing stakeholder value. |
| In these rare cases, the project manager should work with the team and stakeholders on revising the iteration plan and, as |
| necessary, reduce the emphasis on less critical tasks.<!-- END:sectionDescription,_Br6VECuxEdqTIKp3l5PtzQ --> |
| </body> |
| </html> |
