This is a feature request to add a burndown chart illustrating a project progress.

A burndown chart is a graphical representation of work (estimated effort) left to do versus time. The remaining work (or backlog) is on the vertical axis and the time on the horizontal.

CommentFileSizeAuthor
#1 burndown-chart.png13.85 KBFrancewhoa
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Francewhoa’s picture

FileSize
13.85 KB

Here is a suggested presentation for the burndown chart.

In above example each team member can track his/her own progress and the progress of the team.

The Sprint Results section shows amount of work Estimated, Completed and Remaining per team member.

The Progress section shows amount of work with different statuses. Colour coding:
* Grey = Will Not Do
* Green = Completed
* Dark_black = Blocked
* Blue = In Progress
* Red = Not Started

The burndown chart is the most important visual tool for those using the Agile Scrum project management methodology. There are no Gantt charts in Agile Scrum. It is replace by a burndown chart.

I would be happy to contribute testing and update the README.txt file.

Image source: Acunote

Dane Powell’s picture

Looks awesome... subscribing

mikeejt’s picture

Subscribing as well...

killua99’s picture

Subscribing ...

juliangb’s picture

How would a burndown chart fit into Storm?

Would it display existing data? If so, which bits?
Would Storm need to store more data?

I'm hoping to understand how this will fit with where Storm is going.

juliangb’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev
Status: Active » Postponed
juliangb’s picture

Project: Storm » Drupal PM (Project Management)
Version: 6.x-2.x-dev » 7.x-1.x-dev

This will be something that is useful to add to the Project Management Module, but can not yet be a priority whilst we are finalising the port to Drupal 7.

dbt102’s picture

Status: Postponed » Active
D34dMan’s picture

My suggestions:

Any functions that would use data in storm and create a display aka results aka Views could be moved to a separate project which could be full of features :). This could be like storm contrib we had in D6.

juliangb’s picture

I'd be perfectly happy for some features to be in external contrib modules.

There is no reason for every usecase to be covered by "PM Core".

In fact, considering that copying is the most sincere form of flattery, I'd like to follow in the Drupal Commerce footsteps:

Drupal PM (a package containing the core modules)
- PM Organization
- PM Project
...

Other community projects:
- PM Agile
- PM Waterfall
...

Project Management Quick Start
- Distribution containing core + useful contrib + configuration ready to go

Sorry, I know that was off topic ;)

In short, I'm fine if features such as these go in this project or a different one, but I agree that we should try to use views and not custom code.

D34dMan’s picture

@juliangb, can you suggest a tag that could be added to such issues.

juliangb’s picture

What sort of a tag are you looking for?

#10 was just an idea - so also hoping for others views if poss.

D34dMan’s picture

A tag like "PM extras candidate" to issues, that could possibly reside in a another contrib module. And a link to issues tagged such could be provided in PM module description so that somebody who is interested in those issue can take over the responsibility of creating such contributed project.

juliangb’s picture

Actually I'd prefer to leave that a bit more open so that developers don't feel that they have to be asking permission to develop an add on modules.

The most valuable feature may be the one that we haven't thought of!

mheinke’s picture

this is a great idea!

i would be happy to co-maintain or support a PM-agile module, and/or a PM Quick start distribution

juliangb’s picture

Version: 7.x-1.x-dev » 7.x-3.x-dev
Component: Miscellaneous » Code
Issue summary: View changes
Status: Active » Postponed
D34dMan’s picture

Version: 7.x-3.x-dev » 4.x-dev