| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-PbfqVxB_j9KN-Jx39_pEUA" |
| name="manage_iteration,_8S2aICbYEdqh1LYUOGRh2A" guid="-PbfqVxB_j9KN-Jx39_pEUA" |
| changeDate="2007-07-18T03:27:16.729-0700" version="1.0.0"> |
| <mainDescription><p>
 |
| Developing the team is part of executing the project. The project manager is responsible for improving the interaction
 |
| of team members and the trust among the team, 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 to meet the iteration objectives by removing constraints and monitoring the progress
 |
| and work remaining to completion. When the team is falling behind,&nbsp;the project&nbsp;manager&nbsp;helps the team to
 |
| assess how it can reduce work and still meet the iteration goals. Stakeholders' needs must be continuously met and
 |
| their issues resolved throughout the iteration. The stakeholders may need to be involved in approving changes and
 |
| actions that affect them.
 |
| </p></mainDescription> |
| <sections xmi:id="_OE65ICuxEdqTIKp3l5PtzQ" name="Capture and communicate status" |
| guid="_OE65ICuxEdqTIKp3l5PtzQ"> |
| <sectionDescription><p>
 |
| The project manager needs to do the following:&nbsp;
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| continuously monitor the project to ensure it is progressing appropriately
 |
| </li>
 |
| <li>
 |
| enable the team to react as soon as possible to any change
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Many alternative means may be used to track the status. Quick, daily meetings with the entire project team 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="elementLinkWithType"
 |
| href="./../../openup/guidances/guidelines/daily_meetings.html" guid="_251UMCmREdyy6Oss2-0s1g">Guideline: Daily
 |
| Meetings</a>.
 |
| </p>
 |
| <p>
 |
| Another approach is the collection of basic metrics, ideally automatically generated from the tools at hand, or
 |
| manually assembled. <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">Burndown
 |
| charts are one of the most useful project progress metrics. They show how many work items where accomplished during
 |
| previous iterations (or days) and the remaining work. They can be used to track project releases and iterations
 |
| (see&nbsp;<a class="elementLinkWithType" href="./../../openup/guidances/reports/project_burndown.html"
 |
| guid="_ePrt8Dj3EduxovfWMDsntw">Report: Project Burndown</a>&nbsp;and <a class="elementLinkWithType"
 |
| href="./../../openup/guidances/reports/iteration_burndown.html" guid="_uAzgkDg3Edu4E8ZdmlYjtA">Report: Iteration
 |
| Burndown</a>).&nbsp;Communicating project status is as important as gathering it. Keep the information visible to
 |
| stakeholders and project team at all times.</span> The <a class="elementLinkWithType"
 |
| href="./../../openup/workproducts/project_plan.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Artifact: Project
 |
| Plan</a>&nbsp;should outline which metrics the project should use.
 |
| </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.&nbsp;A record of issues that have to be solved within the team may be kept in the <a
 |
| class="elementLink" href="./../../openup/workproducts/iteration_plan.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration
 |
| Plan</a><font color="#003399">.</font>
 |
| </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;
 |
| </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="./../../openup/workproducts/risk_list_C4B6F290.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>&nbsp;should be revisited weekly, or as 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 prevents the team&nbsp;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&nbsp;to revise the <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a> and, as necessary, reduce the emphasis on less critical tasks postponing
 |
| them to a subsequent iteration. In rare cases, if the iteration objectives still seem impossible to be met, the team might
 |
| consider terminating the iteration or reformulating the iteration to a new objective.</sectionDescription> |
| </sections> |
| <purpose><p>
 |
| 
 |
| 
 |
| To help the team to meet the iteration objectives and&nbsp;keep the project on track.&nbsp;Manage stakeholders
 |
| 
 |
| 
 |
| expectations as technical and practical discoveries are made during the project.
 |
| 
 |
| 
 |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
