Planning Poker in Jira: The Complete Guide for Scrum Teams (2026)

Planning Poker is the most widely adopted estimation technique in agile software development. It helps teams reach consensus on story point estimates through structured voting and discussion. But for teams that live in Jira, running Planning Poker in an external tool creates unnecessary friction.

This guide covers everything you need to know about running Planning Poker natively inside Jira — from setup and card set selection to advanced workflows for distributed teams.

What is Planning Poker?

Planning Poker (also called Scrum Poker) is an estimation technique where team members independently select a card representing their effort estimate for a user story or task. All cards are revealed simultaneously to prevent anchoring bias, and any significant disagreements are discussed before re-voting.

The technique was first described by James Grenning in 2002 and popularized by Mike Cohn in his book “Agile Estimating and Planning.”

Why Run Planning Poker Inside Jira?

Most agile teams already manage their backlog, sprints, and work tracking in Jira. Running estimation in a separate tool introduces several friction points:

• Context-switching: Moving between Jira and an external tool breaks focus
• Data duplication: Issue details must be copied or linked externally
• Manual data entry: Estimates must be transferred back to Jira fields
• Account management: Team members need separate logins for the estimation tool
• Onboarding overhead: New team members must learn an additional tool

A Jira-native Planning Poker solution eliminates all of these by embedding the estimation experience directly into the Jira workflow.

Setting Up Planning Poker in Jira

Step 1: Choose a Jira Planning Poker Plugin

The Atlassian Marketplace offers several Planning Poker plugins. Key features to evaluate:

Feature	Why It Matters
Multiple card sets	Different teams prefer different scales
Direct field writing	Saves estimates to Jira story point fields automatically
Refinement sessions	Estimate multiple issues in a structured session
Offline voting	Supports distributed teams across time zones
Real-time updates	Shows live voting status and card reveals
Issue preview	View issue details without leaving the estimation room

Agile Toolbox for Jira supports all of the above, plus includes retrospective boards — making it the only plugin that covers both estimation and retrospective ceremonies in one install.

Step 2: Configure Your Card Set

Choose the card set that matches your team’s estimation style:

Fibonacci (most common): 0, 1, 2, 3, 5, 8, 13, 21, 34 The increasing gaps between larger numbers reflect the natural uncertainty in estimating larger work items. This is the default choice for most Scrum teams.

T-Shirt Sizes: XS, S, M, L, XL, XXL Best for teams that prefer relative sizing without numeric precision. Useful during early-stage backlog grooming before items are refined enough for numeric estimates.

Power of 2: 0, 1, 2, 4, 8, 16, 32, 64 A cleaner doubling scale that some teams prefer for its mathematical consistency.

Custom: Define your own values For teams with specific scales (e.g., half-day increments, ideal hours, or company-specific point systems).

Step 3: Configure the Target Field

Set up the Jira field where estimates will be saved. Most teams use the built-in Story Points field, but you can target any numeric custom field.

Step 4: Save Default Configurations

If your team uses different card sets for different issue types (e.g., Fibonacci for stories, T-shirts for epics), save default configurations per project and issue type. This eliminates repeated setup for recurring estimation patterns.

Running a Planning Poker Session

Preparing the Refinement

1. Create a new refinement session from the Refinements tab on your Jira project page
2. Add issues from the backlog or an upcoming sprint
3. Optionally share a direct link with the team

During the Session

1. Open the first issue — the Planning Poker room displays the cards
2. Each team member selects their estimate privately
3. When all votes are in, reveal the cards
4. Review the results: average, median, and individual votes
5. If estimates are close, accept the consensus and save
6. If estimates diverge, discuss and re-vote
7. Move to the next issue

After the Session

The estimates are saved directly to the Jira story point field. No manual data entry needed. The refinement session stays accessible for reference.

Advanced: Async Estimation for Distributed Teams

For teams spanning multiple time zones, synchronous Planning Poker sessions are expensive. Offline (async) voting offers an alternative:

1. The Scrum Master prepares the refinement session
2. Team members estimate on their own schedule — votes are saved immediately
3. The SM reviews results once all votes are in
4. Only divergent estimates need synchronous discussion

This approach respects everyone’s schedule and produces better individual estimates by eliminating anchoring bias entirely.

Best Practices

1. Prepare issues in advance. Don’t estimate issues cold. Share the refinement session at least a day before the meeting so team members can review.

2. Keep sessions focused. Estimate 8–12 issues per session maximum. Beyond that, estimation quality drops.

3. Discuss, don’t average. When estimates diverge, the conversation is more valuable than the number. Ask the outliers to explain their reasoning.

4. Use relative estimation. Start with a well-understood reference story (“this is a 3”) and estimate others relative to it.

5. Time-box each issue. 3–5 minutes per issue. If consensus doesn’t emerge, either break the story down or flag it for more research.

Getting Started

Install a Planning Poker plugin from the Atlassian Marketplace and try it with your next refinement. Most plugins offer free trials.

Agile Toolbox for Jira includes both Planning Poker and Retrospective boards, so you can cover both ceremonies with a single plugin. Get Agile Toolbox for Jira — free forever for up to 10 users.