Postponed
Project:
Drupal PM (Project Management)
Version:
4.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Feb 2010 at 02:03 UTC
Updated:
24 Feb 2023 at 23:33 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
francewhoaHere is a suggested presentation for the burndown chart.
rel="nofollow">
width="*">
In above example each team member can track his/her own progress and the progress of the team.
The
Sprint Resultssection shows amount of work Estimated, Completed and Remaining per team member.The
Progresssection 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
Comment #2
danepowell commentedLooks awesome... subscribing
Comment #3
mikeejt commentedSubscribing as well...
Comment #4
killua99 commentedSubscribing ...
Comment #5
juliangb commentedHow 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.
Comment #6
juliangb commentedComment #7
juliangb commentedThis 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.
Comment #8
dbt102 commentedComment #9
d34dman commentedMy 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.
Comment #10
juliangb commentedI'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.
Comment #11
d34dman commented@juliangb, can you suggest a tag that could be added to such issues.
Comment #12
juliangb commentedWhat sort of a tag are you looking for?
#10 was just an idea - so also hoping for others views if poss.
Comment #13
d34dman commentedA 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.
Comment #14
juliangb commentedActually 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!
Comment #15
mheinke commentedthis is a great idea!
i would be happy to co-maintain or support a PM-agile module, and/or a PM Quick start distribution
Comment #16
juliangb commentedComment #17
d34dman commented