addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1launch-new-window--smalllight-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Omaha Agile Development Message Board › What is the best way to determine priority of user stories?

What is the best way to determine priority of user stories?

Ronnie T.
user 11822973
Omaha, NE
Post #: 4
- Question was submitted as a burning question prior to this week's session, please help out your fellow peers by responding to this discussion group.
Andy H.
user 33682182
Bennington, NE
Post #: 2
1. value to the business (high value with low cost help gain some momentum and confidence from the business)
2. dependency on another story
3. logical grouping of stories to gain efficiency in work and delivery
Helen B.
user 12692487
Omaha, NE
Post #: 1
If I'm talking with a high level executive or product owner, I like to utilize the MoSCoW technique.
They have to really think about the priorities.

MoSCoW is a prioritization technique used to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement. The capital letters in MoSCoW stand for:

* M - MUST have this.
* S - SHOULD have this if at all possible.
* C - COULD have this if it does not affect anything else.
* W - WON'T have this time but WOULD like in the future.
Bill L.
user 13931410
Omaha, NE
Post #: 1
Cost of Delay

All operate roughly on the same idea and are useful tools to visualize story value. More importantly to me is the process of decoupling the prioritization process from the development team so that the product stakeholders that demand development time truly own the responsibility of dealing with resource contention.
Powered by mvnForum

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy