https://bugs.eclipse.org/bugs/show_bug.cgi?id=242272
diff --git a/libraries/EPF_Practices_Library/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi b/libraries/EPF_Practices_Library/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi
index cf60ef7..22f0f38 100644
--- a/libraries/EPF_Practices_Library/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi
+++ b/libraries/EPF_Practices_Library/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi
@@ -10,7 +10,8 @@
right during the iteration. This knowledge will help everybody make informed decisions on the next iteration planning
and determine the best course of action for the project. This task is performed at the end of every iteration until the end
of the project.</mainDescription>
- <sections xmi:id="_o28GgMMsEdmdo9HxCRR_Gw" name="Review iteration results" guid="_o28GgMMsEdmdo9HxCRR_Gw">
+ <sections xmi:id="_o28GgMMsEdmdo9HxCRR_Gw" name="Prepare for iteration assessment"
+ guid="_o28GgMMsEdmdo9HxCRR_Gw">
<sectionDescription><p>
Towards the end of the iteration, the team jointly assesses whether the objectives and evaluation criteria established
in the <a class="elementLink" href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
@@ -20,6 +21,13 @@
successfully run against it.
</p>
<p>
+ The team prepares a demo of the features implemented at that point, so during the iteration assessment stakeholders can
+ have a real sense of progress made. The team decides on whether&nbsp;each developer demonstrates the features they
+ implemented or the project manager or senior developer demonstrates it all, having other team members present to answer
+ questions. The project manager&nbsp;prepares&nbsp;reports that show&nbsp;project status, such as&nbsp;work burndown and
+ test case reports.&nbsp;
+</p>
+<p>
These activities happen in preparation for the iteration assessment meeting with stakeholders that occur on the last
day of the iteration.
</p></sectionDescription>
@@ -27,12 +35,15 @@
<sections xmi:id="_iSiDEIx4Edyzd4h-mxj9YA" name="Demonstrate value and gather feedback"
guid="_iSiDEIx4Edyzd4h-mxj9YA">
<sectionDescription><p>
- The team should demonstrate the product to customers, end-users, and other stakeholders to collect their feedback, or
- better yet, have end users to use the product themselves. This should be done throughout the iteration, or at least in
- a separate session towards the end of the iteration (see <a class="elementLinkWithType"
+ The team demonstrates the product to customers, end-users, and other stakeholders to collect their feedback, or better
+ yet, have end users to use the product themselves. This can be done throughout the iteration,&nbsp;but at least during
+ the iteration assessment that occurs at the end of the iteration (see <a class="elementLinkWithType"
href="./../../practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_assessment_E27E9DDE.html"
guid="_FekBAC4IEdyhZrtGEIITGQ">Guideline: Iteration Assessment</a>). Work that is not completed should not be
- demonstrated. Resulting knowledge, such as new functionality, requested changes and defects are recorded in the <a
+ demonstrated.
+</p>
+<p>
+ Resulting knowledge, such as new functionality, requested changes and defects are recorded in the <a
class="elementLink" href="./../../core.mgmt.common.base/workproducts/work_items_list_39D03CC8.html"
guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, so project priorities, scope and duration can be refined in the
next iteration planning.