*** empty log message ***
diff --git a/EPF_Practices/core.mgmt.slot.base/guidances/examples/resources/ex_work_items_list.xls b/EPF_Practices/core.mgmt.slot.base/guidances/examples/resources/ex_work_items_list.xls
deleted file mode 100644
index 234f2a5..0000000
--- a/EPF_Practices/core.mgmt.slot.base/guidances/examples/resources/ex_work_items_list.xls
+++ /dev/null
Binary files differ
diff --git a/EPF_Practices/core.tech.slot.base/guidances/examples/resources/ex_work_items_list.xls b/EPF_Practices/core.tech.slot.base/guidances/examples/resources/ex_work_items_list.xls
deleted file mode 100644
index 234f2a5..0000000
--- a/EPF_Practices/core.tech.slot.base/guidances/examples/resources/ex_work_items_list.xls
+++ /dev/null
Binary files differ
diff --git a/EPF_Practices/practice.mgmt.release_planning.base/tasks/plan_the_project.xmi b/EPF_Practices/practice.mgmt.release_planning.base/tasks/plan_the_project.xmi
index 60d9603..0e1f38a 100644
--- a/EPF_Practices/practice.mgmt.release_planning.base/tasks/plan_the_project.xmi
+++ b/EPF_Practices/practice.mgmt.release_planning.base/tasks/plan_the_project.xmi
@@ -1,8 +1,8 @@
<?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.5/uma.ecore"
- xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf"
- epf:version="1.5.0" xmi:id="_fPbdIKe2Edmzde8VFK5bxg"
+ xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc"
+ rmc:version="7.5.0" xmi:id="_fPbdIKe2Edmzde8VFK5bxg"
name="plan_the_project,_0lC70MlgEdmt3adZL5Dmdw" guid="_fPbdIKe2Edmzde8VFK5bxg"
changeDate="2008-07-14T13:50:23.405-0700" version="1.0.0">
<mainDescription>Developing the project plan provides an opportunity for the team to agree on project scope, objectives, initial timeframe,
@@ -37,16 +37,16 @@
<p>
If the project is feature-driven, the team uses the <a class="elementLink"
href="./../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html" guid="_1QZI8EfUEdyiPI8btkmvmw">[Project
- Work]</a>&nbsp;and target velocity to forecast the number of iterations required to complete the project.&nbsp;&nbsp;If
- the project instead is date-driven, the team assesses (using the known velocity of the&nbsp;team) roughly how much work
- can be done in the given time-frame. Out-of-scope work can be considered&nbsp;for future releases.
+ Work]</a>&nbsp;and target velocity to forecast the number of iterations required to complete the project. If the
+ project instead is date-driven, the team assesses (using the known velocity of the&nbsp;team) roughly how much work can
+ be done in the given time-frame. Out-of-scope work can be considered&nbsp;for future releases.
</p>
<p>
- The team should not spend too much time&nbsp;doing this planning. The Project plan should document only&nbsp;a brief
- summary of&nbsp; project milestones&nbsp;and between one and three objectives for each iteration. Do not commit
+ The team should not spend too much time&nbsp;doing this planning. The project plan should document only&nbsp;a brief
+ summary of&nbsp;project milestones&nbsp;and between one and three objectives for each iteration. Do not commit
individual work items to the plan, because this will force too much re-planning. The goal is just to create a
high-level plan outlining how&nbsp;the team&nbsp;can build the resulting application in the given set of iterations.
- Extra levels of detail will be achieved in other planning sessions throughout the project (example, when planning
+ Extra levels of detail will be achieved in other planning sessions throughout the project (for example, when planning
iterations). You may need to revisit&nbsp;this plan&nbsp;later to adapt it based on what you will
learn&nbsp;by&nbsp;running&nbsp;the iterations.
</p></sectionDescription>
diff --git a/EPF_Practices/practice.mgmt.risk_value_lifecycle.base/guidances/reports/resources/ex_project_burndown.xls b/EPF_Practices/practice.mgmt.risk_value_lifecycle.base/guidances/reports/resources/ex_project_burndown.xls
deleted file mode 100644
index e63fef8..0000000
--- a/EPF_Practices/practice.mgmt.risk_value_lifecycle.base/guidances/reports/resources/ex_project_burndown.xls
+++ /dev/null
Binary files differ
