Child pages
  • Agile Poker Cheatsheet / Battle cards


Agile Poker for Jira - planning and estimation tool for Jira

Jira Cloud and Jira Server

Atlassian Verified


Estimate your backlog no matter how your team works.
Tool inspired by Planning Poker, Wideband Delphi, Team Estimation Game and Silent Grouping derives the best practices from each.

Getting started with Agile Poker is simple and easy as it blends in naturally with the existing UI
in Jira Software.

Top reasons to use Agile Poker

  • One tool, different estimation methods for different needs (including very popular Planning Poker).

  • For both distributed and collocated teams.

  • Good for making quickly rough estimations thanks to relative session mode.

  • Secure and much more precise estimates thanks to reference and historical issues.

  • Self-paced or interactive sessions.

  • With moderation mode for a scrum master or product owner.

  • Can be run on mobile and desktop devices.

  • Using Fibonacci sequence, T-shirt sizes or custom values.

  • Seamless Jira backlog integration.

  • Very responsive support - 24h SLA  (10 hrs avg. time to response).

  • To find realistic project deadline and the scope for project or future sprints.

  • To understand complexity of features.

Target groups

  • Scrum masters

  • Product Owners still using Excel sheets

  • Dev Teams working in agile that want to be more effective at planning

  • Agile teams working in different places and different time zones

  • Business Analyst

  • IT Analyst

  • QA Engineer

Use case scenarios

  • Scrum master needs to make sure that a team can provide estimate values for the issues from the top of the backlog before every planning.

  • Product Owner needs to answer the question “when will you deliver project X?”. Agile Poker will let him or her with the estimation of backlog size and will do it relatively fast.

  • Higher management needs unified estimations across an organization to be able to plan and report on a higher level.

  • Distributed agile teams which cannot meet in one place for planning session - they need to use an online tool, preferably the one that can be integrated with their Jira.

  • Dev teams that are not improving their estimates accuracy from sprint to sprint - Agile Poker will help them improve thanks to reference and historical issues.

  • Teams that need one tool for different types of planning sessions - sometimes the team may need interactive mode, sometimes asynchronous mode if they work remotely and sometimes they have so many issues to estimate that they need something fast like Relative Estimates mode.

  • An agile team in the company, that focuses a lot about the safety of their data - they won’t be able to export their issues to another tool so they need the one integrated with their Jira.




Team size

Monthly price

Average price/user

Team size




n/a (flat fee)














































Atlassian Marketplace stats (status on 29.05.2018)

  • 815 active installs

  • 4/4 stars

  • 36 reviews

  • On the Marketplace since 2011

  • Frequent releases - 71 Server versions from the launch

Quotes from Agile Poker users

  • “With the release of the async mode for the Cloud version this plugin becomes really handy for us! It helps a lot to speed up the process and helps us to focus on the important things.
    Also, the customer service is really helpful and it feels like "working together" :)”

  • “Have been looking for a tool to work within JIRA server and discovered this add-on earlier in the week. I was pleasantly surprised at how well it was integrated into the JIRA backlog both Scrum and Kanban boards. I tested it out with a few engineers and got position reviews.”

  • “My team works entirely remotely, in many different time zones.
    Asynchronous grooming has made our meeting shorter, and our lives easier.”

Who is using Agile Poker

  • Nordea

  • Cisco

  • EA

  • IBM

  • Adidas

  • Oracle

  • And over 500 others

Common customer pain points

  • Hard to estimate with distributed teams (especially when team operate in different time zones).

    • When it’s hard to estimate at the same time, try estimating when it suits the team best. Asynchronous mode let you estimate whenever you like
      Another benefit of this mode is that everyone has a voice and you’re avoiding situations where louder people have more to say.

  • Guesstimating rather than estimating.

    • Prepare yourself better and use reference and historical issues feature
      As a Scrum Master, choose issues from previous sprints as reference points.
      These historical issues will be benchmarks for the whole team to secure a better understanding of future estimates.

    • Another good practice is to show issues that were estimated previously as given story point values – e.g. three issues previously estimated as 1, 3, or 5 story points. Thanks to that, your team will have much better context.

    • Why is it so important? In many scenarios, team members have a different understanding of how big the points are. Giving them examples and a bit of history helps them come up with more accurate estimations.

  • When estimating, some team members try to convert story points into units of time

    • On a project or epic level, try t-shirt sizing rather than story points
      In this method, instead of using numbers from the Fibonacci sequence, your team will use sizes of t-shirts – S, M, L, XL.
      As “State of Agile report” states – 51% of teams use points, 23% of them use t-shirt sizing. Both methods of estimation have their own benefits. If you struggle with people that are converting and calculating story points into days and hours, try T-shirt sizing first.

    • This method is more abstract than story points so it’s harder to convert them into units of time (since t-shirts sizes are not numbers). When your team learns how comparing issues with each other works in practice and why it’s better than estimating in work-hours or days, you can then proceed with story points.

  • Too many issues to estimate

    • If you have many issues to estimate, try Relative Estimates
      Relative estimation is one of the fastest techniques used for estimating projects. It’s based on the well-known Planning Poker alternative – Team Estimation Game – which helps teams sort features and user stories based on relative complexity.

