All modules
Connected estimation

The first number spoken still owns the room

Most sizing sessions burn time on logistics, then calibrate to whoever spoke first. Ibis Flow pulls tickets from your backlog, briefs the room before the first vote, lets everyone cast at once with votes hidden until you reveal them, and writes the accepted estimate back in one click.

Votes hidden until reveal
Shared AI briefing
Writes back to your backlog
Whole team in one room
Start Free Trial
See Plans & Pricing
Book a demo
Works with JiraWorks with Azure DevOpsWorks with GitHubWorks with GitLab
EU hosted Google & Microsoft SSO GDPR-ready operations
SEE IT WORK

Vote together. Reveal together.

Two people cast at the same time. Nobody sees a number until you reveal. Then you accept a number that writes back to the ticket.

Silent. Hidden vote, reveal, accept. Book a demo instead

What usually goes wrong

Sizing the work is the easy part. The hour disappears into logistics, and the first confident voice quietly sets the number.

  • Screen share, turn-taking, and a spreadsheet that never quite matches the backlog eat the first half of the session
  • Whoever speaks first sets a number. Everyone else calibrates to it, even when they disagree
  • The agreed estimate still has to be typed back into Jira or Azure DevOps, and the why rarely travels with it

When Ibis Flow Estimation fits, and when a simple poker board is enough

Pick based on whether the estimate has to live on the ticket afterwards.

Choose Ibis Flow Estimation when

  • Your backlog is already connected, and tickets should arrive with real descriptions and acceptance criteria
  • You need independent estimates from the whole room before anyone hears the first number
  • You want a shared briefing before people invent different tickets in their heads
  • Done means an accepted number written back to Jira, Azure DevOps, GitHub, or GitLab

Choose a simple poker board when

  • It is a one-off workshop and nobody needs the number written back
  • You only need cards on a shared screen, and a spreadsheet is fine afterwards
  • The team is not in Ibis Flow yet, and the job is a quick size check outside the backlog

In that setup, a lightweight poker tool is enough. Ibis Flow is for the sessions where the estimate has to leave with the ticket.

What you get

What a connected sizing session should leave you with.

Independent estimates from the whole room

Hidden until the host reveals

Everyone votes at once. Votes stay hidden until the host reveals them, so each number is what that person thought before hearing the room.

A shared briefing before the first vote

Same ticket, same starting point

AI surfaces overview, risks, and complexity signals from the ticket. It prepares the conversation. It does not invent the estimate.

Reveal the spread, then decide as humans

Host accepts the number

See the distribution at once. Discuss the outliers. Re-vote when you need to. The host accepts the number when the room is ready.

Write the number back to the backlog

Connected provider write-back

Accept the estimate and sync it to the connected provider. The sizing session ends with the ticket updated, not a note in chat.

At a glance

Brief the same ticket. Vote together. Land the number in the backlog.

  1. Pull the tickets to size

    Connect your backlog and pick the board or sprint items for the session. Descriptions come with the tickets.

  2. Brief the same ticket

    Open a shared AI briefing before the first vote, so the room is sizing the same story.

  3. Vote together, hidden

    Everyone casts at once. Nobody sees anyone else’s number until the host reveals. Classic planning poker, without the logistics tax.

  4. Reveal and decide

    Discuss the spread with confidence signals, then land on one number as humans, not an AI average.

  5. Accept and write it back

    Sync the accepted estimate to Jira, Azure DevOps, GitHub, or GitLab so the backlog stays the source of truth.

Pull

Pull the tickets you need to size

Connect your backlog once, then pick the board or sprint items for the session. Descriptions and acceptance criteria come with the tickets, so the room is not estimating from a title alone.

Brief

Open the same briefing before the first vote

AI Insights give every participant the same overview, risk signals, and complexity drivers from the ticket. Use it to start the discussion. The team still owns the number.

Vote

Everyone votes at the same time

Start voting on a ticket and watch Team Progress as people cast. Votes stay hidden until the host clicks Results, so the first confident voice does not set the room.

Flag

Flag risk on the ticket while you talk

Drop a reaction on the story surface and add a short note during the session. The concern stays attached to the ticket you are sizing, not only in call chat.

