| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription 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" epf:version="1.0.0" xmi:id="-buxz4BVToq97bSxaqyjySg" name="work_items_list,_rGNWsCbSEdqh1LYUOGRh2A" guid="-buxz4BVToq97bSxaqyjySg" changeDate="2006-10-30T14:42:59.632-0800" version="1.0.0"> |
| <mainDescription><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 needs to be done, get references to |
| material required to carry out the work, and one place to go to report progress made. |
| </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. Work Items are analyzed and broken down into smaller Work Items so they |
| can 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. |
| </p></mainDescription> |
| <purpose>To collect all requests for work that will potentially be taken on within the project, so work can be prioritized, effort |
| estimated and progress tracked.</purpose> |
| <representationOptions><h3> |
| As a spreadsheet or database |
| </h3> |
| <p> |
| The Work Items List can be captured as a separate artifact, represented by a spreadsheet or database table, see <a class="elementLinkWithType" href="./../../openup_basic/guidances/examples/work_items_list,_nHomIDgzEdu4E8ZdmlYjtA.html" guid="_nHomIDgzEdu4E8ZdmlYjtA">Example: Work Items List</a>. |
| </p> |
| <h3> |
| In specific tools |
| </h3> |
| <p> |
| Project Management, Requirements Management and Change Request tools are an option to capture the list of work to be |
| done. |
| </p> |
| <h3> |
| Subset As part of the Iteration Plan |
| </h3> |
| <p> |
| The <a class="elementLinkWithType" href="./../../openup_basic/workproducts/iteration_plan,_0aQBEslgEdmt3adZL5Dmdw.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Artifact: Iteration Plan</a> typically references Work Items that are assigned to that |
| iteration. If the team is capturing the Iteration Plan on a Whiteboard for example, the team may choose to reference |
| high-level work items in the Work Items List that are assigned to the iteration, and maintain low-level child work |
| items used to track day-to-day work only within an iteration plan.<br /> |
| </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |