What is Planning Poker?

The license is available here: Consider purchasing a two-minute sand timer, and allowing anyone in the meeting to start it at any time. The moderator takes notes during this agile planning session that will be helpful when the story is programmed and tested. The cards are revealed, and the estimates are then discussed. The description of http:

Navigeringsmeny

What is Planning Poker?

Teams starting out with story points use an exercise called planning poker. Want to add to the discussion? This planning poker video forms part of a series that complements our open source Agile in Practice Help Sheets on our website at www.

We hope you enjoy it. Kevin Thompson in a demonstration of the wideband delphi and planning poker method to estimation. Learn how to estimate your Agile and conventional projects faster. Sep 11, 0 Comment. By using this site, you agree to the Terms of Use and Privacy Policy.

Privacy policy About Wikipedia Disclaimers Contact Wikipedia Developers Cookie statement Mobile view This planning poker video forms part of a series that complements our open source Agile in Practice Help Sheets on our website at www. The deck contains the following cards: 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 conservative estimate accounting for the uncertainty and play an 8.

Planning Poker is a tool for estimating software development projects. It is a technique that minimizes anchoring by asking each team member to play their estimate card such that it cannot be seen by the other players. After each player has selected a card, all cards are exposed at once. A study by K. Haugen [ 3 ] found that estimates obtained through the Planning Poker process were less optimistic and more accurate than estimates obtained through mechanical combination of individual estimates for the same tasks.

Anchoring occurs when a team openly discuss their estimates. A team normally has a mix of conservative and impulsive estimators and there may be people who have agendas; developers are likely to want as much time as they can have to do the job and the product owner or customer is likely to want it as quickly as possible.

The estimate becomes anchored when the product owner says something like, "I think this is an easy job, I can't see it taking longer than a couple of weeks", or when the developer says something like, "I think we need to be very careful, clearing up the issues we've had in the back end could take months". Please help improve this article by adding citations to reliable sources.

Unsourced material may be challenged and removed. February Learn how and when to remove this template message. Effective Agile Planning and Estimation". Retrieved 30 March Retrieved 1 February Agile Estimating and Planning 1 ed. Retrieved from " https: Agile software development Software project management Software development philosophies. Articles needing additional references from February All articles needing additional references All articles with unsourced statements Articles with unsourced statements from October All articles with specifically marked weasel-worded phrases Articles with specifically marked weasel-worded phrases from December Views Read Edit View history.

This page was last edited on 4 September , at By using this site, you agree to the Terms of Use and Privacy Policy.

Menú de navegación

Leave a Reply