| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\openup_basic\guidances\reports\iteration_burndown.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: iteration_burndown.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_uAzgkDg3Edu4E8ZdmlYjtA CRC: 130522951 -->Iteration Burndown<!-- END:presentationName,_uAzgkDg3Edu4E8ZdmlYjtA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_uAzgkDg3Edu4E8ZdmlYjtA CRC: 2347347768 -->The iteration burndown shows the trend for how much work is left to do within that iteration.<!-- END:briefDescription,_uAzgkDg3Edu4E8ZdmlYjtA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-Aw8p59vJ9rWsOV82rljQiQ CRC: 1463150831 --><p> |
| The iteration burndown is 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. 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><!-- END:mainDescription,-Aw8p59vJ9rWsOV82rljQiQ --> |
| </body> |
| </html> |
