Opened 8 years ago

Closed 8 years ago

#905 closed enhancement (wontfix)

Alternate scrum burndown chart

Reported by: charris Owned by: sambloomquist
Priority: normal Component: ScrumBurndownPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.10


Check out the scrum burndown chart at This is a great way to visualize the difference between work being added to a project and the work being completed. The most obvious benefit is that one can forecast the future project end-date more reliably.

Drwing bar charts above & below the x axis is easy enough - but how to do the two regressions isn't obvious to me. Because a project can have funny "bumps" in the burndown chart - it's not clear to me that you want to just do a blind regression trend line through the entire project.

Therefore, I would propose to add the two regression lines (one for tasks completed, the other for tasks added). The user then has 4 boxes (to enter the start & end dates for each trendline) which control the points over which the trendline happens.

Attachments (0)

Change History (1)

comment:1 Changed 8 years ago by sambloomquist

  • Resolution set to wontfix
  • Status changed from new to closed

This is pretty interesting, but it's not something I plan to implement for this plugin. For one thing, I don't think it's really in line with the Scrum methodology. The problem this set of charts tries to solve should not be a problem with typical scrumming. New work should not be added to any given Sprint/Release. New work should be prioritized, estimated, and added to the Product Backlog. If the new items are high enough in priority, they'll make it into the next Sprint during the next planning session.

I can see this chart being useful for getting a complete picture of the project as a whole, but that's not the intent of this plugin. Thanks for the link, though. It definitely was worth a look.

Add Comment

Modify Ticket

as closed The owner will remain sambloomquist.
The resolution will be deleted. Next status will be 'reopened'.

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

Note: See TracTickets for help on using tickets.