blob: ded8e7100689e918e6ef9aca6e1daa8200e473e7 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="" xmlns:org.eclipse.epf.uma="" epf:version="1.0.0" xmi:id="-hrDndmFd0zexB0HNYX3gww" name="project_burndown,_ePrt8Dj3EduxovfWMDsntw" guid="-hrDndmFd0zexB0HNYX3gww" changeDate="2006-09-25T17:07:38.314-0700" version="1.0.0">
Project burndown is usually communicated in graphical form.&amp;nbsp;Project burndown is very useful to quickly communicate
the overall project progress based on actual data and to diagnose a trend for the remainder of the project.&amp;nbsp;
The project burndown chart consists of two perspectives, the horizontal axis showing the iterations and the vertical
axis indicating the remaining points from the work items list. Additionally the average burndown from previous
iterations is calculated and a trend for the remainder of the project diagnosed and forecasted.
Project burndown management is a enabling technique that allows direct linkage of iteration goals to work items. The
project manager will use the project burndown information for communicating progress and trend to senior management.
See &lt;a href=&quot;./resources/ex_project_burndown.xls&quot; target=&quot;_blank&quot;&gt;ex_project_burndown.xls&lt;/a&gt;&amp;nbsp;for an example of
project burndown.&lt;br /&gt;</mainDescription>