diff --git a/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi b/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi
index 3b75734..c76563d 100644
--- a/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi
+++ b/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi
@@ -1,5 +1,5 @@
 <?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.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="_a3uz4LBYEdm7Eph_l9Cn9w" name="assess_results,_0l53cMlgEdmt3adZL5Dmdw" guid="_a3uz4LBYEdm7Eph_l9Cn9w" changeDate="2008-07-14T09:22:56.000-0700" version="1.0.0">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="_a3uz4LBYEdm7Eph_l9Cn9w" name="assess_results,_0l53cMlgEdmt3adZL5Dmdw" guid="_a3uz4LBYEdm7Eph_l9Cn9w" changeDate="2008-07-14T09:22:56.000-0700" version="1.0.0">
   <mainDescription>Coordinate the assessment and discuss with the team how the iteration results will be best presented to stakeholders, so&#xD;
 that they can learn as much about the solution as possible. Listen to what the team has to say about what went wrong (and&#xD;
 what went right) during the iteration. This knowledge will help everybody make informed decisions about the next iteration&#xD;
@@ -8,18 +8,19 @@
   <sections xmi:id="_o28GgMMsEdmdo9HxCRR_Gw" name="Prepare for iteration assessment" guid="_o28GgMMsEdmdo9HxCRR_Gw">
     <sectionDescription>&lt;p>&#xD;
     Towards the end of the iteration, the team jointly assesses whether the objectives and evaluation criteria established&#xD;
-    in the &lt;a class=&quot;elementLink&quot; href=&quot;./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html&quot;&#xD;
-    guid=&quot;_0aQBEslgEdmt3adZL5Dmdw&quot;>Iteration Plan&lt;/a> were met, and whether the team adhered to the plan and completed all&#xD;
-    of the work items committed to the iteration. The team makes use of objective measures to the greatest extent possible.&#xD;
-    To assess that a given work item is completed, the team ensures that the corresponding test cases were successfully run&#xD;
-    against it.&#xD;
+    in the Iteration Plan were met, and whether the team adhered to the plan and completed all of the work items committed&#xD;
+    to the iteration. The team makes use of objective measures to the greatest extent possible. To assess that a given work&#xD;
+    item is completed, the team ensures that the corresponding test cases were successfully run against it.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
     The team prepares a demonstration of the features implemented at that point, so that during the iteration assessment&#xD;
     stakeholders can have a real sense of progress made. The team decides whether each developer should demonstrate the&#xD;
     features that they implemented, or if the project manager or senior developer demonstrates it all, with other team&#xD;
-    members present to answer questions. The project manager prepares reports that show project status, such as work&#xD;
-    burndown and test case reports.&#xD;
+    members present to answer questions.&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    In addition to the demonstration,&amp;nbsp;prepare reports that show project status, such as work burndown and test case&#xD;
+    reports.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
     These activities happen in preparation for the iteration assessment meeting with stakeholders that occurs on the last&#xD;
@@ -36,8 +37,8 @@
     demonstrated.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
-    Resulting knowledge (such as new functionality, requested changes, and defects) are recorded in the &lt;a&#xD;
-    class=&quot;elementLink&quot; href=&quot;./../../core.mgmt.common.extend_supp/workproducts/work_items_list_39D03CC8.html&quot;&#xD;
+    Record resulting knowledge (such as new functionality, requested changes, and defects) in the &lt;a class=&quot;elementLink&quot;&#xD;
+    href=&quot;./../../core.mgmt.common.extend_supp/workproducts/work_items_list_39D03CC8.html&quot;&#xD;
     guid=&quot;_rGNWsCbSEdqh1LYUOGRh2A&quot;>Work Items List&lt;/a>, so that project priorities, scope, and duration can be refined in&#xD;
     the next iteration planning.&#xD;
 &lt;/p></sectionDescription>
@@ -46,19 +47,17 @@
     <sectionDescription>&lt;p>&#xD;
     Review with the team the approach taken to development and collaboration, the effectiveness of the development&#xD;
     environment, the suitability of the working environment, and other factors. Discuss what things went well, what could&#xD;
