| <?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.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" xmi:id="-buxz4BVToq97bSxaqyjySg" name="work_items_list,_rGNWsCbSEdqh1LYUOGRh2A" guid="-buxz4BVToq97bSxaqyjySg" changeDate="2008-10-08T09:41:03.000-0700" 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&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></mainDescription> |
| <keyConsiderations><p>
 |
| Work Items should contain estimates. See guidelines on managing work items and agile estimation.
 |
| </p></keyConsiderations> |
| <purpose>To collect all requests for work that will potentially be taken on within the project, so that work can be prioritized,
 |
| effort estimated, and progress tracked.</purpose> |
| <impactOfNotHaving>Without this artifact, there is not a single place that provides a list of all of the work to be done and its current
 |
| status.&nbsp; Individual team members may also be unclear as to&nbsp;what work has been&nbsp;assigned to them.</impactOfNotHaving> |
| <reasonsForNotNeeding>This artifact may not be needed&nbsp;if the work assignments are going to be managed using a different technique or
 |
| artifact.</reasonsForNotNeeding> |
| <briefOutline><p>
 |
| This artifact should consist of the following information for each work item:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Name and Description
 |
| </li>
 |
| <li>
 |
| Priority
 |
| </li>
 |
| <li>
 |
| Size Estimate
 |
| </li>
 |
| <li>
 |
| State
 |
| </li>
 |
| <li>
 |
| References
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Assigned work items should also contain the following:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Target Iteration or Completion Date
 |
| </li>
 |
| <li>
 |
| Assignee
 |
| </li>
 |
| <li>
 |
| Estimated Effort Remaining
 |
| </li>
 |
| <li>
 |
| Hours Worked
 |
| </li>
 |
| </ul></briefOutline> |
| <representationOptions><p>
 |
| The recommended representation for the&nbsp;work items list is to&nbsp;capture it&nbsp;as a separate artifact,
 |
| represented by a spreadsheet or database table. See <a class="elementLinkWithType"
 |
| href="./../../core.mgmt.common.extend_supp/guidances/examples/work_items_list_F527B77D.html"
 |
| guid="_nHomIDgzEdu4E8ZdmlYjtA">Example: Work Items List</a>.
 |
| </p>
 |
| <p>
 |
| Alternatively, the work items list may be captured in tools such as project management, requirements management, or
 |
| change request. In fact, the work items list may&nbsp;be spread over several tools, as&nbsp;you may choose to keep
 |
| different types of work items in different repositories to take advantage of features in those tools.&nbsp;For example,
 |
| you could use a requirements composition or management tool to track information about requirements, and use another
 |
| tool to capture defects.&nbsp;Work items may start in one representation (such as in a spreadsheet) and move to more
 |
| sophisticated tools over time, as the number of work items and the metrics you wish to gather grows more sophisticated.
 |
| </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
