Planning Poker for Jira: A Standalone Alternative to the Plugin Tax
If your team uses Jira and you have ever Googled „planning poker for Jira”, you have probably hit the same wall most Scrum Masters hit: Jira does not include planning poker out of the box. There are several paid plugins from the Atlassian Marketplace — Agile Poker for Jira, Easy Agile Planning Poker, Cprime’s Planning Poker, and others — but none of them ship with Jira itself. They cost money per user, require admin approval to install, and add another moving part to your team’s setup.
This post is for Scrum Masters and project leads who want planning poker in a Jira-driven workflow but do not want to pay for a plugin, fight their Jira admin for installation rights, or add another paid SaaS to the team’s stack. We will be honest upfront: we make Scrum Poker Online, which is not a Jira plugin. It is a standalone planning poker tool. The point of this article is to make the case that, for most teams, the standalone-in-a-browser-tab workflow is faster, cheaper, and less brittle than a Jira plugin — even though a native integration sounds more elegant on paper.
What Jira Actually Provides Out of the Box
Jira is a project management tool. It tracks issues, backlogs, sprints, and reports. It supports a „story points” field on every issue (more on that below), but the act of deciding how many story points an issue is worth — the actual planning poker process — is not in Jira’s core feature set.
What you get by default in Jira:
- A „Story Points” field on every issue (you have to add it to your screens; some teams already have it)
- A backlog view where you can see all unestimated issues
- A sprint board where assigned story points show up next to each issue
- Reports (velocity, burndown) that aggregate story points across sprints
What you do not get by default:
- A voting mechanism for team members to estimate stories
- A simultaneous-reveal flow that prevents anchoring
- A discussion-and-revote loop
- Any kind of „session” concept that groups multiple stories into a single estimating run
That gap — between „Jira can store a story point value” and „Jira can help your team agree on a story point value” — is what every Jira planning poker plugin tries to fill.
The Plugin Options (and What They Cost)
The Atlassian Marketplace offers several planning poker plugins. The most popular ones at the time of writing:
Agile Poker for Jira (by AppFox / Spartez Software): One of the more established options. Supports synchronous poker sessions and async voting flows. Pricing scales with Jira user count — at 25 users you are looking at roughly 800 USD/year, and it climbs from there.
Easy Agile Planning Poker: Another mainstream option. Cleaner UI than some competitors, but similar per-user pricing model. Tied tightly to Jira’s permission model, which can be a plus or minus depending on your team’s setup.
Planning Poker (by Cprime Apps): A simpler entry-level option. Free for very small teams (typically up to 10 users), paid above that.
There are several other niche options, but the pricing pattern is consistent: scaled per Jira user, billed annually, and tied to your team’s continued use of Jira. The total cost of ownership for a 20-person team is typically 400–1200 USD/year, depending on the plugin.
When a Jira Plugin Genuinely Makes Sense
Before we make the case against plugins, let us name when they are actually the right choice:
- You estimate 50+ stories per session and need automation: A native Jira plugin can write the estimate back to the issue automatically. If you are doing high-volume estimation, the manual copy-paste-from-Scrumpoker-back-to-Jira workflow becomes annoying.
- Audit or compliance requires the estimate to be logged in Jira’s history: Some regulated environments need every estimate change tied to a Jira issue with a timestamp and a user. A plugin handles this natively.
- You are running planning poker as part of a larger structured Jira workflow: If your team uses Jira automations that depend on the story point field being populated immediately, a plugin keeps the workflow tight.
- Your Scrum Master genuinely prefers staying in one tool: Tool-switching has real cognitive cost. If your facilitator strongly prefers Jira-only sessions, that preference matters.
For these cases, a paid plugin is a legitimate choice. The rest of this article is about the case where it is not.
The Browser-Tab Workflow
The actual mechanics of running planning poker for a Jira team without a plugin are extremely simple:
- Tab 1: Jira. Open the backlog view filtered to the issues you plan to estimate this session. The team can see the stories, read the descriptions, ask questions — same as always.
- Tab 2: Scrum Poker Online. Open a new planning poker room. Share the room link in the team’s chat (or just say the URL out loud in a video call).
- Estimate. The team votes via Scrum Poker Online. Discussions happen, cards are revealed, consensus is reached. The Scrum Master keeps Jira open in the other tab to read the next story aloud.
- Write the estimate back to Jira. After each story is estimated, the Scrum Master (or any team member with edit rights) types the agreed number into Jira’s „Story Points” field. Takes about three seconds per story.
That last step — manual copy of one number into Jira — is the entire trade-off. You give up automation, you gain everything else: zero plugin cost, zero install friction, zero admin approval, zero plugin updates breaking your workflow at the wrong moment.
For a typical sprint estimation session covering 10–20 stories, the total manual-entry overhead is about 30 to 60 seconds across the entire session. That is rarely the bottleneck.
Why This Workflow Is Less Brittle
Beyond cost, there are practical reasons teams end up running planning poker outside Jira even when they have a plugin installed:
- Plugin updates break your flow. Jira plugin updates are not always smooth. When an Atlassian update breaks a planning poker plugin mid-sprint, the team loses the tool exactly when they need it. A standalone web app does not depend on your Jira upgrade cycle.
- Permission complexity. Plugins inherit Jira’s permission model. If a team member does not have edit rights on a project, they may not be able to vote. With a standalone tool, anyone with the link can vote — no Jira admin involved.
- Outside-contractor inclusion. External contributors, agency consultants, or contractors who do not have Jira accounts can still participate in a planning poker session via a shared link. That alone is enough reason for many teams.
- Visual separation. Reading a story in Jira and voting in a separate tab keeps the team’s attention on the discussion. Some teams find that a plugin-embedded poker UI inside Jira is visually noisier than the split-tab approach.
What About Story Points in Jira?
Story points are a Jira-native field, regardless of which planning poker tool you use. To make sure your team’s points end up correctly tracked:
- Add the Story Points field to your issue screens. In Jira Cloud, this is under Project Settings → Issue Types → [type] → Add field. Some templates include it by default, others do not.
- Pick a scale and stick to it. Most teams use the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21). Jira accepts any decimal, but the team’s consistency matters more than the specific numbers.
- Track velocity in Jira’s built-in reports. Once story points are populated, Jira’s velocity report works the same whether you got those numbers from a plugin, a standalone tool, or a sticky note.
Story points are an output of the planning poker process, not a feature of the planning poker tool. Both plugin and standalone workflows produce the same final state in Jira: a number in the field.
When Scrum Poker Online Is the Wrong Choice
To be fair to the plugin options, there are cases where Scrum Poker Online (or any other standalone tool) is genuinely not the right fit:
- High-volume estimation (50+ stories per session): The manual write-back overhead adds up. A plugin’s auto-write is a real time saver here.
- You need automated reporting on estimation history: Scrum Poker Online does not store session results. If you need to look back six months and see how the team estimated a specific story, a plugin that logs to Jira’s issue history is better.
- You are 100+ users and need SSO/SAML: Scrum Poker Online does not support SSO. For enterprise teams with strict identity-management requirements, a plugin tied to Jira’s auth is simpler.
In these cases, we would recommend evaluating Agile Poker for Jira or Easy Agile Planning Poker. They cost more, but they are built for the cases where the automation pays for itself.
The Honest Trade-Off
| Aspect | Jira Plugin | Standalone (Scrum Poker Online) |
|---|---|---|
| Cost | $1–$3 per user per month | Free; Premium $40/year (team, not per user) |
| Install + admin approval | Required | None — just open the URL |
| External participants | Usually need a Jira seat | Anyone with the link |
| Plugin updates | Ongoing; can break workflows | Nothing to maintain |
| Story Points → Jira | Automatic | ~3 sec manual entry per story |
| Estimation history + workflow hooks | Native logging and automation | Not in Jira |
| Session distractions | Varies by vendor | No upsell, no story-count cap |
For most small-to-mid-size teams (3–25 people), the trade-off favors the standalone workflow. For larger or more regulated teams, the plugins earn their keep.
How to Try It
Open a free Scrum Poker Online room (no signup required), share the link with your team, and run one estimation session in parallel with Jira. You will know within one session whether the browser-tab workflow fits your team — and you will not have spent anything to find out.