Burndowns only represent yesterday's data. It would be much better if we could have realtime/near-realtime/configurable intervals/or on-demand burndown updates.
Team members are often reminded each morning that they haven't updated Versionone as they should have, or sometimes they update just before the daily scrum. By the time we have the stand-up meeting, the burndown is called 'inaccurate' and is considered unusable.
While this could be remedied by having people enter their time before they leave each day, it is easier said than done. It simply shouldn't be something that our chosen tool demands. It is a limitation and has been identified as one reason people prefer competing products.
by: Heath S. | over a year ago | Reporting & Analytics
Comments
All reports in the core VersionOne application reflect the current state of the system. If you close a Backlog Item (aka Story), the Project Burndown is reduced by that items estimate value. Similarly when you reduce the ToDo value on a Task or Test, the Sprint Burndown reflects this change. You must run or refresh the report after the change is made in order to see the change.