Manage team health, not sticky notes.

QRetro is an operating system for continuous workflow improvement. Assess team health, sync key findings, and turn discussions into a transparent action plan.

Press to register N

Retrospectives

Start retrospective

Action Items

Set up Slack alerts for Laravel Horizon worker crashes.

Conduct flaky tests backlog grooming with the QA lead.

Update Sanctum access rights documentation for the new API.

Successes

Kirill

Nuxt 4 migration completed with zero downtime. CI/CD worked perfectly.

🔥 4

Maria

Finally cleaned up the legacy code in the billing module.

👍 2

Challenges

Roman

Waited 2 days for infrastructure approval again. Releases are blocked.

😡 6

Anna

Flaky tests in the cart are burning time on pipeline restarts.

💯 3

Daria

Business requirements changed three times during the sprint, scope creeped.

Ideas

Roman

Give seniors merge rights to staging without DevOps engineers.

Kirill

Implement a strict linter on pre-commit to avoid code style arguments during reviews.

Meetings end. Actions remain. Most retrospective tools are just digital boards where ideas die when the tab closes. We built QRetro to close the loop: from gathering feedback to completing action items. No chaos. Just focused work and measurable results.

Single source of truth for team tasks

Stop losing track of agreements. QRetro automatically aggregates open action items from all boards into a global list. Assign owners and track progress wherever you work.

Jira

Analyze past sprints and quickly generate new tickets.

Linear

Connect retrospectives directly to projects: estimate and create issues.

Bot for instant notifications and sharing retrospective reports.

Slack

Keep your team aligned with convenient reports and channel notifications.

View all integrations

Action Items

Set up Slack alerts for Laravel Horizon worker crashes.

Conduct flaky tests backlog grooming with the QA lead.

Update Sanctum access rights documentation for the new API.

Meeting value assessment

Team time is your most valuable resource. An automated scoring system helps spot low-value meetings and adjust the format before they become the norm.

Team Morale Trend

4.8Average Score

13 Last sprints

+0.0%

17

17 votes this sprint

Engagement growth +15%

Meeting format change recommended based on recent signals

Positive (4-5)

Critical (1-3)

Instant follow-ups, zero busywork

Forget manual reporting after hour-long calls. Upon finishing a retrospective, the system automatically compiles successes, pain points, and decisions into a concise summary. One click, and the meeting context is synced to your workspace messenger.

Signal over noise
The engine aggregates cards into a single meaningful paragraph, highlighting key signals. No fluff, just facts.
Stakeholder alignment
Push results to Slack, Telegram, or email. The entire organization stays aligned on team challenges, even if they missed the meeting.
Audit trail
Immutable record of participants and the exact timestamp of report delivery.

Thanks for participating!

Roman

Maria

Kirill

Anna

Daria

We are happy with the seamless database migration and progress in speeding up CI/CD pipelines, alongside successful zero-downtime releases. However, we are concerned about Stripe webhook timeouts and want to avoid OOM Kills for Kubernetes workers, improve queue monitoring, implement PagerDuty alerts, and stop ignoring critical Sentry errors.

Estimation without authority pressure

No more juniors echoing the tech lead's estimate. Hidden voting until cards are revealed ensures an honest consensus.

Fibonacci, T-Shirt, and Custom decks supported.

Sprints

Tasks — Growth S28 (Growth Board)

Planning Poker

? ? ?

???

Roman

? ? ?

555

Maria

? ? ?

888

Implement onboarding funnel tracking in Mixpanel

Assignee:

Unassigned

Reporter:

Daria

We lose 40% of users. Events to track:

workspace_created
invite_modal_opened

Team Games

Play together — with or without a retro

Four built-in games: guess the word letter by letter, answer with a GIF, draw it, or lay it out in emoji. Run one as the icebreaker before a retrospective, or open a game room on its own whenever the team needs a break.

Four games to choose from
Hangman with words from the world of development and teamwork, “Sprint in one GIF” — everyone answers the round question with an animation, “Draw and guess” — one draws, the rest guess in the chat, and “Decoded” — the word is hidden in five emoji.
Real-time Collaboration
Every letter opened, every GIF picked, every line drawn and every emoji added shows up for all players instantly.
No board required
Start a game room, send the link, and people join without an account. Or turn the icebreaker on and play the same game right inside the retrospective.

Playing now

Errors: 0 of 6

Real-time Presence

Real-time collaboration with live cursors

Watch your teammates work in real time. Brainstorm, write notes, group cards, and vote on action items simultaneously with zero lag.

Instant Visual Focus
See exactly who is looking at what and which card they are editing at this very second.
Zero-Lag Collaboration
Fast, hardware-accelerated rendering at 60fps makes cursor movements feel as natural as a shared physical whiteboard.
Personal Privacy Control
Feel like working alone? Hide other cursors and stop sending yours with a simple switch in settings.

Sprint 24 Retrospective 3 active users

What went well

Great sprint velocity! 🚀

The icebreaker was very fun!

To improve

CI build pipeline takes too long

Document the new Echo configs

Anna

Artem

Maria

Templates

Ready-made retrospective templates

Pick a format that fits the moment — from a classic sprint review to focused prioritization. Every template opens as a board in one click.

Browse all templates

Went Well - To Improve - Action Items

A classic retrospective for reviewing the results of a sprint or stage of work. The team captures what worked well, where it lost momentum and which concrete steps will move things forward. The simple three-column structure keeps the focus balanced between celebrating successes and turning problems into action items that the team can actually take ownership of.

