Scrum burndown with support for re-estimates
This is a plugin for creating burndown charts using Adobe Flash, a common part of Scrum and other Agile development methodologies.
I have used the existing ScrumBurndownPlugin as a model to develop a version including support for re-estimates which we needed. As far as the license info is concerned all of it should be completely free licensing.
If you have any issues, create a new ticket.
Download the zipped source from here.
Installing this plugin involves the following:
- Install the TimingAndEstimationPlugin.
- Install the BurndownPlugin egg.
- Assign permissions.
- Reload/Restart the server.
Installing the egg
- Install just like you would any other Trac plugin. Drop the egg into your plugins or site-packages folder and then try to access Trac in your browser. Add plugin to [components] section in your trac.ini (at least the following plugins must be enabled):
[components] timingandestimationplugin.* = enabled burndown.* = enabled
- Assign permissions to users for BURNDOWN_VIEW.
- Finally, you will need to restart your webserver to see some of the features that BurnDownPlugin provides, such as the addition of a 'burndown' link on the trac navbar.
You can view different burndown charts, selectable by milestone by choosing from the dropdown and clicking the 'Show Burndown Chart' button.
At the beginning of a milestone (eg sprint), make sure the tickets have been inputted and estimated in Trac. The 'Hours to Add' earliest entered determine the start of the milestone (i.e. sprint) while the one entered last define the end of the milestone.
For this to work, it is imperative that developers keep the 'Estimated Hours' and 'Total Hours' fields accurate and up-to-date on the tickets they are working. The 'Total Hours' field itself should never be manually edited, but rather, it can be changed by inputting positive and negative values into the 'Hours to Add' field.
During the sprint you can entered revised estimates. The chart display 2 bars per day: one for the total amount of work estimated including revised estimates and a second one displaying the total amount of work performed. Like this you can also see how the total amount of work estimated evolves during the sprint: