search

software-project / scrum-pm

Scrum PM is a plugin for Redmine ticket management system. It adds Scrum items like backlog, dashboard and others.
www.software-project.eu/EN/scrumpm
126 stars 47 forks source link

would it be possible to associate issues with user stories in the burndown page? #46

Open jeacott opened 14 years ago

jeacott commented 14 years ago

would it be possible to associate issues with user stories in the burndown page? ie without having to assign a sprint. then in each sprint, issues/tasks can be assigned. on the dashboard page a new backlog column would be helpful as the first column indicating 'assigned to a story' but 'not yet assigned to this sprint'.

software-project commented 14 years ago

Now its not possible and there is a reason for that. Adding issues to user story is a part of sprint planing which is supposed to be done at the begining of that sprint. So following the book such feature is not required. But if you still want to do it that way, you can allways create a teporary sprint assing issues to US, move us back to backlog and delete sprint.

jeacott commented 14 years ago

I have been doing this, but its very annoying as I cannot simply look at the backlog and know whats there. Also I dont think your take on the "book' is correct! It states that a product backlog "is a list of all features, functions, technologies, enhancements, and bug fixes that constitute the changes that will be made to the product for future releases". I dont think anyone is really suggesting that you create a new userstory for every bug in the system! - as they arrive they should be able to be allocated to an existing userstory. also from "the book" : "The Sprint Backlog consists of the tasks the Team performs to turn Product Backlog items into a “done” increment. Many are developed during the Sprint Planning Meeting" Notice it states MANY not ALL tasks are created during the sprint planning meeting. For me this implies that tasks can be properly created outside of sprint plans, and the only place for them to go is the backlog. As a workflow if a new bug or task is identified as belonging to an existing user story, then it should be able to be added to it there and then. not collected in a box somewhere and later remembered to add in. Since this plugin also doesnt allow a user story to be assigned to multiple sprints, nor does it display currently incomplete stories in the backlog page, nor does it allow a story to span multiple sprints (so when you move one you lose your history, velocity etc). its very hard to use this plugin past sprint 1. just my 2 cents. would love to see this improved.