Learn how to choose best estimation method with Agile Poker on Atlassian Blog.

Objection handling

  1. Too expensive - there is a lot of free apps on the web

    1. Agile Poker is seamlessly integrated with Jira. There is no need to launch anything else, just invite your team and do the estimation

    2. More precise estimates - thanks to reference and historical issues

    3. Asynchronous mode - for distributed teams or teams that want to make the estimation meeting much faster (usually around 2 times)

    4. Relative sessions - not really available online (tell us if you find it), very useful for rough estimations or larger batches of issues

    5. Safety - there is no need to export data to another tool, everything stays safely in Jira

    6. Support - we are very responsive and ready to even develop some extra features for our clients

  2. My team is not engaged, so it will be hard to convince them to even try the tool

    1. Agile Poker is easy to use and guides users on every step

    2. Agile Poker helps to make more confident choices based on history and reference points

    3. Agile Poker fosters collaboration and is fun to use, so just try it - that should be enough to become convinced

  3. Despite the fact, that we want to work in Agile, our management/clients still need estimation based on time, not story points

    1. Explain, why relative based estimations are better than absolute values

    2. Start with t-shirt sizing first

Discovery questions

  1. Is your team agile?

    1. If yes, you can proceed, if no - Agile Poker probably won’t help.

  2. Is there a need for your organization to estimate?

    1. If yes, you can proceed, if no - go to point 3

  3. Do teams in your organization plan sprints work collaboratively?

    1. If yes, you can proceed, if 2 and 3 are no’s - Agile Poker probably won’t help.

  4. Is your team collocated or distributed?

    1. Agile Poker will help both types of teams, but it will be more helpful for teams that don’t work in the same location - those teams are probably looking for the online solution anyway, so why not have it in their Jira? It eliminates a lot of overhead and switching dialogues between Jira and a tool.

  5. Are you using Planning Poker for estimations?

    1. If yes, the team is probably using physical cards or free web-based solutions.
      Try to show them Reference and historical issues mode to help them make more precise estimates based on better context.

    2. Show them, how well integrated with their Jira Agile Poker is. They can instantly start using it on their backlog view (no need for exporting - importing issues to another tool).

    3. If they are already aware of such method, show them alternatives which may help them estimate in different situations (f.e. Too big backlog and not enough time - show them Relative Estimates mode).

    4. Do they work with sensitive data? If they use a free tool they need to export-import their tasks to external, a free tool which may not be safe enough. With Agile Poker, they don’t have to do it, issues are safe on their Jira.

Agile Poker vs Planning Poker vs PlanItPoker

Agile Poker

Planning Poker
(Jira app*)



Jira Cloud and Server

Jira Cloud only


Works with Jira




Asynchronous mode




Interactive mode




Relative sessions




Reference Issues




Historical Issues




Capacity calculator




Countdown timer





Yes (mobile view, server only)

Yes, mobile apps


Use different values
(t-shirt sizing, Fibonacci sequence, custom)




User Interface

Integrated into Jira



Paid / Free

Paid with support

Paid with support


*Planning Poker for Jira is an app developed by Lizard Brain UG, not official trademark owner which is Mountain Goat Software, LLC - author of .


Marketing materials product page

Relative Estimates demo video

Reference Issues demo video

Atlassian Blog about best methods for estimation using Agile Poker

Atlassian Marketplace page

Why Spartez?

Spartez (Atlassian Verified) is one of the very first vendors on Atlassian Marketplace.  

We're a company focused on the Atlassian ecosystem™ and agile methodology.

We live and breathe Atlassian every day.
Since day one in 2007, Atlassian has been our biggest and strategic customer and a friend at the same time.

On a daily basis, Spartez developers are involved in all areas of development (vision, design, implementation, testing, maintenance) of several Atlassian products, such as Jira®, Bamboo®, Fisheye®, Crucible®, or Clover®.

Spartez is Atlassian Gold Partner 

Atlassian Partners portal

Premium support channel for Atlassian Partners

Write to us and we could help you in the presale processes including demoing to your clients.
Our support team also provide quick assistance in TFS4JIRA configuration and technical problems you encountered with during the set up.

Premium Support Channel is avaible here -

Company & contact Information

Have an opportunity?

Have an issue?

For marketing and sales opportunities (brown bags, webinars, AUG meetings, blogging, video content), please contact:

Jacek Wizmur - Szymczak

The best contact time 
is 9:00 - 17:00 (Warsaw time).

For any support issues and demo requests, please contact:

Paweł Mazur

The best contact time 
is 9:00 - 17:00 (Warsaw time).

Other apps by Spartez

This page has no comments.