| <?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="_fPbdIKe2Edmzde8VFK5bxg" |
| name="plan_the_project,_0lC70MlgEdmt3adZL5Dmdw" guid="_fPbdIKe2Edmzde8VFK5bxg" |
| changeDate="2007-04-12T11:51:12.011-0700" version="1.0.0"> |
| <mainDescription>Developing the project plan provides an opportunity for the team to agree on project scope, objectives, initial timeframe,
 |
| 
 |
| and deliverables. It allows the team to begin demonstrating self-organization by defining success criteria and work
 |
| 
 |
| practices to be used. Collaboration and consensus by all key project participants is the goal, but the project manager has
 |
| 
 |
| ultimate responsibility for ensuring that everybody is committed to the plan.</mainDescription> |
| <sections xmi:id="_JLWeYOeUEdusqr8cJFUf_w" name="Establish a cohesive team" guid="_JLWeYOeUEdusqr8cJFUf_w"> |
| <sectionDescription>Project planning, even at the summary level, should not be done in isolation since it outlines what the project will
 |
| deliver and how. The team starts by discussing who plays which roles and agrees on their responsibilities. The project
 |
| manager needs to make sure that staffing is made in accordance with the project's interests and that every necessary role
 |
| is covered.</sectionDescription> |
| </sections> |
| <sections xmi:id="_oQ7PQOeUEdusqr8cJFUf_w" name="Determine project size and scope" |
| guid="_oQ7PQOeUEdusqr8cJFUf_w"> |
| <sectionDescription><p>
 |
| The&nbsp;team produces rough size estimates for each item&nbsp; in the <a class="elementLinkWithType"
 |
| href="./../../openup/workproducts/work_items_list.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items
 |
| List</a>&nbsp;(see <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/agile_estimation.html"
 |
| guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>).&nbsp; Considering product <a class="elementLink"
 |
| href="./../../openup/workproducts/vision.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>, the estimates will be used
 |
| for discussing with the stakeholders priorities for what seems realistic to develop within the constraints of the
 |
| project.&nbsp;
 |
| </p>
 |
| <p>
 |
| If the project is feature-driven, the team looks at how many people they would need to complete these work items, which
 |
| gives them a high level understanding of project duration, staffing profile, and scope.&nbsp;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.
 |
| Out-of-scope work can be considered in future releases.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_pzgcUOeUEdusqr8cJFUf_w" name="Evaluate risks" guid="_pzgcUOeUEdusqr8cJFUf_w"> |
| <sectionDescription><p>
 |
| The team identifies project risks, performs a qualitative risk analysis to assess their order of magnitude, and updates
 |
| the <a class="elementLinkWithType" href="./../../openup/workproducts/risk_list.html"
 |
| guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Artifact: Risk List</a>. The project manager facilitates the team decision about which
 |
| risks they should respond to, and which risks they should watch for.
 |
| </p>
 |
| <p>
 |
| Responses may include avoiding or mitigating risks, exploring opportunities or increasing the probability and positive
 |
| impacts of the risk. Depending on the case, work items may have to be added or removed from the Work Items List to make
 |
| sure that responses will be prioritized and handled by the team along with project work. As it is not feasible to plan
 |
| responses for all risks identified, the team can decide to accept some of them. Risks to watch will be communicated to
 |
| stakeholders and remain on the Risk List and actions will be determined only if they occur.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_sWzfgOeUEdusqr8cJFUf_w" name="Outline project lifecycle" guid="_sWzfgOeUEdusqr8cJFUf_w"> |
| <sectionDescription><p>
 |
| Define the iteration length and use it to assess target velocity (see <a class="elementLinkWithType"
 |
| href="./../../openup/guidances/guidelines/agile_estimation.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile
 |
| Estimation</a>). The number of items to be delivered in each iteration will be set by the velocity of the team and the
 |
| estimates for each item. The team uses the Work Items List to outline what features to implement in what iteration,
 |
| putting top priority work items first, including planned responses to the higher risks or opportunities.
 |
| </p>
 |
| <p>
 |
| OpenUP organizes iterations into a set of phases. Each phase in the project lifecycle will end with a milestone aimed
 |
| at providing stakeholders with&nbsp;oversight and steering mechanisms to control project funding, scope, risk exposure,
 |
| value provided, and other aspects of the process (see <a class="elementLinkWithType"
 |
| href="./../../openup/guidances/concepts/project_lifecycle.html" guid="_nSfVwCNYEdyCq8v2ZO4QcA">Concept: Project
 |
| Lifecycle</a>)
 |
| </p>
 |
| <p>
 |
| You don't need to spend too much time in doing this planning. The Project plan should document only&nbsp;&nbsp;a brief
 |
| summary of&nbsp; project milestones&nbsp;and 1-3 objectives for each iteration. Do not commit individual work items to
 |
| the plan, since this will force too much re-planning. The goal is just to create a high-level plan outlining
 |
| how&nbsp;the team&nbsp;can build the resulting application in the given set of iterations. Extra level of detail will
 |
| be achieved in other planning sessions throughout the project (see <a class="elementLinkWithType"
 |
| href="./../../openup/tasks/plan_iteration.html" guid="_0keUEMlgEdmt3adZL5Dmdw">Task: Plan Iteration</a>). You may need
 |
| to revisit&nbsp;this plan&nbsp;later to adap it based on what you will learn&nbsp;by&nbsp;running&nbsp;the iterations
 |
| (see <a class="elementLinkWithType" href="./../../openup/workproducts/iteration_plan.html"
 |
| guid="_0aQBEslgEdmt3adZL5Dmdw">Artifact: Iteration Plan</a>&nbsp;from previous iterations).
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_rGkmsOeUEdusqr8cJFUf_w" name="Establish costs and articulate value" |
| guid="_rGkmsOeUEdusqr8cJFUf_w"> |
| <sectionDescription><p>
 |
| Develop a rough order of magnitude estimate for the costs of resources needed to complete project work items.&nbsp; A
 |
| simplified project costing model&nbsp;can be&nbsp;applied by&nbsp;multiplying the approximate cost per person for the
 |
| entire team by the length of an iteration to derive ongoing financial impact (i.e., cost per iteration). This first
 |
| round of planning should keep things very rough and flexible. The goal is just to articulate value against the budget
 |
| constraints of the project and help stakeholders to decide whether it's worth moving forward with the project or not.
 |
| If necessary propose options to decrease costs, such as removing from the scope low value and high cost work items.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_tuymIOeUEdusqr8cJFUf_w" name="Plan deployment" guid="_tuymIOeUEdusqr8cJFUf_w"> |
| <sectionDescription>Plan the strategy for deploying the software (and its updates) into the production environment. Discuss release timeframe
 |
| with the operations and support departments to ensure that your project fits into your overall corporate deployment system.
 |
| If you are replacing an existing system, decide whether you will run the new system in parallel with it or you will perform
 |
| a cutover. You may also have to negotiate with the owners of the systems that the new system has dependencies on. Update
 |
| the Work Items List with additional work that may be needed for deployment. Add significant deployment risks to the Risk
 |
| List and, if necessary, make adjustments to the Project Plan.</sectionDescription> |
| </sections> |
| <keyConsiderations><p>
 |
| 
 |
| 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&nbsp;necessary.
 |
| 
 |
| </p></keyConsiderations> |
| <purpose>Get stakeholder buy-in for starting the project and team commitment to move forward with it. This plan can be updated along
 |
| 
 |
| the project based on feedback and changes in the environment.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
