Modify ↓
Opened 10 years ago
Closed 10 years ago
#1094 closed defect (wontfix)
Misleading calculation of remaining hours
Reported by: | anonymous | Owned by: | sambloomquist |
---|---|---|---|
Priority: | normal | Component: | ScrumBurndownPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
When updating the 'current effort remaining' figures the plugin sums up the (estimated - total) differences for all tickets in all components. With respect to Scrum, it produces a misleading result because it assumes that the total figures always mean work that can entirely be subtracted from the estimation.
- Example:
- If 10 hours are estimated for my Ticket-A and I spent (added) 8 hours on it it is still possible that my current estimation for the remaining work amount is not 2 but e.g. 6 hours.
- Suggestion:
- Do not subtract the total hours from the estimation (in burndown_job.py).
Attachments (0)
Change History (1)
comment:1 Changed 10 years ago by sambloomquist
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You're definitely welcome to change burndown_job.py any way that you see fit for your personal running instance. However, this plugin is designed with the assumption that the estimated field is a current estimate, so I'd recommend the following for your example:
As you add the 8 hours and realize that you've still got 6 more hours of work, set the estimated number of hours field to 14. If you are wanting to keep track of what your original estimates, I'd recommend adding an additional custom field to your tickets...maybe called 'original estimate' or something? That's what we're doing on my team, and it's working well so far.