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>&lt;p>&#xD;
-    Gather the information required to describe the change request. This should include a description of the requested&#xD;
-    change, the reason for the change (defect or enhancement), the&amp;nbsp;artifact&amp;nbsp;affected, including&amp;nbsp;the version,&#xD;
-    and&amp;nbsp;the priority of the change. If possible,&amp;nbsp;provide an estimate of the effort required to implement the&#xD;
-    change.&#xD;
-&lt;/p></sectionDescription>
-  </sections>
-  <sections xmi:id="_r2aP0KuoEdmEGLSmmpF1Sg" name="Update the Work Item List" guid="_r2aP0KuoEdmEGLSmmpF1Sg">
-    <sectionDescription>Update the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
-href=&quot;./../../opn.swd.prac.legacy_pm/workproducts/work_items_list_39D03CC8.html&quot;&#xD;
-guid=&quot;_rGNWsCbSEdqh1LYUOGRh2A&quot;>Artifact: Work Items List&lt;/a>&amp;nbsp;to&amp;nbsp;document the information that you gathered in the&#xD;
-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>&lt;p>&#xD;
-    This artifact provides a focal point for the entire team:&#xD;
-&lt;/p>&#xD;
-&lt;ul>&#xD;
-    &lt;li>&#xD;
-        It provides one list containing all requests for additional capabilities or enhancement for that application. Note&#xD;
-        that some of these requests may never be implemented, or be implemented in later projects&#xD;
-    &lt;/li>&#xD;
-    &lt;li>&#xD;
-        It provides one list of all the work to be prioritized, estimated, and assigned within the project. The risk list&#xD;
-        is prioritized separately.&#xD;
-    &lt;/li>&#xD;
-    &lt;li>&#xD;
-        It provides one place to go to for the development team to understand what &lt;a class=&quot;elementLink&quot;&#xD;
-        href=&quot;./../../practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments_C8773066.html&quot;&#xD;
-        guid=&quot;_S80VwCNbEdyCq8v2ZO4QcA&quot;>Micro-Increments&lt;/a>&amp;nbsp;need to be delivered, get references to material required&#xD;
-        to carry out the work, and one place to go to report progress made.&#xD;
-    &lt;/li>&#xD;
-&lt;/ul>&#xD;
-&lt;p>&#xD;
-    These are the typical work items that go into this list:&#xD;
-&lt;/p>&#xD;
-&lt;ul>&#xD;
-    &lt;li>&#xD;
-        Use cases (and references to use-case specifications)&#xD;
-    &lt;/li>&#xD;
-    &lt;li>&#xD;
-        System-wide requirements&#xD;
-    &lt;/li>&#xD;
-    &lt;li>&#xD;
-        Changes and enhancement requests&#xD;
-    &lt;/li>&#xD;
-    &lt;li>&#xD;
-        Defects&#xD;
-    &lt;/li>&#xD;
-    &lt;li>&#xD;
-        Development tasks&#xD;
-    &lt;/li>&#xD;
-&lt;/ul>&#xD;
-&lt;p>&#xD;
-    Work items can be very large in scope, especially when capturing requests for enhancements, such as “Support Financial&#xD;
-    Planning” for a personal finance application. To allow the application to be developed in micro-increments, work items&#xD;
-    are analyzed and broken down into smaller work items so they can be assigned to an iteration, such as a use-case&#xD;
-    scenario for&amp;nbsp;“Calculate Net Worth”. Further breakdown may be required to identify suitable tasks to be assigned to&#xD;
-    developers, such as “Develop UI for Calculate Net Worth”. This means that work items often have parent/child&#xD;
-    relationships, where the lowest level is a specification and tracking device for micro-increments.&#xD;
-&lt;/p></mainDescription>
-  <keyConsiderations>&lt;p>&#xD;
-    Work Items should contain estimates, see &lt;a class=&quot;elementLinkWithType&quot;&#xD;
-    href=&quot;./../../practice.mgmt.iterative_dev.base/guidances/guidelines/managing_work_items_32AC6ABD.html&quot;&#xD;
-    guid=&quot;_7vEXEMA4EdqSgKaj2SZBmg&quot;>Guideline: Managing Work Items&lt;/a>&amp;nbsp;and &lt;a class=&quot;elementLinkWithType&quot;&#xD;
-    href=&quot;./../../core.mgmt.common.base/guidances/guidelines/agile_estimation_A4EF42B3.html&quot;&#xD;
-    guid=&quot;_CGHskBEdEdqY7JB6N6CW2w&quot;>Guideline: Agile Estimation&lt;/a>.&#xD;
-&lt;/p></keyConsiderations>
-  <purpose>To collect all requests for work that will potentially be taken on within the project, so work can be prioritized, effort&#xD;
-estimated and progress tracked.</purpose>
-  <representationOptions>&lt;h3>&#xD;
-    As a spreadsheet or database&#xD;
-&lt;/h3>&#xD;
-&lt;p>&#xD;
-    The Work Items List can be captured as a separate artifact, represented by a spreadsheet or database table. See &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup/guidances/examples/work_items_list_F527B77D.html&quot; guid=&quot;_nHomIDgzEdu4E8ZdmlYjtA&quot;>Example: Work Items List&lt;/a>.&#xD;
-&lt;/p>&#xD;
-&lt;h3>&#xD;
-    In specific tools&#xD;
-&lt;/h3>&#xD;
-&lt;p>&#xD;
-    Project Management, Requirements Management and Change Request tools are&amp;nbsp;options to capture the list of work to be&#xD;
-    done.&#xD;
-&lt;/p>&#xD;
-&lt;h3>&#xD;
-    As part of the Iteration Plan&#xD;
-&lt;/h3>&#xD;
-&lt;p>&#xD;
-    The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup/workproducts/iteration_plan_B46FED39.html&quot; guid=&quot;_0aQBEslgEdmt3adZL5Dmdw&quot;>Artifact: Iteration Plan&lt;/a> typically references work items that are assigned to that&#xD;
-    iteration. If the team is capturing the iteration plan on a whiteboard, for example, the team may choose to reference&#xD;
-    high-level work items in the Work Items List that are assigned to the iteration, and maintain low-level child work&#xD;
-    items used to track day-to-day work only within an iteration plan.&lt;br />&#xD;
-&lt;/p></representationOptions>
-</org.eclipse.epf.uma:ArtifactDescription>