<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription 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" xmi:id="-G1Oxlk6F0R09vClqy1EzOw" name="work_items_list,_7vEXEMA4EdqSgKaj2SZBmg" guid="-G1Oxlk6F0R09vClqy1EzOw" changeDate="2007-07-24T05:09:42.625+0330" version="7.1.0">
  <mainDescription>The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../openup/workproducts/work_items_list-3.html&quot;&#xD;
guid=&quot;_rGNWsCbSEdqh1LYUOGRh2A&quot;>Artifact: Work Items List&lt;/a>&amp;nbsp;captures all scheduled work to be done within the&#xD;
project, as well as proposed work that may affect the product. Some of the Work Items may be implemented in this project,&#xD;
some of them may be implemented in a future project, and some of them may never be implemented. &#xD;
&lt;p>&#xD;
    Some of the Work Items may still be poorly defined; therefore, it could represent a big chunk of work, requiring&#xD;
    potentially several staff months of effort. As the priority of these Work Items increases, they are typically&#xD;
    decomposed into smaller work items that represent specific and well-defined tasks that may take hours or days to&#xD;
    address, see &lt;a class=&quot;elementLink&quot; href=&quot;./../../../openup/guidances/concepts/micro_increments.html&quot;&#xD;
    guid=&quot;_S80VwCNbEdyCq8v2ZO4QcA&quot;>Micro-Increments&lt;/a>. In other cases, specific and well-defined Work Items are created&#xD;
    directly, representing, for example, a defect to be addressed, as this figure illustrates.&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;center&quot;>&#xD;
    &lt;strong>&lt;font face=&quot;Verdana, Arial, Helvetica, sans-serif&quot; size=&quot;2&quot;>Work Items List provides one prioritized list of&#xD;
    scheduled and proposed work&lt;/font>&lt;/strong>&#xD;
&lt;/p>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
    &lt;br />&#xD;
    &lt;img alt=&quot;&quot; src=&quot;resources/work_item_prioritization_diagram.jpg&quot; />&lt;br />&#xD;
&lt;/div>&#xD;
&lt;p>&#xD;
    A Work Item may represent work associated with a defect, enhancement request, change request, use case, scenario, user&#xD;
    story, supporting requirement, stakeholder request, or anything else that captures a potential requirement or&#xD;
    improvement to your system. A Work Item may reference any type of requirement or other useful information that guides&#xD;
    you in what needs to be done.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    A big advantage with the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../openup/workproducts/work_items_list-3.html&quot;&#xD;
    guid=&quot;_rGNWsCbSEdqh1LYUOGRh2A&quot;>Artifact: Work Items List&lt;/a>&amp;nbsp;is that it enables you to prioritize only one list&#xD;
    containing all of the things that may need to be addressed, whether the Work Item represent a work related to a&#xD;
    requirement, enhancement, or defect. The one exception is that we prioritize the risk list separately.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Nothing in the project will get done if not represented or mapped to a Work Item. This means that all requirements,&#xD;
    defect reports, and change requests have to be mapped to a Work Item at some stage. Also, a developer will not take on&#xD;
    work that is not represented in a Work Item. Only Work Items needs to be prioritized. This also means that tracking&#xD;
    Work Items are a primary means of understanding the status of the project.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    There are two major types of Work Items:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Unscheduled Work Items:&lt;/strong> These Work Items have not yet been assigned to an iteration, and there is&#xD;
        no detailed effort estimate for the Work Item yet.&lt;br />&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Scheduled Work Items:&lt;/strong> These Work Items are assigned to an iteration, and they typically have an&#xD;
        additional set of attributes filled in, such as detailed effort estimates.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h1>&#xD;
    Unscheduled Work Items&#xD;
&lt;/h1>&#xD;
&lt;p>&#xD;
    Most Work Items are initially unscheduled, meaning that it has not yet been decided whether to do them and when to do&#xD;
    them. Unscheduled Work Items should always represent something meaningful to deliver to stakeholders, such a scenario&#xD;
    to be detailed, designed, implemented, and tested. You may consider capturing the following data for such Work Items:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Name&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Description&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Priority&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Size estimate, such as a point estimate (see &lt;a class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../openup/guidances/guidelines/agile_estimation.html&quot; guid=&quot;_CGHskBEdEdqY7JB6N6CW2w&quot;>Guideline: Agile&#xD;
        Estimation&lt;/a>)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        State, such as New, Assigned, Resolved, Verified, Closed (see Work Items states, which follows here)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Links to other reference material, such as requirements or detailed specifications of what needs to be done&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h1>&#xD;
    Scheduled Work Items&#xD;
&lt;/h1>&#xD;
&lt;p>&#xD;
    After a Work Item has been assigned to an iteration, it becomes &lt;i>scheduled&lt;/i>. We assign Work Items only to the&#xD;
    current or next iteration. There is no point in assigning Work Items to a specific future iteration, since we cannot&#xD;
    predict what a meaningful schedule will be more than an iteration in advance (see &lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../openup/guidances/guidelines/iteration_planning.html&quot; guid=&quot;_0auiMMlgEdmt3adZL5Dmdw&quot;>Guideline:&#xD;
    Iteration Planning&lt;/a>).&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The following additional attributes are useful for Scheduled Work Items:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Target iteration&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Responsible team member&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Effort estimate left, such as actual hours of work (see &lt;a class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../openup/guidances/guidelines/agile_estimation.html&quot; guid=&quot;_CGHskBEdEdqY7JB6N6CW2w&quot;>Guideline: Agile&#xD;
        Estimation&lt;/a>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Hours worked&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    This provides the information required to plan and manage an iteration. We can plan iterations by understanding effort&#xD;
    involved, and we can &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../openup/guidances/reports/iteration_burndown.html&quot;&#xD;
    guid=&quot;_uAzgkDg3Edu4E8ZdmlYjtA&quot;>Report: Iteration Burndown&lt;/a> by tracking how much work is left to do.&#xD;
&lt;/p>&#xD;
&lt;h1>&#xD;
    Work Item states&#xD;
&lt;/h1>&#xD;
&lt;p>&#xD;
    We have found the following states to be useful for tracking Work Items:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;b>New:&lt;/b> Work Item has been created, but not yet assigned to a team member.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Assigned:&lt;/b> A team member has been identified as responsible for the Work Item.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Resolved:&lt;/b> The team member responsible for the Work Items has implemented and tested the Work Item.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Verified:&lt;/b> The Work Item has been independently tested.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Closed:&lt;/b> The Work Item is no longer active.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    You may choose another set of states, based on your needs.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
