| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-PbfqVxB_j9KN-Jx39_pEUA" name="manage_iteration,_8S2aICbYEdqh1LYUOGRh2A" guid="-PbfqVxB_j9KN-Jx39_pEUA" changeDate="2006-08-31T06:45:37.803-0700" version="1.0.0"> |
| <sections xmi:id="_OE65ICuxEdqTIKp3l5PtzQ" name="Capture status" guid="_OE65ICuxEdqTIKp3l5PtzQ"> |
| <sectionDescription><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&nbsp;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>&nbsp;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>&nbsp;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>&nbsp;and <a class="elementLinkWithType" href="./../../openup_basic/guidances/reports/project_burndown,_ePrt8Dj3EduxovfWMDsntw.html" guid="_ePrt8Dj3EduxovfWMDsntw">Report: Project Burndown</a>&nbsp;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>&nbsp;for more information. |
| </li> |
| </ul> |
| <br /></sectionDescription> |
| </sections> |
| <sections xmi:id="_ztF0UCuxEdqTIKp3l5PtzQ" name="Communicate status" guid="_ztF0UCuxEdqTIKp3l5PtzQ"> |
| <sectionDescription><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></sectionDescription> |
| </sections> |
| <sections xmi:id="_oIZdkCbZEdqh1LYUOGRh2A" name="Handle exceptions and problems" guid="_oIZdkCbZEdqh1LYUOGRh2A"> |
| <sectionDescription><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.&nbsp;<br /> |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_xiFJwCbZEdqh1LYUOGRh2A" name="Identify and manage risks" guid="_xiFJwCbZEdqh1LYUOGRh2A"> |
| <sectionDescription><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>&nbsp;and <a class="elementLinkWithType" href="./../../openup_basic/workproducts/risk_list,_Ckay8Cc_EduIsqH1Q6ZuqA.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Artifact: Risk List</a>&nbsp;for more details. The entire team should be involved in |
| identifying and mitigating risk. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_Br6VECuxEdqTIKp3l5PtzQ" name="Reprioritize work as needed" guid="_Br6VECuxEdqTIKp3l5PtzQ"> |
| <sectionDescription>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.</sectionDescription> |
| </sections> |
| <purpose><p> |
| Identify blocking issues and/or opportunities early to take action and keep the project on track. |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
