large_Post-Its-Lots-of-them.webp

medium_Post-Its-Lots-of-them.webp

small_Post-Its-Lots-of-them.webp

thumbnail_Post-Its-Lots-of-them.webp

Post-Its-Lots-of-them.webp

Learn how to run your first Planning Poker meeting. Step-by-step guide to enhance agile estimation and improve team collaboration.

SmartGuess setup with a Fibonaccy approximation card deck

SmartGuess-Fibonaccy-Approximation.jpg

After a couple of refinement meetings, you might see a reason to remove or add cards - but for now - keep it simple and use the default card deck.

 ## Step 4. Before giving an Estimate - Explain each Story Clearly 
Before estimating a story, go through the story and clarify who your target users are, their motivations, purpose of story, it's expected outcome, etc. Encourage team members to ask questions, discuss implementation options and share insights. 

If a story lacks sufficient details and some aspect needs further clarification, delay estimation until the story is ready for estimation. Check out [Definition of Ready](https://www.atlassian.com/agile/project-management/definition-of-ready) for more information.

## Step 5. How to Estimate the First Story - Establishing a reference point
Estimating the first story can be challenging since there is no prior reference for comparison. To establish a reference point, start by allowing the team to identifying the smallest story in the backlog. Once the smallest story is found, assign it a low story point value, such as 2 or 3.

Avoid assigning a value as low as 0.5 or 1 for the reference story, unless you are certain you will not see a smaller story in your backlog. This ensures that when the team encounters an even smaller story later, lower values (e.g., 0.5 or 1) remain available.

From now on, this story serves as a “reference point” for future estimations. By establishing this baseline, the team can compare subsequent stories to it, ensuring consistent and relative estimation throughout the backlog.

It’s considered a best practice to establish a reference story for each story point value (e.g., 2, 3, 5, 8) over time. Doing so provides the team with concrete examples for different levels of complexity and effort. When a new story is being estimated, the team can compare it to these established reference stories to determine the most appropriate story point value. This practice helps maintain consistency in estimations and improves accuracy as the team builds a shared understanding of what each story point value represents.

For example, if the reference story is two story points, the team can compare new stories against it: 
- If a new story seems to require roughly twice as much effort, assigning five-story points, might be appropriate.
- If a story seems to require more effort than five-story points, assigning eight-story points, or more should be considered.

As the team assigns story point values to more stories, they quickly develop a good feeling for matching story points to user stories based on their complexity and expected effort to implement. 

## Step 6. Voting and Discussion
1. Each team member privately selects a card that represents their estimate.
2. The Scrum Master reveals all estimates when everyone has selected.
3. If estimates vary significantly, discuss the differences. Team members with high and low estimates should explain their reasoning.
4. Repeat the estimation until consensus is reached or use the highest estimate as a precautionary approach.

With Smart Guess here is how it's done:

Jira-Backlog-3-2.png

## Step 7. Save the estimate and Move Forward
Once the team reaches an agreement, save the estimate and continue until you have covered all relevant backlog items in the session.

## Best Practices when using Relative Estimates

### Use estimates for: 
- **Release Planning:** Forecasting which features can be delivered by specific dates, aiding in setting realistic release schedules.
- **Backlog Prioritization:** Determining the order in which tasks or features should are implemented based on their estimated effort and value.
- **Decision-Making:** On how you implement your solution when different solution options, effort and value, are present.
- **Capacity Planning:** Assessing the team’s workload capacity to ensure they are not overcommitted.
- **Identifying High-Risk Items:** Highlighting important tasks with high effort to recognize potential risks or complexities that may need further analysis and potential scope cutting. 

### Don't use estimates to:
- **Compare teams performance:** One team's velocity is inherently not comparable to another team's velocity. Velocity is a relative measure that only holds meaning within the team that produces it.
- **Assess Individual Performance:** Using estimates to judge individual contributions can create unhealthy competition and undermine collaboration. Often the most valuable team member is the person who is sharing his knowledge and knowhow generously.
- **Push Estimates Down:** [Forcing teams to commit to lower estimates](/blog/challenging-agile-estimates/) can lead to unrealistic expectations, compromised quality and toxic working environment for team members.
- **Setting Fixed Deadlines:** Treating estimates as exact timelines can result in [undue pressure and toxic development environment](https://www.reddit.com/r/programming/comments/17cha28/comment/k5rvhqc/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)


By following these steps, you’ll make your Planning Poker refinement sessions more effective, leading to better planning and alignment within your team. Happy estimating!



How to Run Your First Planning Poker meeting: A Step-by-Step Guide

Try One-Click Planning Poker you run from the Jira Backlog and you will never look back.



"After trying many tools in Jira, we landed on Smart Guess. It's the best app ❤️ we've ever used!"

Now available for free — no budget approval needed! 🚀

Transform your Planning Poker


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

Forever Free. No setup. One Click—Planning Poker you run directly from the Jira backlog. Including
- **Fully featured Planning-** & [Async -Poker](/solutions/async-planning-poker/)
- **Fully configurable** [Card decks](/blog/configurable-card-decks/)
- **Role-based controls**, [Team lead, Observer, etc.](/blog/smartguess-role-based-controls-observing-leading-sharing/)

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

How to Run your first Planning Poker session in Jira

Story Points 101

Topics covered in the series

Popular posts

Transform your Planning Poker

Transform your Planning Poker

Share your thoughts

Smart Guess Free

Smart Guess Pro