Planning Poker In Agile Methodology

Steps to start a Planning Poker. To start a Planning poker session, the customer or the product owner should read an agile story or describe a feature of the estimators. Each estimator would be holding a deck of planning poker cards with values like 0,1,2,3,5,8,13,20,40,100 which is the sequence that is recommended.

Effective estimation is one of the toughest challenges software developers face in their jobs. Regardless of team size, they need to define, estimate, and distribute work throughout a team. As teams get larger, it becomes even more important to build good habits around planning and estimating work. Lack of planning and estimating reduce confidence in a program, breaks down relationships between the team and the business, and makes development harder on everyone.

  1. Planning poker is also referred to as Agile Poker. It is a group estimation technique often used by agile teams to estimate the amount of effort or relative size of development goals in software development.
  2. In scrum methodology, the team needs to estimates story using a different mechanism. One of the most useful technics is Pocker. Krosswall has developed and released this tool as freeware to all. This tool will help a team to estimates each story one by one. Agile Planning Poker. Indispensable for any planning poker session.
Planning

Best Scrum Software Every Project Needs

Planning Poker In Agile Methodology Framework

A powerful scrum software that supports scrum project management. It features scrum tools like user story map, product backlog management, sprint backlog management, task management, daily scrum meeting, sprint planning tool, sprint review tool, sprint retrospective tool, burndown, impediment, stakeholder and team management.

The Accuracy of Group vs. Individual Estimation

According to some study on the accuracy of estimation of effort between individual and group in an experiment for a software project. 20 software professionals from the same company individually estimated the work effort required to implement the same software development project. The participants had different background and roles and the software project had previously been implemented. After that, they formed five groups. Each group agreed on one estimation by discussing and combining of the knowledge among them.

Result – The estimates based on group discussions were more accurate than the individual estimates.

Planning Poker In Agile Methodology

What is Planning Poker?

Planning poker (also known as Scrum poker) is a consensus-based, gamified technique for estimating, mostly used to estimate effort or relative size of development goals in software development.

PokerPlanning Poker In Agile Methodology

Steps for Planning Poker

  1. To start a poker planning session, the product owner or customer reads an agile user story or describes a feature to the estimators.
    For example:
    “Customer logs in to the reservation system”
    “Customer enters search criteria for a hotel reservation”
  2. Team members of the group make estimates by playing numbered cards face-down to the table without revealing their estimate (Fibonacci values: 1,2,3,5,8,13,20,40)
  3. Cards are simultaneously displayed
  4. The estimates are then discussed and high and low estimates are explained
  5. Repeat as needed until estimates converge

By hiding the figures in this way, the group can avoid the cognitive bias of anchoring, where the first number spoken aloud sets a precedent for subsequent estimates.

Agile Estimation – Relative vs Absolute

An estimate is nothing more than a well educated guess. We use all the knowledge and experience at hand to make a guess about the amount of time it is going to take. So instead of looking at every new work item separately, why not compare it to previously finished work items? It’s easier for humans to relate to similar items than to guess the actual size of things anyway.

For example, is it closer to this really small thing? Or is it more like this normal sized item? Or is it really huge like that one piece of work we finished last month? Doing relative estimates will not only reduce the amount of time spent on estimating work, it will also heavily increase the accuracy of the estimates.

Agile Point Poker

Our brain is not capable of doing absolute estimates; we always put that new thing that we need to estimate in relationship to things we already know.

Fibonacci sequence and Planning Poker

Planning Poker uses of the Fibonacci sequence to assign a point value to a feature or user story. The Fibonacci sequence is a mathematical series of numbers that was introduced in the 13th century and used to explain certain formative aspects of nature, such as the branching of trees. The series is generated by adding the two previous numbers together to get the next value in the sequence: 0, 1, 1, 2, 3, 5, 8, 13, 21, and so on.

For agile estimation purposes, some of the numbers have been changed, resulting in the following series: 1, 2, 3, 5, 8, 13, 20, 40, 100 as shown in the Figure below:

The Interpretation of the point assigned to a poker card is listed in the table below:

Planning Poker Agile Online

Card(s)Interpretation
0Task is already completed.
1/2The task is tiny.
1, 2, 3These are used for small tasks.
5, 8, 13These are used for medium sized tasks.
20, 40These are used for large tasks.
100These are used for very large tasks.
<infinity>The task is huge.
?No idea how long it takes to complete this task.
<cup of coffee>I am hungry 🙂

Point vs Hour Value in Estimation

So why use story points instead of time values? Story pointing allows the team to focus on the complexity and time involved in delivering a piece of work. The team compares the new work against work they’ve already done. They compare the complexity of the new assignment against past challenges and rank the difficulty as well as the time required.

Poker Estimation In Agile

Agile planning poker cards

For example, we don’t often account for “the cost of doing business.” Meetings, email, code reviews, etc. with time values. But in reality, all these are necessary practices throughout in our daily life, but don’t actually count as “work.” Story points isolate the software development work from the associated logistic work items, so estimates using point based should more consistent than hour base approach.

About Visual Paradigm
Visual Paradigm help organizations stay competitive and responsive to change faster and better in today’s fast changing environment. Our award-winning products are trusted by over 320,000 users in companies ranging from small business, consultants, to blue chip organizations, universities and government units across the globe. It enables organizations to improve business and IT agility and foster innovation through popular open standards and process frameworks.Visual Paradigm, a killer Agile feature in 2018, introduced Scrum Process Canvas for automating the way a Scrum team to create, manage and deploy software application that empowers the team to continuously improve their performance at unprecedented speed and scale.

Manage the Entire Scrum Process in One Page

  • Automate the Scrum Framework in a fun and enjoyable dashboard with eye-catching updated status.
  • Manage Backlog, Multiple Sprints of different Scrum Roles with a single-page visually executable canvas
  • Allow instantly access, review and generate scrum artifacts and related documents to be archived in the Shared Cabinet
  • Automate the Scrum events and related activities with self-explanatory instructions, samples and required document templates.