Online planning poker for agile teams, run in Slack
Set up a planning poker session over your backlog, run it on a schedule across time zones, and let the team size the work. Troopr aggregates the votes and comments, then writes the agreed estimate to the Jira issue. No separate estimation app, no meeting on the calendar.
Free for 3 users. No credit card required. Runs in Slack.
Trusted by 600+ engineering teams worldwide
One session covers the whole backlog.
Queue up the issues to estimate, and the team votes on each in turn at their own pace.
The estimate is written to the issue.
Troopr aggregates the votes and sets the agreed story points on the Jira issue, with the full report kept on record.
A repeatable estimation ceremony that runs where your team works
Online planning poker is built for the sprint and backlog estimation you run on a cadence. Configure it once, and the session comes back on schedule without anyone leaving Slack.
Configure a session in three steps
Estimation stalls when it lives in a separate tool the team has to be invited into. Troopr keeps it in Slack. Search and select the Jira issues to size, pick your estimation method, and set who participates.
- Search and select the issues - Pull in the backlog or sprint issues you want sized, by JQL or by picking them directly.
- Choose method and participants - Set the estimation scale and the Slack channel or people who vote.
- Set the schedule - Run it on a cadence or open it on demand. Everyone takes part from Slack.
Run it on a cadence, vote across time zones
A distributed team cannot get everyone into one room at one time, and it should not have to. Schedule the session to recur, and people vote when they reach a stopping point. The round stays open until the window closes, then Troopr compiles the result.
- Recurring sessions - Set planning poker to run on a schedule for every sprint, so backlog sizing becomes routine.
- Vote on your own time - People estimate asynchronously, so a team spread across regions still sizes the work together.
- Reminders before the window closes - Troopr nudges people who have not voted yet, so the session does not stall on one person.
The estimate lands on the issue, not in a thread
An estimate that lives in a Slack message is lost by the next sprint. When the round closes, Troopr aggregates the votes and writes the agreed number to the issue's estimate field, so the work is sized in Jira where planning happens.
- Estimate written to the right field - Set story points or your team's estimate field on the issue from Slack.
- Update other fields too - Adjust other fields on the Jira issue from the same place, without a context switch.
- Confirmed before it is set - The aggregate is shown first; you confirm the number that gets written to the issue.
One report in Slack, full history on the web
When the round closes, Troopr reveals every vote and comment in a summary posted to the channel. The same data lives in web reports you can browse, search, and export, so estimation history is there when you need to revisit how a task was sized.
- Summary report in Slack - Votes and comments revealed in the configured channel or sent to specific people.
- Web reports and dashboards - Browse and search historical sessions in the web app, easier than scrolling Slack.
- Export to PDF - Export the report data out of the web app when you need it elsewhere.
Why agile teams run planning poker online
Sizing the backlog should not depend on getting a distributed team into one meeting. Online planning poker keeps the ceremony async and on record.
Time-zone friendly
People vote when they get a moment, so a team across regions sizes the work without one shared slot.
Fewer interruptions
No standing meeting to size the backlog; the session runs alongside the work instead of breaking it.
Kept on record
Every session is saved to web reports, so there is no manual write-up and history stays searchable.
Cross-team retros
The whole session runs in Slack, so people estimate from wherever they are working.
Everything else in the session
The details that make estimation honest, repeatable, and easy to keep running.
Estimation methods
Fibonacci, modified Fibonacci, T-shirt sizes, and more, or define your own deck of cards.
Hidden votes
Cards stay concealed until the round closes, so nobody anchors to the first number played.
Anonymous participation
Planning poker supports anonymous voting, so estimates are honest and not swayed by who voted what.
Comments with votes
Add a note to a card so the reasoning behind an outlier estimate is in the report.
Multiple issues per session
Queue a set of backlog issues and size them in sequence in one session.
Re-run rounds
Run the round again any number of times until the team reaches consensus on an estimate.
Write the estimate to Jira
Set the agreed story points or estimate on the issue, and update other fields from Slack.
Scheduled or on demand
Recur the session for every sprint, or open it whenever the backlog needs sizing.
Reminders
Automated nudges before the window closes, so the session does not wait on one person.
Web reports and export
Browse and search historical sessions in the web app and export them to PDF.
Slack Grid support
Works across a Slack Grid, with profiles shared across the grid.
All three modules included
Poker is part of Troopr Check-ins; Projects and Reports are on every plan, including Free.
Estimation that meets your security and scale requirements
Troopr runs planning poker for engineering orgs that need enterprise controls and reliability, on infrastructure built for scale.
SOC 2 Type II & ISO 27001
Both maintained through annual third-party audits, alongside GDPR compliance.
Slack Grid support
Installed across all workspaces in a Slack Grid, with shared-channel support.
SSO & RBAC
Single sign-on and role-based access control, with OAuth that respects Jira permissions.
Built to handle scale
Hosted on AWS with EC2 Auto Scaling to hold performance as usage grows.
Bot white-labeling
Rename the Troopr Assistant to match your team or company brand.
24x7 premium support
A dedicated Slack channel for priority support, plus a dedicated success manager.
Teams that run their ceremonies in Slack
Netflix
82%
Reduction in time spent in status-update meetings; ~67% less time finding and updating Jira.
Snowflake
86%
Of weekly status-meeting time eliminated with async check-ins.
Roku
45%
“Reduction in Slack ↔ Jira context-switching overhead. Viral org-wide adoption.
Yahoo!
3.8 hrs
Saved per week for managers on meeting logistics. ~28 minutes a day saved per employee.
Do more than planning poker
Online planning poker is one of six built-in check-in templates. Run the rest of your ceremonies the same way, in Slack.
Instant planning poker
Need a single estimate right now? Start a one-task poker session in any channel with a slash command, no scheduling required.
Daily standup
The standup that writes itself. Troopr drafts each person's update from their real Jira, GitHub, and Slack activity and posts the team report.
Retrospective
Periodic retros with a question template; collect replies and track action items for continuous improvement.
Team mood
Check how the team is feeling, spot trends over time, and act before morale becomes a problem.
Jira Issues Check-in
Prompt the team with a list of their Jira issues and action buttons; people update those issues from Slack. Also how teams run backlog refinement.
Standup bot for Slack
Async daily standups across time zones, with replies and Jira context rolled into one report.
Built to clear your security review
The privacy posture is a precondition of the product, not a later add-on. It's what makes an AI-native model safe to put in front of your team and your auditors.
- No training on customer data. Your work never trains a model.
- No storage of raw messages. Troopr derives and persists a structured set of facts about how your team works, not the raw firehose.
- Clear scope. Team channels, connected work tools, and a person's own shared activity. Troopr does not read other people's private DMs.
- OAuth and Jira permissions. Troopr authenticates via OAuth and never bypasses your Jira project, issue, or field permissions.
Questions agile teams ask
Online planning poker is the configured, recurring session for sizing your backlog: queue a set of Jira issues, set a schedule, and let a distributed team vote asynchronously. Instant planning poker is the on-demand version for a single task, started with a slash command in any channel when you need one estimate right away. Both write the result to Jira; pick the one that fits the moment.
Yes. The round stays open until its window closes, so people across regions vote when they get a moment. Troopr reminds anyone who has not voted, then compiles the aggregate once the window ends. Nobody has to be online at the same time.
Choose from built-in scales like Fibonacci, modified Fibonacci, and T-shirt sizes, or define your own deck of cards. People can add a comment with their vote, so the reasoning behind an estimate carries into the report.
Yes. Troopr aggregates the votes and, once you confirm, writes the agreed number to the issue's estimate field such as Story Points. You can update other fields on the issue from Slack in the same flow, so the work is sized in Jira and not lost in a thread.
Troopr posts a summary report to the configured Slack channel or people, revealing votes and comments. The same data is available as web reports you can browse, search, and export to PDF, so estimation history stays accessible.
Free for 5 users, no credit card. Planning poker is part of Troopr Check-ins, and all three modules, Check-ins, Projects, and Reports, are on every plan. Paid plans start at $79/mo billed annually ($99 monthly) for 15 users.
Size your next sprint in Slack
Join Netflix, Snowflake, Roku, and 600+ engineering teams. Free for 3 users, no credit card required.
The AI project manager for engineering teams. Forms its own view of the work and does the coordination, right where your team already works.
101 Arctic Circle, Round Rock, Texas 78664, United States.