Upcoming SlideShare
×

# planning poker

459 views

Published on

planning poker

0 Likes
Statistics
Notes
• Full Name
Comment goes here.

Are you sure you want to Yes No
• Be the first to comment

• Be the first to like this

Views
Total views
459
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
11
0
Likes
0
Embeds 0
No embeds

No notes for slide

### planning poker

1. 1. Planning Poker <br />Spredfast 2011 <br />
2. 2. Planning Poker <br />Planning Poker is attributed to Greening and is fairly a recent development (2002) <br />Planning Poker combines expert opinion, analogy, and disaggregation into a fun approach to estimating that results in quick, unambiguous estimates. <br />Participants in Planning Poker include the entire development team (Developers and QA) <br />
3. 3. Story Points<br />Used to denote a name of the estimating unit <br />Derived from calling a unit of work a user story <br />Based on a combination of size and complexity of the work <br />Produces Unitless but numerically relevant numbers <br />A 10 point story would take twice as long as a 5 point story <br />
4. 4. Story Points <br />Have three key benefits<br />Forces the use of relative estimating <br />Focuses us on estimating the size, not the duration <br />Puts estimates in units we can add together <br />Uses Fibonacci sequence – 1, 2, 3, 5, 8, 13, 21, …<br />
5. 5. Planning Poker - Steps<br />Each estimator is given a deck of cards, each card has a valid estimate written on it <br />Customer/Product owner reads a story and the team briefly discusses <br />Each estimator selects a card that’s his/her estimate <br />Cards are turned over so all can see them <br />Discuss Differences (especially outliers) <br />Re-estimate until estimates converge <br />
6. 6. Planning Poker – Why it Works<br />Those who do the work, will estimate the work <br />Estimators are required to justify their estimates <br />Focuses most estimates within an approximate one order of magnitude<br />Combining of individual estimates through group discussion leads to better estimates <br />Estimates are constrained to a set of values so we don’t waste time in meaningless arguments <br />
7. 7. Planning Poker – Side Effects<br />Greater understanding of work to be completed <br />Expectation setting <br />Implementation hints<br />High Level architecture and design discussion <br />Ownership of estimate <br />