User guides

Planning Poker guide

How to run planning poker in EstimateIt. The Scrum Master chooses the settings, creates the room and runs it. Developers and QA each vote in secret, or the whole team votes together if the room is set up for one team estimate.

For Scrum Masters

1Choose your settings

Before you start a room, choose the room settings. When you pick Scrum Master on the start screen, the checkboxes appear under Start a new room. If you're logged in, they're also under Settings on Your account. They are:

Your choices are saved in your browser straight away and used for every room you start from then on. Each room keeps the settings it was started with, so changing them here doesn't affect a room that's already running. Everyone who joins your room works with your room's settings, whatever their own settings say.

The start form with the role Scrum Master, the Start a new room button, and the room settings box with its two checkboxes
Choose Scrum Master and the room settings appear under Start a new room.

2Create a room

Open EstimateIt, type your name and choose Scrum Master as your role. The Start a new room button only appears for the Scrum Master role. Press it and your room opens straight away, using your current settings. There is no sign-up.

The start form with the name Sam, the role Scrum Master and the Start a new room button
Choose Scrum Master to see the Start a new room button.

3Share the room link

Press Copy room link and send it to your team in Teams, Slack or email. Everyone who opens it joins the same room. The participant list shows who has joined, and a faded name means that person has gone offline.

Copy host link is for you only. It lets you run the room from another device or browser. Keep it private, because anyone with it can control the room.

The Room settings line shows which settings this room uses, so everyone can see whether Developer and QA vote separately, whether totals are rounded and whether median estimates are pre-populated.

As the facilitator, you can change a running room's settings: press Change room settings on that line. On the Room settings page, tick or untick Don't round Total pts to a card value and Pre-populate median estimates for Developer and QA totals, then press Return to poker room. The changes apply to the room for everyone as soon as you're back, and the median is used from the next reveal. Separate Developer and QA estimates can't be changed once the room has started, because it decides everyone's roles. These changes are for this room only. Your settings for new rooms stay as they are.

The room bar showing the room code, Copy room link, Copy host link, the participants and the Room settings line
The room code, the two links, who has joined and the settings this room uses.

4Paste in a list of Jira links

Scroll down to Paste a list of Jira links. First choose the Type (Story, Feature or Epic) in the Add an item row, because every pasted link uses it. Then paste your links, separated by spaces or new lines, and press Add all.

To add one item without a Jira link, type a title in Add an item and press Add.

The Add an item form and the Paste a list of Jira links box with four links pasted in
Choose the Type first, then paste the links and press Add all.

5Check the list and pick an item

The items appear in the Items and totals table, and the first one is selected for estimating. Press Estimate on any row to estimate that item instead. The highlighted row is the one the team is voting on.

Remove takes an item off the list. Removed items are kept, with their votes, in a Removed list below the table, where you can re-add them or delete them for good.

The Items and totals table with four stories, each with Estimate and Remove buttons
Each pasted link is now an item. Estimate picks it, Remove takes it off the list.

6Choose the cards and wait for votes

Above the votes, choose the cards: Numbers for stories, or T-shirt for features and epics. You can switch until the votes are revealed, but switching clears any votes already cast.

Developers and QA vote in separate sections. A name gets a tick when that person has voted, but nobody can see the card itself. When everyone has voted, press Reveal developer votes, Reveal QA votes or Reveal both QA and Dev votes.

In a Team room there is one Team estimate section that everyone votes in, and a single Reveal votes button.

The current item SHOP-101 with Priya and Tom ticked as voted for developers, Jo ticked for QA, and the reveal buttons
Ticks show who has voted. The cards stay hidden until you reveal.

7Discuss the result

After the reveal, everyone sees each card with its owner's name, plus the average and median. If the votes are more than one card apart, EstimateIt marks the result as Split and highlights the highest and lowest cards. Ask those two people to explain their thinking.

If people in a section picked different cards, you also get a message at the top of the page asking you to bring the team to agreement. Only Scrum Masters see it; developers, QA and team members don't. Press Dismiss to close it. It won't come back for that round, but it appears again if a new round still disagrees. A ?, ∞ or Pass card doesn't count as a different card.

The message Scrum Master to facilitate agreement on higher or lower Story Point value, with a Dismiss button
The message only the Scrum Master sees when votes differ, here in a room with rounding switched off.

Press Vote again to start a new round for that section. The old votes are cleared and everyone picks again.

Revealed developer votes of 5 and 13, marked Split, with an average of 9 and Agree on buttons
A split vote. The 5 and the 13 explain, then the team votes again or agrees.

8Agree the estimate

When the team has settled on a size, press that value in the Agree on row. Do this for the developer and the QA estimate separately, or once for the Team estimate in a Team room. Press Clear to undo it. If the room pre-populates median estimates, the median card is already selected with "(median)" beside it: leave it, or press another value to override it.

If you move on without agreeing, EstimateIt sets the agreed estimate for you from the revealed votes: the most common card, or the middle card when there is a tie.

The developer estimate with 8 selected as the agreed estimate
The agreed developer estimate is 8.

9Move through the items

Next item jumps to the next item that still needs a developer or QA estimate (in a Team room, a team estimate). Previous item goes back to the one you were on before. You can also press Estimate on any row of the table.

10Read the totals and copy them out

The table shows the agreed developer and QA estimate for every item. Total pts is the developer plus QA estimate, rounded to the nearest card once both are agreed, unless rounding is switched off in Settings. Only story points are added up. T-shirt sizes are shown but never turned into points.

When you are done, press Copy summary for a plain-text list to paste into Jira, Confluence or a chat, or Copy as CSV to paste into a spreadsheet. In a Team room both show one Team value per item.

