| <?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.3/uma.ecore" epf:version="1.0.0" xmi:id="-Aw8p59vJ9rWsOV82rljQiQ" name="iteration_burndown,_uAzgkDg3Edu4E8ZdmlYjtA" guid="-Aw8p59vJ9rWsOV82rljQiQ" changeDate="2006-11-03T07:59:14.929-0800" version="1.0.0"> |
| <mainDescription><p> |
| The iteration burndown is&nbsp;the primary tool for understanding the status of the current iteration. It shows the |
| trend for how much work is left to do within the iteration. This is accomplished by adding up the estimated effort left |
| for each of the work items to be addressed within the iteration, and showing how the estimated effort is changing over |
| the duration of the iteration. The iteration backlog should be updated frequently, preferably on a daily basis. |
| </p> |
| <p> |
| Factors that impact the team’s assessment of how much work remains include: |
| </p> |
| <ul> |
| <li> |
| Work that has been completed, which means there is less work remaining. |
| </li> |
| <li> |
| The developer responsible for a work item changes the assessment of effort required to complete the work item. This |
| should be expected, since we typically understand what it really takes to complete a task after we have done a |
| subset of the task.&nbsp;It's common for estimates of the work remaining to increase in the beginning of the |
| iteration, especially for inexperienced teams, since they often underestimate efforts. Expect estimates to continue |
| changing as teams become more experienced, but the modifications are as frequently upward as downward. |
| </li> |
| <li> |
| Estimated effort left can increase during the iteration as a result of the team learning more about what needs to |
| be done. |
| </li> |
| </ul> |
| <p> |
| Daily or frequent updates to the iteration burndown allows the team to react to changes. For example, cutting scope by |
| removing work items from the iteration, reducing the ambition level associated with a work item, or finding better ways |
| of approaching work items such as having an expert team member help out with difficult work items. |
| </p> |
| <p> |
| See <a href="./resources/ex_iteration_burndown.xls" target="_blank">ex_iteration_burndown.xls</a> for an example |
| iteration burndown report.<br /> |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |