The Slack scrum bot for every ceremony your team runs

Standups, retros, planning poker, and team mood, run in one Slack app instead of four tools and a calendar that never works. And Troopr forms its own view of the work from Jira, GitHub, and Slack.

Free for 3 users. No credit card required. Runs in Slack.

Trusted by 600+ engineering teams worldwide

Four ceremonies usually mean four tools and a scheduling headache. Troopr runs the full scrum rhythm in Slack, and forms its own view of the work from Jira, GitHub, and Slack, on every plan including Free.

The standup writes itself from real activity

Planning poker and instant poker on every plan

Retros with action items tracked in Jira

Team mood and engagement, one app on Free

The ceremonies

The full scrum rhythm, run in Slack

One install for the four ceremonies your team already runs, no calendar juggling.

The standup that writes itself

Daily standups

Async standups that draft themselves from real Jira, GitHub, and Slack activity, with AI summaries, blockers, and the option to update Jira from inside the thread.

Planning poker

Estimate stories with planning poker and Instant Planning Poker, with anonymous voting, right in Slack and tied to your Jira issues. Included on every plan.

Retrospectives

Run structured retros in Slack and turn takeaways into action items tracked in Jira, so the retro changes the next sprint instead of scrolling away.

Team mood

Track sentiment over time with regular mood check-ins and engagement trends, surfacing morale issues while there is still time to act on them.

Why teams run scrum on Troopr

A scrum bot that forms its own view

A poll bot collects votes and answers. Troopr connects the ceremonies to the actual work.

Collects what people enter

Most scrum bots gather answers and votes, then leave the result in a channel. The ceremony happens, but nothing connects back to Jira or the work itself.

Connects ceremonies to the work

Troopr drafts standups from real activity, ties poker to Jira issues, and tracks retro actions in Jira, so each ceremony moves the board, confirmed in a DM before any Jira write. On every plan, including Free.

Proof

Scrum teams that got their ceremonies back

90%

Time saved on weekly status meetings

Snowflake's engineering teams run async check-ins in Slack with Jira context in the report, instead of context-switching to status calls.

engineering, Jira Cloud

4 hrs

Saved per week for managers

Yahoo's distributed teams moved to async check-ins where members participate at their own time, freeing four hours a week for managers.

distributed teams

Everything a real team needs

Everything to run your ceremonies

The controls a scrum team reaches for in week two, included on every plan.

Anonymous poker voting

Instant Planning Poker

Multi time-zone prompts

Team holidays

Planned absences

Late submissions

Late submissions, skip, answer ahead

Multiple administrators

Anonymous participation

Bulk absence upload

External participants

Slack Grid support

Web reports and history

PDF export

Filter by member

For Enterprise

Slack Grid

Workflow Builder

Bot white-labeling

SSO & RBAC

Success manager

Self-hosted option

Slack Connect check-ins

Buyer's checklist

What to evaluate in a Slack scrum bot

Four questions that separate a poll bot from a scrum tool.

Does one app cover every ceremony?

Running four tools means four bills and four schedules. Check that standups, poker, retros, and mood live in one app, on one cadence.

Do ceremonies connect to Jira?

A vote or a takeaway that never reaches the board is lost. Confirm poker ties to issues and retro actions track in Jira, two-way.

What is gated behind paid tiers?

Some tools gate poker or the Jira link to higher plans. With Troopr, every ceremony is on Free, capped only by users and automations.

Does it meet enterprise security?

Confirm SOC 2 Type II, ISO 27001, and SSO, with permissions that inherit your Jira access, so adoption does not become a security exception.

Security & privacy

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.
Looking for employee or customer support automation? That's a different job, and a different product.
Check enjo ↗
FAQ

Common questions about the Troopr scrum bot

Which ceremonies does Troopr run?

Troopr runs standups, retros, planning poker and Instant Planning Poker, and team mood in one Slack app, with standups that draft themselves and retro actions tracked in Jira.

Is planning poker really on the free plan?

Yes. Every ceremony, including planning poker, is on Troopr's Free plan for 5 users, capped only by users and automations rather than by feature.

How do ceremonies connect to Jira?

Standups draft from Jira activity and can update issues, poker ties estimates to Jira issues, and retro action items are tracked in Jira, with every write confirmed in a DM first.

Does Troopr support Microsoft Teams?

Troopr is built for Slack, where its deep two-way Jira integration lives. That focus is what lets the ceremonies connect to the actual work on the board.

Run your whole scrum in Slack

Standups, poker, retros, and mood in one app, connected to the work in Jira. Your first ceremony runs this sprint.