| <?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" rmc:version="7.1.0" epf:version="1.0.0" xmi:id="_fPbdIKe2Edmzde8VFK5bxg" name="plan_the_project,_0lC70MlgEdmt3adZL5Dmdw" guid="_fPbdIKe2Edmzde8VFK5bxg" changeDate="2006-09-27T13:20:13.359-0700" version="1.0.0"> |
| <sections xmi:id="_lrYj0MBAEdqSgKaj2SZBmg" name="Evaluate risks" guid="_lrYj0MBAEdqSgKaj2SZBmg"> |
| <sectionDescription><p> |
| The project manager evaluates project risks with the team and updates the <a class="elementLink" href="./../../openup_basic/workproducts/risk_list,_Ckay8Cc_EduIsqH1Q6ZuqA.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>. The risk list will aid the team in prioritization of what to do in which iteration. Higher-ranked risks are |
| addressed in the earlier iterations. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_k1bY4MMsEdmdo9HxCRR_Gw" name="Determine project size and scope" guid="_k1bY4MMsEdmdo9HxCRR_Gw"> |
| <sectionDescription><p> |
| Analyze the size and the <a class="elementLink" href="./../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>&nbsp;of the project, and whether it is realistic to deliver what is asked for |
| within the constraints of the project. |
| </p> |
| <p> |
| If the project is feature-driven, meaning that release criteria is defined as a set of features captured in the <a class="elementLink" href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, the team assesses the size of these work items, see <a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/agile_estimation,_CGHskBEdEdqY7JB6N6CW2w.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>. They then look at how many people they would need to |
| complete these work items, which gives them a ballpark understanding of project duration, staffing profile, and scope. |
| </p> |
| <p> |
| If the project instead is date-driven, the team assesses how much work can roughly be done in the time-frame given and |
| using the available team, captured as a candidate list of work items. |
| </p> |
| <p> |
| The end result of the two approaches is the same; a rough understanding of the size of the capabilities to be |
| delivered, the size of the team, and expected time of completion. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_OfFTEABjEdqHlpDr8LcRqg" name="Define length, number, and objectives of iterations" guid="_OfFTEABjEdqHlpDr8LcRqg"> |
| <sectionDescription><p> |
| Determine iteration length, see <a class="elementLinkWithType" href="./../../openup_basic/guidances/concepts/iteration,_lam4ADkBEduxovfWMDsntw.html" guid="_lam4ADkBEduxovfWMDsntw">Concept: Iteration</a>, or use 4 weeks as default iteration length. Use iteration length |
| to assess target velocity, see <a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/agile_estimation,_CGHskBEdEdqY7JB6N6CW2w.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>. Based on the target velocity and overall size of the |
| project, calculate the number of iterations required. |
| </p> |
| <p> |
| Determine 1-3 high-level objectives for each iteration. The goal is to create a high-level plan outlining how you can |
| build the resulting application in the given set of iterations. The plan will change as you learn more, so time-box |
| this analysis to a few hours or less. Use the Work Items List to outline what features to implement in what iteration, |
| putting top priority work items first. This can be done rapidly by leveraging expected velocity and size estimate of |
| work items. |
| </p> |
| <p> |
| Produce a brief summary of your analysis in your plan by documenting 1-3 objectives for each iteration. Do not commit |
| individual work items to the plan, since this will force too much re-planning. For some projects, you may have to wait |
| until after the first iteration until you can provide a meaningful plan at this level of detail.<br /> |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_qcOtIE5dEdu3aqt7VHtzgw" name="Define phase milestones and refine iteration objectives" guid="_qcOtIE5dEdu3aqt7VHtzgw"> |
| <sectionDescription><p> |
| Phases provide a focus for a team on meeting key management objectives, see <a class="elementLinkWithType" href="./../../openup_basic/guidances/concepts/iteration,_lam4ADkBEduxovfWMDsntw.html" guid="_lam4ADkBEduxovfWMDsntw">Concept: Iteration</a>. For example the Elaboration phase should answer the question “Do |
| we agree on the overall solution, and do we understand risks, costs and schedule parameters reasonably well?” |
| </p> |
| <p> |
| With this in mind, the project manager determines the start and end dates of the phases and aligns the content of the |
| iterations with the perspective of the phase. Therefore the objectives of the iterations assigned to a phase, need to |
| map to the goals of its phase. The milestones, which guard the transition from one phase to another, will provide |
| checkpoints if these goals are satisfied.&nbsp; Revisit the plan to see if you should change the focus of iterations to |
| allow more rapid completion of&nbsp;certain phases. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_F2dQYABjEdqHlpDr8LcRqg" name="Map roles to team members" guid="_F2dQYABjEdqHlpDr8LcRqg"> |
| <sectionDescription><p> |
| The project manager assigns project members (people) to roles according to a table like this:<br /> |
| <br /> |
| </p> |
| <table style="WIDTH: 227px; HEIGHT: 116px" cellspacing="2" cellpadding="2" width="227" border="2"> |
| <tbody> |
| <tr> |
| <td> |
| <strong>Team Member&nbsp;</strong> |
| </td> |
| <td> |
| <strong>Analyst</strong> |
| </td> |
| <td> |
| <strong>Developer</strong>&nbsp; |
| </td> |
| </tr> |
| <tr> |
| <td> |
| John |
| </td> |
| <td> |
| &nbsp;&nbsp;&nbsp;&nbsp; X |
| </td> |
| <td> |
| </td> |
| </tr> |
| <tr> |
| <td> |
| Judy&nbsp;&nbsp; |
| </td> |
| <td> |
| </td> |
| <td> |
| &nbsp;&nbsp;&nbsp;&nbsp; X |
| </td> |
| </tr> |
| <tr> |
| <td> |
| Jim&nbsp; |
| </td> |
| <td> |
| &nbsp;&nbsp;&nbsp;&nbsp; X |
| </td> |
| <td> |
| &nbsp;&nbsp;&nbsp;&nbsp; X |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| <br /> |
| <p> |
| The project manager needs to make sure that the roles are staffed according to skills and interests and that every role |
| is covered. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_toVK0E5fEdu3aqt7VHtzgw" name="Tune and get concurrence on the plan" guid="_toVK0E5fEdu3aqt7VHtzgw"> |
| <sectionDescription>Gain agreement with stakeholders and the rest of the project team regarding the order of objectives and the duration of the |
| project and make adjustments as necessary.</sectionDescription> |
| </sections> |
| <purpose>To describe a roadmap that provides direction to the team and continually adapt it based on feedback and changes in the |
| environment.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
