*** empty log message ***
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/tasks/request_change.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/tasks/request_change.xmi
deleted file mode 100644
index 0277d93..0000000
--- a/praclib/temp/practice.mgmt.iterative_dev.base/tasks/request_change.xmi
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0"
- xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore"
- xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.2.0" xmlns:epf="http://www.eclipse.org/epf"
- epf:version="1.2.0" xmi:id="_Nr0S4KeqEdmKDbQuyzCoqQ"
- name="submit_change_request,_0mwzEclgEdmt3adZL5Dmdw" guid="_Nr0S4KeqEdmKDbQuyzCoqQ"
- changeDate="2005-07-07T14:57:19.105-0700">
- <sections xmi:id="_qEkewKuoEdmEGLSmmpF1Sg" name="Gather change request information"
- guid="_qEkewKuoEdmEGLSmmpF1Sg">
- <sectionDescription><p>
- Gather the information required to describe the change request. This should include a description of the requested
- change, the reason for the change (defect or enhancement), the&nbsp;artifact&nbsp;affected, including&nbsp;the version,
- and&nbsp;the priority of the change. If possible,&nbsp;provide an estimate of the effort required to implement the
- change.
-</p></sectionDescription>
- </sections>
- <sections xmi:id="_r2aP0KuoEdmEGLSmmpF1Sg" name="Update the Work Item List" guid="_r2aP0KuoEdmEGLSmmpF1Sg">
- <sectionDescription>Update the <a class="elementLinkWithType"
-href="./../../opn.swd.prac.legacy_pm/workproducts/work_items_list_39D03CC8.html"
-guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>&nbsp;to&nbsp;document the information that you gathered in the
-previous step.</sectionDescription>
- </sections>
-</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/workproducts/work_items_list.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/workproducts/work_items_list.xmi
deleted file mode 100644
index 15ba02d..0000000
--- a/praclib/temp/practice.mgmt.iterative_dev.base/workproducts/work_items_list.xmi
+++ /dev/null
@@ -1,86 +0,0 @@
-<?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.4/uma.ecore"
- xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.2.0" xmlns:epf="http://www.eclipse.org/epf"
- epf:version="1.2.0" xmi:id="-buxz4BVToq97bSxaqyjySg"
- name="work_items_list,_rGNWsCbSEdqh1LYUOGRh2A" guid="-buxz4BVToq97bSxaqyjySg"
- changeDate="2008-02-13T14:04:39.593-0500" 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 <a class="elementLink"
- href="./../../practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments_C8773066.html"
- guid="_S80VwCNbEdyCq8v2ZO4QcA">Micro-Increments</a>&nbsp;need to be delivered, get references to material required
- to carry out the work, and one place to go to report progress made.
- </li>
-</ul>
-<p>
- These are the typical work items that go into 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 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 <a class="elementLinkWithType"
- href="./../../practice.mgmt.iterative_dev.base/guidances/guidelines/managing_work_items_32AC6ABD.html"
- guid="_7vEXEMA4EdqSgKaj2SZBmg">Guideline: Managing Work Items</a>&nbsp;and <a class="elementLinkWithType"
- href="./../../core.mgmt.common.base/guidances/guidelines/agile_estimation_A4EF42B3.html"
- guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>.
-</p></keyConsiderations>
- <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/guidances/examples/work_items_list_F527B77D.html" guid="_nHomIDgzEdu4E8ZdmlYjtA">Example: Work Items List</a>.
-</p>
-<h3>
- In specific tools
-</h3>
-<p>
- Project Management, Requirements Management and Change Request tools are&nbsp;options to capture the list of work to be
- done.
-</p>
-<h3>
- As part of the Iteration Plan
-</h3>
-<p>
- The <a class="elementLinkWithType" href="./../../openup/workproducts/iteration_plan_B46FED39.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>