Start - Stop - Continue

An action-oriented format that pushes the team toward concrete decisions rather than abstract discussion. Participants name practices worth starting, those to stop because they get in the way, and the ones that already work and should continue. The result is a clear, immediately usable list of changes that supports a culture of continuous improvement.

4Ls Retrospective

A simple, popular method for Scrum Masters and their teams that captures both the positive and the negative sides of a sprint. Across four lenses — what people liked, what they learned, what they lacked and what they longed for — the team gathers honest feedback and turns it into ideas for improvement. The structure makes it easy for everyone to contribute, even in quieter teams.

Sailboat Retrospective

A metaphorical exercise that turns reflection into a picture of the team's journey. The wind represents what moves the team forward, the anchors what holds it back, the rocks the risks lurking ahead and the island the shared goal everyone is sailing toward. The visual framing makes it easier to talk openly about obstacles and align around where the team wants to go.

Mad Sad Glad

Mad, Sad, Glad helps a team explore how it felt about the past sprint before moving on to the next one. By naming what made people angry, what saddened them and what brought joy, the team surfaces emotional signals that plain metrics miss. Done well, it builds emotional awareness, strengthens team spirit and turns frustration into a constructive conversation.

Thumbs up, Thumbs down, new ideas and recognition

A light, balanced format that keeps the conversation moving between the good, the bad and the forward-looking. The team marks what deserves a thumbs up, what gets a thumbs down, the new ideas worth trying and the people worth recognizing. Adding recognition to the mix keeps the tone positive while still leaving room for honest criticism.

Lean Coffee

A meeting format that minimizes wasted time and boosts engagement by letting participants build the agenda themselves. Topics are proposed, voted on and discussed in order of priority, so the team spends time only on what truly matters to everyone in the room. First run in Seattle in 2009, Lean Coffee is easy to learn and adapts to almost any team conversation.

Original 4

The classic retrospective that laid the foundation for every method that followed. Built around four questions proposed by Norman Kerth in Project Retrospectives: A Handbook for Team Reviews, it asks what went well, what didn't, what the team learned and what still puzzles it. This timeless structure helps teams reflect honestly and keep striving for continuous improvement.

Starfish Retrospective

The Starfish gives the team five degrees of nuance instead of a simple good-or-bad split. Across keep doing, more of, less of, start doing and stop doing, participants fine-tune their practices rather than just label them. This granularity is especially useful for mature teams that want to adjust what already works rather than overhaul everything.

Three Little Pigs

Based on the fairy tale, this retrospective sorts the team's work by how sturdy it is. The house of straw stands for things that could easily fall apart, the house of sticks for what works but needs reinforcing, and the house of bricks for what is solid and stable. The playful metaphor makes it easy to spot fragile areas before they collapse.

Dot Voting

A fast, democratic way to prioritize when there are more topics or ideas than time to discuss them. Everyone gets a limited number of dots to spend on the items that matter most to them, and the team's attention naturally flows to what gathers the most votes. It's a simple technique to reach quick alignment without long debates.

Speed Car Retrospective

The Speed Car pictures the team as a vehicle racing toward its goals. The engine is everything that makes the team go faster, while the parachute is whatever drags it back and slows it down. This compact, two-part metaphor sparks a focused conversation about accelerators and brakes in the team's way of working.

Deep context

You shape the context. The engine runs in the background, autonomously finding hidden patterns without intrusive chatbots.

Action tracking

Capture agreements after retrospectives and assign clear owners. Track the progress until every task is fully completed.

Poker planning

Estimate tasks with your team: honestly, transparently, and without authority pressure. Available on any device.

Connect your favorite MCP client

Give the client one address — mcp.qretro.com — sign in to QRetro, and analyze boards, get summaries, and extract action items from there. Works with Claude, Claude Code, Cursor, VS Code, and anything else that speaks the Model Context Protocol.

One address, nothing to paste
The client brings you to QRetro, shows the permissions it asks for, and renews access on its own. Revoke it any time in Settings.
Bring your own model
Claude Opus 5, GPT-5.6 Sol, Gemini 3.1 Pro, Grok 4.5 — your board data goes to whichever model your client runs.
Deep analytics
Analyze team health (ROTI) and sprint-over-sprint trends with automated contextual reports.
Auto Action extraction
Let the system handle the routine work. It compiles Agreed Actions from the team's discussion automatically.

View documentation Connect MCP

Available tools

Team listretro.teams.list

Retrospectives listretro.boards.list

Open action items across retrosretro.actions.list

Board messagesretro.board.messages.list

Board summaryretro.board.summary.get

Action itemsretro.board.actions.list

Board insightsretro.board.insights.list

Team healthretro.board.health.get

ROTI scoreretro.board.roti.get

Search retrospectivesretro.boards.search

Create action itemretro.actions.create

Update action itemretro.actions.update

Complete action itemretro.actions.complete

Update messageretro.board.messages.update

Find a sprintpoker.iterations.list

Open a poker gamepoker.games.create

Import sprint taskspoker.game.tasks.import

Sync estimatespoker.game.task.sync

~/qretro — claude

✻ Welcome to Claude Code

qretro MCP server connected · 29 tools

cwd: ~/qretro

Press ↵ to run this question on a real retrospective.

⏵⏵ accept edits on (shift+tab to cycle)? for shortcuts

Start your retrospective today

Set up your team workspace and run your first retrospective in 30 seconds.

Get started with QRetro