The Items and totals table with SHOP-101 at 8 developer points, 3 QA points and 13 total points
With the default rounding, 8 developer points plus 3 QA points is rounded to 13.

Rounding switched off: Total pts is exactly Developer + QA, which can be a number that isn't a card, such as 11 or 1.5.

The Items and totals table for a room with rounding off, with SHOP-101 at 8 developer points, 3 QA points and 11 total points
With rounding switched off, 8 + 3 stays 11.

Team rooms: the table has just one Team column with the agreed team estimate, and the total at the bottom adds them up. There is no Total pts or Children dev / QA column.

The Items and totals table for a Team room, with a single Team column showing 5 for SHOP-101
A Team room has a single Team column.

11Good to know

For developers, QA and team members

1Join the room

Open the room link your Scrum Master sent. Type your name, choose Developer or QA, and press Join room. If the room is set up for one team estimate, the roles are Team and Scrum Master instead, so choose Team. The room link offers the right roles for that room, whatever your own settings say. Your name and role are fixed once you are in. To change them, press Leave room and join again before you vote.

The join form with the room code filled in, the name Priya and the role Developer
The room link fills in the room code for you.
The join form for a Team room, with the name Priya and the role Team
Joining a Team room: choose Team.

2Pick your card

When the Scrum Master picks an item, a row of cards appears in your section: Developer estimate for developers, QA estimate for QA, or Team estimate for everyone in a Team room. Click a card to vote. It turns blue, and your name gets a tick so the team knows you have voted.

Nobody can see your card until the Scrum Master reveals the votes, and you can change it as often as you like until then. Click the Jira key next to the item title to open the story in Jira.

The developer card row with 5 selected, and Priya ticked as voted while Tom is still waiting
Priya has picked 5. Tom has not voted yet.
The Team estimate section with 5 selected, Priya and Tom ticked as voted and Jo still waiting
In a Team room everyone votes in one Team estimate section.

3After the reveal

Everyone's cards appear with names, the average and the median. If the result is marked Split, the people with the highest and lowest cards explain their reasoning, and the Scrum Master may ask for another round.

The developer view after the reveal, showing the cards of Priya at 5 and Tom at 13 marked Split
After the reveal you can see every card in your section.

4What the cards mean

The ?, ∞ and Pass cards are never counted in averages or totals. The Estimation guide at the bottom of the room explains the sizes.

The Estimation guide panel describing the t-shirt sizes and the story point cards
The Estimation guide at the bottom of every room.

5Good to know

Ready? Start or join a room.

Glossary

The words used in a planning poker room, A to Z. For more estimating terms, such as velocity and spikes, see the planning poker glossary.

?, ∞ and Pass
? means you need more information, ∞ that the item is too big or unclear and should be broken down, and Pass that you are not voting on this item. None of them is counted in averages or totals.
Agreed estimate
The size the team settles on for an item, chosen by the Scrum Master in the Agree on row. If nobody agrees one, EstimateIt uses the most common card.
Average
The mean of the number cards played in a section after the reveal.
Copy summary and Copy as CSV
Copy the items and their agreed estimates as plain text (for Jira, Confluence or a chat) or as a table for a spreadsheet.
Developer estimate and QA estimate
The two separate sections developers and QA vote in, unless the room has one Team estimate. Each gets its own agreed estimate.
Epic, Feature and Story
The Type of an item. Stories are usually sized in story points; features and epics are bigger and usually sized in T-shirt sizes.
Facilitator
The person running the room, normally the Scrum Master. They add items, reveal votes and agree estimates, and can hand the room to someone else with Hand over facilitator.
Host link
A private link that lets the facilitator run the room from another device or browser. Anyone with it can control the room, so keep it to yourself.
Item
One thing to estimate: a story, feature or epic, usually named by its Jira key, such as SHOP-101.
Items and totals
The table of every item in the room with its agreed estimates and the totals.
Jira key
The short name of a Jira issue, such as SHOP-101. In a room it is a link that opens the issue in Jira; EstimateIt never reads from or writes to Jira.
Median
The middle card played after the reveal. With Pre-populate median estimates on, the agreed estimate starts as the card closest to the median.
Past sessions
Rooms you ran or joined while logged in, kept on Your account with every agreed estimate and Jira link.
Reveal
Showing everyone's cards at once. Until then nobody can see anyone else's card, only a tick to say they have voted.
Room
One estimating session, with its own room code and link. A room is deleted after two weeks without use.
Room code and room link
The code that names a room, and the link that opens it with the code filled in. Send the room link to your team.
Room settings
Whether Developer and QA vote separately, whether Total pts is rounded to a card, and whether median estimates are pre-populated. Each room keeps the settings it was started with.
Rounding
Unless it is switched off, a Total pts that isn't a card value is rounded to the nearest card, with ties going up, so 8 + 3 = 11 becomes 13.
Scrum Master
The role that starts and runs a room. The Scrum Master doesn't vote.
Split
A result where the votes are more than one card apart. The people with the highest and lowest cards explain their thinking.
Story points
A relative size for a piece of work, taking in effort, complexity and risk, not hours. See story points explained.
T-shirt sizes
XS to XXL, used for features and epics. They are compared with similar work and never turned into points.
Team estimate and Team room
A room where everyone votes together in one Team section, chosen by unticking Separate Developer and QA estimates.
Total pts
An item's Developer estimate plus its QA estimate, rounded to a card value unless rounding is switched off.
Vote again
Clears a section's votes and starts a new round for the same item.

Cookie policy · Cookie settings · Accessibility · EstimateIt is an independent tool and is not affiliated with Atlassian or Jira. · Version 1.23.0