| <?xml version="1.0" encoding="UTF-8"?> |
| <xmi:XMI 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"> |
| <org.eclipse.epf.uma:ProcessDescription xmi:id="-b6sTuOuA7eFhaR_H3EfgBw" name="plan_manage_iteration,_oZgCsdOEEdyqlogshP8l4g" guid="-b6sTuOuA7eFhaR_H3EfgBw" version="7.2.0"> |
| <mainDescription><p> |
| This activity is performed throughout the project lifecycle. The goal of this activity is to identify risks and issues |
| early enough that they can be mitigated, to establish the goals for the iteration, and to support the development team |
| in reaching these goals. |
| </p> |
| <p> |
| The project manager and the team launch the iteration. The prioritization of work for a given iteration takes place. |
| The project manager, stakeholders, and team members agree on what is supposed to be developed during that iteration. |
| </p> |
| <p> |
| Team members sign up for the work items they will develop in that iteration. Each team member breaks down the work |
| items into development tasks and estimates the effort. This provides a more accurate estimate of the amount of time |
| that will be spent, and of what can be realistically achieved, in a given iteration. |
| </p> |
| <p> |
| As the iteration runs, the team meets regularly to report status of work completed, the work to do next, and issues |
| blocking the progress. In some projects, this status checking occurs in daily meetings, which allows for a more precise |
| understanding of how the work in an iteration is progressing. As necessary, the team makes corrections to achieve what |
| was planned. The overall idea is that risks and issues are identified and managed throughout the iteration, and |
| everyone knows the project status in a timely manner. |
| </p> |
| <p> |
| During iteration assessments, the key success criterion is the demonstration that planned functionality has been |
| implemented. Lessons learned are captured in order to modify the project or improve the process. If the iteration end |
| coincides with the phase end, make sure the objectives for that phase have been met (see <a class="elementLinkWithType" href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_milestones_5678231E.html" guid="_HNxbwMBJEdqSgKaj2SZBmg">Concept: Phase Milestones</a> for more information). |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ProcessDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-HoXXyN2BKM1DoI1eHGVrGw" name="plan_iteration,_y05RQNOJEdyqlogshP8l4g" guid="-HoXXyN2BKM1DoI1eHGVrGw"> |
| <refinedDescription><p>
 |
| During project planning, iterations are identified, but the estimates have an acceptable uncertainty due to the lack of
 |
| detail at the project inception. This task is repeated for each iteration within a release. It allows the team to
 |
| increase the accuracy of the estimates for one iteration, as more detail is known along the project.
 |
| </p>
 |
| <p>
 |
| Ensure that the team commits to a reasonable amount of work for the iteration, based on team performance from previous
 |
| iterations.
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-b0cwbrvCtusECT9Bx_eEkQ" name="iteration_plan,_y1MMMNOJEdyqlogshP8l4g" guid="-b0cwbrvCtusECT9Bx_eEkQ"> |
| <keyConsiderations><p>
 |
| Work items assigned to an iteration do not necessarily have the same priority. When selecting work items from the Work
 |
| Items List, the iteration plan may end up having work items with different priorities (for example, you assign the
 |
| remaining high priority work items, plus a few mid-priority ones from the Work Items List). Once work items have been
 |
| assigned to the iteration, the team ensures that they can complete all work, regardless of original work item
 |
| priorities. Deciding what to develop first on an iteration will vary across projects and iterations.
 |
| </p></keyConsiderations> |
| <refinedDescription><p>
 |
| This artifact captures the key milestones of an iteration, showing start and end dates, intermediate milestones,
 |
| synchronization points with other teams, demos, and so on. This artifact is also used to capture issues that need to be
 |
| solved during the iteration.
 |
| </p>
 |
| <p>
 |
| You should list a few objectives for the iteration, which will help guide you throughout the iteration. Also, assess at
 |
| the end if those objectives have been achieved.
 |
| </p>
 |
| <p>
 |
| The task assignments for an iteration are a subset of all tasks on the <a class="elementLinkWithType"
 |
| href="./../../core.mgmt.common.extend_supp/workproducts/work_items_list_39D03CC8.html"
 |
| guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>. Therefore, the iteration plan ideally references those
 |
| work items.
 |
| </p>
 |
| <p>
 |
| The evaluation criteria and iteration assessment information are captured in this artifact, so that you can communicate
 |
| results and actions from assessments.
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-uiigawastH3uIscV6br3Mg" name="risk_list,_y1MMMdOJEdyqlogshP8l4g" guid="-uiigawastH3uIscV6br3Mg"> |
| <keyConsiderations><p>
 |
| This list should capture the critical and serious risks. If you find this list extending beyond 20 items, carefully
 |
| consider whether they are really serious risks. Tracking more than 20 risks is an onerous task.
 |
| </p></keyConsiderations> |
| <refinedDescription><p>
 |
| This list identifies, in decreasing order of priority, all the <a class="elementLinkWithUserText"
 |
| href="./../../core.mgmt.common.base/guidances/termdefinitions/risk_33255339.html"
 |
| guid="_ii2LUEvGEdunZcj9T5hrMQ">risks</a> associated to a project.&nbsp;It serves as a focal point for project
 |
| activities, and is the basis around which iterations are organized.
 |
| </p>
 |
| <p>
 |
| See <a class="elementLinkWithType" href="./../../core.mgmt.common.extend_supp/guidances/concepts/risk_AF5840DA.html"
 |
| guid="_0bsLgMlgEdmt3adZL5Dmdw">Concept: Risk</a>&nbsp;for more details.<!--EndFragment-->
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-mTtAiA6WcEVWloBE8ZdcOg" name="work_items_list,_y1MMMtOJEdyqlogshP8l4g" guid="-mTtAiA6WcEVWloBE8ZdcOg"> |
| <keyConsiderations><p>
 |
| Work Items should contain estimates. See guidelines on managing work items and agile estimation.
 |
| </p></keyConsiderations> |
| <refinedDescription><p>
 |
| This artifact provides a focal point for the entire team:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| It provides one list containing all requests for additional capabilities or enhancement for that application. Note
 |
| that some of these requests may never be implemented, or be implemented in later projects.
 |
| </li>
 |
| <li>
 |
| It provides one list of all the work to be prioritized, estimated, and assigned within the project. The risk list
 |
| is prioritized separately.
 |
| </li>
 |
| <li>
 |
| It provides one place to go to for the development team to understand what&nbsp;micro-increments&nbsp;need to be
 |
| delivered, get references to material required to carry out the work, and report progress made.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| These are the typical work items that go on this list:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Use cases (and references to use-case specifications)
 |
| </li>
 |
| <li>
 |
| System-wide requirements
 |
| </li>
 |
| <li>
 |
| Changes and enhancement requests
 |
| </li>
 |
| <li>
 |
| Defects
 |
| </li>
 |
| <li>
 |
| Development tasks
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Work items can be very large in scope, especially when capturing requests for enhancements, such as "Support Financial
 |
| Planning" for a personal finance application. To allow the application to be developed in micro-increments, work items
 |
| are analyzed and broken down into smaller work items so that they can be assigned to an iteration, such as a use-case
 |
| scenario for&nbsp;"Calculate Net Worth". Further breakdown may be required to identify suitable tasks to be assigned to
 |
| developers, such as "Develop UI for Calculate Net Worth". This means that work items often have parent/child
 |
| relationships, where the lowest level is a specification and tracking device for micro-increments.
 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ZTgIJKYY8ZpIoo7b-pFrFg" name="manage_iteration,_zjF0ANOJEdyqlogshP8l4g" guid="-ZTgIJKYY8ZpIoo7b-pFrFg"> |
| <refinedDescription><p>
 |
| Developing the team is part of executing the project. Improve 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>
 |
| Help 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, help 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>
 |
| <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></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-2lpprtg7ud6uXyuBYZMnIg" name="assess_results,_0Qiv4NOJEdyqlogshP8l4g" guid="-2lpprtg7ud6uXyuBYZMnIg"> |
| <refinedDescription>Coordinate the assessment and discuss with the team how the iteration results will be best presented to stakeholders, so
 |
| that they can learn as much about the solution as possible. Listen to what the team has to say about what went wrong (and
 |
| what went right) during the iteration. This knowledge will help everybody make informed decisions about the next iteration
 |
| planning, and determine the best course of action for the project. This task is performed at the end of every iteration
 |
| until the end of the project.</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| </xmi:XMI> |
