Modify

Opened 5 years ago

Last modified 5 years ago

#4517 new defect

Change method for computing burndown

Reported by: adean@… Owned by: daan
Priority: normal Component: ScrumBurndownPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.11

Description

Opening ticket after discussion started here : http://stuq.nl/weblog/2008-12-25/scrum-burndown-plugin-191-released#comment-5468

The plugin currently calculates burndown as 'hours estimated for ticket - hours spent on ticket'. Per Scrum best practices, burndown should be only the 'estimated hours', and should not involve the actual hours spent on the task.

Attachments (1)

burndown_without_actual.patch (2.0 KB) - added by Alex Dean 5 years ago.
Quick patch. Quick test on sqlite only.

Download all attachments as: .zip

Change History (3)

Changed 5 years ago by Alex Dean

Quick patch. Quick test on sqlite only.

comment:1 Changed 5 years ago by anonymous

Some people may want to preserve the original estimate, thus having the fields 'original estimate', 'estimated hours left' and 'hours spent on ticket'.

  • 'estimated hours left' would be used for the burndown
  • 'hours spent on ticket' for billing or tracking
  • 'original estimate' would be compared to 'hours spent on ticket' after it's completed to improve future estimates.

I currently do burndowns in Excel and I have the fields estimate and percent completed with percent completed x estimate used for the burndown. I'm thinking about moving us to trac for the burndowns and in that case the above three fileds would be what I need.

This would not change the logic of the patch above, just split up the estimate field in one original and one that you update while working on the ticket.

comment:2 Changed 5 years ago by adean@…

The 'original estimate' is always available. It is the first 'estimatedhours' record for the ticket in the ticket_change table.

select * from ticket_change where field='estimatedhours' and ticket='20';

It may be more convenient to store the original estimate separately. Just pointing out that it isn't strictly necessary.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.