RE: [scrumdevelopment] Presenting options for product owner/stakeholders
Why not just list all the items and let the business prioritize? Give the
business a list like:
Story A 1 point
Story B 2 points
Story C 1 point
Story ZZZ 3 points
Write the stories in terms of business value so that they can be easily
understood by those reading the list. Tell the business they can prioritize
in up to X points. Make that easy by equating a point to an ideal day of
work and then assume 3 calendar days per ideal day. (So, for a 20-working
day sprint, each person on the team can do 6-7 points).
Once the work is prioritized, let the team do a sprint planning meeting
where they break those stories into actionable tasks and put real hour
estimates on the tasks. Let the team decide if X points was too much or too
little based on the interactions of the selected stories.
Author of User Stories Applied for Agile Software Development
From: gabby_robertson [mailto:gabby_robertson@...]
Sent: Wednesday, April 07, 2004 11:07 PM
Subject: [scrumdevelopment] Presenting options for product
One of our teams is in their first set of sprints and have come up with a
backlog and estimates. The challenge is to achieve as much of the product
backlog within a month. Everything is of course 'critical' to the business.
They have come up with a set of options to present with different approaches
that may help the business get the most bang for their buck.
To present should they do this as a team with the product owner and
stakeholders (there are 12 developers total although they will probably
into smaller groups), or select a few people to represent them, or have the
Scrum Master represent them?
My feeling is to either have the team present together, or to select a small
group. If the Scrum Master presents options and does the negotiation they
could be signing the team up to something they may not want to do. How
have you done this before?
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to:
Yahoo! Groups Links