Planning Poker

  • Adam Trendowicz
  • Ross Jeffery


Planning Poker represents expert-based estimation with a structured group consensus approach. The method originates from agile software development where it was created in order to provide a lightweight approach for estimating software development interactions and planning the scope of software releases. Unlike other alternative expert-based methods, Planning Poker explicitly makes use of historical project data. Actually, the method focuses on estimating the functional size of developed software and then uses historical data on development productivity to come up with the effort required to develop software of a given functionality.


  1. Beck K, Fowler M (2000) Planning extreme programming. Addison-Wesley Longman Publishing Company, Boston, MAGoogle Scholar
  2. Cohn M (2004) User stories applied: for agile software development. Addison-Wesley Professional, Boston, MAGoogle Scholar
  3. Cohn M (2006) Agile estimating and planning. Prentice-Hall, Upper Saddle River, NJGoogle Scholar
  4. Grenning J (2002) Planning poker or how to avoid analysis paralysis while release planning. White Paper, Renaissance Software ConsultingGoogle Scholar
  5. Miranda E, Bourque P, Abran A (2009) Sizing user stories using paired comparisons. Inform Softw Technol 51(9):1327–1337CrossRefGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  • Adam Trendowicz
    • 1
  • Ross Jeffery
    • 2
  1. 1.Fraunhofer Institute for Experimental Software EngineeringKaiserslauternGermany
  2. 2.The University of New South WalesSydneyAustralia

Personalised recommendations