large_Team-running-refinement-meeting.jpg

medium_Team-running-refinement-meeting.jpg

small_Team-running-refinement-meeting.jpg

thumbnail_Team-running-refinement-meeting.jpg

Team-running-refinement-meeting.jpg

## Understanding Async Poker in Jira
Asynchronous Planning Poker enhances the traditional planning poker process by allowing team members to estimate user stories independently, in their own time, before refinement meetings. 

This adaptation of the Planning Poker method is particularly powerful for teams with members in different time zones as it allows members to participate in the estimation process when convenient. Using this method successfully can shorten the time of the next upcoming refinement meeting. 

## When Asynchronous Planning Poker works and when it doesn't

**When it works**

Asynchronous Planning Poker aims to reduce the time required during refinement meetings while keeping the process collaborative. It assumes the majority of stories are well defined, so all team members share the same understanding, and each can give an estimate without further clarification or discussion involving the whole team.

**When it doesn't**

The method depends on the user stories to be well-prepared and clear so that only minor details are open when the team gives estimates.  If team members have major questions about a story, they will likely have a different understanding of what needs to be done, causing a vastly different effort estimate. 

Clarifying stories by using Written QAs. You might address this by using written questions and answers, but take care not to spend more time clarifying in writing than running regular refinement meetings. 


## Implementing Async Planning Poker in your Jira workflow
Successfully implementing asynchronous planning requires a structured approach. Here's your step-by-step guide:

**Before the Backlog Refinement Meeting**

1. **Product Owner - Prepares the backlog** so the stories are Ready for Sprint Planning. Check out the [Definition of Ready](https://www.scruminc.com/definition-of-ready/) for more details.
2. **Product Owner - Notifies the team** - _The first X stories on our backlog are Ready for refinement. Please review and give your estimate and feedback before our meeting_
3. **Team members - Estimate stories in their own time** and raise questions - that might impact the effort considerably
4. **Product Owner - Answer questions** the team has  
5. **Scrum Master -  Make sure estimates** are all in place  before refinement - so everyone's time isn't wasted

**During the Backlog Refinement Meeting**

1. **Review submitted estimates**
2. **Discuss estimate variations** and decide what is included and what is not
3. **Reach a consensus** on the final story points
4. **Update the Jira story points** with One Click

## Best practices for Asynchronous Planning for Scrum teams
To maximize the effectiveness of Async Poker in Jira:
1. **Story Preparation:** Ensure stories are well-defined before asking your team to give estimates. Poor preparation leads to confusion and delays.
2. **Clear Communication:** Establish guidelines for asking and answering questions asynchronously. For stories that require discussion, use Jira labels so team members don't spend time giving an estimate before the discussion takes place.
3. **Documentation:** Keep track of key points during estimation discussions such as decisions within Jira for future reference.

## "The most efficient App for Asynchronous estimates"
Frederik Schottey, Founder & CEO at www.oakfields.io, [said in a review that Smart Guess was](https://marketplace.atlassian.com/apps/1225496/smart-guess-for-planning-poker-for-jira-cloud?hosting=cloud&tab=reviews):

> "The most efficient app we could find for doing asynchronous estimations. While other apps send you off to specific 'estimation' pages, Smart Guess allows you to do the entire estimation process right from the issue. Making the entire estimation process lightweight & intuitive, not yet another task team members have to complete." 

## Transform Your Story Estimation with Smart Guess
Join thousands of developers who are transforming their story estimation process. See how with [Smart Guess's Async Planning Poker](/solutions/async-planning-poker)


Complete Guide to Asynchronous Planning Poker in Jira


https://marketplace.atlassian.com/apps/1225496/

Free app

nav-try-button

SG-full-color-black.svg

SG-full-color-blue.svg

SG-logo-black-07.svg

SG-logo-color-05-MarketPlace.svg

SG-logo-white-06.svg

SG-full-color-white.svg

Using existing tools

Not using existing tools

Are you?

Planning Poker

Async Planning Poker

Bucket Estimation

Backlog Forecasting

Solutions

Blog

Pricing

Creator

Story

About

Contact Support

Documentation

Security FAQ

Support

Forever Free. No setup. One Click—Planning Poker you run directly from the Jira backlog. Including
- **Fully featured Planning-** & Async -Poker
- **Fully configurable** Card decks
- **Role-based controls**, Team lead, Observer, etc.

Perfect for two teams - up to 31 story estimates/week.

Everything in Free included, plus:
- **Unlimited Estimates:** No limits, no boundaries.
- **Silent Estimation:** Estimate large backlogs fast.
- **Atlassian Fortified:** Enhanced security and reliability.
- **Free Demo and Trial:** Experience the Pro Plan before committing.


Smart Guess can be used from within the Jira Backlog

large_PlanningPoker-from-Backlog-E.png

medium_PlanningPoker-from-Backlog-E.png

small_PlanningPoker-from-Backlog-E.png

thumbnail_PlanningPoker-from-Backlog-E.png

PlanningPoker-from-Backlog-E.png

Silent Estimation by Smart Guess allows teams to estimate large number of stories faster

Blog: Complete Guide to Asynchronous Planning Poker in Jira

Share your thoughts

Smart Guess Free

Smart Guess Pro