| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:PracticeDescription 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" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-txho2faQkfNfyMw-X-Y_aA" |
| name="release_planning,_ijFkcB4sEd2bS8fFOQ7WWA" guid="-txho2faQkfNfyMw-X-Y_aA" |
| changeDate="2009-07-15T16:19:13.316-0700" version="7.5.0"> |
| <additionalInfo><h3>
 |
| Additional Resources
 |
| </h3>
 |
| <p>
 |
| For more information on the Release Planning approach, see the following:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Kroll, P. and&nbsp;Kruchten, P. <em>The Rational Unified Process Made Easy</em>, Addison Wesley, 2003. Chapter 12:
 |
| Planning an Iterative Project.
 |
| </li>
 |
| </ul></additionalInfo> |
| <problem><h3>
 |
| Why adopt this practice?
 |
| </h3>
 |
| <p>
 |
| Release&nbsp;Planning improves the accuracy of project planning, the ability to predict resource usage, and the ability
 |
| to meet established delivery dates. In adopting this practice, the project team can better manage scarce resources and
 |
| focus on delivering scope with higher quality and value to the organization.
 |
| </p>
 |
| <p>
 |
| In some development approaches, project managers would plan the whole project at project initiation, and then execute
 |
| the plan, with little or no modifications to the original project plan unless there were significant scope changes or
 |
| risks that derailed the project. These approaches depend a lot on the project managers' personal knowledge of the
 |
| scope, and the resources available to deliver the scope. In many cases, these plans would become inaccurate and useless
 |
| after the first one or two phases. At that point, many project managers would simply manage the milestones and abandon
 |
| the detailed tasks.
 |
| </p>
 |
| <p>
 |
| Even seasoned project managers can benefit from Release Planning. As more and more software developers move to
 |
| iterative methods for delivering software, the need to perform just-in-time project planning is critical.
 |
| Planning&nbsp;for the next few weeks is always more accurate than planning&nbsp;for the next few months. The goal of
 |
| this practice is to balance the high-level and low-level planning such that detailed (low-level) planning occurs
 |
| just-in-time to support the successful delivery of the software products.<br />
 |
| &nbsp;
 |
| </p></problem> |
| <background><p>
 |
| Project planning is very inaccurate when you attempt to plan beyond the initial phases of work for any
 |
| project.&nbsp;The Release Planning practice ensures that your planning efforts are iterative in nature, aligned with
 |
| the software delivery to ensure a more accurate estimate of work efforts.
 |
| </p>
 |
| <p>
 |
| In many cases, the planning horizon for a software project is a hard concept to understand. Software development
 |
| project managers tend to want to plan the entire project, and then let the team work the plan, resisting changes to the
 |
| plan as it executes. The Release Planning practice emphasizes the need to plan the next iteration in detail, while
 |
| planning the whole project at a high level. This practice also encourages the project manager to feel comfortable with
 |
| re-planning as needed to ensure accuracy in delivery dates and costs based on events that impact the project.<br />
 |
| </p></background> |
| <application><p>
 |
| The best way to read this practice is first to&nbsp;get familiar&nbsp;with its overall structure: what it is in it and
 |
| how it is organized.&nbsp;
 |
| </p>
 |
| <p>
 |
| Start with the available work products:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <a class="elementLink"
 |
| href="./../../../practice.mgmt.two_level_project_planning.base/workproducts/project_plan_1CDBB7E4.html"
 |
| guid="_0a6vcMlgEdmt3adZL5Dmdw">Project Plan</a>
 |
| </li>
 |
| <li>
 |
| <a class="elementLink" href="./../../../core.mgmt.common.extend_supp/workproducts/risk_list_C4B6F290.html"
 |
| guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Also, check the&nbsp;work product templates and&nbsp;reports. See:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <a class="elementLink"
 |
| href="./../../../practice.mgmt.two_level_project_planning.base/guidances/templates/project_plan_1534BA2B.html"
 |
| guid="_0c7hoMlgEdmt3adZL5Dmdw">Project Plan</a> template
 |
| </li>
 |
| <li>
 |
| <a class="elementLink"
 |
| href="./../../../practice.mgmt.two_level_project_planning.base/guidances/examples/project_burndown_report_example_847643C1.html"
 |
| guid="_Yiq2EDcGEdyTZ9G7ByfQTw">Project Burndown Report</a> example
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Finally, get more details on how to perform project planning and staff a project by looking at:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <a class="elementLink"
 |
| href="./../../../practice.mgmt.two_level_project_planning.base/tasks/plan_the_project_A4A80C96.html"
 |
| guid="_0lC70MlgEdmt3adZL5Dmdw">Plan Project</a>&nbsp;task
 |
| </li>
 |
| <li>
 |
| <a class="elementLink"
 |
| href="./../../../practice.mgmt.two_level_project_planning.base/guidances/guidelines/staffing_project_70705561.html"
 |
| guid="_Jq64EJjsEduad8I_c-ogIA">Staffing a Project</a> guideline
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| See more information on <a class="elementLink"
 |
| href="./../../../practice.mgmt.two_level_project_planning.base/guidances/roadmaps/how_to_adopt_520D7115.html"
 |
| guid="_ihr3sOMPEdyM47cGD2jiaQ">How to Adopt the Two-Level Project Planning Practice</a>.
 |
| </p></application> |
| </org.eclipse.epf.uma:PracticeDescription> |
