Redmine

+1 for this.

duplicates #443

Brad Mace wrote:

duplicates #443

Subtasking is in my opinion only one aspect of user stories. A feature can be related to more than one user story. And a user story must lead to an acceptance test. I'm not sure how to implement this user driven workflow in redmine ...

• Definition of User Stories at extremeprogramming.org
• Definition of User Story at c2.com

The quest for an implemenation of the feature user stories is a good example for the usefulness of user stories. How is it possible to collect all ideas about a feature and improve them together? Something like a condensed form of the comments.

• As a user I want to write down short descriptions of things I want to do with the software.
• As a user I want to follow the specifications that follow my informal description.
• As a user I want to define some acceptance test based on the informal description that is used to define a story as solved.
• As a developer I want to define a list of specifications that should be implemented to solve a user story.
• As a developer I want to get a clear definition of what is meant with a user story.
• As a user I want to assign user stories to milestones.
• As a user or developer I want to get an overwiew over the current user stories and their work status.

So, how can the work on this list be coordinated and implemented in redmine?

Brad-

Great definition of (and stories for) what's needed for user stories.
I'm working on a testing plugin and would really like to integrate it with a user story plugin. i've looked at the ScrumDashboard plugin, but I didn't really like it, and ToDos wouldn't work for me anyway.

Tasks and Tests are the major things needed. They need to be able to associated to Stories and ideally they should be able to be created and manipulated from the story view.