| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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:epf="http://www.eclipse.org/epf" |
| epf:version="1.2.0" xmi:id="-hrDndmFd0zexB0HNYX3gww" |
| name="project_burndown,_ePrt8Dj3EduxovfWMDsntw" guid="-hrDndmFd0zexB0HNYX3gww" |
| changeDate="2007-05-01T12:03:57.571-0700" version="1.0.0"> |
| <mainDescription><p> The project burndown report is a primary tool for understanding the status 
 |
| of a project. It shows the trend for how much work is left to do within that 
 |
| project. This is done by adding the estimated effort left for each of the Work 
 |
| Items to be addressed within the project and showing how the estimated effort 
 |
| is changing from iteration to iteration. The project burndown report should 
 |
| be updated at the end of each iteration. </p>
 |
| <p> The project burndown rate is usually communicated in graphical form.&nbsp;The 
 |
| project burndown chart consists of two perspectives, with the horizontal axis 
 |
| showing the iterations and the vertical axis indicating the remaining points 
 |
| from the Work Items List. Additionally, the average burndown rate from previous 
 |
| iterations is calculated, and a trend for the remainder of the project forecasted 
 |
| from that historical data.&nbsp; </p>
 |
| <p> 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 trends to senior management. </p>
 |
| See <a href="./resources/ex_project_burndown.xls" target="_blank">ex_project_burndown.xls</a>&nbsp;for 
 |
| an example of project burndown report.<br /></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
