History of Planning Poker

Agile, Scrum, and Extreme Programming creators and supporters described numerous aspects of their frameworks in detail a long time ago. Yet, they didn’t give instructions about one of the most important ceremonies: a backlog estimation. Teams knew they had to estimate, but there was no rulebook for it.

It became more clear only when Mike Cohn promoted Planning Poker.

Since 2002 Planning Poker evolved significantly: from a card game, where card decks were present in most of the IT companies’ offices, through numerous web services supporting Planning Poker players, or chatbots that replaced the Poker cards, to the services integrated with issue trackers. And finally, to apps like Agile Poker, combined with project management systems like Jira.

Planning Poker eventually evolved into Asynchronous Poker that unblocked estimation for distributed or remote teams.

Planning Poker: The golden standard

Almost 20 years after its introduction, Planning Poker is still a golden standard for estimation in most Agile teams. It comes with a set of benefits that makes it tangible even now as it:

encourages group discussion and collaboration
leaves team members with a shared understanding of every story
has an engaging game flow
is made for unbiased estimation to get everyone’s point of view
allows team members to feel more committed to the project plan
is relatively fast

Although Planning Poker might seem like a fun way to estimate effort and work as a group, the process of the “game” or technique itself isn’t entirely intuitive. It can take a significant amount of time to figure out how to play the game in the first place and then come up with accurate estimates.

Learn more about Planning Poker.

Async Poker: A must-have for remote teams

Asynchronous (or Async) Poker was introduced in Agile Poker for Jira and quickly became popular due to a lack of alternatives for teams distributed in different timezones or even spread across various office locations.

Instead of finding a timeslot that suits all the participants (that might be challenging to achieve), players were able to provide estimates at their own pace in a given timeframe, providing detailed comments explaining each personal estimate.

Usually, the person responsible for planning submits final estimates based on personal scores and comments from the team.

The peculiarity of Async Poker is that it is missing most of the Planning Poker benefits, which in fact, some teams appreciate.

Another problem is that during an interactive poker session moderator can add a new task or break a story into two, and the team will estimate it right away. However, in the case of Async, a moderator should create a whole new session.

Learn more about Asynchronous Poker.

"Hybrid” Poker: The next generation poker

Now, let’s look at a concept that some Agile Poker users call the next step in Planning Poker evolution – the hybrid of Asynchronous and classic interactive Planning Poker.

Let’s call it Hybrid Poker for convenience.

Hybrid Poker is a combination of Async and Planning Poker. It is very popular among Agile Poker users, who previously used either Interactive or Async estimation sessions for their backlog estimation.

In three simple steps, the process of estimation in this hybrid mode looks like this:

One of the team members creates an estimation session several days before the refinement or planning, specifying the session scope and sending invites to the team informing the team members about the scope and a deadline when they should submit their personal estimates.
Team members estimate at their own pace at any time before a specific due date, additionally leaving comments explaining personal estimates or pointing out missing details. There is no additional discussion taking place at this point.
When the final estimation session starts, the team gets together and can discuss user stories’ results if the consensus was not reached with the ability to reset estimates and carry out the voting interactively.

Benefits of Hybrid Poker for Planning Poker users

Let’s imagine members of a team that used to do planning Poker. They come to the final estimation or refinement session with all personal estimates provided and a complete understanding of issues details easily. That team also has a moderator who has read through all the comments and was able to adjust some User Stories, break down the others and provide the missing information. In this case, the session is swift, and here is why.

While doing personal estimates, team members can quickly go through the user stories since they are already familiar with them (in the classic Planning Poker, they would have to wait for others who need more time to cast their estimate);
Participants of different seniority can spend proper time to understand each issue, not holding on or waiting for others, less experienced;
The moderator provides extra information missing from tickets;
The moderator can address participants’ comments with some additional actions, like breaking stories in two, adding missing acceptance criteria, providing extra feedback from business people prior to the final estimation session; all the missing activities with the backlog like breaking down User Stories or creating new ones based on the comments are done;
The team already provided personal estimates, so only re-estimation to reach a consensus will take extra time.

Benefits of Hybrid Poker for Async session users

Imagine a team that used to do Async Poker and can get together – maybe partially – for a short estimation session since the final estimation will be very quick now. Here is what this means.

All of the Planning Poker benefits mentioned above stay since the final estimation session takes place;
Personal estimates are faster because there is no need to be very detailed with estimation comments;
The team can re-vote and reach a consensus;
The team can estimate new stories or tasks right away.

What’s better, the Hybrid session is pretty flexible so that you can adjust the process for your team’s needs.

Hybrid Poker in Agile Poker for Jira

Follow these simple steps below to run Planning Poker in Asynchronous mode in Agile Poker:

Make sure you install Agile Poker for Jira first.
Navigate to a Jira project and select your board.
Click on Agile Poker from the board menu and create an Asynchronous session.

Asynchronous session setup in Agile Poker for Jira

Specify participants, settings, and scope of the session. Optionally, send session invitation emails, don’t forget to mention a due date.

Agile poker asynchronous participants

Wait for the teammates to provide personal estimates.
When the due date comes, enter the session and click on Review personal estimates.
Address questions, concerns, and suggestions from the comments of colleagues.
Invite the team for a short Final estimation session by sharing the session link with them.
Submit final estimates for the session scope. Don’t forget to reach a consensus by re-estimating issues during an interactive Poker game.

Agile Poker for Jira helps you optimize work and save hundreds of precious working hours. If you are ready to put it into play, try Agile Poker for Jira.

Adopting various estimation techniques with Planning Poker

Subscribe for updates