-    have gone better, and how things could be changed to deliver better results. Capture in the current &lt;a&#xD;
-    class=&quot;elementLink&quot; href=&quot;./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html&quot;&#xD;
-    guid=&quot;_0aQBEslgEdmt3adZL5Dmdw&quot;>Iteration Plan&lt;/a> the assessment results, stakeholder feedback, and actions to be taken&#xD;
-    to improve the development approach for the next iteration. Record lessons learned in this iteration with a collection&#xD;
-    of lessons learned for the entire project.&#xD;
+    have gone better, and how things could be changed to deliver better results. Capture in the current Iteration Plan the&#xD;
+    assessment results, stakeholder feedback, and actions to be taken to improve the development approach for the next&#xD;
+    iteration. Record lessons learned in this iteration with a collection of lessons learned for the entire project.&#xD;
 &lt;/p></sectionDescription>
   </sections>
   <sections xmi:id="_1YHH8DLqEdueZPye-FaNgA" name="Close-out project" guid="_1YHH8DLqEdueZPye-FaNgA">
     <sectionDescription>&lt;p>&#xD;
-    This step must be performed only when the iteration review coincides with the end of the project. Involve the team and&#xD;
-    stakeholders in a final assessment for project acceptance which, if successful, marks the point when the customer&#xD;
-    accepts ownership of the software product. Complete the close-out of the project by disposing of the remaining assets&#xD;
-    and reassigning the remaining staff.&#xD;
+    Perform this step when the iteration review coincides with the end of the project. Involve the team and stakeholders in&#xD;
+    a final assessment for project acceptance which, if successful, marks the point when the customer accepts ownership of&#xD;
+    the software product. Complete the close-out of the project by disposing of the remaining assets and reassigning the&#xD;
+    remaining staff.&#xD;
 &lt;/p></sectionDescription>
   </sections>
   <purpose>Demonstrate the value of the solution increment that was built during the iteration and apply the lessons learned to modify&#xD;
diff --git a/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/manage_iteration.xmi b/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/manage_iteration.xmi
index 30945b9..9ac7968 100644
--- a/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/manage_iteration.xmi
+++ b/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/manage_iteration.xmi
@@ -1,25 +1,24 @@
 <?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.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="-PbfqVxB_j9KN-Jx39_pEUA" name="manage_iteration,_8S2aICbYEdqh1LYUOGRh2A" guid="-PbfqVxB_j9KN-Jx39_pEUA" changeDate="2008-07-14T09:47:00.000-0700" version="1.0.0">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-PbfqVxB_j9KN-Jx39_pEUA" name="manage_iteration,_8S2aICbYEdqh1LYUOGRh2A" guid="-PbfqVxB_j9KN-Jx39_pEUA" changeDate="2011-03-25T16:39:44.587-0700" version="1.0.0">
   <mainDescription>&lt;p>&#xD;
-    Developing the team is part of executing the project. The project manager is responsible for improving the interactions&#xD;
-    and trust between team members, incorporating team building into project activities, and empowering the team to make&#xD;
-    decisions. Management is done by objectives and not by time reporting.&#xD;
+    Developing the team is part of executing the project. Improve the interactions and trust between team members,&#xD;
+    incorporating team building into project activities, and empowering the team to make decisions. Management is done by&#xD;
+    objectives and not by time reporting.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
-    The project manager helps the team meet the iteration objectives by removing constraints, and by monitoring the&#xD;
-    progress and work remaining to completion. When the team is falling behind, the project manager helps the team assess&#xD;
-    how it can reduce work and still meet the iteration goals. Involve stakeholders in approving changes and actions that&#xD;
-    affect them, so that their objectives for the iteration can be met, and the issues they raise can be solved throughout&#xD;
-    the iteration.&#xD;
-&lt;/p></mainDescription>
-  <keyConsiderations>&lt;p>&#xD;
+    Help the team meet the iteration objectives by removing constraints, and by monitoring the progress and work remaining&#xD;
+    to completion. When the team is falling behind, help the team assess how it can reduce work and still meet the&#xD;
+    iteration goals. Involve stakeholders in approving changes and actions that affect them, so that their objectives for&#xD;
+    the iteration can be met, and the issues they raise can be solved throughout the iteration.&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
     Select an approach for the collection of basic metrics: ideally, they are automatically generated from the tools at&#xD;
     hand, but can be manually assembled, or both. &lt;span&#xD;
     style=&quot;FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA&quot;>Outline&#xD;
     which metrics the project should use in the &lt;a class=&quot;elementLink&quot;&#xD;
     href=&quot;./../../core.mgmt.slot.base/workproducts/project_definition_and_scope_slot_BB8EB6F7.html&quot;&#xD;
     guid=&quot;_RJMUcNpUEdyzZqGyZ7hwdw&quot;>[Project Definition and Scope]&lt;/a>.&lt;/span>&#xD;
