Postponed
Project:
Drupal PM (Project Management)
Version:
4.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
18 Oct 2009 at 11:16 UTC
Updated:
2 Mar 2023 at 21:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Magnity commentedHi @webritter,
In your view - what would this need to add to Storm? What information would need to be recorded about the sprint?
Comment #2
webritter commentedHi Magnity,
Thank you for replay!
In my view I would like to create different sprints for each project.
For each sprint I would like the following fields:
- Title
- Target (Body)
- Category (Incremental, Exploration, Training, ...)
- Status (Scheduled, Active, Review, Accepted)
- Begin (Date)
- End (Date)
- Resources (The total amount of available Resources for the sprint)
- Resources Unit (Points, Work Days, Hours)
I would like to have a Sprint-Overview in the Project (List of all sprints with Title, Category, Status, Begin, End, Resources.
I have started to implement a module "stomtasks" for this part an I am in a good way :-)
There are a view other features to implement:
- Each task in the project can be assigned to as sprint.
- Each task should have a new field "planned resources"
- for each sprint, there should be a "sprint backlog view" showing all incomplete tasks for the sprint.
- for the project there should be a "project backlog view" showing all incomplete tasks in the project.
- in a "planning view" there should be the tasks without a sprint in the left side. In the right side, there should be a list with all sprints and the assigned tasks to the sprint. With drag and drop the tasks can be moved in the sprints.
This is my idea to handle agile projects with storm and I am sure, there are some more :-)
Very kind regards,
webritter
Comment #3
francewhoa+1 for this new feature. I would be happy to contribute testing. And update the README.txt file.
Here is a suggested presentation for the Sprints Overview.
The overview would include a list of all sprints with Status (Active or Completed), Title, Begin, End.
rel="nofollow">
width="*">
Comment #4
francewhoaAttaching image for comment #3. Image source: Acunote
Comment #5
francewhoaRelated feature request for a Burndown chart http://drupal.org/node/713182
Comment #6
mikeejt commentedThis would be a great feature to have...subscribing...
Wondering, what's the status of this feature?
Also, another great feature would be svn linked to tickets in storm...
Comment #7
juliangb commentedMoving to Project Management module queue for tracking.
Cross reference #1992264: add agile specific project templates (keeping both issues currently as both have good discussion and screenshots).
Comment #8
d34dman commentedComment #9
francewhoaFor the backlogs and sprints I propose to use the jQuery plug-in "jsTree". Find attached screenshots to preview the feel and look.
If you want to try it live
1. Go to http://demo.erpal.info/ Log in with the "pm" role.
2. Then go to http://demo.erpal.info/node/100/tasks?nid=&title=
3. Under "Tree" tab drag and drop the Backlog, Sprints, or User Stories. You can also edit them.
If the above is not working here are the steps to create a new project and new tasks/user stories
1. Go to http://demo.erpal.info/ Log in with "pm" role
2. Click on "Projects" -> Under "In progress" tab click on any project title. Click on "Tasks" tab. Click on "Add a task".
3. Under "Tree" tab drag and drop the items
If above is not working go to http://www.jstree.com/demo/ this is the jQuery plug-in they use. It's called "jsTree".
"jsTree" is free and open source. It's also used by Erpal. Which is contributed to the Drupal community at https://drupal.org/project/erpal
Maybe some of Erpal code could be recycle for Drupal PM? Any volunteers? We're happy to contribute testing and documentation.
Another benefit of jsTree is that it works for any types of Agile methodologies. It's not limited to one or just a few. You can name or re-names any items. Seems more flexible. And the drag and drop is awesomely useful for setting priorities.
Comment #10
francewhoaOther options at
They support drag and drop
Maybe some more options at https://www.drupal.org/node/398508
Comment #11
juliangb commentedComment #12
d34dman commentedComment #13
francewhoaTwo additional options to consider for Agile Sprints and Backlog in PM:
Both modules above support Agile Kanban board. Using drag and drop.
The first column of a Kanban board is one option to create a Backlog. This column is often titled New. But can be renamed by the user to Backlog.
Optimally, adding Swimlines to a Kanban board could allow multiples simultaneous Backlog. In addition, Kanban Swimlines could be used as Springs.
Visual examples of Swimlines at https://kanbanize.com/kanban-resources/kanban-software/kanban-swimlanes
https://archive.ph/8rBdc
Comment #14
francewhoaComment #15
francewhoaFor adding Agile Sprints and Backlogs in Drupal PM (Project Management), my vote goes to adding support for Burndown in PM. Three benefits with Burndown:
This API approach also seems like a good idea. That I know of, Burndown does not presently have an API. But, in the future, jeremylichtman might be interested in adding this API feature to his Burndown module? In turn, PM and Burndown would be able to interact. Another benefit with an API approach is that PM could use various modules or external apps for a Kanban board. In other words, the end user could pick and choose a Kanban board to their liking. So more flexible and more durable. Because if somehow one Kanban board product is no longer available, the others would still be available.
Comment #16
francewhoaFor easier search, and communication, clarified and simplified the ticket title
Comment #17
d34dman commented@francewhoa,
Thanks for cleaning up and organising. Much appreciated.
I had a brief look at the code and api in burndown. It has been written with "extensibility" in mind. Thus it is possible to "extend" the modules functionality as there is a well defined event system and proper triggers. Its not obvious for me, how I could re-use only parts of the project though.
Is this about creating a dedicated module that can be used by both PM and Burndown? Sounds like a plausible idea to me.
Just to clarify, the by "API Approach", I was thinking in the lines of being able to use PM in a Decoupled App via JSON:API.