Reveal

Reveal the spread, then accept a number

When the host reveals, the distribution appears at once. Clean consensus is easy to land. A wide spread is the conversation you needed. Accept when the room is ready.

Sync

Write it back where the work lives

Accept the estimate and sync it to the connected provider. The session ends with the backlog updated, not a follow-up for someone to type story points later.

Who it is for

For the people who run the room, the people who vote in it, and the leaders who need sizing that lands in the tracker.

Runs the session

Scrum Master / PO host

You need the hour to produce independent estimates and an updated backlog, not a logistics exercise.

  • Pull tickets and start voting without a separate poker tab
  • Reveal when the room is ready, re-vote when it is not
  • Accept the number and sync it back in one move
  • Keep discussion notes on the ticket, not only in the call chat

Casts a number

Engineers and specialists

You want to size the work you understand, without waiting your turn or guessing after someone else spoke.

  • Vote at the same time as everyone else
  • Keep your number private until reveal
  • Read the same briefing before you commit
  • Flag risk or questions on the ticket while you talk

Needs sizing in the tracker

Delivery leadership

You need estimates that reflect the team, not the loudest voice, and numbers that actually land on the tickets planning uses next.

  • Independent estimates reduce first-speaker bias
  • Shared briefings reduce “I thought we meant something else”
  • Accepted estimates live on the tickets planning uses next
  • Sized work can move straight into prioritisation

Compare estimation approaches

Choose the estimation workflow around the way your team works

A simple poker room, a tracker plugin or a ceremony platform can all be sensible. The useful question is what you need around the vote: shared context, relevant past work, discussion, consensus and a route back to the backlog.

Compare this
Ibis Flow Estimation
What to check in a focused tool
Compare this Primary job
Ibis Flow Estimation Collaborative backlog estimation with shared preparation
What to check in a focused tool Is estimation the main workflow, one tracker feature, or part of a broader meeting suite?
Compare this Context before voting
Ibis Flow Estimation A shared AI briefing plus relevant past work for everyone in the room
What to check in a focused tool Is the same preparation visible to every participant, or does each person assemble context separately?
Compare this Team decision
Ibis Flow Estimation Voting, discussion and consensus around the connected item
What to check in a focused tool How are disagreement, re-voting and the final estimate handled?
Compare this Historical reference
Ibis Flow Estimation Similar past work is surfaced as context, not an automatic answer
What to check in a focused tool Is historical work selected manually, suggested automatically or unavailable?
Compare this Backlog connection
Ibis Flow Estimation Jira, Azure DevOps, GitHub and GitLab, with supported outcomes returned to the tracker
What to check in a focused tool Which tracker editions and fields are supported in each direction?
Compare this Wider workflow
Ibis Flow Estimation Can sit alongside Story Studio and Prioritisation on the same connected backlog
What to check in a focused tool Do you want estimation only, a collection of ceremonies, or a broader PM platform?

A focused poker or plugin tool is enough when

  • You mainly need cards on a screen for a live session
  • Your work lives in one tracker ecosystem and site licensing fits how you buy apps
  • Write-back and shared briefing are secondary to running the ceremony
  • Estimation does not need to connect into crafting or prioritisation

Choose Ibis Flow Estimation when

  • Everyone should see the same briefing before the first vote
  • Similar past work should inform the discussion without inventing an automatic estimate
  • Accepted numbers need a supported path back to the backlog
  • Estimation should sit next to Story Studio and Prioritisation on the same backlog

AI prepares the conversation. The team still makes the estimate.

Ibis Flow uses AI to give participants a shared briefing and surface relevant past work. It should help the team ask better questions before voting, not replace team judgement.

Planning Poker® is a registered trademark of Mountain Goat Software, LLC. Category comparison based on publicly available product information; capabilities and packaging can change.

See Estimation pricing
Compare all modules

What's next

You know how big it is. Next, decide what is worth building.

Estimation sizes the work. Prioritisation decides order. Carry a sized backlog into an async stakeholder session when the next job is ranking, not more poker.

Explore Prioritisation

Run the next sizing session with the whole team in one room

Free trial. No credit card. Connect your backlog and invite the team.

Start Free Trial