Product

One session, start to finish.

Prepare a ticket list, estimate it together in minutes, and send the numbers back to the tracker. Everything below is shipped unless it says otherwise.

A Two Weeks session from draft through reveal to a finalised estimate.
A Two Weeks session from draft through reveal to a finalised estimate.
A session, from draft to finalised estimate.

Three steps, one tool

  1. Prepare

    Build the ticket list in a draft session over as many days as you like. Type tickets in, or pull them from Jira with JQL or from GitLab.

  2. Estimate

    Share the session code. Everyone votes at once, the server-side timer keeps rounds short, and votes reveal together with the low, high and median.

  3. Write it back

    Finalise each ticket and the estimate goes straight back to Jira or GitLab. When the session ends, the backlog is sized.

What’s in the box

  • Estimation

    Votes are hidden until the reveal, so the first number spoken does not become everyone’s number. Pick the sizing method that fits the team, and keep each round short.

    Available on: Every plan

  • Coming soon

    Async voting

    Open a voting window instead of booking a room. People vote ahead of time, from any time zone, and the host reveals and finalises when the votes are in.

    Available on: Every plan

  • Planning

    Sessions start as drafts. Build the ticket list whenever suits you, then go live when the team arrives.

    Available on: Every plan

  • Integrations

    Import from Jira or GitLab, estimate together, and the final number lands back on the ticket. No copying results into a spreadsheet afterwards.

    Available on: Every plan

  • History and reporting

    Every round and every finalised estimate is kept with its session, so you can look back at how a number was reached.

    Available on: Estimation analytics: Team and Enterprise

Your next estimation session could be the short one.