blob: fb829e9b8a599cf0570bfb94587a308e08184c5a [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<!-- VERSION rmc:7.1.0 -->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<!-- START NON-TRANSLATABLE -->
<title>\openup_basic\workproducts\work_items_list.xmi</title>
</head>
<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
<body>
Element Name: work_items_list.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_rGNWsCbSEdqh1LYUOGRh2A CRC: 699774998 -->Work Items List<!-- END:presentationName,_rGNWsCbSEdqh1LYUOGRh2A -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_rGNWsCbSEdqh1LYUOGRh2A CRC: 1905799635 -->This artifact contains a list of all scheduled work to be done within the project, as well as proposed work that may affect the product in this or future projects. Each Work Item may contain references to information relevant to carry out the work described within the work item.<!-- END:briefDescription,_rGNWsCbSEdqh1LYUOGRh2A -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: mainDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:mainDescription,-buxz4BVToq97bSxaqyjySg CRC: 929956055 --><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><!-- END:mainDescription,-buxz4BVToq97bSxaqyjySg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,-buxz4BVToq97bSxaqyjySg CRC: 4044898541 -->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.<!-- END:purpose,-buxz4BVToq97bSxaqyjySg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: representationOptions<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:representationOptions,-buxz4BVToq97bSxaqyjySg CRC: 2697716961 --><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><!-- END:representationOptions,-buxz4BVToq97bSxaqyjySg -->
</body>
</html>