Loading Profile...
In a feature driven release it should be possible to identify User Stories that must be done before the product can be released vs. ones that we want to do but are not absolutely necessary and can wait for a followup release. Something like "Must-have" vs. "Can-wait". Once the Release is released the unfinished user stories that didn't make it would then be moved to the next release.
There are a couple of existing ways to model this but both have deficiencies:
- create 2 separate Releases: one for Must-have and another for Can-wait
- another approach is to create a dummy User Story to visually delineate backlog between Must-have above and Can-wait below
Ideally I'd like to see a simple line that can be inserted into the release to visually mark the end of the Must-have User Stories and beginning of Can-wait.
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
Identifying "Must-have" vs. "Can-wait" User Stories for Feature Driven releases
-
EMPLOYEE
1Have you considered using Themes for this purpose? You could then highlight or filter based on Must Have or Can Wait, etc.
Cheers,
-- VictorComment -
-
Hi,
Using a "must-have" theme and then highlighting would be a another workaround but requires that you manually Apply/Remove themes whenever you modify priorities.
Right now we are using an un-estimated User Story as a dividing line but it skews reports. It would be better if it was a special UI element that didn't affect reports.
/Mirko -
-
I am using separate releases for must, should, could and wont (MoSCoW priority). This works well for us. If we want predictions including everything or some subset of the releases, then this can be achieved easily as most of the charts allow multiple releases to be included. Would it be possible for you to be specific about what are the disadvantages of having the stories in multiple releases?
-