-&lt;/p></keyConsiderations>
+&lt;/p></mainDescription>
   <sections xmi:id="_OE65ICuxEdqTIKp3l5PtzQ" name="Track current iteration progress" guid="_OE65ICuxEdqTIKp3l5PtzQ">
     <sectionDescription>&lt;p>&#xD;
     Continuously monitor the iteration to ensure that it is progressing appropriately. Track the progress of the current&#xD;
@@ -72,10 +71,10 @@
   </sections>
   <sections xmi:id="_oIZdkCbZEdqh1LYUOGRh2A" name="Handle exceptions and problems" guid="_oIZdkCbZEdqh1LYUOGRh2A">
     <sectionDescription>&lt;p>&#xD;
-    One of the project manager's key responsibilities is to know about the project team's problems and issues. The manager&#xD;
-    needs to focus on problems that are blocking progress. A quick, daily meeting is usually a good way to monitor those&#xD;
-    problems and issues. A record of issues that have to be solved within the team may be kept in the &lt;a&#xD;
-    class=&quot;elementLink&quot; href=&quot;./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html&quot;&#xD;
+    Know about the team's problems and issues and&amp;nbsp;focus on problems that are blocking progress. A quick, daily meeting&#xD;
+    is usually a good way to monitor those problems and issues. Keep&amp;nbsp;a record of issues that have to be solved within&#xD;
+    the team in the &lt;a class=&quot;elementLink&quot;&#xD;
+    href=&quot;./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html&quot;&#xD;
     guid=&quot;_0aQBEslgEdmt3adZL5Dmdw&quot;>Iteration Plan&lt;/a>&lt;font color=&quot;#003399&quot;>.&lt;/font> If a critical problem or issue is&#xD;
     likely to take a lot of time to solve, capture it in the Work Items List so that it can be assigned to an individual.&#xD;
 &lt;/p>&#xD;
@@ -87,23 +86,22 @@
   </sections>
   <sections xmi:id="_xiFJwCbZEdqh1LYUOGRh2A" name="Identify and manage risks" guid="_xiFJwCbZEdqh1LYUOGRh2A">
     <sectionDescription>&lt;p>&#xD;
-    Identify risks as soon as the project starts, and continue identifying and managing risks throughout the project. The&#xD;
-    &lt;a class=&quot;elementLink&quot; href=&quot;./../../core.mgmt.common.extend_supp/workproducts/risk_list_C4B6F290.html&quot;&#xD;
-    guid=&quot;_Ckay8Cc_EduIsqH1Q6ZuqA&quot;>Risk List&lt;/a> should be revisited weekly, or at a minimum once per iteration. The entire&#xD;
-    team should be involved in identifying and mitigating risks.&#xD;
+    Identify risks as soon as the project starts, and continue identifying and managing risks throughout the project.&#xD;
+    Revisit the &lt;a class=&quot;elementLink&quot; href=&quot;./../../core.mgmt.common.extend_supp/workproducts/risk_list_C4B6F290.html&quot;&#xD;
+    guid=&quot;_Ckay8Cc_EduIsqH1Q6ZuqA&quot;>Risk List&lt;/a> weekly, or at a minimum once per iteration. Involve the entire team in&#xD;
+    identifying and mitigating risks.&#xD;
 &lt;/p></sectionDescription>
   </sections>
   <sections xmi:id="_Br6VECuxEdqTIKp3l5PtzQ" name="Manage objectives" guid="_Br6VECuxEdqTIKp3l5PtzQ">
     <sectionDescription>When a team is falling significantly behind, or critical problems occur that prevent the team from meeting the iteration&#xD;
 objectives, it may be necessary to descope work to ensure that the team delivers a useful product increment by the end of&#xD;
