140:
129:
25:
256:
The reason for using the
Fibonacci sequence instead of simply doubling each subsequent value is because estimating a task as exactly double the effort as another task is misleadingly precise. A task that is about twice as much effort as a 5, has to be evaluated as either a bit less than double (8) or
260:
Several commercially available decks use the sequence: 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100, and optionally a ? (unsure), an infinity symbol (this task cannot be completed), and a coffee cup (I need a break, and I will make the rest of the team coffee). The reason for not exactly following the
340:
The cards are numbered as they are to account for the fact that the longer an estimate is, the more uncertainty it contains. Thus, if a developer wants to play a 6 he is forced to reconsider and either work through that some of the perceived uncertainty does not exist and play a 5, or accept a
226:
The reason to use planning poker is to avoid the influence of the other participants. If a number is spoken, it can sound like a suggestion and influence the other participants' sizing. Planning poker should force people to think independently and propose their numbers simultaneously. This is
175:. In planning poker, members of the group make estimates by playing numbered cards face-down to the table, instead of speaking them aloud. The cards are revealed, and the estimates are then discussed. By hiding the figures in this way, the group can avoid the cognitive bias of
335:
To ensure that discussion is structured; the
Moderator or the Product Owner may at any point turn over the egg timer and when it runs out all discussion must cease and another round of poker is played. The structure in the conversation is re-introduced by the
269:
in the estimation. Alternatively standard playing cards of Ace, 2, 3, 5, 8, and king can be used. Where king means: "this item is too big or too complicated to estimate". "Throwing a king" ends the discussion of the item for the current sprint.
307:
The
Product Owner provides a short overview of one user story to be estimated. The team is given an opportunity to ask questions and discuss to clarify assumptions and risks. A summary of the discussion is recorded, e.g. by the
332:
Repeat the estimation process until a consensus is reached. The developer who was likely to own the deliverable has a large portion of the "consensus vote", although the
Moderator can negotiate the consensus.
265:"You must be very certain to have estimated that task as 21 instead of 20." Using numbers with only a single digit of precision (except for 13) indicates the
198:. Agile software development methods recommend the use of Planning Poker for estimating the size of user stories and developing release and iteration plans.
253:
including a zero: 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89; other decks use similar progressions with a fixed ratio between each value such as 1, 2, 4, 8, etc.
311:
Each individual lays a card face down representing their estimate for the story. Units used vary - they can be days duration, ideal days, t-shirt sizes or
544:
506:
266:
539:
534:
457:
108:
42:
89:
46:
61:
297:
At the estimation meeting, each estimator is given one deck of the cards. All decks have identical sets of cards in them.
350:
68:
235:
Planning poker is based on a list of features to be delivered, several copies of a deck of cards, and optionally, an
316:
187:
176:
171:
35:
75:
57:
278:
315:. During the discussion, estimations must not be mentioned at all in relation to feature size to avoid
372:
286:
195:
191:
250:
480:
384:
282:
139:
82:
353:, which generally has support for planning poker, either included or as an optional add-on.
201:
The method was first defined and named by James
Grenning in 2002 and later popularized by
183:
128:
528:
274:
227:
accomplished by requiring that all participants show their cards at the same time.
162:
329:
to offer their justification for their estimate and then the discussion continues.
409:
249:
The cards in the deck have numbers on them. A typical deck has cards showing the
179:, where the first number spoken aloud sets a precedent for subsequent estimates.
312:
24:
388:
243:
210:
166:
435:
262:
236:
202:
281:
over the internet can be used as replacement for physical cards. Several
326:
341:
conservative estimate accounting for the uncertainty and play an 8.
460:. Trademark Status & Document Retrieval (TSDR). 15 January 2008
507:"How I use T-Shirt sizing as a Product Owner to estimate delivery"
239:
that can be used to limit time spent in discussion of each item.
481:"Planning Poker Cards: Effective Agile Planning and Estimation"
322:
Everyone calls their cards simultaneously by turning them over.
18:
261:
Fibonacci sequence after 13 is because someone once said to
325:
People with high estimates and low estimates are given a
410:"Wingman Software | Planning Poker - The Original Paper"
246:, describes some software that needs to be developed.
373:"On using planning poker for estimating user stories"
458:"Planning Poker - Trademark, Service Mark #3473287"
304:
A Moderator, who will not play, chairs the meeting.
49:. Unsourced material may be challenged and removed.
275:teams are not in the same geographical locations
8:
165:technique for estimating, mostly used for
109:Learn how and when to remove this message
363:
182:Planning poker is a variation of the
7:
213:the term and a digital online tool.
186:method. It is most commonly used in
47:adding citations to reliable sources
371:Mahnič, Viljan (1 September 2012).
242:The feature list, often a list of
14:
545:Software development philosophies
300:The meeting proceeds as follows:
138:
127:
23:
436:"Agile Estimating and Planning"
377:Journal of Systems and Software
34:needs additional citations for
1:
257:a bit more than double (13).
207:Agile Estimating and Planning
434:Cohn, Mike (November 2005).
351:Comparison of scrum software
540:Software project management
561:
535:Agile software development
188:agile software development
509:. Medium. 7 February 2020
389:10.1016/j.jss.2012.04.005
487:. Mountain Goat Software
438:. Mountain Goat Software
161:, is a consensus-based,
16:Technique for estimating
289:exist for the purpose.
485:Mountain Goat Software
279:collaborative software
148:Planning poker decks
43:improve this article
287:mobile applications
196:Extreme Programming
190:, in particular in
251:Fibonacci sequence
119:
118:
111:
93:
552:
519:
518:
516:
514:
503:
497:
496:
494:
492:
476:
470:
469:
467:
465:
454:
448:
447:
445:
443:
431:
425:
424:
422:
420:
406:
400:
399:
397:
395:
368:
283:web applications
209:, whose company
172:Agile principles
142:
131:
114:
107:
103:
100:
94:
92:
58:"Planning poker"
51:
27:
19:
560:
559:
555:
554:
553:
551:
550:
549:
525:
524:
523:
522:
512:
510:
505:
504:
500:
490:
488:
478:
477:
473:
463:
461:
456:
455:
451:
441:
439:
433:
432:
428:
418:
416:
408:
407:
403:
393:
391:
370:
369:
365:
360:
347:
295:
233:
224:
219:
184:Wideband delphi
152:
151:
150:
149:
145:
144:
143:
134:
133:
132:
115:
104:
98:
95:
52:
50:
40:
28:
17:
12:
11:
5:
558:
556:
548:
547:
542:
537:
527:
526:
521:
520:
498:
471:
449:
426:
414:wingman-sw.com
401:
362:
361:
359:
356:
355:
354:
346:
343:
338:
337:
333:
330:
323:
320:
309:
305:
294:
291:
232:
229:
223:
220:
218:
215:
157:, also called
155:Planning poker
147:
146:
137:
136:
135:
126:
125:
124:
123:
122:
117:
116:
31:
29:
22:
15:
13:
10:
9:
6:
4:
3:
2:
557:
546:
543:
541:
538:
536:
533:
532:
530:
508:
502:
499:
486:
482:
475:
472:
459:
453:
450:
437:
430:
427:
415:
411:
405:
402:
390:
386:
382:
378:
374:
367:
364:
357:
352:
349:
348:
344:
342:
334:
331:
328:
324:
321:
318:
314:
310:
306:
303:
302:
301:
298:
292:
290:
288:
284:
280:
276:
271:
268:
264:
258:
254:
252:
247:
245:
240:
238:
230:
228:
221:
216:
214:
212:
208:
204:
199:
197:
193:
189:
185:
180:
178:
174:
173:
168:
164:
160:
156:
141:
130:
121:
113:
110:
102:
99:February 2012
91:
88:
84:
81:
77:
74:
70:
67:
63:
60: –
59:
55:
54:Find sources:
48:
44:
38:
37:
32:This article
30:
26:
21:
20:
511:. Retrieved
501:
489:. Retrieved
484:
479:Cohn, Mike.
474:
462:. Retrieved
452:
440:. Retrieved
429:
417:. Retrieved
413:
404:
392:. Retrieved
380:
376:
366:
339:
313:story points
299:
296:
272:
259:
255:
248:
244:user stories
241:
234:
225:
211:trade marked
206:
205:in the book
200:
181:
170:
158:
154:
153:
120:
105:
96:
86:
79:
72:
65:
53:
41:Please help
36:verification
33:
267:uncertainty
159:Scrum poker
529:Categories
513:22 October
442:1 February
358:References
336:soapboxes.
308:Moderator.
167:timeboxing
69:newspapers
317:anchoring
293:Procedure
263:Mike Cohn
237:egg timer
231:Equipment
222:Rationale
203:Mike Cohn
177:anchoring
491:30 March
345:See also
327:soap box
163:gamified
217:Process
83:scholar
464:26 May
419:5 July
394:2 July
85:
78:
71:
64:
56:
383:(9).
273:When
192:Scrum
90:JSTOR
76:books
515:2022
493:2016
466:2014
444:2008
421:2017
396:2024
285:and
194:and
62:news
385:doi
169:in
45:by
531::
483:.
412:.
381:85
379:.
375:.
277:,
517:.
495:.
468:.
446:.
423:.
398:.
387::
319:.
112:)
106:(
101:)
97:(
87:·
80:·
73:·
66:·
39:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
