Software Development Cross Solution - Index of - Free

your customer decides priority
Title:
Est:
Title:
Est:
Title:
Est:
Title:
Est:
Title:
Est:
Title:
Est:
Our
View shuttle deals
12 days
Priority: 10
15 days
Priority: 10
Manage special
offers
13 days
Priority: 10
Priority: 20
Book a shuttle
Pay with Visa/
MC/PayPal
15 days
Priority: 10
80 Chapter 3
BE the Customer Solution
Your job was to play the customer and prioritize the
Milestone 1.0 user stories. Here are the priorities
that we assigned to each of the user stories.
We also laid out the user stories in order of
Choose seating
12 days
Order In-flight
meals
13 days
Priority: 20
priority...
Order of priority, most to least
important to the customer
Title:
Est:
Title:
Est:
Title:
Est:
Title: Apply for “frequent
Est:
Title:
Est:
Title:
Est:
Review flight
13 days
Priority: 30
View flight reviews
12 days
Priority: 30
Login to “Frequent
Astronaut” account
15 days
Priority: 50
astronaut” card
14 days
Priority: 40
Priority: 50
View “Space Miles”
account
14 days
Priority: 50
Pay using “Space Miles”
15 days
Download at WoweBook.Com
Q: Why are the priorities 10, 20, 30,
40, and 50?
A: Powers of ten get the brain thinking
about groupings of features, instead
of ordering each and every feature
separately with numbers like 8 or 26 or
42. You’re trying to get the customer to
decide what is most important, but not
get too hung up on the exact numbers
themselves. Also, powers of ten allow
you to occasionally specify, say, a 25
for a particular feature when you add
something in later, and need to squeeze
it between existing features.
Q: If it’s a 50, then maybe we can
leave it out, right?
A: No, 50 doesn’t mean that a user
story is a candidate for leaving out. At
this point, we’re working on the user
stories for Milestone 1.0, and so these
user stories have already been filtered
down to the customer’s most important
features. The goal here is to prioritize,
not figure out if any of these features
aren’t important. So a 50 just says it can
come later, not that it’s not important to
the customer
Q: What if I have some non–
Milestone 1.0 user story cards?
A: Assign a priority of 60 to those
cards for now, so they don’t get mixed in
with your Milestone 1.0 features.
Q: And the customer does all this
work?
A: You can help out and advise,
maybe mentioning dependencies
between some of the user stories. But
the final decision on priorities is always
the customer’s to make.