-the iteration, while maximizing stakeholder value. The project manager should work with the team and stakeholders to revise&#xD;
-the &lt;a class=&quot;elementLink&quot; href=&quot;./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html&quot;&#xD;
-guid=&quot;_0aQBEslgEdmt3adZL5Dmdw&quot;>Iteration Plan&lt;/a> and, as necessary, reduce the emphasis on less critical tasks by&#xD;
-postponing them to a subsequent iteration. In rare cases, if the iteration objectives still seem impossible to meet, the&#xD;
-team might consider terminating the iteration or reformulating the iteration to a new objective.</sectionDescription>
+the iteration, while maximizing stakeholder value. Work with the team and stakeholders to revise the Iteration Plan and, as&#xD;
+necessary, reduce the emphasis on less critical tasks by postponing them to a subsequent iteration. In rare cases, if the&#xD;
+iteration objectives still seem impossible to meet, the team might consider terminating the iteration or reformulating the&#xD;
+iteration to a new objective.</sectionDescription>
   </sections>
   <purpose>&lt;p>&#xD;
-    To help the team meet the iteration objectives and keep the project on track. Manage stakeholders' expectations as&#xD;
+    Help the team meet the iteration objectives and keep the project on track. Manage stakeholders' expectations as&#xD;
     technical and practical discoveries are made during the project.&#xD;
 &lt;/p></purpose>
 </org.eclipse.epf.uma:TaskDescription>
diff --git a/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/plan_iteration.xmi b/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/plan_iteration.xmi
index 6d0df39..c3e7278 100644
--- a/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/plan_iteration.xmi
+++ b/epf_prac_151/practice.mgmt.iterative_dev.base/tasks/plan_iteration.xmi
@@ -1,16 +1,17 @@
 <?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.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="_Wk7noKe1EdmGSrcKGOYDGg" name="plan_iteration,_0keUEMlgEdmt3adZL5Dmdw" guid="_Wk7noKe1EdmGSrcKGOYDGg" changeDate="2008-02-21T00:32:50.000-0800" version="7.2.0">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="_Wk7noKe1EdmGSrcKGOYDGg" name="plan_iteration,_0keUEMlgEdmt3adZL5Dmdw" guid="_Wk7noKe1EdmGSrcKGOYDGg" changeDate="2011-03-25T16:37:07.803-0700" version="7.2.0">
   <mainDescription>&lt;p>&#xD;
     During project planning, iterations are identified, but the estimates have an acceptable uncertainty due to the lack of&#xD;
     detail at the project inception. This task is repeated for each iteration within a release. It allows the team to&#xD;
-    increase the accuracy of the estimates for one iteration, as more detail is known along the project. The project&#xD;
-    manager has the responsibility of ensuring that the team commits to a reasonable amount of work for the iteration,&#xD;
-    based on team performance from previous iterations.&#xD;
+    increase the accuracy of the estimates for one iteration, as more detail is known along the project.&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    Ensure that the team commits to a reasonable amount of work for the iteration, based on team performance from previous&#xD;
+    iterations.&#xD;
 &lt;/p></mainDescription>
   <sections xmi:id="_7bz7AIyAEdyhZb-MhCJrlA" name="Prioritize Work Items List" guid="_7bz7AIyAEdyhZb-MhCJrlA">
-    <sectionDescription>The work items list should be prioritized before you plan the next iteration. Consider what has changed since the last&#xD;
-iteration plan (such as new change requests, shifting priorities of your stakeholders, or new risks that have been&#xD;
-encountered).</sectionDescription>
+    <sectionDescription>Prioritize the work items list before you plan the next iteration. Consider what has changed since the last iteration plan&#xD;
+(such as new change requests, shifting priorities of your stakeholders, or new risks that have been encountered).</sectionDescription>
   </sections>
   <sections xmi:id="_CtKCMMBHEdqSgKaj2SZBmg" name="Define iteration objectives" guid="_CtKCMMBHEdqSgKaj2SZBmg">
     <sectionDescription>&lt;p>&#xD;
@@ -23,27 +24,27 @@
   </sections>
   <sections xmi:id="_HzNVgIyBEdyhZb-MhCJrlA" name="Identify and review risks" guid="_HzNVgIyBEdyhZb-MhCJrlA">
     <sectionDescription>&lt;p>&#xD;
-    Throughout the project, new assumptions and concerns may arise. The team identifies and prioritizes new risks as part&#xD;
-    of iteration planning, updating the risk list. Responses to risks are added to the work items list, influencing the&#xD;
-    work that is being planned for that iteration.&#xD;
+    Throughout the project, new assumptions and concerns may arise. Help the team identify and prioritize new risks as part&#xD;
+    of iteration planning, updating the risk list. Add risk responses to the work items list, influencing the work that is&#xD;
+    being planned for that iteration.&#xD;
 &lt;/p></sectionDescription>
   </sections>
   <sections xmi:id="_307v0MMsEdmdo9HxCRR_Gw" name="Commit work to the iteration" guid="_307v0MMsEdmdo9HxCRR_Gw">
     <sectionDescription>&lt;p>&#xD;
-    The project manager works with the team, and especially the project stakeholders, to identify the high-priority work&#xD;
-    items from the work items list to be addressed. The high-level objectives provide guidance on what work items should be&#xD;
-    considered. The iteration plan from previous iteration should include an assessment of the results, and can also be&#xD;
-    used as input to the current iteration planning. The team reviews its velocity and determines the amount of work that&#xD;
-    can be done within the iteration. The team breaks down into tasks those work items that are assigned to the iteration,&#xD;
-    and estimates the effort to complete each task. Typical tasks range from half a day to two days in length, and are&#xD;
-    captured in the work items list. See &lt;a class=&quot;elementLinkWithType&quot;&#xD;
+    Work with the team, and especially the project stakeholders, to identify the high-priority work items from the work&#xD;
+    items list to be addressed. The high-level objectives provide guidance on what work items should be considered. The&#xD;
+    iteration plan from previous iteration should include an assessment of the results, and can also be used as input to&#xD;
+    the current iteration planning. The team reviews its velocity and determines the amount of work that can be done within&#xD;
+    the iteration. The team breaks down into tasks those work items that are assigned to the iteration, and estimates the&#xD;
+    effort to complete each task. Typical tasks range from half a day to two days in length, and are captured in the work&#xD;
+    items list. See &lt;a class=&quot;elementLinkWithType&quot;&#xD;
     href=&quot;./../../core.mgmt.common.extend_supp/guidances/guidelines/agile_estimation_A4EF42B3.html&quot;&#xD;
     guid=&quot;_CGHskBEdEdqY7JB6N6CW2w&quot;>Guideline: Agile Estimation&lt;/a> for more information.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
     When the team has decided to take on a work item, it will assign the work to one or several team members. Ideally, this&#xD;
     is done by team members signing up to do the work, since this makes people motivated and committed to doing the job.&#xD;
-    However, based on your culture, you may instead have the project manager assign the work.&lt;br />&#xD;
+    However, based on your culture, you may instead assign the work to team members.&lt;br />&#xD;
 &lt;/p></sectionDescription>
   </sections>
   <sections xmi:id="_7Hqr4MMsEdmdo9HxCRR_Gw" name="Define evaluation criteria" guid="_7Hqr4MMsEdmdo9HxCRR_Gw">