Software Development Cross Solution - Index of - Free

The goal is convergence
After a solid round of planning poker, you should not only have estimates
for each user story but be confident in those estimates. The goal now is to
get rid of as many assumptions as possible, and to converge all of the
points on each user story’s spread of estimates.
1
2
3
4
The estimate you
and your team
reach consensus on.
Talk to the customer
First and foremost, get as much information and remove as many assumptions
and misunderstandings as possible by talking to your customer.
Play planning poker
Play planning poker with each of your user stories to uproot any hidden
assumptions. You’ll quickly learn how confident you are that you can
estimate the work that needs to be done.
Clarify your assumptions
Using the results of planning poker, you’ll be able to see where your
team may have misunderstood the user stories, and where additional
clarification is needed.
How close is “close enough”?
These estimates are pretty
close to one another.
8 10
13
Come to a consensus
Once everyone’s estimates are close, agree on a figure for the user
story’s estimate.
Deciding when your estimates are close enough for consensus is really up to you.
When you feel confident in an estimate, and you’re comfortable with the
assumptions that have been made, then it’s time to write that estimate down on
your user story card and move on.
15
You’ve gotten rid of
any outlying estimates.
Run through this cycle of steps till you reach a consensus:
Download at WoweBook.Com
gathering requirements
Head back to Step 1 if you
find assumptions that only
the customer can answer.
It can also be useful to
note the low, converged,
and high estimates to
give you an idea of the
best and worst case
scenarios.
you are here 4 57