Planning Poker that saves time of sprint estimation

Speed up preparation by 23%
and estimation by 16%.
Boost estimate precision by 34%.
Already estimate with Chpokify
How Chpokify planning poker saves
time for Agile teams
Speed up preparation by 23%
All your manual work is automated. Plus, enjoy JIRA integration, import/export, auto-summary.
Cut estimation time by 16%
Multiple teams' sessions, smart voting management, auto-reveal of all cards.
Boost precision
by 34%
Less optimistic and more realistic estimates with planning poker estimation technique.
The data is based on the feedback from over 300 users of Chpokify scrum poker.
Also, see research from Haugen, N.C Combining Estimates with Planning Poker—An Empirical Study
Features and user interface breakdown
• JIRA integration
• Video calls
• Multi-story input
• Session and story timers
• Multiple teams in one session
• Smart voting
• Estimation summary
• Export .CSV
What our clients say
Since we started using Chpokify we saved 14 minutes per estimation, mostly thanks to multiple teams in one session. I stopped wasting time manually copying-pasting issues from JIRA using integration. I also forgot about excel files thanks to automated summary that allows me to export and share results with team members.

It turned out that 14 minutes per estimation saved us more than $10,000 per year.
★★★★★
Projects manager in LiveXP
It has clear and simple interface and all the functionality you may need: paste story list easily, create different teams and assign members to them, create separate spaces for different projects in your company, view team stats during sessions, keep all your sessions' history in the same place, etc. It doesn't matter what devices we're using -- it works perfectly for both desktop and mobile. We don't spend our time on any technical imperfections anymore as we did with other tools. Instead we can focus on story details only and have really effective discussions.
★★★★★
COO at Wisebits
Great product. Already a user of Chpokify since the closed beta version. Really like its clear and fast UI, simple way to launch tasks estimation. Love it.
★★★★★
CTO at Live Streaming Platform
Awesome experience with Chpokify. Today we successfully used it for the DevOps team's PBR and really enjoyed the tool. Highly recommend it to all development teams.
★★★★★
Project Manager at Affiliate Platform
Ready to save time and money on estimation?
Small Team
  • Up to 5 users
  • Jira integration
  • Unlimited Teams
  • Unlimited Poker Sessions
  • Unlimited Video Calls
FREE
Create free account
Enterprise
  • Unlimited users
  • Jira integration
  • Unlimited Teams
  • Unlimited Poker Sessions
  • Unlimited Video Calls
Custom price
Create fee account

How planning poker online actually works?

In the Scrum Agile framework, a sprint planning meeting is an event aimed at setting the product development goal and laying out a plan for the upcoming sprint based on a product backlog review by the team. Planning poker (or estimation poker) is a gamified method for estimating backlog items.
Each task is estimated by team members individually. Every team member picks a planning poker card with a estimate number. Initially, everyone's estimate is hidden from the others. This prompts everyone to think for themselves. When everybody's picked a card, every team member reveals their estimate.
Step-by-step guide for a planning poker session
1
Register at Chpokify
and get your own workspace
When you sign up, we create a cozy space for you and your teammates. In that space, you will have everything you need to create stories and estimate them. You can have as many spaces as you need for different projects or companies.
2
Invite people and team them up
Invite people to your space in a second. No more stuttering registrations for your co-workers – we will auto-register them by an invite. Have a big team? Assign invited people to teams at any time.
3
Start a session and create stories
Create a poker session dedicated to the sprint that you've planned and fill it with stories.
4
Vote and moderate
Control the field. Decide when and which team is going to vote right now. Got different or wrong results? Discuss with the team, take notes, and reset or revote if needed.
5
Finalize and analyze
Ready to finish the sprint estimate session? Well done! Create reports of the team's progress during a sprint and review other statistics.
Use different estimation techniques
There are many different types of project estimation techniques that help your remote teams be more productive.
Why is Chpokify's planning poker great?
This planning poker estimation technique lets you easily assess how big and time-consuming the stories in your upcoming sprint are. It's a widespread Agile technique loved by many, especially remote teams. It's quick, collaborative, and helps take into account all the factors that could impact the implementation of the task at hand.
Scrum poker for Agile teams of any size
Whether there are 3 or 23 people in your team, sprint planning with a Scrum poker is easy and simple. The difference between team members' estimates prompts discussions that may uncover interesting insights, biases, lacking information, and assumptions that can be addressed right there and then.
What are story points and T-shirt sizing?
First things first, a team should choose the unit of measure for their sprint planning meetings. Story points and T-shirt sizes are two popular choices in Agile planning. These units, unlike hours and days, come from an understanding how much effort is required to implement a story or an epic task.

At first glance, these measure units may seem a little tricky to understand. We are used to hours and days in everything. But to presume that a story point equals one hour would be wrong. It would undermine the very idea of a story point.

When planning in story points, it's not about how much time we assume it may take to finish this story. Instead, it's about what activities it will take to complete the story and how complex we as a team with our current knowledge think these activities are. Then we estimate the story relative to a previously defined baseline story.

It means that one and the same story does not necessarily get the same estimate by two different teams. It all depends on the teams' experience, knowledge, and skills. For instance, the task is to paint a room. One team could give 1 story point to the painting of one of the walls without a window. The same team could give 0.5 story points to the painting of a wall with a window, since there is less surface to be painted. However, another team could give 2 story points to the painting of a wall with a window because they might not have the tools necessary to cover the window while painting. It's more complex and requires more effort from their point of view.

You might go for T-shirt sizing for estimation if your team is not very familiar with the concept of story points. Every T-shirt size stands for the amount of work needed to be done to complete a task. Just like story points, T-shirt sizes do not equal hours or days.

To kick things off, you can take a story (a small one) that you've implemented previously and make sure that everyone on the team understands what activities and requirements it entailed. It is important to be on the same page regarding this baseline story. Then decide how many story points or what T-shirt size your team agrees to give this story, and you have on your hands a sample estimate to guide you when estimating other stories.

Made on
Tilda