| <?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-PbfqVxB_j9KN-Jx39_pEUA" name="manage_iteration,_8S2aICbYEdqh1LYUOGRh2A" guid="-PbfqVxB_j9KN-Jx39_pEUA" changeDate="2008-07-14T09:47:00.000-0700" version="1.0.0"> |
| <mainDescription><p>
 |
| Developing the team is part of executing the project. The project manager is responsible for improving the interactions
 |
| and trust between team members, incorporating team building into project activities, and empowering the team to make
 |
| decisions. Management is done by objectives and not by time reporting.
 |
| </p>
 |
| <p>
 |
| The project manager helps the team meet the iteration objectives by removing constraints, and by monitoring the
 |
| progress and work remaining to completion. When the team is falling behind, the project manager helps the team assess
 |
| how it can reduce work and still meet the iteration goals. Involve stakeholders in approving changes and actions that
 |
| affect them, so that their objectives for the iteration can be met, and the issues they raise can be solved throughout
 |
| the iteration.
 |
| </p></mainDescription> |
| <keyConsiderations><p>
 |
| Select an approach for the collection of basic metrics: ideally, they are automatically generated from the tools at
 |
| hand, but can be manually assembled, or both. <span
 |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Outline
 |
| which metrics the project should use in the <a class="elementLink"
 |
| href="./../../core.mgmt.slot.base/workproducts/project_definition_and_scope_slot_BB8EB6F7.html"
 |
| guid="_RJMUcNpUEdyzZqGyZ7hwdw">[Project Definition and Scope]</a>.</span>
 |
| </p></keyConsiderations> |
| <sections xmi:id="_OE65ICuxEdqTIKp3l5PtzQ" name="Track current iteration progress" guid="_OE65ICuxEdqTIKp3l5PtzQ"> |
| <sectionDescription><p>
 |
| Continuously monitor the iteration to ensure that it is progressing appropriately. Track the progress of the current
 |
| iteration by maintaining visibility on the status of the items that are being worked on during the iteration. In
 |
| particular, it is important to be able to understand how quickly the team is moving through the work scheduled for the
 |
| iteration, and how accurate the estimates were <a class="elementlinkwithusertext"
 |
| href="./../../core.mgmt.common.base/guidances/supportingmaterials/references.mgmt_D80619F3.html#LEF07"
 |
| guid="_JlTPUM6aEdyuBO4ZIzcyig">[LEF07]</a>.
 |
| </p>
 |
| <p>
 |
| Share information about the progress being made by having quick, frequent meetings with the entire project team. These
 |
| 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="elementLink"
 |
| href="./../../core.mgmt.slot.base/guidances/guidelines/collaboration_guidance_slot_D3B8DD40.html"
 |
| guid="_68JUYN8-Edyhmsbt0Xyl8A">[Collaboration Guidance]</a> for more information.
 |
| </p>
 |
| <p>
 |
| Track the status of each work item by using visual indicators of state information (for example: defined, completed,
 |
| accepted) in a wall or automated tool. Since iterations are typically fixed in duration, another primary way to gauge
 |
| progress is to continuously monitor current status and also estimate how much work remains. Plot an iteration burndown
 |
| chart on a daily basis in order to visualize progress on a given iteration. This chart is plotted with the total
 |
| estimates for all the items that are not yet started and the estimated remaining effort for any item in progress. See
 |
| <a class="elementLinkWithType"
 |
| href="./../../practice.mgmt.iterative_dev.base/guidances/reports/iteration_burndown_9C1C96F5.html"
 |
| guid="_uAzgkDg3Edu4E8ZdmlYjtA">Report: Iteration Burndown</a> for more information.
 |
| </p>
 |
| <p>
 |
| Take corrective actions to adjust the course of the iteration if the burndown chart shows that the work will not be
 |
| finished as planned.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_urvQkGSyEd2DNqLAFatITA" name="Capture and communicate project status" guid="_urvQkGSyEd2DNqLAFatITA"> |
| <sectionDescription><p>
 |
| Because outside stakeholders do not participate in the daily activities of the team, it is important that the status of
 |
| the project should be communicated to them as often as possible. This communication significantly lowers the risk of
 |
| disconnect between the development team and the stakeholders. The status provides the team with data they can use to
 |
| improve their development process.
 |
| </p>
 |
| <p>
 |
| Besides the iteration status, the overall project status can be captured and communicated in a burndown report for the
 |
| whole project. This report should show the progress toward the release date, and should be updated at the end of every
 |
| iteration (when metrics, such as the team's velocity, can also be provided). This allows the team to predict what it
 |
| can accomplish on the remaining project iterations. Other metrics (such as number of test cases passed) can also be
 |
| used to present iteration and project status.
 |
| </p>
 |
| <p>
 |
| Keep the status information visible to stakeholders and the project team at all times in a project workspace (walls or
 |
| automated tool), where stakeholders can come and experience first-hand the progress being made by the team.
 |
| </p></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. A record of issues that have to be solved within the team may be kept in the <a
 |
| class="elementLink" href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
 |
| guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a><font color="#003399">.</font> If a critical problem or issue is
 |
| likely to take a lot of time to solve, capture it in the Work Items List so that it can be assigned to an individual.
 |
| </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. Identify who needs to be involved in implementing the
 |
| solution. Define the corrective actions and implement them.
 |
| </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
 |
| <a class="elementLink" href="./../../core.mgmt.common.extend_supp/workproducts/risk_list_C4B6F290.html"
 |
| guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a> should be revisited weekly, or at a minimum once per iteration. The entire
 |
| team should be involved in identifying and mitigating risks.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_Br6VECuxEdqTIKp3l5PtzQ" name="Manage objectives" guid="_Br6VECuxEdqTIKp3l5PtzQ"> |
| <sectionDescription>When a team is falling significantly behind, or critical problems occur that prevent the team from meeting the iteration
 |
| objectives, it may be necessary to descope work to ensure that the team delivers a useful product increment by the end of
 |
| the iteration, while maximizing stakeholder value. The project manager should work with the team and stakeholders to revise
 |
| the <a class="elementLink" href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
 |
| guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a> and, as necessary, reduce the emphasis on less critical tasks by
 |
| postponing them to a subsequent iteration. In rare cases, if the iteration objectives still seem impossible to meet, the
 |
| team might consider terminating the iteration or reformulating the iteration to a new objective.</sectionDescription> |
| </sections> |
| <purpose><p>
 |
| To help the team meet the iteration objectives and keep the project on track. Manage stakeholders' expectations as
 |
| technical and practical discoveries are made during the project.
 |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
