Agile — The Agile retrospective asks four basic questions that get the team thinking about the outcomes of the last sprint, and what actions they should focus on next. While it is straightforward, it sends a clear message that you are listening and geared for improvement.
## Great retrospective templates to use to support people A supported team is a productive team. Here are three of the templates we use that deliver effective meetings and shine a spotlight on team empowerment and support.Four Ls — The Four L's retrospective presents your team with the opportunity to share both thoughts and feelings about their last sprint in a safe way. You can use it to gain insight into how they prefer to be supported and their aspirations.
Personal Growth — The Personal Growth retrospective has been designed to support the empowerment and well-being of your team members. It gives each team member the space to set goals and identify how others can support their efforts.
Scrum Values — The Scrum Values retrospective is a deep dive into the behaviors and actions each person takes in their daily life and work practices that reflect the values of Scrum. It's an opportunity to explore the connection between the Scrum Values and those of the team.
## The best retrospective templates to use to support the process When things aren't progressing as well as planned it might be time to look at processes. These are three of the templates we use when it comes to process. They help us drill down into what's happening and help us shape steps to get things back on track.Stop Start Continue — The Start Stop Continue retrospective throws processes into sharp focus. It's a great tool to hone in on actions and quickly identify those that deliver value and those that don't.
KALM — The KALM retrospective creates a safe space in which a team can fine-tune its processes. It promotes a sense of agency and utility allowing the team to come up with ideas to help them move forward.
Starfish — The Starfish retrospective supports an examination of the varying degrees of value delivered by actions and activities. It helps the team look at current practices and which ones should have more or less energy directed toward them.
## The best retrospective templates to support product management A Scrum Team's purpose is to deliver outputs that address the requirements of Stakeholders. Product management, therefore, is core to their success.Must Should Could Won't — The Must Should Could Won't retrospective is a great tool that offers the team a mechanism to step into the shoes of a customer and view the product from their perspective. It is a particularly useful tool to maintain focus on priorities for projects with a large number of feature requests and competing stakeholders.
Three Little Pigs — The Three Little Pigs retrospective offers your team a creative sprint retrospective idea to help identify short, medium, and long-term actions that will bring stability and value-added features to your product. It helps analyze the current product or technology stack and which elements can be easily broken, need fixing up, or are part of the foundational core to deliver your service.
Rose Bud Thorn — The Rose, Bud, Thorn retrospective is an effective technique designed to help identify the positive outcomes, the opportunities, and the challenges from your last sprint. This is a great retrospective to use if you wish to help remind your team to view challenges as manageable accompaniments to the delivery of value.
## Great retrospectives to use if you've had a bad sprint We're human. We will have good days and bad days. Our team will have good sprints and bad sprints. When it comes to the bad, the important thing is we learn from them.What? So what? Now what? — The What, so what, now what? retrospective was designed to bring a neutral pragmatism to the review of a sprint. It helps your team suspend emotion and side-step bias in order to create a safely objective space to conduct your retrospective.
Working Not Working — The Working Not Working retrospective gets straight to the point. Its simplicity makes it impactful. If your team needs a direct approach to get them moving again, then this is the retrospective template you should use.
And when the sprint went wrong but nobody quite agrees why, run a root cause analysis before you pick fixes. The [Fishbone (Ishikawa) retrospective](/retrospective-templates/fishbone-ishikawa-retrospective/) maps the causes behind a problem — people, process, tools — using the classic Ishikawa diagram, so your team debates the actual cause rather than the loudest theory. ## Easy retrospectives to use when it's time to have fun Bringing an element of play into the workplace has been shown to deliver a myriad of benefits. It helps build teams and even supports individual well-being. For more ways to lighten the meeting without losing the point, see our [fun and easy retrospective ideas](/blog/fun-and-easy-retrospective-ideas/).Witches and Warlocks — The Witches and Warlocks retrospective has been deliberately crafted to position team members to adopt an optimistic view of the sprint. It's a sprint retrospective idea that shows creativity and fun bring value to a project, and can be embraced without sacrificing productivity, focus or purpose.
Oscar Academy — The Oscar Academy retrospective creates a stage where people can learn from stories, are recognized for their contributions, and celebrate their successes. It embraces deliberate cheerfulness as a gentle reminder to team members to adopt a perspective of optimism when reflecting on the sprint.
Superhero — The Superhero retrospective is a fun, creative exercise that can be especially engaging for remote teams that have to come together to solve a common problem or work toward a goal. Of course, each team has its own set of superpowers, but they will also have their vulnerabilities and this retrospective template can help uncover these.
## Frequently asked questions ### What is a retrospective template? A retrospective template is a ready-made board of prompts that guides a team's reflection and captures their responses in one place. It both structures the meeting (the questions the team answers) and records its output (the ideas, themes, and actions), which becomes the basis for the team's next steps. ### How do I choose the right retrospective template? Start from what you want to achieve. Choose by focus — people, process, or product — or by context, such as how the last sprint went and how experienced the team is. A simple format like the Agile or Start/Stop/Continue retrospective suits new teams; themed or playful templates help re-energize teams that have fallen into autopilot. ### Should you use the same retrospective template every time? No. Changing the template regularly keeps the meeting fresh and surfaces different insights, because each format frames the sprint through a different lens. Reusing one template indefinitely invites "retro autopilot," where people give standard answers instead of considered ones. Rotating templates is one of the simplest ways to keep retrospectives engaging. --- # Running the AI collaboration retro URL: https://www.teamretro.com/guides/ai-agent-retrospectives/running-the-ai-collaboration-retro/ *At TeamRetro we're interested in every continuous-improvement cycle a team runs. AI-assisted work is a new area we've been thinking through via our retrospective lens; this guide shares where we've landed so far. Take it, adapt it, run it in whatever tool or ceremony you already have.* ## Part 1 — the guide ### Why this belongs in a team ceremony Somewhere on your team this month, an AI assistant spent forty minutes auditing a "broken" ad campaign that had been deliberately paused, because the brief didn't say so. The person running the session corrected it, shrugged, and moved on. If four colleagues hit versions of the same gap, that's hours of silent waste per month — and nobody knows, because each person absorbed it alone. That's the pattern with AI-session friction: it's chronic and minor, so it never triggers a postmortem, and it's ephemeral, so it evaporates when the session ends. Most teams can already *watch* it (around 90% instrument their agent traces), but far fewer turn it into fixes: only about 37–52% systematically evaluate what they capture ([LangChain, Jun 2026](https://www.langchain.com/state-of-agent-engineering)). The improvement loops that do exist are good, and this practice builds on all of them: `AGENTS.md` and context-file updates, memory systems, vendor self-improvement pipelines, error analysis on traces ([Husain & Shankar, evals FAQ](https://hamel.dev/blog/posts/evals-faq/)). Even the vendors reach for the retro word: OpenAI's Codex guidance reads *"when Codex makes the same mistake twice, ask it for a retrospective and update AGENTS.md"* ([best practices](https://learn.chatgpt.com/guides/best-practices)). But nearly all of these loops are solo: one person and their agent, or one platform and its fleet. What the team layer adds is **aggregation**: friction that's five shrugged-off minutes per person becomes a top team cost only in the aggregate view — and acting on it (rewrite the shared template, change the intake process, buy the tool) needs a decision ceiling no individual has. Rahul Garg's Feedback Flywheel names the venue, *"an agenda item in the existing sprint retrospective: what worked with AI this sprint?"* ([martinfowler.com](https://martinfowler.com/articles/reduce-friction-ai/feedback-flywheel.html)), and this guide is one way to run it. One honest concession up front: what this needs is a recurring, blameless, evidence-fed ceremony with the fix-owners in the room. For most teams that's the [retro](/retrospectives/), but a sprint planning slot, a monthly ops review, or a media team's account review can host it just as well. The retro, or your existing ceremony of equivalent shape. Worth knowing as a facilitator: Scrum.org approaches the same territory from the metrics side; their [guide to running the sprint retrospective when half your team is AI agents](https://www.scrum.org/resources/blog/how-run-sprint-retrospective-when-half-your-team-ai-agents) reframes the event as a data-driven review of agent performance (prompt rewrites, deviation rates, token burn). This guide takes the complementary path: root causes and fixes across the whole collaboration, with the agents contributing their own account of the work, filed via the [TeamRetro MCP server](/mcp/) if you use TeamRetro. Teams with heavy agent fleets may want elements of both. ### How the practice works, end to end 1. **Capture, per session.** At the end of each substantial AI-assisted session, the agent writes a [short structured entry](/guides/ai-agent-retrospectives/ai-friction-records/): what went well, what dragged (each item labeled with a root cause and a proposed fix), what it guessed, and the single highest-leverage fix. One file per entry, in a shared log. 2. **Synthesize, after ~5 entries.** Before the ceremony, the agent condenses the log into a one-page brief: recurring themes ranked by frequency × cost, a root-cause distribution, a check on whether past fixes were adopted, and the top three recommended actions. 3. **Decide, in 15 minutes.** The brief is one agenda item in your existing retro, not a new meeting. The team triages: keep or kill each friction, confirm where each fix should land, assign owners to the top actions. Next cycle's brief reports whether the friction actually dropped. The capture and synthesis steps are implemented as open-source agent skills in our [teamretro-skills repo](https://github.com/TeamRetroHQ/teamretro-skills) if you want a running start. The agent reports ungated: an agent that needs permission to record friction [under-reports](/blog/gather-feedback-from-ai-agents/), and human corrections after the fact are additive signal, not a checkpoint the loop waits on. Judgment stays with the team, and not as a courtesy: the fixes land in budgets, documents, processes, and tools that people own and answer for. The agent brings evidence and drafts; the room decides. ### What a good entry looks like Here's a real-shaped example, deliberately not a coding session: ```markdown # 2026-07-16 — Monthly ads account review **Session size:** ~25 turns, 1 deliverable **Outcome:** shipped ## Went well - Exec summary shipped in one pass; the account structure doc from last month held up ## Friction - **[missing-context]** The brief didn't say the French campaigns were deliberately paused for Q3; ~40 min (est.) auditing a "broken" campaign that was fine. → Fix (altitude: process): add campaign-status flags to the monthly brief template ## Guesses made - Assumed the target CPA unchanged from June — unverified ## Do this first Campaign-status flags in the brief template — kills the largest single time sink this month. ``` Notice the discipline. Every friction item cites a moment and a cost (soft estimates marked `(est.)`), carries exactly one root-cause label from a small fixed vocabulary (labels like `ambiguous-instruction`, `missing-context`, `missing-documentation`, `missing-access-or-tool`, `agent-error`, or `work-material-friction`, where the material itself was the drag: a tangled campaign structure, a legacy spreadsheet, a module nobody wants to touch — always with the concrete material named), and ends with a ticket-sized fix that names its [**altitude**](/guides/ai-agent-retrospectives/where-should-the-fix-land/): does this fix belong in a private memory note, a procedure, the environment, the docs, the work material itself, the process, or upstream with a vendor? Fixed labels are what make entries comparable across people and sessions; "the docs were confusing" can't be aggregated, but eight `missing-documentation` entries can. Vague is the failure mode; "nothing notable" is a valid entry. A good **brief** is one page: themes with prevalence ("4 of 9 sessions") and dated examples, a plain statement of which root-cause group dominates (briefing, documentation, work material, tooling, or agent; that's where the team's attention should go), the adoption check on past suggestions, and three owner-assignable actions. It feeds the conversation; it doesn't replace it.
## Calculate your velocity
Run your own numbers: the points your team completed in each recent sprint, and — if you want the forecast — the points left in the backlog.
Read the range, not just the average. Your next sprint lands somewhere between your best recent sprint and your worst, so a forecast quoted as a single number carries more certainty than the data does. "Eight to ten sprints" is an honest answer; "8.7 sprints" is false precision wearing a decimal point.
## How many story points per sprint?
Searching "how many story points per sprint" is a category error. There's no industry number, no "good" number, no per-developer-per-day rate. Velocity is the team's measured throughput, and the only useful version is the rolling average over the team's own last few sprints. Fifteen points, forty points, a hundred points — none is right or wrong. They're calibrated to the team's reference story.
Anthropic Claude Haiku 4.x | | Automated grouping, group title suggestions | AWS Bedrock | Anthropic Claude Sonnet 4.x
Anthropic Claude Haiku 4.x | | Action suggestions | AWS Bedrock | Anthropic Claude Sonnet 4.x | | Search embeddings | AWS Bedrock | Amazon Titan Text Embeddings v2
Cohere Embed Model 3 | | AI image generation — cover and topic images | fal – Features & Labels, Inc. | Image-generation models hosted on fal.ai | *Learn more about our [AI-powered features](https://help.teamretro.com/article/445-ai-features). Learn more about our [sub-processors](/security/subprocessors/).* ## Our principles We are committed to responsible AI governance. Our AI use must: - Be fair, transparent, and accountable. - Avoid bias and discrimination. - Use data ethically and lawfully, with appropriate consent. - Be explainable to users, with clear documentation of decision-making processes. - Comply with our SOC 2 Type 2, GDPR and other privacy rules. ## Our commitment to safety Principles are important, but so are practices. To make sure our AI stays aligned with your needs, we utilize AWS Bedrock Guardrails to actively monitor, moderate, and restrict AI use where appropriate. These include, but are not limited to: - Input prompts and user content are monitored by TeamRetro to reduce the risk of inappropriate or unsafe AI results. - Output from AI features is automatically moderated to prevent unwanted or potentially harmful responses. - AI features in TeamRetro are configured to avoid generating content related to: - - Medical information or health advice. - Self-harm or mental health diagnoses. - Sexually explicit material. - Political topics, including commentary on elections or political figures. ## AI regulation and the EU AI Act TeamRetro does not develop or train AI models, so the conformity assessments and conformance testing the EU AI Act requires of model providers do not apply to us. The models behind our features are built and operated by our providers — OpenAI, Anthropic and Amazon (via AWS Bedrock), Cohere, and fal.ai — who carry the model-level obligations, including those for general-purpose AI models. Our own use of AI is assistive. Features like summaries, suggested groupings, and action suggestions support your team’s discussion — a person always reviews the output and decides what to keep. TeamRetro’s AI features do not make automated decisions about individuals, and based on our assessment they are not high-risk AI systems under the EU AI Act, so no conformity assessment is required for them either. We monitor the EU AI Act and related regulation as obligations come into force, and we will update this page if our position changes. ## Reporting and feedback Responsible AI is not a one-time promise; it’s an ongoing journey. We continuously review, refine, and update our practices as technology evolves, ensuring our solutions remain aligned with the highest ethical standards. If you encounter inappropriate, inaccurate, or unexpected AI content, or believe a prompt or output was incorrectly flagged, please contact our support team so we can investigate at [info@teamretro.com](mailto:info@teamretro.com). ## Frequently asked questions --- # Responsible Disclosure URL: https://www.teamretro.com/security/responsible-disclosure/ ## Responsible Disclosure ## Our customers trust us to keep their data secure and confidential. We take security seriously and work constantly to ensure that trust is well-founded. Have something to report? Please reach out to us at security@teamretro.com ## Responsible disclosure We encourage everyone that practices responsible disclosure and complies with our policies and terms of service to participate in our vulnerability disclosure program. Please avoid automated testing and only perform security testing with your own data. Please do not disclose any information regarding the vulnerabilities until we fix them. We may, at our sole discretion, offer recognition for high-quality, impactful reports that demonstrate a genuine security risk. You can report vulnerabilities by contacting [security@teamretro.com](mailto:security@teamretro.com). Please include a proof of concept. We will respond as quickly as possible to your submission and won’t take legal actions if you follow the rules. ***Coverage:*** - secure.teamretro.com ***Exclusions:*** - \*.eu.teamretro.com - ww1.teamretro.com - ww2.teamretro.com - ww3.teamretro.com - www.teamretro.com - at.teamretro.com - help.teamretro.com - feedback.teamretro.com - mail.teamretro.com - status.teamretro.com - track.teamretro.com - games.teamretro.com - icebreaker.teamretro.com - ideas.teamretro.com - planning-poker.teamretro.com - www-assets.teamretro.com ***Accepted vulnerabilities are the following:*** - Cross-Site Scripting (XSS) - Open redirect - Cross-site Request Forgery (CSRF) - Command/File/URL inclusion - Authentication issues - Code execution - Code or database injections ***This vulnerability disclosure program does NOT include:*** - Account/email enumerations - Denial of Service (DoS) - Attacks that could harm the reliability/integrity of our business - Spam attacks - Clickjacking on pages without authentication and/or sensitive state changes - Mixed content warnings - Lack of DNSSEC - Content spoofing / text injection - Timing attacks - Social engineering - Phishing - Insecure cookies for non-sensitive cookies or 3rd party cookies - Vulnerabilities requiring exceedingly unlikely user interaction - Exploits that require physical access to a user’s machine - Missing security headers which do not lead directly to a vulnerability - Missing best practices (we require evidence of a security vulnerability) - Reports generated by automated scanners without demonstrated impact - Missing security headers without a demonstrated exploit - SSL/TLS configuration issues without a demonstrated exploit - Missing rate limiting - Self-XSS (requires victim to paste code into their own console) - Login/logout CSRF - Vulnerabilities requiring outdated or unsupported browsers - Duplicate reports or previously known issues ### Submission requirements ***All reports must include the following or they will not be reviewed:*** - Affected URL or endpoint - Step-by-step reproduction instructions - Proof of concept (screenshots, video, or code) - Description of the security impact Automated scanning is not permitted without prior written approval. All testing must be performed manually and all vulnerability disclosure program details must remain confidential. #### Our thanks go to the following security researchers: - Abin Joseph - daniel\_v - Ananda Dhakal - Luiz Viana - Aman Gupta - Vipul Sahu - Hsu Myat Noe - Tomasz Bartoszewski - Harry Gertos - Sathwik Veeramaneni - Yassine Nafiai - SIDN SOC - Burhan Chhotaudepur - Faizan Nehal - Aaditya Kumar Sharma - Syed Ahsan Raza - Mohammed Eldawody - Yaniv Shoshani - Lucas Werkmeister - Ankit Rathva --- # TeamRetro Subprocessors URL: https://www.teamretro.com/security/subprocessors/ ## TeamRetro third-party subprocessors TeamRetro uses the third-party entities in the table below to perform limited activities in connection with the provision of its services. ## TeamRetro core product subprocessors Subprocessors in this section apply to the use of the TeamRetro product. | Entity | Task | Entity Country | Processing Country | More Info | | :-- | :-- | :-- | :-- | :-- | | [Amazon Web Services](https://www.aboutamazon.eu/) 38 Avenue John F. Kennedy, L-1855, Luxembourg | **TeamRetro EU Region** Hosting services for the core TeamRetro application EU environment (VPC, ALB, WAF, ECR, ECS, RDS, Elasticache, Backup), content storage and distribution (S3, CloudFront), infrastructure security and management (CloudWatch, CloudTrail, GuardDuty, SecurityHub). | Luxembourg | Germany | [Privacy](https://aws.amazon.com/privacy/) [Security](https://aws.amazon.com/security/) [Status](http://status.aws.amazon.com/) | | [Amazon Web Services](https://aws.amazon.com/) 410 Terry Ave N, Seattle, Washington 98019 United States | **TeamRetro US Region** Hosting services for the core TeamRetro application (VPC, ALB, WAF, ECR, ECS, RDS, Elasticache, Backup), content storage and distribution (S3, CloudFront), infrastructure security and management (CloudWatch, CloudTrail, GuardDuty, SecurityHub). | United States | United States | [Privacy](https://aws.amazon.com/privacy/) [Security](https://aws.amazon.com/security/) [Status](http://status.aws.amazon.com/) | | [Ably Realtime Ltd.](https://ably.com/) Scale Space, 58 Wood Lane London W12 7RZ United Kingdom | **TeamRetro EU Region** Real-time data synchronization via Websockets | United Kingdom | Cross-border (Ireland, Germany, United Kingdom, France, Sweden) | [Privacy](https://ably.com/privacy) [Security](https://ably.com/security-and-compliance) [Status](https://status.ably.io/) | | [Ably Realtime, Inc.](https://ably.com/) 2100 Geng Road, Suite 210 Palo Alto, CA 94303 United States | **TeamRetro US Region** Real-time data synchronization via Websockets | United States | United States | [Privacy](https://ably.com/privacy) [Security](https://ably.com/security-and-compliance) [Status](https://status.ably.io/) | | [Twilio Inc.](https://www.twilio.com/en-us) 101 Spear St 5th floor, San Francisco, CA 94105, United States | Processes and delivers transactional emails (SendGrid) | United States | United States | [Privacy](https://sendgrid.com/privacy/) [Security](https://sendgrid.com/security/) [Status](http://status.sendgrid.com/) | | [PayPal](https://www.paypal.com/) 2211 N First St, San Jose, CA 95131, United States | Payment processing for online self-subscriptions (Braintree Payments). | United States | United States | [Privacy](https://www.paypal.com/us/legalhub/paypal/privacy-full) [Security](https://www.paypal.com/us/security) [Status](https://www.paypal-status.com/product/production) | | [Rollbar, Inc.](https://rollbar.com/) 548 Market St #60587, San Francisco, CA 94104, United States | Error logging | United States | United States | [Privacy](https://docs.rollbar.com/docs/privacy-policy) [Security](https://docs.rollbar.com/docs/security) [Status](https://status.rollbar.com/) | | [Better Stack, Inc.](https://betterstack.com/) Rybna 716/24, 11000 Prague, Czech Republic | **TeamRetro EU Region** Application logging (Better Logs) and application uptime monitoring (Better Uptime). | Czech Republic | Germany | [Privacy](https://betterstacks.com/privacy) [Security](https://betterstack.com/security) [Status](https://status.betterstack.com/) | | [Better Stack, Inc.](https://betterstack.com/) 9450 SW Gemini Drive PMB 98229 Beaverton, Oregon 97008-7105 | **TeamRetro US Region** Application logging (Better Logs) and application uptime monitoring (Better Uptime). | United States | United States | [Privacy](https://betterstacks.com/privacy) [Security](https://betterstack.com/security) [Status](https://status.betterstack.com/) | | [Datadog, Inc.](https://www.datadoghq.com/) 620 8th Ave 45th Floor, New York Times Bldg, New York, NY 10018, USA | Application monitoring, telemetry, and metric services. | United States | United States | [Privacy](https://www.datadoghq.com/legal/privacy/) [Security](https://docs.datadoghq.com/security/) [Status](https://status.datadoghq.com/) | ## TeamRetro AI synthesis subprocessors Subprocessors in this section are optionally engaged when you make use of TeamRetro’s AI synthesis features such as suggested grouping, retrospective and health check meeting summaries and health check response summaries. AI Synthesis features can be globally disabled at the account level at any time. | Entity | Task | Entity Country | Processing Country | More Info | | :-- | :-- | :-- | :-- | :-- | | [Amazon Web Services](https://www.aboutamazon.eu/) 38 Avenue John F. Kennedy, L-1855, Luxembourg | **TeamRetro EU Region** Optional suggested grouping, retrospective and health check meeting summaries and health check response summaries powered by [AWS Bedrock](https://aws.amazon.com/bedrock/?gclid=Cj0KCQjw8pKxBhD_ARIsAPrG45kPMSUGI5Jexo7YnQ3ma92h2Lql3xApMg2rKESuKct-dwe-LOWKD70aAoyOEALw_wcB&trk=1325fdf1-f38b-4c89-8bf9-dc39eeb87ff8&sc_channel=ps&ef_id=Cj0KCQjw8pKxBhD_ARIsAPrG45kPMSUGI5Jexo7YnQ3ma92h2Lql3xApMg2rKESuKct-dwe-LOWKD70aAoyOEALw_wcB:G:s&s_kwcid=AL!4422!3!692062112141!e!!g!!aws%20bedrock!21054970946!157173566817). *AWS Bedrock does not log, store, or use your content for any other purposes.* | Luxembourg | France, Germany, Ireland | [Privacy](https://aws.amazon.com/privacy/) [Security](https://aws.amazon.com/security/) [Status](http://status.aws.amazon.com/) | | [Amazon Web Services](https://aws.amazon.com/) 410 Terry Ave N, Seattle, Washington 98019 United States | **TeamRetro US Region** Optional suggested grouping, retrospective and health check meeting summaries and health check response summaries powered by [AWS Bedrock](https://aws.amazon.com/bedrock/?gclid=Cj0KCQjw8pKxBhD_ARIsAPrG45kPMSUGI5Jexo7YnQ3ma92h2Lql3xApMg2rKESuKct-dwe-LOWKD70aAoyOEALw_wcB&trk=1325fdf1-f38b-4c89-8bf9-dc39eeb87ff8&sc_channel=ps&ef_id=Cj0KCQjw8pKxBhD_ARIsAPrG45kPMSUGI5Jexo7YnQ3ma92h2Lql3xApMg2rKESuKct-dwe-LOWKD70aAoyOEALw_wcB:G:s&s_kwcid=AL!4422!3!692062112141!e!!g!!aws%20bedrock!21054970946!157173566817). *AWS Bedrock does not log, store, or use your content for any other purposes.* | United States | United States | [Privacy](https://aws.amazon.com/privacy/) [Security](https://aws.amazon.com/security/) [Status](http://status.aws.amazon.com/) | ## TeamRetro AI content generation subprocessors Subprocessors in this section may be engaged when you make use of TeamRetro’s Generative AI features such as AI-generated retrospective templates, health models and icebreaker questions. No PII or commercially sensitive information shared with these subprocessors. | Entity | Task | Entity Country | Processing Country | More Info | | :-- | :-- | :-- | :-- | :-- | | [OpenAI LLC](https://openai.com/) Pioneer building 3180 18th St, San Francisco, CA 94110, USA | OpenAI generative AI is used for AI content generation (retrospective templates, health models, icebreaker questions) | United States | United States | [Privacy](https://openai.com/policies/row-privacy-policy/) [Security](https://openai.com/security-and-privacy/) [Status](https://status.openai.com/) | ## TeamRetro AI image generation subprocessors Subprocessors in this section power TeamRetro’s AI image generation, such as cover and topic images. No PII or commercially sensitive information is shared with these subprocessors. | Entity | Task | Entity Country | Processing Country | More Info | | :-- | :-- | :-- | :-- | :-- | | [fal – Features & Labels, Inc.](http://fal.ai) 2261 Market St., Suite 10467, San Francisco, CA 94114 | fal.ai generative AI is used for AI image generation | United States | United States | [Privacy](https://fal.ai/legal/privacy-policy) [Security](https://trust.fal.ai/) [Status](https://status.fal.ai) | ## GroupMap Technology Pty Ltd business operations subprocessors Subprocessors included in this section apply when you engage with GroupMap Technology Pty Ltd as an organization and purchase or use any of our offerings. | Entity | Task | Entity Country | Processing Country | More Info | | :-- | :-- | :-- | :-- | :-- | | [Google LLC](https://workspace.google.com/intl/en_au/) 1600 Amphitheater Parkway, Mountain View, California, 94043, USA | Google Workspace processes email messages. Customer content may be processed by Google Workspace but only if customer chooses to provide customer content in email interactions with GroupMap staff. | United States | United States | [Privacy](https://policies.google.com/privacy) [Security](https://safety.google/security-privacy/) [Status](https://www.google.com/appsstatus/dashboard/) | | [Salesforce, Inc.](https://www.salesforce.com/ap/?ir=1) ([Slack](https://slack.com/)) 415 Mission Street, San Francisco, California, USA | Internal team communication tool, which may include customer support or technical incident response information. | United States | United States | [Privacy](https://slack.com/trust/privacy/privacy-policy) [Security](https://slack.com/security-practices) [Status](https://slack-status.com/) | | [Xero](https://www.xero.com/au/) 19–23 Taranaki Street Te Aro, Wellington 6011 New Zealand | Enterprise invoicing and financial accounting. | New Zealand | United States | [Privacy](https://www.xero.com/legal/privacy/) [Security](https://www.xero.com/security/) [Status](https://status.xero.com/) | | [PayPal](https://www.paypal.com/) 2211 N First St, San Jose, CA 95131, United States | Enterprise invoice payment processing | United States | United States | [Privacy](https://www.paypal.com/us/legalhub/paypal/privacy-full) [Security](https://www.paypal.com/us/security) [Status](https://www.paypal-status.com/product/production) | | [Skcript Technologies Pvt. Ltd](https://www.skcript.com/) ([FeatureOS](https://featureos.app/)) L3, VR Mall, The Hive, Madras House, near Madras House, Anna Nagar, Chennai, Tamil Nadu 600040, India | Feature suggestions | India | United States | [Privacy](https://featureos.app/legal/privacy) [Security](https://featureos.app/legal/security) [Status](https://status.featureos.app/) | | [HelpScout](https://www.helpscout.com) Boston, Massachusetts, United States | Sales & support ticketing system | United States | United States | [Privacy](https://www.helpscout.com/company/legal/privacy/) [Security](https://www.helpscout.com/company/legal/security/) [Status](https://status.helpscout.com/) | | [Linear Orbit, Inc (Linear)](https://linear.app) 440 Barranca Ave #4242, Covina, CA 91723, United States | Feature backlog, task and client management | United States | United States | [Privacy](https://linear.app/privacy) [Security](https://linear.app/security) [Status](https://linearstatus.com/) | | [GitHub, Inc.](https://github.com/) 88 Colin P Kelly Jr St, San Francisco, CA 94107, United States | Source code management and CI/CD | United States | United States | [Privacy](https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement) [Security](https://github.com/security) [Status](https://www.githubstatus.com/) | | [Kinsta, Inc.](https://kinsta.com/) 8605 Santa Monica Blvd #92581, West Hollywood, CA 90069, United States | Marketing website hosting (teamretro.com, groupmap.com) | United States | Not a data subprocessor — no customer data processed | [Privacy](https://kinsta.com/legal/privacy-policy/) [Security](https://trust.kinsta.com/) [Status](https://status.kinsta.com/) | --- # Cookie Policy URL: https://www.teamretro.com/cookies/ This is the Cookie Policy for TeamRetro, accessible from teamretro.com ## 1. What are cookies As is common practice with almost all websites and software-as-a-service products, TeamRetro uses cookies, which are tiny files that are downloaded to your computer, to improve your experience. This page describes what information they gather, how we use it and why we sometimes need to store these cookies. We will also share how you can prevent these cookies from being stored however this may downgrade or ‘break’ certain elements of TeamRetro functionality. For more general information on cookies see the Wikipedia article on [HTTP Cookies](https://en.wikipedia.org/wiki/HTTP_cookie). ## 2. How we use cookies We use cookies for a variety of reasons detailed below. Unfortunately in most cases there are no industry standard options for disabling cookies without completely disabling the functionality and features they add to this site. It is recommended that you leave on all cookies if you are not sure whether you need them or not in case they are used to provide a service that you use. ## 3. Disabling cookies You can prevent the setting of cookies by adjusting the settings on your browser (see your browser help for how to do this). Be aware that disabling cookies will affect the functionality of this and many other websites that you visit. Disabling cookies will usually result in also disabling certain functionality and features of this site. Therefore it is recommended that you do not disable cookies. ## 4. The cookies we set ### Account related cookies If you create an account with us then we will use cookies for the management of the signup process and general administration. | **Cookie Name** | **Description** | **Retention** | | :-- | :-- | :-- | | teamretro-production.defaultRegion | Captures the TeamRetro region the user has most recently signed into, United States or European Union. | 1000 days | ### Login related cookies We use cookies when you are logged in so that we can remember this fact. This prevents you from having to log in every single time you visit a new page. These cookies are typically removed or cleared when you log out to ensure that you can only access restricted features and areas when logged in. | **Cookie Name** | **Description** | **Retention** | | :-- | :-- | :-- | | teamretro-us-production.session teamretro-eu-production.session | A random token identifying the active user login session. | 16 hours | ### Site preferences cookies In order to provide you with a great experience on this site, we provide the functionality to set your preferences for how this site runs when you use it. In order to remember your preferences we need to set cookies so that this information can be called whenever you interact with a page that is affected by your preferences. ### Third Party Cookies We do not use any third party tracking cookies. ## 5. More information Hopefully that has clarified things for you and as was previously mentioned if there is something that you aren’t sure whether you need or not it’s usually safer to leave cookies enabled in case it does interact with one of the features you use on our site. However if you are still looking for more information then you can contact us at [privacy@teamretro.com](mailto:privacy@teamretro.com) --- # GDPR Compliance URL: https://www.teamretro.com/gdpr/
East Victoria Park WA 6101
Australia #### Email [info@teamretro.com](mailto:info@teamretro.com) #### Website [www.teamretro.com](/) ## Other ways to get help Already using TeamRetro and need a hand? The [TeamRetro help center](https://help.teamretro.com) covers setup, integrations, billing, and security, and is the fastest route to an answer for most account questions. Weighing TeamRetro up for your team and want to see it in action? You can [book a demo](https://calendly.com/groupmap/teamretro-demo) and a member of our team will walk you through retrospectives, team health checks, and agile estimation, and answer anything specific to how your team works. For procurement, security reviews, or rolling TeamRetro out across several teams, the [rollout checklist](/roll-out-checklist/) walks through plans, onboarding, and the documentation IT usually asks for — and you're welcome to email [info@teamretro.com](mailto:info@teamretro.com) directly. --- # Enterprise-ready tool for agile teams URL: https://www.teamretro.com/enterprise/ {/* Role icons: inline SVG (?raw) so `fill="currentColor"` is recolored from var(--marker). */} {/* Product screenshot (the brand PageHeader above carries the H1 + lead + the email-capture/Request-a-demo hero CTA via heroEmailCapture). */} {/* Trusted-by logo wall — the shared customer marquee. */} ## Cross-team reporting & insights Get organization-wide clarity and uncover trends, spot risks, and drive strategic improvements. ### Track key metrics and actions Get perspective from meeting cadence to tracking actions. ### Boost productivity with TeamRetro AI Let AI suggest themes, actions, and meeting summaries. ### Uncover recurring challenges Explore shared themes and blockers to focus on what matters most. ### Monitor sentiment trends Spot early signs of disengagement or misalignment. ### Visualize team health Monitor team happiness, engagement and maturity. ### Measure ROTI on retros Give feedback to boost meeting outcomes and decision quality. ## Collaborate at scale with smart role management ### Guest Access ### Observer Role ### Facilitator Only Role ### Role-Based Permissions ### No Extra Seats Needed {/* Support-team avatars centred above the heading (the live dark support band). */} ## Enterprise support that has your back With TeamRetro, you get more than a platform. You receive dedicated support tailored to your organization. {/* A checkmark list (matching live's dark support band); prose text reads white on the dark tint — Card's own surface would render dark-on-dark and be unreadable. */}
- Enterprise Agreements and SLA
- DPA (Data Processing Agreements)
- Custom Onboarding and Roll Out
- Security Questionnaires
- Dedicated Account Manager
- Vendor Onboarding and Purchase Orders
- Volume-Based Pricing
- DPA (Data Processing Agreements)
- Custom Onboarding and Roll Out
- Multi-Year Discounts
- Multiple Currency Options
- Vendor Onboarding and Purchase Orders
| Feature area | Other tools | |
|---|---|---|
| Security | SOC 2 Type 2, GDPR Compliant, SSO, SCIM, IP whitelisting | Basic security, limited compliance |
| Insights and analytics | Key agile metrics, team sentiment, action tracking, word clouds, heat maps | Manual collation or tagging, limited insights or drill down |
| Flexibility | Customizable templates and workflows at team and organization level | Limited workflow customization |
| Facilitation tools | Guided facilitation, ice breakers, check in / check out questions, live reactions, presentation mode and quick polling | Limited or restrictive workflow and facilitation tools |
| AI capability | Inbuilt, context driven AI capability to boost productivity | No, or limited AI capability |
| Team health checks | Ready to go survey templates with trend history and radars | Basic polling |
At Big Give, small means mighty. Big Give is the UK's largest match funding platform, helping thousands of UK-registered charities…
Client Stories How Culture Amp uses TeamRetro to unify agile feedback and boost visibilityAt Culture Amp, building a better world of work starts from within. Culture Amp is a leading employee experience platform…
Client Stories Helping nonprofits thrive through agile grant writingBeth Archer wears two hats at DH Leonard Consulting & Grant Writing Services, LLC — as both a Registered Scrum Master and grant writer…
{/* Closing band: the enterprise overview deck + the "start scaling" CTA, merged into one brand section (the live layout — previously two stacked sections that read as broken). */} ## Start scaling best practices across your organization Security, scale, and smarter collaboration tailored for enterprise teams. Want the full picture? Talk with our team for a guided overview of TeamRetro for enterprise. Request a demo Talk with us --- # Improve your sprint planning with agile estimation poker URL: https://www.teamretro.com/estimations/ ## Align fast with clearer estimates Say goodbye to manual calculations and messy tallies. TeamRetro's agile estimation helps teams find common ground — fast. It's a sprint planning tool built around how agile teams really estimate: run story point estimation as a team, use planning poker so every vote stays independent, and land on a number everyone stands behind — without spreadsheets or anchoring on the first guess. ### Create alignment Get everyone on the same page before work starts — with structured rounds and reveals. ### Build delivery confidence Turn "I think" into shared clarity — so your plan matches reality more often. ### Reduce uncertainty Surface assumptions, risks, and unknowns early — so you avoid surprises mid-sprint. ## Start estimating and agile planning in minutes Transform your sprint planning and backlog grooming sessions with guided facilitation, anonymous estimates and easy team engagement. ### Create a clean, focused list easily Pull items from retros, health checks, or your backlog — or import straight from TeamRetro, Jira, Azure, GitHub, or Linear — and keep everything in sync with your source of truth. ### Invite your team into a safe, secure space Bring everyone into the same agile estimation flow — instantly. Everyone sees the same estimation items in real time. Flexible anonymity options let you build safety or accountability. ### Discuss each item to gain more data Ensure everyone understands the requirements, scope, and acceptance criteria. Run polls, give kudos and use live reactions for real-time feedback. Keep discussions focused by parking items or creating follow-up actions and team agreements. ### Estimate privately — free from bias Cards remain hidden until everyone is done to prevent anchoring bias. Choose from a library of estimation decks that fit your team's style or life cycle. ### Reveal results and agree on a final score View all estimates at once to spot alignment or gaps. Surface risks, clarify requirements, and uncover assumptions — then re-vote to reach consensus and lock in the final story points together. ### Share results and sync with workflow tools Get a complete summary of final estimates for sprint planning and backlog prioritization. Sync estimates to Jira, Linear, GitHub, and your project tools, and export meeting notes to Confluence, Slack, and more — so everyone stays aligned. ### Engage more with the team Throw in an icebreaker to kick things off, a check-out question to get feedback on delivery confidence, or run quick polls. ## Choose the estimation deck that drives better planning outcomes Select from our library of proven estimation decks. ### Scrum The classic scrum deck with story points including half values, perfect for standard agile estimation. ### Fibonacci Based on the fibonacci sequence, ideal for highlighting the uncertainty in larger estimates. ### Sequential Simple sequential numbers for teams who prefer straightforward linear estimation. ### Half card Granular half-point increments for teams that need more precision in their estimates. ### Power of two Exponential growth pattern, great for technical teams estimating complexity and effort. ### Modified fibonacci A refined fibonacci deck with smoother jumps, great for teams balancing speed, clarity, and estimation confidence. ### Five fingers An easy-to-use deck based on the five fingers on your hand for when teams want simplicity. ### T-shirt sizes Relative sizing with familiar clothing sizes, perfect for high-level backlog estimation. *…or build your own.* ### Animal estimation deck Set a deck up once and reuse it across all your sessions. ## Planning poker for Jira If your backlog lives in Jira, you don't have to choose between estimating well and keeping Jira up to date. Pull the issues you're planning straight from Jira into a TeamRetro estimation session, run planning poker so every vote stays independent, and write the agreed story points back to the Jira issues — no copy-paste, no second spreadsheet. The estimation itself stays a team conversation rather than a field one person fills in later: everyone votes privately, the reveal happens together, and where votes split you talk through why before the number is locked. Jira ends up holding the point the team actually agreed on, with the reasoning still fresh. See the [Jira integration](/integrations/jira/) for setup, or [try planning poker free](/free-planning-poker-for-agile-teams/) in your browser first — no account needed. ## Frequently asked questions New to estimating as a team? Our [agile estimation guide](/guides/agile-estimation-guide/) works through story points, planning poker, and velocity in depth, and our roundup of the [best planning poker tools](/blog/best-planning-poker-tools-for-agile-teams/) compares the options — or [try planning poker free](/free-planning-poker-for-agile-teams/) in your browser, no sign-up needed. --- # Free Planning Poker by TeamRetro URL: https://www.teamretro.com/free-planning-poker-for-agile-teams/ ## Built with care by TeamRetro TeamRetro helps scrum masters, product owners, and development teams run better retrospectives, health checks, and estimations — with ready-to-use templates, action tracking, and continuous improvement built in for remote, hybrid, and in-person teams. ## Simple, easy estimations for better sprint planning Keep everyone aligned, reduce anchoring bias, and get to consensus faster. ### Add items for discussion Discuss the items to be estimated and let people ask questions before estimating. ### Estimate items privately Each player selects a hidden value card. Cards stay hidden until revealed, so no one anchors on someone else's number. ### Reach a shared decision All cards are revealed with a tally and team average. Discuss, re-vote, or agree on a final estimate. ## Ready-to-go estimation card decks Choose the scale that works best for your team — classic Fibonacci, simple t-shirt sizing, or anything in between. ### Scrum ### Fibonacci ### Sequential ### Half card ### Power of two ### T-shirt size## Learn how to run better estimation sessions Planning poker is easy to start and surprisingly easy to get wrong. These free, practical guides — from the team behind TeamRetro — go deeper than the basics, written for the scrum masters and engineers who actually run the sessions:
The technique, where it came from, and when it's the wrong tool.
The facilitator's playbook: ground rules, the four phases of a round, ruthless time-boxing, and which card deck to use.
What story points really measure, and the points-to-hours trap that quietly breaks velocity.
Planning poker compared with t-shirt sizing, affinity mapping, and bucket sizing.
Real stories — login, payments, migrations — walked through the conversations they need.
The recurring ways sessions fall apart, and how to pull them back.
## When your team outgrows the free tool The free planning poker room is yours to use for as long as you like — no account, no limits on estimating together. When you want estimates to live alongside the rest of your team's work, [TeamRetro's estimation](/estimations/) brings it into one place: run your retrospectives, health checks, and estimation together, reuse your own decks, and sync final story points to Jira, Linear, and GitHub — with a record every session builds on.## Frequently asked questions Everything you need to know about planning poker. --- # Agile team health checks and radars URL: https://www.teamretro.com/health-checks/ ## Build high-performing teams TeamRetro is team health check software that shows how your team rates their performance and satisfaction across the dimensions that matter. Create your own health models or start from a template, then turn the results into a continuous improvement habit. New to running one? Our [team health check guide](/guides/team-health-check/) covers choosing dimensions, the questions to ask, and how to facilitate the session. ### Custom Health checks Create your own health models or use a template. ### Visualize team health Evaluate health dimensions over time. ### Find the gaps Address issues early and improve productivity. ### Create actions for change Propose and track actions that create happier teams. ## Team health check methods and formats Out of the box, TeamRetro has industry-based health checks to choose from — including the [Spotify squad health check model](/health-check-templates/squad-health-check/) ready to run. Customize an existing model or use our AI-generated suggestions to create the ideal fit for your team. New to the practice? Our [team health check guide](/guides/team-health-check/) covers questions, cadence, and what to do with the scores. ### Numeric ### Happiness Scale ### Matrix Model ### Likert Scale ## Run better team health checks Survey the team and capture comments with ease, free from bias. Run open surveys or facilitate in-person meetings. Device friendly and no downloads required. ## Data-driven discussions Real-time results plot every dimension on a team radar, so you see the overall picture and how it moves over time at a glance. Prioritize discussions by focusing on what is most important to you. Dive into individual results or statistics like standard deviation, range and mean. ## Present, discuss and create actions Use presentation mode to sync screens and facilitate discussions. Propose and create actions that drive change. ## Review your action plan Assign due dates and owners and check things off. Actions are tracked from meeting to meeting with gentle reminders when things are due. ## Create summaries in seconds Generate summaries of comments for each health dimension and the overall health check, ready to share. ## Go further with maturity models Organize health dimensions into categories to reveal deeper insights across your agile journey. {/* Live links to the dedicated feature page /health-checks/agile-maturity-assessment/. That page (hero + 13 templates + social proof) isn't migrated yet, so this points at the on-topic blog post as a stand-in. When the feature page is migrated, repoint this CTA there and add a redirect for /health-checks/agile-maturity-assessment/. */} Learn more about maturity models ## Enterprise insights Managing multiple teams? Get cross-team reporting across your portfolio with our enterprise plan, and a sense of what teams are talking about. ### Word clouds Get a sense of what the teams are talking about. ### Timelines See how individual health dimensions move over time. See all health check features Browse health check templates ## You're in good company --- # Agile maturity assessment URL: https://www.teamretro.com/health-checks/agile-maturity-assessment/ ## Accelerate continuous improvement with agile maturity assessments Regular assessments are the foundation of continuous improvement. Here's why leading teams choose TeamRetro. ### Custom maturity models Create your own model or start from a proven template. ### Visualize trends over time Track maturity by dimension and spot patterns early. ### Find the highest-impact gaps Focus discussion on what will move outcomes, not vanity scores. ### Turn insights into actions Create accountable action items and follow through. ## Choose your agile maturity assessment template Select from our library of curated agile maturity models designed for each area of agile transformation. ### Agile delivery Planning & prioritization · Delivery flow · Team collaboration · Continuous feedback & improvement ### Agile teams Teamwork & collaboration · Agile ways of working · Planning & prioritization · Technical excellence & quality · Product delivery & customer value · Agile mindset, culture & continuous improvement ### Customer support Support operations · Customer success outcomes · Knowledge & enablement · Voice of customer (VOC) ### Data & analytics Data quality & governance · Reporting & insight · Infrastructure & accessibility · Experimentation & optimization · Data literacy & culture ### DevOps & continuous delivery CI/CD pipeline · Release & deployment · Reliability & operations · Security & compliance automation · Platform & infrastructure ### Engineering excellence Code quality & standards · Architecture & scalability · Technical debt management · Engineering collaboration & enablement ### Finance Financial planning & forecasting · Financial control & compliance · Cash flow & financial health ### Leadership Vision & strategic alignment · Communication & influence · Team development & support · Adaptability & innovation ### Marketing Strategy & positioning · Content & messaging · Campaign execution · Analytics & performance ### People operations Hiring & onboarding · Performance & growth · Culture & engagement · People operations excellence · Workforce planning & capability ### Product discovery Customer understanding · Experimentation & validation · Research practices · Lifecycle learning ### Product management Vision & strategy · Roadmapping & prioritization · Execution & collaboration · Data & customer insight · Market & stakeholder alignment ### Product strategy & customer value Product strategy & customer value · Discovery, innovation & experimentation · Engineering excellence & platform · Customer success & market performance · Data, measurement & enterprise operations ### SaaS growth & lifecycle Acquisition & activation · Engagement & retention · Monetization & billing · Analytics & lifecycle optimization · Growth strategy & market fit Browse health check templates Learn about health checks ## Run your agile maturity assessment in TeamRetro Run a quick assessment, gather honest input, and turn results into a shared improvement plan. ## Capture feedback privately Create categories and clearly defined dimensions. Design the model for your organization that fits best. ## Data-driven discussions Real-time, visual results show you the overall picture and trends over time. Prioritize discussions by focusing on what is most important to you. Dive into individual results or statistics like standard deviation, range and mean. ## Present, discuss and create actions Use presentation mode to sync screens and facilitate discussions. Propose and create actions that drive change. ## Review your action plan Assign due dates and owners and check things off. Actions are tracked from meeting to meeting with gentle reminders when things are due. ## Create summaries in seconds Generate summaries of comments for each health dimension and the overall health check which can be shared. ## Enterprise insights Standardize maturity models across teams, compare trends, and identify systemic blockers with cross-team reporting. ### Detect key topics and themes Get a sense of what the teams are talking about. ### Trends over time See how individual health dimensions move over time. ## You're in good company --- # All the features you need for insightful agile team health checks URL: https://www.teamretro.com/health-checks/features/ {/* Section illustrations. */} {/* Survey-style rating scales. */} {/* Feature-item images (one per item, mirroring the live page). */} {/* Capability icons (inline SVG ?raw → recolored from --marker). */} ## Create meaningful health checks Choose a template, customize your health check and define the dimensions that matter to your team. ### Dark mode ### Responsive ### 29 Languages ### 40+ health check models Used by top agile teams around the world. [Browse the template library →](/health-check-templates/) ### …plus AI-generated suggestions Pick a focus for your team and explore the possibilities. ## Choose from a range of survey styles Pick the rating style that fits your team and the question you're asking. ### Numeric Rate each dimension on a simple numeric scale. ### Happiness Scale Capture sentiment with an expressive happiness scale. ### Matrix Model Plot responses across two dimensions with a matrix. ### Likert Scale Measure agreement across a familiar Likert scale. ## Easily survey the team, free from bias Capture private ratings and comments without bias. Choose how people participate and customize your process for in-person or asynchronous surveys. ### Timer ### Music ### Team chat ### Team roles ### Fully anonymous meetings Choose between anonymous, aliases and named. ### …or give participants a choice Optional anonymity for individual comments or ideas. ### Customize your process Design your health check for in-person or asynchronous surveys. ### Run an icebreaker Create engagement from the very beginning. ### Check-in questions Focus the team before starting a survey. ### Review open actions Create accountability and recognize success. ### Whiteboards Sketch diagrams, map frameworks, and collaborate visually. ### Kudos & shoutouts Celebrate wins, big or small, with quick appreciation. ## Lead team discussions with visual radars Real-time radars make the overall picture clear, with customizable steps to guide the conversation. ### Easily sort results From most positive to most negative to most mixed responses. ### Get data happy Drill down into a range of statistics, or see individual results. ### Spot the trend Compare past trends and get AI summaries of comments. ### Capture team agreements Improve the way the team works and how they collaborate. ## Focus your conversation with Presentation Mode Sync screens and talk through one dimension at a time with live meeting feedback polls. ### Live reactions ### Quick poll ### Meeting feedback ### Deepen discussions Capture comments, reactions and replies on ratings. ### Parking lot Move items to the parking lot for follow up and keep things moving. ## Capture actions for continuous improvement Turn discussion into change — capture actions and AI summaries, and push them into the tools your team already uses. ### Use check-out questions Get quick feedback on your health checks. ### Generate summaries Easily create, publish and share with AI summaries. ### Integrate actions into your workflow Publish actions into your workflow tools at the touch of a button. ### Personal dashboard Each person can see their actions, open meetings and teams. ### Get suggested actions Harness the power of AI to suggest actions based on your meeting. ## Unlock team potential with data-driven insights See the bigger picture across health checks — meeting effectiveness, health dimension trends and your team's pulse over time. ### Return on time invested Assess how effective your meeting was. ### Timelines See how individual health dimensions shift over time. ### Track check-in/out trends Get the pulse of your team over time. ### Explore common themes Drill down into your word clouds. --- # Ask your AI assistant about your teams URL: https://www.teamretro.com/mcp/ ## Your retros, health checks and actions — now a question away TeamRetro speaks MCP, so the assistant you already work in can read your retros, summarize meetings, chase actions and keep working agreements current. No new dashboard to open, no context-switch. ## With TeamRetro MCP you can… ### See across every team Ask which teams need attention and get overdue retros, slipping health scores and stalled actions, already flagged. _Cross-team views are an [Enterprise](/enterprise/) capability._ ### Run your rituals from chat Spin up a retro, health check or planning poker session using the same template as last time — ready to join. ### Set up estimation from your backlog Hand the assistant this sprint's stories and have it open a planning poker session, ready for the team to vote. ### Never lose a follow-up Check what's on your plate, mark actions done and push due dates. Park an idea for the next retro the moment it comes up. ### Participate, not just observe Cast votes, rate health-check dimensions and leave feedback as yourself — every contribution respects your team's anonymity settings. ### Connect it to everything else Pull incidents from Slack into the retro, post summaries to your channel, cross-check actions against the Jira tickets they reference. ## Three prompts your team will run every week ### Summarize our last retro Runs `list_retrospectives` → `get_retrospective` and hands back the summary with owners and due dates. ### Start the next one Sets up the meeting, ready to share — no template hunting. ### Park it before it's lost Captures the topic as a parked item the moment it comes up in conversation. ## Prompts for every role ### Engineering managers & coaches Enterprise ### Scrum masters & facilitators ### Team members ### Working agreements ## Bring the signal in, push the outcomes out Your other tools hold the raw signal; TeamRetro is where the team acts on it. Pull incidents from Slack and park the themes. Turn a postmortem's commitments into actions with owners and due dates. Post Friday's retro summary to your channel, or open a Jira ticket for every open action — linked back to the meeting. ## Connect in about five minutes Add the TeamRetro MCP server in your assistant, sign in to TeamRetro in the browser, and start asking. The endpoint is the same everywhere: ```text https://mcp.teamretro.com/mcp ``` Or follow a step-by-step guide for your assistant: Working in Cursor, Windsurf, Zed or VS Code instead? Add a new MCP server with the URL above and the **Streamable HTTP** transport, then approve the OAuth sign-in. ## What it can do today ### Read - List teams and members - Summarize and compare retrospectives, health checks and estimation sessions - List and filter actions - Read working agreements - Track health-check trends over time ### Do - Start retros, health checks and planning poker sessions - Create and update actions, and park topics - Keep working agreements current - As yourself, vote and add health-check feedback Write actions respect your permissions and anonymity settings. ## Built on permissions you already trust You connect with **OAuth 2.1** — a browser sign-in, no API key to copy. The connection is **account-level** (one TeamRetro account per connection; add it more than once for multiple accounts). The assistant only ever sees what your account can see — on standard plans, the teams you belong to; **cross-team, organization-wide insights are an [Enterprise](/enterprise/) capability.** Revoke any connection at any time, and **organization admins can turn API & MCP access off for the whole account** whenever they need to. Requires a plan with API & MCP access. ## Questions, answered --- # Connect TeamRetro to ChatGPT URL: https://www.teamretro.com/mcp/chatgpt/ ## Bring your retros into ChatGPT Add the TeamRetro connector and ChatGPT can recap meetings, surface open actions and track team health — without leaving the chat. ## What you can do in ChatGPT ## Set up in ChatGPT OpenAI updates this surface often — if the menus look different, follow the [TeamRetro MCP help article](https://help.teamretro.com/article/535-mcp) for the current steps. You'll also need a TeamRetro plan with **API & MCP access**. ## First prompts to try ## Permissions & access ChatGPT only sees what your account can see. On standard plans that's the teams **you belong to**; **cross-team, organization-wide insights are an [Enterprise](/enterprise/) capability.** Every action respects your team's anonymity settings, and you can revoke the connector at any time. **Organization admins can turn API & MCP access off for the whole account** whenever they need to. ## Set up another assistant ## Questions, answered --- # Connect TeamRetro to Claude URL: https://www.teamretro.com/mcp/claude/ ## Run your retros from Claude Connect once and Claude can summarize meetings, chase actions and track team health — all from the chat you already work in. ## What you can do in Claude ## Set up in Claude You'll need a TeamRetro plan with **API & MCP access** and account-admin permission to approve the connected app. Connecting signs you in with OAuth 2.1 — there's no API key to copy. ## First prompts to try ## Permissions & access Claude only sees what your account can see. On standard plans that's the teams **you belong to**; **cross-team, organization-wide insights are an [Enterprise](/enterprise/) capability.** Anything Claude does on your behalf respects your team's anonymity settings, and you can revoke the connection at any time. **Organization admins can turn API & MCP access off for the whole account** whenever they need to. ## Set up another assistant ## Questions, answered --- # Connect TeamRetro to Microsoft Copilot URL: https://www.teamretro.com/mcp/copilot/ ## Ask Microsoft Copilot about your teams Connect the MCP server and Copilot can summarize retros, chase actions and track team health, right alongside the Microsoft 365 tools your team already uses. ## What you can do in Microsoft Copilot ## Set up in Microsoft Copilot You'll need a TeamRetro plan with **API & MCP access**. Connecting signs you in with OAuth 2.1 — there's no API key to copy. Microsoft updates this surface often; for the latest steps, see the [TeamRetro MCP help article](https://help.teamretro.com/article/535-mcp). ## First prompts to try ## Permissions & access Copilot only sees what your account can see. On standard plans that's the teams **you belong to**; **cross-team, organization-wide insights are an [Enterprise](/enterprise/) capability.** Every action respects your team's anonymity settings, and you can revoke the connection at any time. **Organization admins can turn API & MCP access off for the whole account** whenever they need to. ## Set up another assistant ## Questions, answered --- # Connect TeamRetro to Gemini URL: https://www.teamretro.com/mcp/gemini/ ## Ask Gemini about your teams — from the terminal Connect the MCP server to the Gemini CLI and ask about retros, health checks and actions straight from your terminal. ## What you can do in Gemini ## Set up with the Gemini CLI You'll need a TeamRetro plan with **API & MCP access**. Connecting signs you in with OAuth 2.1 — there's no API key to copy. For the latest steps, see the [TeamRetro MCP help article](https://help.teamretro.com/article/535-mcp). ## First prompts to try ## Permissions & access Gemini only sees what your account can see. On standard plans that's the teams **you belong to**; **cross-team, organization-wide insights are an [Enterprise](/enterprise/) capability.** Every action respects your team's anonymity settings, and you can revoke the connection at any time. **Organization admins can turn API & MCP access off for the whole account** whenever they need to. ## Set up another assistant ## Questions, answered --- # Paper Airplane Game URL: https://www.teamretro.com/paper-airplane-game/ ## A good game that explores continuous improvement and lean workflow The Paper Airplane game is a hands-on way to see lean workflow in action. Teams fold as many quality airplanes as they can, but only one person can fold at a time — so bottlenecks, waste and handovers show up fast, and the team improves the process between rounds. ### Learning goals Lean workflow, value stream mapping and continuous improvement. ### Time and format About 60 minutes, in person or virtual. ### What you need 4+ players and recycled or scrap paper. ## How the game works The objective is to fold as many airplanes as possible in a given timeframe, with one constraint: only one person can make a fold at a time. The team runs timed iterations with a short retrospective between each one, so they can spot waste and improve the flow round after round. ## Paper Airplane game rules - There are 3 minutes per iteration and 5 iterations. - In between, there is a 1-minute retrospective. - Every airplane must meet the same design and quality standard. - Only one person can fold at any one time; the rest of the team supports as needed. - The team agrees on the airplane design before they start, simple enough to fly about a meter. - After each round, count only the airplanes that meet the quality standard. ### How to facilitate 1. Gather the team and agree on a single airplane design and quality standard. 2. Start the timer and run the iteration, with one fold at a time. 3. Count the airplanes that meet the standard and record the score. 4. Hold a 1-minute retrospective so the team can adjust its approach and re-estimate. 5. Repeat for all five iterations. ## Debrief questions Run the debrief as a retrospective in TeamRetro so everyone can add their own perspective before you discuss as a group. - Where did you notice you were waiting (waste)? - How often was everyone engaged? - What changes were made, and how did they affect the production process? - What design aspects could make the flow slower or faster? - How would this game differ if played virtually versus in person? - How did quality controls play a part in this process? - Did you experience the concept of flow? - Which iteration stood out? - How did you feel working as a team? - Did leadership change during the iterations? - What did you learn from playing this game? ## Variations - Measure the time required to produce a set number of airplanes, rather than counting output in a fixed time. - Adjust the complexity of the airplane design up or down. - Introduce a quality check midway through, rather than only at the end. - Raise the difficulty — for example, require each plane to fly at least two meters. Capture the debrief as a retrospective in TeamRetro so lessons about waste and flow turn into tracked action items the team can follow through on. --- # Plans and pricing URL: https://www.teamretro.com/plans/ ## Our plans and features ## Frequently asked questions --- # Run agile retrospectives that lead to action URL: https://www.teamretro.com/retrospectives/ ### Save time, create value with more efficient, focused and worthwhile retros. ### Drive continuous improvement by getting buy in on actions and creating accountability. ### Build happier teams with easy, engaging and empowered meetings. ## Make every sprint count TeamRetro is an online retro tool that gives everyone a safe space to share ideas, foster collaboration and drive continuous improvement — face to face or fully remote. Run your sprint retro in retrospective software built for the job: create shared understanding, capture actions for positive change and improve outcomes. New to facilitating retros? Our [Scrum Master's retrospective guide](/guides/scrum-masters-retrospective-guide/) walks through the formats, stages and psychological safety that make them work. ### Create the perfect retro Ready to go templates you can adapt to your specific project, sprint or goals. ### Easy to use, anywhere Guided step by step facilitation keeps everyone on the same page and moving forward. ### Data driven insights Discover and share meeting summaries, key metrics, and track outcomes. ### Harness the power of AI Get template and icebreaker suggestions, automated grouping and meeting summaries (if enabled). ## Facilitate effective retros with confidence Start your retro off with an icebreaker or check-in question and boost the mood. Set the context of the retro, review open actions and get everyone moving in the right direction. ## Brainstorm and vote privately Avoid bias and fear by having people brainstorm anonymously and privately. Multiple voting options let the team prioritize items for discussion and focus on what really matters. ## Effortlessly group ideas Use our AI to automatically suggest groups or manually group ideas. Quickly identify common themes and focus your discussions, saving you time (if enabled). ## Power up your facilitation Control the flow with guided facilitation and live meeting feedback. Use presentation mode to sync everyone up and talk through one idea at a time. Easily capture ideas, actions and team agreements. ## Create actions and track progress Empower teams to propose and agree on actions. Assign dates and owners for accountability. Effortlessly track open actions to eliminate barriers and integrate them with your workflow tools. ## Generate summaries in seconds Create summaries of the meeting with key metrics, action outcomes and key highlights. Share them easily or publish them into your workflow tools (if enabled). ## Discover insights and share outcomes From meeting summaries and team sentiment to pivotal themes and emerging trends, you'll gain useful insights from your retrospectives, all easily shared. ## See a retrospective board in action Start from a ready-made template like the classic retrospective, then make it your own. See all retrospective features Explore retro templates See how TeamRetro compares ## You're in good company Thousands of teams from Fortune 500 companies, banks, government, and innovative startups use TeamRetro to make their good teams great! ## Frequently asked questions --- # All the features you need for effective, fun and easy retrospectives URL: https://www.teamretro.com/retrospectives/features/ {/* Card banner images (one per feature card, mirroring the live page). */} {/* At-a-glance feature icons (inline SVG ?raw → recolored from --marker, like enterprise roles). */} ## Create the perfect retrospective for your team Build a retro that fits the way your team works — customizable steps, free idea input, fun GIFs, and a clear panel for actions and agreements, all designed for agile teams. ### Dark mode ### Responsive ### 29 Languages ### 200+ retrospective templates Used by the top agile teams around the world. [Browse the template library →](/retrospective-templates/) ### …plus unlimited AI-generated possibilities Pick a theme for your team and let AI do the rest. ## Rich facilitation at your fingertips Guide the conversation with confidence — built-in timers, chat, a parking lot and team roles keep the meeting flowing while you stay focused on the team. ### Comment ### Timer ### Chat ### Team roles ### Parking lot ### Fully anonymous meetings Choose between anonymous, aliases and named. ### …or give participants a choice Optional anonymity for individual comments or ideas. ### Customize your process From a short and sharp meeting to a team think tank. ### Review open actions Create accountability and recognize success. ### Choose your brainstorm style Add ideas alone or together. ### Automated grouping Save time with automated suggestions or group manually. ## Engage your team, build participation Open with a quick icebreaker or check-in question to set the mood, then keep everyone involved with roles, private voting and visual collaboration. ### Music ### Mentions ### Live reactions ### Quick poll ### Meeting feedback ### Quick and easy icebreakers Choose, create or get an AI suggestion… then spin to start! ### Check-in questions Increase focus as you start the meeting. ### Assign meeting roles Invite co-facilitators, guests and observers. ### Independent voting Vote privately and without bias across topics. ### Whiteboards Sketch diagrams, map frameworks, and collaborate visually. ### Kudos & shoutouts Celebrate wins, big or small, with quick appreciation. ### Check-out questions Get quick feedback from the meeting. ## Focus the conversation Sync everyone's screen with presentation mode to talk through one idea at a time, or share the screen — but not your input — so people can participate freely. ### Presentation mode Sync everyone's screen to facilitate discussion. ### Share screen mode Share the screen, but not your input, and participate freely. ## Capture actions for continuous improvement Turn discussion into change — propose and agree on actions, get AI suggestions, and push them into the tools your team already uses. ### Propose actions Propose and create actions for continuous improvement. ### Get suggested actions Harness the power of AI to suggest actions based on your meeting. ### Integrate actions into workflow Push actions straight into your workflow tools. ### Personal dashboards Each person can see their actions, open meetings and teams. ### Meeting summaries Easily create, publish and share with AI summaries. ### Capture team agreements Create team culture and expectations to improve teamwork. ## Data-driven insights to help you level up See the bigger picture across retros — meeting cadence, sentiment trends, team health and action tracking, all in one place. ### Meeting cadence Track meeting frequency and activity over time. ### Meeting sentiment Explore team and meeting sentiment based on topics. ### Track team health Run health checks to measure and track team happiness. ### Action tracking Monitor and track actions to create progress. ### Explore common themes Drill down into your word clouds. --- # TeamRetro Roll-out Checklist URL: https://www.teamretro.com/roll-out-checklist/ {/* The brand PageHeader above carries the H1 + the intro question (description). */} Here's a list to help you prepare the necessary steps to roll out TeamRetro to your teams. Tick off each step as you go — your progress is saved on this device. {/* Featured product-board screenshot (matches the live hero media + caption). */} ## Drive continuous improvement with your team --- # Scrum Master Self-Assessment Quiz URL: https://www.teamretro.com/scrum-master-self-assessment-quiz/ --- # Security URL: https://www.teamretro.com/security/ Our customers trust us to keep their data secure and confidential. We take security seriously and work constantly to ensure that trust is well-founded. Have questions? Feel free to reach out to us at [security@teamretro.com](mailto:security@teamretro.com). TeamRetro is SOC 2 Type 2 accredited for security, availability, confidentiality, and privacy. An independent auditor has evaluated our policies, product, platform, and infrastructure in accordance with the Standard on Assurance Engagements (ASAE 3150) and verified that TeamRetro complies with their stringent requirements.
## Secure platform #### Secure infrastructure Our services are hosted on [Amazon Web Services](https://aws.amazon.com/) (AWS) infrastructure. We don’t host or run our own routers, load balancers, DNS servers or physical servers. Amazon data-centers feature 24-hour manned security, biometric access control, video surveillance, and physical locks. All systems, networked devices, and circuits are constantly monitored. AWS facilities are accredited under [ISO 27001](https://aws.amazon.com/compliance/iso-certified/), [SOC 1 and SOC 2](https://aws.amazon.com/compliance/soc-faqs/)/SSAE 16/ISAE 3402 (Previously SAS 70 Type II), PCI Level 1, FISMA Moderate and Sarbanes-Oxley (SOX). Learn more about [AWS security](https://aws.amazon.com/security/). #### USA or EU hosted – your choice **United States** – served by US-located data-centers and subprocessors, with our primary services hosted in Northern Virginia; and the **European Union** – served by data-centers and subprocessors located exclusively in EU member-state countries, with our primary services hosted in Frankfurt, Germany. #### Always encrypted *Encryption in transit –* All data sent to or from our infrastructure is encrypted in transit via industry best-practices using Transport Layer Security (TLS 1.2 or 1.3). Our SSL configuration receives an A+ security grade from [Qualys SSL Labs](https://www.ssllabs.com/ssltest/analyze.html?d=secure.teamretro.com&hideResults=on&latest). *Encryption at rest –* All our user data is encrypted using the battle-proofed AES256 encryption algorithm in our databases. #### Secure payments Our platform is PCI DSS compliant, ensuring secure handling of payment data with industry-leading protection and compliance measures. We aren’t in the business of handling or storing credit card numbers – your card details are directly captured and stored securely by [Braintree](https://www.braintreepayments.com/) (a PayPal company), our payments provider. Braintree is certified as PCI Level 1 compliant, and listed as a Visa® Global Compliant Provider and MasterCard® Compliant Provider (SDP). Learn more about [Braintree security and compliance](https://www.braintreepayments.com/products-and-features/data-security). #### Application security monitoring - We use a security monitoring solution to get visibility into our application security, identify attacks and respond quickly to a data breach. - We use technologies to monitor exceptions, logs and detect anomalies in our applications. - We collect and store comprehensive logs to provide an audit trail of our applications activity. Our logs are frequently reviewed by our security team to identify anomalies. - Security events are logged and notifications are sent in case of critical attacks to allow for fast remediation. #### Application security protection - We use Amazon [Web Application Firewall](https://aws.amazon.com/waf/) to protect our users from a wide variety of vulnerabilities. AWS WAF integrates protections against the most critical attack categories like SQL injections and cross-site scripting. It blocks attacks in real-time and warns us when attackers start stressing our applications. - We use security headers to protect our users from attacks. Our services have received an A+ grade from [SecurityHeaders.io](https://securityheaders.com/?q=secure.teamretro.com&followRedirects=on). #### Incident management Suspected security incidents, including any logical and physical security breaches are ticketed, tracked and resolved following our incident response policy and procedures. Where required by applicable law, including the EU Cyber Resilience Act, we notify relevant authorities (such as ENISA) of significant security incidents within mandated timeframes. If you have any questions or suspect an incident may have occurred, please contact [security@teamretro.com](mailto:security@teamretro.com). #### Downtime reporting Enterprise customers can elect to be notified of any problems via email. Our hosting platform usually obviates the need for downtime when we make changes to our services. However, we will notify customers by email at least 24 hours in advance of any planned downtime. #### Your privacy, protected Your data remains owned by you; and only accessible to those whom you choose to share. TeamRetro (and the GroupMap Technology team) may only access your data in limited circumstances such as when required by law or to provide technical support. Full details can be found in the TeamRetro [Privacy Policy](/privacy/). #### Data retention and removal We retain our users' data for a period of 365 days after their trial or subscription ends. All data is then completely removed from the application. Users can request the removal of data at any time by deleting their account or contacting TeamRetro support. Read more about our privacy settings in our [Privacy Policy.](/privacy/) #### Business continuity and disaster recovery We back up all our critical assets and regularly attempt to restore the backup to guarantee a fast recovery in case of disaster. We capture a full backup of customer data every 24 hours. Backups are securely encrypted and stored for 30 days, at which point they are securely destroyed. We have established Business Continuity and Disaster Recovery plans and review them annually. [](https://cloudsecurityalliance.org/star/registry/groupmap-technology/services/teamretro/) ## User protection #### Single sign-on Single sign-on (SSO) via your SAML Identity Provider (IdP) is available for all TeamRetro customers. #### Passwords – protected TeamRetro passwords are stored salted and cryptographically hashed using the state-of-the-art bcrypt algorithm. TeamRetro enforces a minimum password complexity requirement using Dropbox’s ZXCVBN library, ensuring passwords are safely unguessable and unbreakable. #### Account verification Users are required to verify their ownership of an email address via a link provided in an automated email prior to using for a TeamRetro account. All users must be authenticated prior to gaining access to customer data. #### Account takeover protection We protect our users against data breaches by monitoring and blocking brute force attacks. #### 2-factor authentication We allow for 2-factor authentication via Google or your SAML IdP to protect against account takeover attacks. #### Role-based access control Advanced role-based access control (RBAC) is offered on all accounts. #### IP whitelisting Once configured and enforced, anyone attempting to access the account from outside the permitted ranges will be blocked. This gives organizations tighter control over how and where their teams access TeamRetro. #### Suspicious user behavior monitoring We use [Datadog](https://www.datadoghq.com/) to monitor suspicious behaviors and react fast in case of account takeovers. It also protects customers against data theft by blocking credential stuffing or brute force attacks. ## Security practices #### Secure coding Our developers are required to follow our formally documented Application Security Policy, and follow security best practices and frameworks (OWASP Top 10, SANS Top 25). We use the following best practices to ensure the highest level of security in our software: - Developers participate in regular security training to learn about common vulnerabilities and threats - We review our code for security vulnerabilities - We regularly update our dependencies and make sure none of them has known vulnerabilities - We use Static Application Security Testing (SAST) to detect basic security vulnerabilities in our codebase - We use Dynamic Application Security Testing (DAST) to scan our applications - By using [Datadog](https://www.datadoghq.com/) we can more efficiently remediate vulnerabilities that were triggered by security tests, audits or vulnerability disclosure program. We are also warned when application components with known vulnerabilities are used in production (dependencies). #### Vulnerability scanning TeamRetro is scanned on a monthly basis, and after significant releases, by [intruder.io](http://intruder.io/) to identify potential infrastructure, platform and application vulnerabilities. Any identified vulnerabilities are triaged and mitigated in accordance with our application security policies. #### Penetration testing We periodically commission independent penetration testing, validating the security of the TeamRetro platform. We fix all critical issues within 48 hours and high-severity issues within 7 days. #### Risk assessments An annual risk assessment is conducted to identify threats and vulnerabilities for TeamRetro systems. Mitigation strategies are developed based on the results of the risk assessment. #### System hardening ***SERVER CONTAINERIZATION*** – TeamRetro uses OS containerization via AWS Fargate to ensure that access to TeamRetro data and code is properly restricted. All TeamRetro services run on dedicated compute resources isolated in their own virtual network. ***SERVER EPHEMERAL FILESYSTEMS*** – TeamRetro servers operate on an ephemeral filesystem, restored to a fresh copy of the most recently deployed code at minimum once per day, or every time a new version is deployed. ***SYSTEM PATCHING*** – Platform-level patching (operating system, system libraries, and services) of TeamRetro application and database servers is performed on an ongoing basis. ***APPLICATION PATCHING*** – Application patching (application libraries etc) is performed by TeamRetro on an ongoing basis. ***COMPUTERS*** – All team assets (such as development laptops and desktops) utilize encrypted storage and are protected by up-to-date anti-virus software. #### Comprehensive logging We maintain comprehensive logs of every transaction on the system; with specific logging for login attempts. Our logs are frequently reviewed by our security team to identify attempted unauthorized access. #### Our team’s access - Our strict internal procedure prevents any employee or administrator from gaining access to user data. We may only access your data in limited circumstances such as when required by law or to provide technical support. Full details can be found in our [Privacy Policy](/privacy/). - Our employees and contractors sign a Non-Disclosure and Confidentiality Agreement to protect our customers' sensitive information. - Our employees and contractors are screened by a leading background checking service. - The access level of each of our employees is determined by need, periodically reviewed and revoked if no longer necessary. We enforce multi-factor authentication for all critical TeamRetro systems. - Two factor authentication is required for administration access. #### Responsible disclosure We encourage everyone that practices responsible disclosure and comply with our policies and terms of service to participate in our vulnerability disclosure program. Please avoid automated testing and only perform security testing with your own data. Please do not disclose any information regarding the vulnerabilities until we fix them. Rewards are done at our discretion depending on the criticality of the vulnerability reported. Learn more about the [TeamRetro responsible disclosure program](/responsible-disclosure/). ## Third-party vendors and subprocessors TeamRetro makes use of a number of third-party vendors to enable a rich online experience. At TeamRetro, we are committed to being transparent about the third party vendors and subprocessors we work with to deliver and support our service. Our subprocessors are carefully selected based on their ability to meet high standards of security, privacy, and reliability. We regularly review our vendor relationships to ensure they remain aligned with our compliance obligations, and we provide customers with clear visibility into how and where their data may be processed. For full details, please refer to our [TeamRetro subprocessor page.](/security/subprocessors/) **Have a question or something to report?** Drop us a line at [security@teamretro.com](mailto:security@teamretro.com). --- # Run daily stand-ups your team doesn't dread URL: https://www.teamretro.com/standups/ ### Keep the fifteen minutes Timeboxed by design, so the daily sync stays a sync — not a status meeting that swallows the morning. ### Stay in sync across time zones Post async in Slack, Teams or the browser, on your own schedule — no one waits on a meeting that doesn't fit their day. ### Surface blockers early Flag what's in your way the moment it appears, and track it to done instead of losing it in a thread. ## Most teams run a stand-up. Far fewer run one worth the fifteen minutes. The daily stand-up is meant to be a short sync — where the team lines up on the day and clears what's in the way. Too often it drifts into status theatre: a lap of the table, everyone reciting yesterday to the manager, no one really listening. [The difference is facilitation, not format](/guides/daily-standup-guide/). TeamRetro is a daily stand-up tool that gives the meeting a shape. Everyone answers the same prompts, the timebox holds, and a blocker becomes a tracked action with an owner — not a comment that scrolls away. Live or async, in the browser or in your chat tool, the meeting stays short and the follow-through outlasts it. ## Async stand-ups for teams that don't share a morning When your team spans time zones, a live stand-up just taxes whoever's awake at the wrong hour. Run it async instead — everyone answers the same prompts on their own schedule, and the summary is waiting when the next person logs on. You still get the sync, without the calendar collision. [See when async wins, and how to run one](/guides/daily-standup-guide/async-and-remote-standups/). ## Stand-ups where your team already works Bring the stand-up into [Slack](/integrations/slack/) or [Microsoft Teams](/integrations/microsoft-teams/). TeamRetro reminds the team to post, collects the responses against the same prompts, and drops a tidy digest back into the channel — so the update lives next to the work, not in another tab someone forgets to open. ## Timeboxed, so it stays a sync The fastest way to lose a stand-up is to start solving problems in it. TeamRetro keeps the meeting moving — one prompt at a time, a visible timebox, and a parking lot for the conversations that only need two people. Fifteen minutes in, everyone's aligned and back to work. [The facilitation moves that keep it tight](/guides/daily-standup-guide/how-to-run-a-daily-standup/). ## Blockers you can actually follow up A blocker mentioned out loud is a blocker forgotten by lunch. In TeamRetro, flagging one creates an action with an owner and a due date, carried across days until it's cleared — and pushed straight to [Jira](/integrations/jira/) if that's where your team works. Nothing falls through the gap between two stand-ups. ## Know who's waiting on whom Status is the least useful thing a stand-up produces. The gold is the handoffs — the API's ready but nothing ships until someone deploys it; design is stuck on a call only the PM can make. TeamRetro turns each "I need X from Y" into a dependency with both names on it, carried from one day to the next until it clears. So the person who's blocked and the person who can unblock them leave the *same* stand-up knowing it — instead of finding out on Thursday they'd each been waiting on the other since Monday. [Make dependencies part of the daily sync](/guides/daily-standup-guide/). ## You're in good company Thousands of teams — from Fortune 500s and banks to fast-moving startups — already run their retrospectives and health checks in TeamRetro. Stand-ups are the newest thing to bring into the same place. --- # 3 nifty ways to keep your retros fun and exciting! URL: https://www.teamretro.com/blog/3-nifty-ways-to-keep-your-retros-fun-and-exciting/ **As important as sprint retrospectives are, there’s also the chance that repetition breeds familiarity. It becomes a chore rather than an opportunity for continuous improvement. Having fun, fresh ideas for your scrum team whether they are distributed or in the same room can shift mindsets and bring back energy.** As part of our job to try out different techniques and games from time-to-time, we found 3 simple ways that can revitalize your sprint retrospectives. ### Fun retro tip 1: get out of the building Your team spends their entire day cooped up in the office or huddled behind their desk. Why not mix things up by taking your retrospective meetings beyond the office walls? A new environment can help your team get a new perspective on the project. A digital online retrospective tool means you are not bound by sticky notes or walls (literally and metaphorically). Grab your devices (Or pen and paper if you choose to go old school). Head outside and enjoy the fresh air in a park, a change of scenery at a quiet cafe or a more informal one at the pub. A really great idea might be to run the retrospective in the environment where the client works and performs their job. This creates empathy and a deep understanding of what your end user is really experiencing. #### What do we do. Our team is distributed. So we ask each team member to pick their favorite cafe and run a Zoom Meeting. For those of us in the same location, we chose to have it in an open air cafe called Lyric Lane. After sharing what our beverage of choice, we created a time box for people to brainstorm directly into TeamRetro. To avoid the talking over each other and to ensure that everyone in the team was included, we did a round robin through the ideas and grouped them as needed. The change of scene was refreshing and a good opportunity to carry on working in a different space for a while after our meeting. ### Fun retro tip 2: run a just-in-time retrospective A regular cadence is important but when something “interesting” has happened mid-sprint, there’s nothing dictating you to wait until the end of the sprint cycle. A Just In Time (JIT) retro brings everyone together to discuss the current hot issue. Moving quickly and in a timely manner helps to avoid sagas, mountains out of molehills, or other blockers that destroy team productivity. Anything from a sudden departure, a change in technology or emerging product issue could be the trigger. In that sense, Agile has similarities to the Just In Time approach used in manufacturing. Rather than a “just in case” approach to running your retro, having your team come together not just because of a planned time but to address a specific set of issues or opportunities which means maximum engagement. This is from Scrum Kanban Guide (about retrospective) *The Scrum Guide dictates that the Sprint Retrospective take place after the Sprint Review and before the next Sprint Planning. This does not change when using Kanban. However, flow-based retrospective opportunities need not coincide within the boundaries of a Sprint. They can occur “just in time”. Correspondingly, changes to a team’s definition of “Workflow” may happen at any time, however, as these changes will have a material impact on how the Scrum Team performs, changes made during the regular cadence provided by the Sprint Retrospective event will reduce complexity and improve transparency.* In short, strike while the iron is hot! #### What do we do. Apart from our usual cadence of sprint based retrospectives, everyone within the team looks for “retrospective opportunities” – any activities to inspect the flow as defined by the Team. Examples include on-boarding a new team member to help them understand our retrospective process, to recognizing a new stakeholder that impacts on our development through to unexplained shifts in behavior or morale. We kick off with a [team health check](/health-checks/) or radar that gives us insight into what might be the key areas of concern to focus our discussion on. We tend to use the [Mad, Sad, Glad retrospective](/retrospective-templates/mad-sad-glad-retrospective/) to air out issues and look at the circle and soups model to help manage expectations. ### Fun retro tip 3: be inspired by a favorite movie or TV show Use a set of characters, places, symbols or concepts from popular culture to enliven the inner geek in us all. It’s a way to relate concepts and characters, spark interest while still addressing the main points at hand. If you want to go the extra mile, theme your retrospective. It will bring a few smiles, witty banter and renewed energy. Here’s one we found based on the TV show The Office. Courtesy of Gretchen Knode Scrum Master / Agile Coach at [Agile Initiatives.](https://www.facebook.com/agileinitiatives/?eid=ARDtvOxaXVOB_Vt13OzVWZCj_ek8Y4ndXalA0igpgy8hAtL9xUeePQlI0v-f9iFpZRdL0COfWe9I6JWM&timeline_context_item_type=intro_card_work&timeline_context_item_source=596025656&fref=tag)  The idea here is that the engagement comes from attaching meaning to characters and using that as a way to guide thinking based on what relates to them. Piggybacking this with a clip or a lead-up is also a great hook. **What do we do?** We recently had a team film night and watched Avengers Endgame. Inspired, we decided to create an Avengers-themed retrospective using the top 6 characters (yes — even Hawkeye was included!) Creating Icons from Icons8, we went about representing different aspects of our online retro. Here’s what we came up with. - **Captain America**: What do we want to protect? - **Iron Man**: What experiments should we try? - **Hulk**: What do we want to change? - **Black Widow**: How can we improve our team? - **Thor**: What are our biggest strengths? - **Hawkeye**: What support do we need? What made this process fun was the sense of empathy and highlights the role each person plays. They each bring their own perspectives and “super powers” for collaboration and teamwork. It was a great way to have open and honest discussions as well as creating our top 3 action items. Do you have any ideas you think we should share around making team retrospectives fun, engaging and fresh? Write to us at [info@teamretro.com](mailto:info@teamretro.com). Ready to run your own fun retro? [Try out TeamRetro now!](/retrospectives/?utm_source=3funtips&utm_medium=trb&utm_campaign=dmcs/) --- # 5 tips for getting the most out of your agile team health check URL: https://www.teamretro.com/blog/5-tips-for-getting-the-most-out-of-your-agile-team-health-check/ Team health checks are a really easy way of measuring and tracking a team’s well-being to inform data driven action points that help support a team’s continuous improvement! If you’re new to team health checks, or if you just want to make sure you’re making the most of them, we’ve pulled together our top five tips to help you on your way. ## Tip 5. aim to support not judge Health checks are a great way to gain insight into the support your team needs; and can show you where you can bring the most benefit. So, take care – this isn’t the time to show off your extrapolation skills. If a health check points to a team being ‘unhappy’, that doesn’t mean they aren’t delivering value. Although it might be tempting to compare individuals or teams based on the results of a health check, such an undertaking is fraught. A team that records mainly “green” responses may simply feel uncomfortable discussing certain issues, while those registering “red” may be embracing the opportunity to improve. That’s why you should make your first step adopting the mantra ‘support don’t judge’. Approach the team with an open and curious mind as such a mindset is conducive to supporting team growth. To check you’ve embraced the right mindset, ask yourself ‘Who are you hoping to benefit?’; if your answer isn’t ‘Your team’, it’s time to recalibrate. ## Tip 4. talk to your team This one may seem obvious, but it’s often missed. When you have – - a backlog of Everest proportions, - an infinity of back-to-back meetings and - you’re seriously considering skipping your morning shower to save yourself some time (please don’t, always shower), you may find yourself inexplicably assuming the talents of your team extend to being able to read your mind. They can’t – so talk to them. The main things to cover when you first run a health check – - What a health check is and why they’re valuable - The dimensions the health check includes and what they mean - How health checks will happen in your team - Any concerns your team may have This step comes with a bonus. Not only is this a chance for you to connect with your team, but it also helps to show you are genuine in your wish to be supportive, that your actions and words align, and that the introduction of health checks is not a box ticking exercise. When a team considers their manager genuine and supportive, team wellness is enhanced. ## Tip 3. connect to your existing process and practice One of the easiest ways of integrating a health check into your team’s world is by aligning it with your retrospective. Performing a health check before or after a retrospective means it won’t interrupt other workflow commitments. They can easily be aligned to asynchronous retros too. Aligning it to your retro doesn’t mean duplicating exactly what happens during your retro. The health check space is one in which responses are captured quickly and independently and it’s not a time to discuss issues nor explore treatments and solutions. It’s an opportunity to gauge team wellness at a particular point in time. You can even run a health check prior to your retro and use the data to define the focus for the next retrospective to address a particular area. ## Tip 2. make it regular There are two key reasons for this – Firstly – the foundation for improving team health is measuring it, and the cornerstone of that foundation is the ability to track it over time. Tracking will allow you to appropriately target areas of concern and assess the effectiveness of the type of support that’s been made available to your team. Using a health check connects to a data driven practice; it’s your tool to help define the actions and resources that will provide the support your team needs so they can improve. Secondly – this is a chance for you to demonstrate you value your team and their well-being, and in a time poor world nothing says that quite like reserving a space for it in your schedule. That’s why it’s important to hold a team health check regularly. If you find a monthly team health check a little too much, try every two months or whatever interval helps you build the health check habit. ## Tip 1. make it safe It’s simply not possible to overstate the importance of conducting a team health check in a psychologically safe space. Your team needs to feel comfortable in their courage; they need to feel they may offer honest and open responses without fear of adverse action (be it direct or indirect). Some of your team members may already feel this, others may need some support to get there, and so here’s how you can help – - Make your team health checks anonymous…really anonymous… not the sort of anonymous that can be easily reversed so it’s possible to take a sneaky peak at who said what…. actually anonymous… so no one knows who owns which response… including you. [ Psst… TeamRetro lets you set health checks that are anonymous to both participants and facilitators.] - Share it with the team (and those supporting them) but no further. Sharing it beyond this increases the likelihood that the results won’t be used for the purpose for which the health check was designed. Of course, you can [customize your team health check templates](https://help.teamretro.com/article/194-custom-health-models) so that it makes sense to your organization and the team, adding to its meaning. Let us know if you have other tips you’d like to share. If you’re new to team health checks, [test-drive our health checks](https://secure.teamretro.com/demo/health-checks?lang=en) with our team of friendly bots. --- # Agile maturity assessment: how to measure and improve your team URL: https://www.teamretro.com/blog/agile-maturity-assessment-how-to-measure-and-improve-your-team/ Your team is running sprints. There’s a backlog, a definition of done, and regular retrospectives. On paper, everything looks agile. But something still feels off. Releases are unpredictable. The same retro themes keep resurfacing. And if someone asked, “How mature is your agile practice?” — it wouldn’t be an easy answer. That hesitation is exactly why agile maturity assessments exist — and why running them well, with the right tool, makes all the difference between a conversation that produces a slide deck and one that produces real change. ## What is an agile maturity assessment? An [agile maturity assessment](/health-checks/agile-maturity-assessment/) is a structured way to evaluate how effectively a team or organization applies agile principles in practice. It goes beyond a count of how many agile ceremonies you run. It looks at whether the underlying thinking is actually there – examining areas like collaboration, delivery flow, technical quality, and continuous improvement to identify strengths and the highest-leverage opportunities for growth. More broadly, [maturity models](https://en.wikipedia.org/wiki/Maturity_model) are designed to measure how capable an organization is at consistently improving its processes over time. As the team matures, this translates into more predictable, adaptable outcomes, not just faster sprints. ## Why agile maturity assessments matter Here’s a sobering stat: according to OutSystems’ [State of Application Development report](https://www.outsystems.com/blog/posts/agile-maturity/) (which surveyed over 1,500 application development professionals), only around 15% of organizations consider themselves fully mature in agile practices. About 60% remain stuck at the second or third maturity stages, going through the agile motions without realizing the full benefits. Agile transformations often stall not because teams lack effort, but because there’s no shared, honest picture of what’s actually happening. Gaps stay invisible. And without visibility, it’s hard to know whether you’re genuinely improving or just staying comfortable. Regular agile maturity assessments help teams and leaders in a few important ways: - **They surface what’s really going on**. Day-to-day work makes it hard to see systemic issues. An assessment creates the structure and the pause, to look clearly at how your team is really operating, not just how it feels. - **They focus your improvement energy**. Not every gap is equally worth fixing. Assessments help identify the changes that will move the needle most, so you stop spreading effort thin and start making targeted progress. - **They create a shared language**. When everyone on the team rates the same dimensions, differences in perspective become visible. That honest gap between how different people experience the team’s ways of working can spark some of the most valuable conversations you’ll have. - **They make progress visible**. Running assessments regularly turns individual snapshots into trends — and trends tell you whether your improvements are actually sticking, or quietly sliding back. - **They give leadership something to work with**. For organizations running multiple agile teams, assessments enable cross-team comparisons and surface systemic blockers that no single retrospective can reveal. ## What does an agile maturity assessment measure? The specific dimensions your assessment covers depend on the model you choose. But across all well-structured assessments, the goal is the same: rating how your team actually operates across the areas that matter most for delivery and improvement — not just whether ceremonies are happening on schedule. Here’s a concrete example. When a team uses the Agile Teams maturity model in TeamRetro, they’re rating themselves across six categories: - **Teamwork & collaboration** — How well the team communicates, resolves conflict, and operates as a self-organizing unit. - **Agile ways of working** — Whether ceremonies are happening consistently and driving real value, not just filling a calendar. - **Planning & prioritization** — Whether the backlog is well-groomed, work is prioritized by value, and capacity planning is realistic. - **Technical excellence & quality** — How technical debt is managed and whether quality is built in from the start. - **Product delivery & customer value** — Whether the team is shipping things that matter, and tracking outcomes not just outputs. - **Agile mindset, culture & continuous improvement** — Whether the team genuinely embraces agile values, and whether psychological safety exists to surface problems early. A team running the DevOps & continuous delivery model would rate themselves on CI/CD pipeline maturity, release and deployment practices, reliability and operations, security and compliance automation, and platform and infrastructure readiness — a completely different lens, built for a different context. This is why model selection matters. The dimensions shape the conversation. Choosing the right one for your team’s current focus is what turns an assessment into a useful discussion rather than a generic survey. ## How agile maturity is measured: the 5-level scale Once you know what dimensions you’re assessing, you need a scale to score them against. The most widely used structure organizes maturity into five levels — each describing a specific pattern of behavior, not just a number: - **Level 1 — Initial / Ad hoc**. Processes are unpredictable and reactive. Agile may exist in name only. - **Level 2 — Developing**. Some agile practices are in place but inconsistent. There’s intent, but limited discipline. - **Level 3 — Defined**. Practices are standardized and consistently followed. The team understands not just what they do, but why. - **Level 4 — Managed**. Performance is measured and decisions are data-driven. Feedback loops are tight. - **Level 5 — Optimizing**. Continuous improvement is embedded in the culture. The team innovates its own practices and consistently delivers real customer value. Each level within a dimension comes with a clear written description of what that level looks like in practice — so team members aren’t guessing what a “3” means. That consistency is what makes the results worth discussing. Pssst…. Not every team needs to reach Level 5 in every dimension. What matters is knowing where you are and having a deliberate plan for the next step. A team that constantly rates at 5 might be the shining star in the organization or they may lack the benchmarking needed. ## TeamRetro’s maturity assessment models A maturity model is the framework your assessment runs against. It defines which dimensions are being rated and what each level looks like in your specific context. Choosing the right model for your team’s current situation is what makes the difference between a focused, useful session and a generic exercise that produces a list of things everyone already knows. TeamRetro offers 20 purpose-built models across the areas agile teams actually care about, along with the opportunity to create your own or to co-create one with AI. Here are 5 that our team have used recently at our last round of team meetings – - **Agile teams** — Measures how well our team collaborates, plans, and delivers value through agile ways of working. - **Leadership** — Assesses how effectively our leaders inspire vision, communicate strategy, and develop us. - **DevOps & continuous delivery** — Evaluates our pipeline reliability, deployment speed, and operational resilience across our engineering team to deliver outputs to you. - **Agile delivery** — Understands how consistently our team plans, flows work, and improves delivery cycle over cycle. - **AI adoption maturity** — Tracks how confidently our team integrates AI tools into daily workflows with proper governance in place to ensure focussed AI features that bring the you benefit, without compromising on security. At the industry level, assessments tend to fall into 3 broader categories. Let’s take a deep dive into these. ### Agile delivery Designed for scrum teams and delivery-focused squads. It assesses how well the team plans and prioritizes work by value; how smoothly and predictably work flows from idea to done; how effectively the team collaborates and self-organizes; and how consistently feedback loops drive genuine improvement. Teams using this model typically run it quarterly, using the results to focus their retrospectives on the dimensions that scored lowest. ### Engineering excellence Built for engineering managers and senior developers who want to go beyond process and assess technical health. It covers code quality and standards, architecture and scalability decisions, how actively technical debt is being managed, and how well the team enables and supports each other as engineers. It’s particularly useful for teams that score well on agile process metrics but still struggle with delivery predictability — the root cause is often here. ### DevOps & continuous delivery Built around the practices that separate teams who ship confidently from those who dread release day. It assesses CI/CD pipeline maturity, release and deployment processes, reliability and operations, security and compliance automation, and platform and infrastructure readiness. Teams working toward DORA metric improvements often find this model maps directly to where the friction actually lives. ## How to run an agile maturity assessment effectively The key is to focus on insight and action, not just measurement. TeamRetro’s built-in flow walks teams through each of these steps automatically — but here’s the thinking behind them. ### 1. Choose relevant focus areas Start with dimensions that are meaningful for your team’s current context. You can choose from purpose-built maturity models covering agile delivery, engineering excellence, DevOps, product management, and more — or build your own from scratch. A Scrum team early in their agile journey has different priorities to a scaled product organization, and your model should reflect that. ### 2. Collect responses privately Honest feedback only happens when people feel safe giving it. You can collect responses anonymously before any results are shared with the group, removing the social pressure that skews ratings toward what people think leadership wants to hear. Every team member rates each dimension independently — the aggregated picture only surfaces once everyone has contributed. ### 3. Review results as a radar chart When results surface in TeamRetro, they appear as a radar chart — showing the shape of your team’s maturity at a glance. High scores, low scores, and gaps between dimensions are immediately obvious. There’s no manual aggregation or waiting. You can sort dimensions from most positive to most negative to most mixed, so the conversation starts in the right place. ### 4. Walk through results as a team TeamRetro’s Presentation Mode syncs screens across the team — in-person or distributed — so the facilitator can walk through results dimension by dimension without losing the room. At [Culture Amp](/case-studies/culture-amp/), a core company value is “learn faster through feedback.” Their engineering teams run both maturity assessments and health checks in TeamRetro precisely because Presentation Mode keeps the conversation anchored to what the data is showing, rather than drifting into anecdotes. ### 5. Prioritize a small number of high-impact improvements Resist the urge to fix everything at once. With TeamRetro’s AI summaries — which generate commentary for each dimension and across the whole session — patterns emerge quickly, even across teams with a lot to say. Identify the areas where the gap is biggest and where closing it would move the needle most. One well-executed change builds more confidence than five half-finished ones. ### 6. Create accountable actions before you leave the room This is where most assessments fall apart — the insights evaporate without owners or due dates. Actions are created directly within the session with an owner and a due date assigned before anyone closes their laptop. Those actions carry forward to the next session automatically, so nothing quietly falls off the radar. For teams using Jira, Asana, Trello, or Azure DevOps, action items can be pushed directly to your existing workflow. ### 7. Track trends across sessions Run the same assessment every quarter or at major milestones. TeamRetro tracks how each dimension moves over time, displaying trend lines directly on the radar so you can see at a glance whether a dimension is improving, static, or regressing. When Ibrahim Abram, Procurement Specialist at Culture Amp, reflected on what he values most in TeamRetro, it was this: “I love the graph that shows the trends.” That’s the difference between a tool and a process. ## Common mistakes to avoid Even well-intentioned assessments can go sideways. Watch out for these: - **Treating it as a one-time event**. A single assessment gives you a starting point. The real value is in the trend — knowing whether you’re moving in the right direction and how fast. - **Letting it become a performance review**. The moment people feel their individual performance is on the line, honest input disappears. Frame it clearly as a tool for the team to improve together. TeamRetro’s anonymous response mode exists specifically for this. - **Optimizing for scores rather than outcomes**. Teams can game maturity assessments if the incentives are wrong. What matters is whether actual practices and delivery outcomes are improving — not whether the numbers look better. - **Skipping the action planning**. An assessment without actions is just an interesting conversation. If the session ends without clear next steps and owners, the insight evaporates within a week. TeamRetro makes this the last required step before closing a session. - **Running it in isolation from retrospectives**. [Agile maturity assessments](/health-checks/agile-maturity-assessment/) and [retrospectives](/retrospectives/) work better together. In TeamRetro, you run both from the same platform — so the themes that keep surfacing in your retros can inform what you focus on in your next maturity assessment, and vice versa. ## Why teams choose TeamRetro for maturity assessments Most teams that try to run maturity assessments without a dedicated tool hit the same wall: the survey gets built in a spreadsheet, results get pasted into a slide, actions get noted down somewhere, and by the next quarter nobody can remember what was agreed. The insight doesn’t compound — it resets. Manual assessments often fail because data is scattered across spreadsheets and slides, causing insights to reset every quarter. TeamRetro prevents this by centralizing the process with these key features: - **Private feedback**: Anonymous responses ensure honest data and a safe environment for teams. - **AI summaries**: Automated reports for each dimension save time on manual write-ups. - **Persistent actions**: Assigned tasks carry over between sessions with reminders to ensure accountability. - **Visual trends**: Radar charts display historical direction to track real improvement over time. - **Workflow integrations**: Syncs directly with tools like [Jira](/integrations/jira/), [Asana](/integrations/asana/), and [Azure DevOps](/integrations/azure-devops/). - **Enterprise reporting**: Organizations like Culture Amp use team tagging to compare trends and surface systemic blockers without losing local context. ## Ready to run your agile maturity assessment? Understanding how your team really works today is the first step toward improving it. An [agile maturity assessment](/health-checks/agile-maturity-assessment/) surfaces the gaps you’ve been sensing but couldn’t quite name — and gives your team a shared, honest foundation for doing something about them. TeamRetro gives you proven templates, private feedback, radar chart results, trend tracking, AI summaries, and built-in action planning — all in one place, with zero setup required. [Start your free assessment today](https://secure.teamretro.com/login/new) — no credit card required. --- # AI in Agile Project Management: What Teams Need to Know URL: https://www.teamretro.com/blog/ai-agile-project-management/ If you've been searching for "ai in agile project management" lately, you're in good company. The [AI4Agile Practitioners Report 2026](https://www.scrum.org/resources/blog/ai4agile-practitioners-report-2026) found that 83% of agile practitioners now use AI tools — yet 55% spend 10% or less of their working time with them, and only 15% have had any formal training in using AI in an agile context. Adoption is nearly universal. Depth isn't. That gap is what this guide is about. Not another opinion piece on whether AI will replace Scrum Masters — the industry has largely moved past that question — but a round-up of what the 2026 research and framework updates actually say: where AI fits across the agile lifecycle, how the Scrum Master role is being redefined, and what teams are doing in their first few sprints of adoption. Where our own experience at TeamRetro is relevant, we'll say so — and where it isn't, we'll point you at the source material instead. ## What AI in Agile Project Management Really Means In agile delivery, AI means using machine learning and automation to support how teams plan, build, reflect, and continuously improve — without handing over the judgment calls humans need to make. A useful way to think about it comes from Dave West's *Scrum Master 2.0: The AI Catalyst* keynote at the Online Scrum Summit 2026, which describes four engagement modes: - **With AI** — tools enhance individual productivity. Most teams start (and stall) here. - **Through AI** — software created by describing intent; specification quality and validation become the bottleneck, not development. - **To AI** — AI acts with meaningful autonomy, and Scrum evolves toward a governance and oversight framework. - **Of AI** — the product itself is AI, making model evaluation and data pipelines first-class engineering concerns. Knowing which mode your team is in matters, because — as West notes — most teams think they're working "with AI" while quietly drifting "through AI" without redesigning anything about how they work together. ## What the 2026 Data Says About AI in Agile Teams The most consistent finding across the current research is a speed paradox: individual gains don't automatically become team gains. The OSM 2026 keynote pulls the evidence together. Controlled studies show AI completing certain development tasks 55% faster (GitHub/Microsoft, 2025). But longitudinal research across 211 million lines of code found code duplication quadrupled as AI adoption rose (GitClear, 2024), and a 2025 METR trial found no statistically significant productivity gain — even though participants believed they were 20% faster. As West puts it: "Individual fluency is not team capability — and nobody is accountable for closing that gap." The AI4Agile report points to the same conclusion from the practitioner side. The biggest barrier to adoption isn't skepticism or tooling — it's integration uncertainty (54%): teams don't know where AI fits in their workflows. And the area where practitioners report the clearest value is the unglamorous one: drafting, summarizing, preparing, and documenting. AI earns its keep by creating space for facilitation, dialogue, and decision-making — not by replacing them. ## Where AI Fits Across the Agile Delivery Lifecycle ### Sprint planning and backlog refinement AI-Native SAFe, released by Scaled Agile in June 2026, recommends starting with forecasting, knowledge discovery, and backlog refinement — augmenting the informed bets that planning has always been about. In practice that means historical velocity data flagging an overloaded sprint before it starts, and surfacing backlog items that lack enough definition to be picked up safely. For distributed teams planning async, that signal replaces the real-time gut-check a co-located team gets for free. One caution from the OSM keynote: five AI-accelerated developers without a shared Sprint Goal create five diverging solutions, faster than ever. AI raises the stakes on alignment; it doesn't lower them. ### Delivery quality and the Definition of Done This is where the 2026 guidance is most pointed. AI generates output fast; the Definition of Done is what ensures it's genuinely done, not done-ish. West's recommendation is to add explicit AI quality gates to the DoD — review checkpoints at consequential handoffs where human judgment is deliberately preserved. The GitClear duplication data is the argument for why: unreviewed AI output degrades quality quietly, in places nobody is watching. ### Retrospectives without the admin load This is the part of the lifecycle we know best at TeamRetro, so treat this section as practitioner experience rather than neutral reporting. The retrospective is where the industry conversation and the tooling meet. The AI4Agile finding — AI is most valued for summarizing and documenting — describes exactly the admin load that undermines retros: sorting feedback, writing up notes, chasing action items between sprints. In [TeamRetro](/retrospectives/), Auto-Suggest Groups clusters similar feedback during the Group step so teams move straight to discussion, and AI-Suggested Actions generates next steps tied back to the specific ideas that shaped them — reasoning shown, team votes, no black-box output the facilitator has to defend. For a step-by-step look at how each of these features works, see our guide to [AI-powered retrospective features](/blog/ai-tools-that-make-agile-retrospectives-easier-and-smarter/). The OSM keynote adds a practice we'd underline: give your retrospective a standing AI lens. What did we delegate this sprint? What did we review? What did we trust too much? Teams that have never retrospected on their own AI use are — in West's words — the most dangerous kind: they think AI is going well because individuals are productive, but have never looked at it collectively. *Want to try an AI-assisted retro with an AI lens built in?* [*Run one free in TeamRetro*](/) *— no setup required.* ### Team health and sentiment over time Research into remote retrospectives has found that [anonymity creates a more secure environment for honest feedback](https://www.researchgate.net/publication/392212352_Strategies_for_Effective_Remote_Retrospectives_Exploring_Retrospective_Games_Anonymity_and_Continuous_Reflection) — psychological safety is simply harder to establish through a screen. The OSM keynote makes the same point from the other direction: humans working alongside AI need *more* trust to speak up when something looks wrong, not less. AI helps here at the pattern level. In TeamRetro, the [Insights dashboard](/blog/unearthing-valuable-metrics-from-retrospective-and-health-checks/) tracks sentiment themes across retrospectives and [health checks](/health-checks/) over time — so if "deployment process" keeps surfacing across three consecutive retros, or psychological safety scores are quietly declining, it shows up in the trend data rather than a spreadsheet nobody opens. ## The Scrum Master's New Role: The AI Catalyst The sharpest reframing of 2026 belongs to Scrum.org. The Scrum Master's accountability hasn't changed — the 2020 Scrum Guide still says "the Scrum Team's effectiveness" — but what effectiveness means has. In 2026, it means ensuring AI accelerates the team, not just the individuals inside it. West calls this the **AI Catalyst**: not the team's AI expert, but its AI effectiveness leader, working three moves — *diagnose* (where is the team on the fluency ladder, and which engagement mode is it really in?), *design* (recalibrate existing Scrum events for AI-assisted work rather than bolting on new ceremonies), and *develop* (build team habits — prompt templates, shared standards, review checkpoints — not individual hacks). One risk the keynote names that deserves wider attention: **capability debt**. When AI takes over the execution work that used to build junior practitioners' judgment, someone has to design deliberate learning pathways alongside AI use. That's a coaching problem, not a tooling one — and it lands squarely in the Scrum Master's lap. ## Governing AI at Scale: Lessons From AI-Native SAFe For teams in scaled environments, [AI-Native SAFe](https://framework.scaledagile.com/ai/) (June 2026) signals where enterprise expectations are heading: smaller, AI-augmented teams; shorter, more iterative work cycles; and — notably — handoffs between humans and AI explicitly designed into the operating model rather than left to individual interpretation. It also introduces an "AI value architect" role covering cost, ethics, legal, and risk, and elevates governance, specifications and intent, and curated data management to first-class framework elements. You don't need to run SAFe for the takeaway to apply: at any scale, the pattern is the same. Pair AI pilots with governance and outcome-focused KPIs, and design the human/AI handoffs on purpose. ## How to Introduce AI Into Your Agile Workflow The OSM keynote closes with a three-sprint plan that matches what we've seen work: start small, stay empirical, and treat adoption itself as something to inspect and adapt. 1. **This sprint — diagnose.** Run a team-level AI fluency assessment, not a tool audit. Which engagement mode are you actually in? Where is AI being used individually and invisibly versus collectively and transparently? Be honest. 2. **Next sprint — design.** Update your Definition of Done for AI-generated output. Run one retrospective with an explicit AI lens: where did we trust too much? 3. **The sprint after — develop.** Build one shared workflow — prompt templates, review checkpoints — moving fluency from individual to team level. 4. **Ongoing — keep the ladder moving.** Retrospect on AI every sprint. Treat capability debt as a backlog item. Track whether recurring blockers are actually declining — TeamRetro's [Insights dashboard](/blog/unearthing-valuable-metrics-from-retrospective-and-health-checks/) makes that trend visible across as many teams as you run. Two principles hold throughout. Be transparent about what the AI is doing — [psychological safety in retrospectives](/blog/how-online-retrospective-tools-build-psychological-safety/) collapses if people don't know whether feedback is anonymous or how AI is using it. And keep the facilitator in the room: AI handles grouping, summarizing, and suggesting, but it doesn't read the room. As West puts it: "You don't need a transformation programme. You need empiricism applied to AI adoption — one sprint at a time." ## The Risks of AI in Agile and How to Manage Them **Overreliance on the output.** The worst version of AI-assisted delivery is a team waiting for the AI to tell them what they think. The honest disagreement — the moment someone finally says the thing nobody's been saying — can't be automated. **Thin data producing thin insights.** Pattern detection is only as good as its inputs. New teams, low-participation teams, and performative retros will get outputs that don't reflect reality. Treat insights as a prompt for discussion, not ground truth. **Capability debt.** Covered above, but worth repeating as a risk: if juniors stop doing the work that builds judgment, your team's future capability is quietly eroding while its current velocity looks great. **Privacy and data security.** Retrospective feedback is sensitive. [Research into agile tool adoption](https://arxiv.org/abs/2508.03369) consistently flags privacy and trust as top adoption blockers. Check where your data lives and who can access it. TeamRetro is [SOC 2 Type 2 accredited](/security/) and GDPR compliant, and customer data is never used to train AI models. ## What AI Changes About Agile and What It Doesn't The 2026 evidence points one direction: AI in agile project management doesn't change what the ceremonies are for. It changes how much friction they carry — and it raises the bar on the human work of alignment, judgment, and honest conversation. The frameworks agree on more than they differ. Scrum.org says upgrade your existing events rather than adding AI ceremonies on top. SAFe says design the human/AI handoffs deliberately and govern them. The practitioner data says AI's real value is clearing the admin so the conversation can happen. What's left, once the grouping is automatic and the summary writes itself, is the conversation — and the conversation was always the point. That's the principle TeamRetro's AI features are built on: the AI shows its work, and the team stays in control. If you want to see what that looks like in your next retro, [try TeamRetro free with your team](/). **Sources referenced:** [AI4Agile Practitioners Report 2026 (Scrum.org)](https://www.scrum.org/resources/blog/ai4agile-practitioners-report-2026) · Dave West, *Scrum Master 2.0: The AI Catalyst*, Online Scrum Summit 2026 · [AI-Native SAFe / Scaled Agile AI guidance](https://framework.scaledagile.com/ai/) · [GitClear code quality research](https://www.gitclear.com/) · [Remote retrospectives and anonymity research](https://www.researchgate.net/publication/392212352_Strategies_for_Effective_Remote_Retrospectives_Exploring_Retrospective_Games_Anonymity_and_Continuous_Reflection) --- # AI-powered retrospective features that make agile retrospectives easier and smarter URL: https://www.teamretro.com/blog/ai-tools-that-make-agile-retrospectives-easier-and-smarter/ At TeamRetro, we’re passionate about helping teams continuously improve through the power of agile retrospectives. Not only is your time valuable, but we want to ensure the effort spent on the do-inspect-adapt cycle empowers teams to make meaningful adjustments. We’ve developed a suite of AI-powered features designed to take your retrospectives to the next level. With TeamRetro, teams can streamline the retrospective process and save time on meeting preparation. Tedious tasks can be automated. Valuable insights are scoured and surfaced and actions can be recommended based on the discussion. Finally, it can even provide you with a summary of comments, as well as the overall meeting – ready to share. Green flag! TeamRetro’s AI features prioritize data privacy—your retrospective data is never stored or used for training AI models, ensuring your sessions remain confidential and secure. Ready to find out more? This article will walk you through what it feels like having an AI powered agile retrospective, offer warnings and tips about AI, and how you can get the most out of TeamRetro’s AI functionality. This post focuses on TeamRetro’s own AI features. For the wider picture — how AI is reshaping planning, delivery, and team health across the whole agile lifecycle — see our round-up of [AI in agile project management](/blog/ai-agile-project-management/). ## Keep things fresh with new AI generated retrospectives Sick of the same old retro but can’t find a good set of new questions. Our [Generative AI](https://help.teamretro.com/article/386-using-ai-generated-templates) suggests various retrospective formats based on the key problem you are trying to solve. Not only can this help align the retrospective more directly with your current team needs, but also save you meeting preparation time. Here’s one created in a few seconds to focus on Customer Value with the team. AI provides a suggested format you can put into play straight away, or tweak to suit. Being able to provide a few prompts such as your language, team type and even the number of topics helps you quickly generate a brand new, fresh set of questions that will help pull your team out of the dreary mundane to a newly engaging think tank. ## Kickstart your retrospective sessions with AI-generated icebreakers Creating a comfortable, engaged atmosphere from the very start can be key to a successful retrospective. [Icebreakers](https://help.teamretro.com/article/405-the-retrospective-process-icebreaker) can ease the session, boost energy and encourage openness without it being a time sink. Add a quick prompt to get suggested icebreaker questions that fit your team’s mood or style. Based on your prompt, TeamRetro’s AI will offer a list of questions to choose from. Each option is crafted to help meet specific objectives—whether it’s building rapport, tapping into creativity, or just getting everyone talking. You can review the list, pick the question that feels right for the group, and easily set the tone for a productive retrospective. Once you select a question, you can run a facilitated icebreaker session that’s both time-boxed and interactive, keeping things efficient and fun. ## Streamline your discussions with automated grouping Our [Automated Grouping](https://help.teamretro.com/article/160-retrospective-group-step) feature helps teams cut through the clutter and focus on what really matters by organizing similar feedback into clusters based on common themes. Instead of manually sorting through each comment, TeamRetro’s AI automatically groups feedback, so you can easily see patterns or themes. Grouping these will make it easier for the team to prioritize the topics that need the most attention. Beyond simple semantics, AI-powered grouping takes into account the context of what is being said, the headers, and the themes to help pull together a list of suggestions that allow Scrum Masters and the team to more quickly make sense of the data. They can agree or disagree with groupings until they have reached a common understanding of the ideas. ## Get quick AI-generated insights of individual health check comments It’s easy to feel overwhelmed by the amount of input when each team member provides detailed feedback. Our [AI-powered Summarization](https://help.teamretro.com/article/191-the-health-check-process-discuss) feature takes care of this by distilling comments into concise summaries. These instant summaries show you the key issues and to see the overall team morale at a glance, without missing out on individual comments. By having the essence of each comment captured, the facilitator can address main points quickly, keeping the conversations concise, while honoring individual contributions. ## Clear, customizable meeting summaries TeamRetro’s [AI-powered Meeting Summaries](https://help.teamretro.com/article/167-retrospective-share-step) bring retrospectives and health checks to a new level by providing a clear, concise overview of each session, including the outcomes and action items. This feature captures the main topics discussed, key themes, and the overall sentiment of the team, allowing people to see the big picture. Each summary highlights: - **Key Topics and Themes**: A quick glance reveals the top issues and successes, making it easy to track recurring themes across meetings. - **Sentiment Analysis**: Gain insights into team sentiment to understand overall morale and address underlying concerns proactively. - **Actionable Outcomes**: Summaries include key outcomes and action items, making follow-ups easy and ensuring issues are tracked over time. For added flexibility, facilitators can edit these AI-generated summaries to fine-tune details or emphasize specific points, speeding up the documentation process. Once finalized, the summary can be easily shared with the team, keeping everyone aligned and ensuring feedback leads to meaningful improvements. ## Get inspiration from automated AI suggested actions One of the most valuable parts of any retrospective is translating feedback into concrete action items. TeamRetro’s AI-Generated Action Suggestions simplify this by analyzing recurring themes and suggesting actions for your team to consider. Based on the feedback collected, TeamRetro’s AI suggests specific actions that address key issues. For example, if recurring feedback points to a backlog that is being overloaded or has not been reviewed and that user stories are not being well prioritized or managed, the AI might suggest setting up a structured backlog grooming process. Once actions are agreed upon and committed, they can then be assigned owners, priorities and deadlines or integrated into the team’s workflow. ## AI-powered vs human-powered retrospectives: creating the perfect balance While we do love what AI can do to support and enrich meetings, save on time and spark new conversations, we do also believe that it is most effective when it complements, rather than replaces, human facilitation. AI is the ally to the Scrum Master or Agile coach in leading engaging and productive discussions. ### Empathy and intuition: the human edge in retrospectives Scrum Masters and Agile Coaches bring empathy, intuition, and real-time adaptability that make retrospectives a space where team members feel comfortable and valued. While AI can efficiently process data and identify patterns, human facilitators create an environment where trust and engagement naturally thrive. They remain the eyes, ears, and perhaps the heart on the ground. While their AI companion churns away in the background, this gives them more capacity to scan the room and get a read of the room, and adjust the flow and energy as needed. Retrospectives often delve into deeper areas, including interpersonal dynamics and team morale. TeamRetro’s AI can highlight recurring themes, but it is the skilled facilitation of a Scrum Master or Agile Coach that helps guide these discussions with care and confidentiality. By combining AI-driven insights with the facilitator’s experience and adaptability, teams get the best of both worlds: fast access to data and a nuanced approach that ensures the discussion stays relevant and impactful. ## Tips for effective AI integration in agile retrospectives To help teams make the most of TeamRetro’s AI-powered tools, here are some practical tips for integrating AI seamlessly: 1. **Start Small** – AI doesn’t have to take over the whole process. It can simply be a workhorse for creating a final summary or just coming up with a new retro format. Introducing new workflows and features over time makes it easier to manage. 2. **Use AI suggestions as discussion prompts** – While teams can be impressed by the speed and accuracy of AI, such as grouping and offering suggested actions, this is also a good time to discuss and debate these prompts. As facilitators, this gives another opportunity to engage folks in critical thinking. 3. **Encourage better input**—AI can be an interesting way to see if the meaning and context of what people have written translate well into more summarized and aggregated formats. It can help be a litmus test for whether or not people have communicated their thoughts well enough to be understood by others. 4. **Make it your own** – Modify AI suggestions and outputs to what makes sense for the teams or individual. This little bit of sense-making will help people re-take ownership of the idea or action. 5. **Get feedback** – You could even run a retro on how AI impacts your team. Very meta! With the right balance between AI tools and human facilitation, TeamRetro’s platform empowers your teams to get more out of their retrospectives, driving continuous improvement and team cohesion. Ready to see how AI can transform your agile retrospectives? TeamRetro’s AI-powered tools make it easy to streamline your feedback process, identify key insights, and generate actionable steps. Start your journey with TeamRetro to create engaging, efficient retrospectives that drive continuous improvement every sprint. **[Try TeamRetro today](https://secure.teamretro.com/login/new)** and experience a smarter way to facilitate retrospectives! --- # 10 retrospective anti-patterns to avoid in 2026 for better team engagement URL: https://www.teamretro.com/blog/avoid-these-retrospective-anti-patterns/ Retrospectives are a cornerstone of Agile, enabling teams to reflect, learn, and improve continuously. But even with the best intentions, retrospectives can fall victim to anti-patterns—subtle, recurring practices that reduce their value. It can leave the team with a bitter distaste for what should be a meeting that is designed to empower and encourage positive change. As we enter 2026, let’s explore common retrospective anti-patterns, their consequences, and actionable solutions to ensure your retrospectives remain effective and engaging. ## 1. The “blame game” **What it looks like:** Team members use the retrospective as an opportunity to blame each other instead of addressing systemic issues, creating a toxic and unproductive environment. **Real-life example:** After a sprint with a failed deliverable, one developer blamed the testers for slow feedback, while the testers blamed incomplete stories. This led to arguments instead of solutions. **How to avoid it:** - Focus on processes, not people. Reframe personal attacks to encourage problem solving, not person blaming. - Remind people of the Agile Prime directive as needed. - Use tools like the 5 Whys technique to find root causes so that it moves the conversation forward. - Create a psychologically safe space as Esther Derby highlights in *Agile Retrospectives: Making Good Teams Great*. **Further Resources:** - [Esther Derby’s Blog](https://www.estherderby.com) - [How to Manage the BMW’s in meeting](/blog/how-to-manage-bmw-in-retrospectives/) ## 2. The team dysfunctions take over **What it looks like**: Underlying team dysfunctions such as mistrust, fear of conflict, or lack of commitment overshadow the retrospective. **Real-life example**: A team avoided discussing a critical defect issue due to fear of offending the lead developer. The problem then resurfaced multiple times, eroding trust and morale. The fear of saying anything only got worse over time. **How to avoid it**: - Address dysfunctions head-on using tools like Patrick Lencioni’s Five Dysfunctions of a Team model. - Use exercises like creating Team Agreements to establish norms for respectful and open communication. - Consider leveraging online retrospective tools like TeamRetro, which includes features to facilitate anonymous feedback, ensuring everyone can safely share their ideas. **Resources**: - [The Five Dysfunctions of a Team by Patrick Lencioni Exercise by Agile Mastery UK](https://agilemastery.co.uk/teams#049221d7-31c9-4a66-9ee9-69fb3abfb4a4) - [Creating Social Contracts with Team Agreements that Improve Culture](/blog/create-social-contracts-with-team-agreements-that-improve-culture/) - [Scrum.org – Creating a Team Working Agreement](https://www.scrum.org/resources/creating-team-working-agreement) ## 3. Lack of outcomes or action items **What it looks like**: Retrospectives end without clear, actionable next steps, leaving issues unresolved. **Real-life example**: A team repeatedly flagged poor sprint planning as an issue but didn’t create actionable steps to address it. The problem persisted, reducing the team’s trust in retrospectives and not understanding its value. **How to avoid it**: - Use the SMART framework to create specific, measurable, achievable, relevant, and time-bound action items. - Assign ownership to each action and follow up in the next sprint review. - Ensure follow-up on actions from retro to retro, celebrate wins, and monitor progress. **Resources**: - [SMART Criteria – Wikipedia](https://en.wikipedia.org/wiki/SMART_criteria) - [Action Tracking in TeamRetro](https://help.teamretro.com/category/184-tracking-actions) ## 4. The “groundhog day” retrospective **What it looks like**: Teams repeatedly discuss the same problems in every retrospective without resolving them. The question set is always the same, and responses are predictable, familiar, and static. **Real-life example**: For consistency, the same retro format was being used each sprint, and because of the nature of the product and job roles, the same repeated ideas and problems were coming up each fortnight. There didn’t seem to be any need for the retrospective. **How to avoid it**: - Prioritize and limit the number of issues tackled in each sprint. - Focus on a specific theme or an aspect of the sprint that allows the team to focus on their ideas. - Change the retro format or questions to explore different angles and perspectives. - Change who facilitates the meeting or invite an observer or external facilitator. **Resources**: - [Choose the best retrospective meeting template for your meeting](/retrospective-templates/) - [Scrum Paradigms: Chickens Vs Pigs – The Observer Role in Agile Meetings](/blog/scrum-paradigms-chickens-vs-pigs-the-observer-role-in-agile-meetings/) ## 5. Not having a clear process **What it looks like**: Retrospectives lack structure, leading to meandering conversations and missed opportunities for valuable insights. The meetings can go over time, or there isn’t the ability to have divergent and convergent thinking, discuss items in priority, or have meaningful discussions on individual items. The process changes each time, which also takes time for the team to relearn what needs to be done each time. **Real-life example**: Without a defined format, a team spent an entire retrospective debating tooling preferences, agreeing on a format and set of questions, and finding the right materials to start the brainstorming process, leaving no time to discuss sprint-related challenges. **How to avoid it**: - Use structured retrospective formats like Start-Stop-Continue or Sailboat retrospectives. - Define objectives before the meeting and use a facilitator to guide discussions. - Have [time-boxed](/blog/making-the-most-out-of-remote-retrospectives/) steps that go from opening the retro, reviewing the agile prime directive, reviewing previous actions, sharing the theme of the current process, and then having a clear process for ideation, prioritization, discussion, and action planning. ## 6. Skipping a retrospective **What it looks like**: Teams decide to skip retrospectives due to time constraints or assuming “everything is fine.” **Real-life example**: A team skipped retrospectives during a hectic product launch, believing they were unnecessary. Over time, unresolved issues piled up, causing delays and team frustration. **How to avoid it**: - Treat retrospectives as non-negotiable. They are essential for continuous improvement, even during busy periods. - Keep them short and focused if time is limited. - Remind teams of the value of retrospectives using data from past improvements. **Resources**: - [Benefits of Retrospectives – Mountain Goat Software](https://www.mountaingoatsoftware.com) - [Why Regular Retrospectives Matter – Scrum Alliance](https://www.scrumalliance.org) ## 7. The “hijacked agenda” **What it looks like**: Discussions veer off-topic, dominated by a single individual or unrelated issues. **How to avoid it**: - Politely redirect tangents and consider anonymous contributions to ensure inclusivity. - Park ideas that don’t relate to the current theme or focus of the retro. ## 8. Focusing on things outside the circle of influence and concern **What it looks like**: Team discussions revolve around problems outside their control or influence, such as company-wide policies or market conditions, leading to frustration and a sense of helplessness. **Real-life example**: In one retrospective, the team spent the majority of the time complaining about upper management decisions and market competition, leaving little energy or time to address internal processes they could actually improve. **How to avoid it**: - Use the Circle of Control, Influence, and Concern framework to help the team identify and prioritize issues they can control or influence. - Encourage reframing: “What can we do given these constraints?” - Redirect conversations back to actionable topics with gentle facilitation techniques. - Set boundaries early in the retrospective, clarifying what can and can’t be addressed. **Resources**: - [Circle of Control Exercise](https://www.dianalarsen.com/blog/2010/07/26/circles-and-soup/) – Diana Larsen ## 9. Lack of engagement and participation **What it looks like**: Team members are disengaged, offering superficial feedback or no feedback at all, often due to fear, boredom, or a sense that their input won’t matter. **Real-life example**: During a retrospective, participants responded with minimal comments like “All good” or “Nothing to add.” The facilitator struggled to draw out meaningful input, leaving the session unproductive. **How to avoid it**: - Build psychological safety by establishing ground rules and ensuring there are no negative repercussions for honest feedback - Use icebreakers or creative exercises to make retrospectives more engaging. - Provide opportunities for anonymous contributions - Vary the format to keep the team interested - Actively follow up on past feedback to show the team that their input is valued and acted upon. - Run a retro on your retro and ask the team about what they would like to see happen at the retrospective so that they can be more involved. - Show how past data and actions that have been followed through have helped lead to positive change to add value to the process. **Resources**: - Building Psychological Safety in Teams – Amy Edmondson - [Icebreaker Activities for Agile Teams](https://games.teamretro.com/) ## 10. The “boil the ocean” retrospective **What it looks like**: The team tries to tackle every issue raised during the sprint, resulting in an overwhelming and ineffective session with too many action items to manage. **Real-life example**: A team identified ten separate issues to address in one retrospective and attempted to solve all of them. They ran out of time, and none of the actions were followed through, leaving the team feeling overwhelmed and demotivated. **How to avoid it**: - Prioritize issues by importance and urgency using techniques like Dot Voting or an Effort-Impact Matrix. - Focus on a maximum of 2–3 key issues per retrospective to ensure actionable outcomes. - Keep a “parking lot” for less critical issues to revisit later. - Remind the team that continuous improvement is an ongoing process and doesn’t require solving everything at once, especially at the retrospective itself. By recognizing and addressing these retrospective anti-patterns, you can improve your effectiveness as a Scrum Master and create an environment where your team thrives. Tools like **TeamRetro** provide structured formats, action tracking, and feedback mechanisms to enhance your retrospectives and ensure they remain meaningful and productive. Start 2026 by empowering your team with retrospectives that drive real change. Stay curious, stay agile, and keep improving! 🚀 --- # Add background images & illustrations to your agile retrospectives (fun, easy, and engaging) URL: https://www.teamretro.com/blog/background-illustrations-to-make-your-retros-fun-as-well-as-easy/ You can now add a [background image or illustration](https://help.teamretro.com/article/317-backgrounds-and-illustrations) to your retrospective! That’s right, with the saying *“a picture is worth a thousand words”* as our inspiration, this new feature helps you set the mood, create a little fun and inspire your team. While words can be used to “describe” and “explain” illustrations can be used to “show”. Not only that, illustrations can also – - communicate concepts - evoke emotions - spark ideas Creating this new feature was the perfect excuse for us to collaborate with our friend and talented Illustrator, [Nelson Yap](https://www.instagram.com/nelson.yiap). Nelson created a number of illustrations based on our fun retro templates. Here are three of them here – *Hot Air Balloon Retrospective* *Three Little Pigs Retrospective* *Roller Coaster Retrospective* You can explore [more of Nelson’s illustration work](https://www.nelsonyiap.com). When adding background illustrations you can choose from – - TeamRetro’s background illustrations - a background photo - one of your own The background will only appear on your online retro, not exports and reports. If the image isn’t quite right for the [mode](https://help.teamretro.com/article/316-dark-mode-theme) you’re using you can always adjust its opacity. We hope these images help you establish a light mood that puts people at ease while appealing to the creative thinkers in your team. Read our guide on [adding a background image to your retrospective](https://help.teamretro.com/article/317-backgrounds-and-illustrations). Happy retro-ing! --- # The best collaboration tools for remote teams in 2026 (and the layer most stacks miss) URL: https://www.teamretro.com/blog/best-collaboration-tools-for-remote-teams/ Working across time zones, Slack threads, and async standups is the default now for most teams. But being technically connected and actually collaborating well are two different things, and the gap between them usually comes down to tools. In Zoom's 2025 research, [75% of employees said their organization's remote-work tools need an upgrade](https://www.zoom.com/en/blog/remote-work-statistics/). The right stack of remote collaboration tools won't fix every problem, but it removes the friction that makes distributed work harder than it needs to be. We've learned this first-hand. Our own team at TeamRetro is fully distributed, and it took us a while to see that having good tools for communication and delivery wasn't enough. The missing piece was always the same: a consistent, structured space to reflect, surface what wasn't working, and actually do something about it. That shaped how we think about collaboration tools, not just what keeps a team connected, but what keeps it improving. This guide breaks down the best collaboration tools for remote teams in 2026 by workflow stage: communication, project management, visual collaboration, and continuous improvement. Each section covers what the tools are actually for, so you can build a stack that supports your whole process, not just the obvious parts. ## What remote collaboration tools actually are Remote collaboration tools are software that lets a distributed team communicate, manage work, and think together, in real time or asynchronously, without being in the same room. A complete stack usually spans four layers: communication (Slack, Microsoft Teams, Zoom), project management (Jira, Linear, Asana), visual collaboration (Miro, FigJam, TeamRetro), and the reflection layer that ties them together (retrospectives and team health checks). Most "best tools" lists stop at the first three. The fourth is the one that decides whether a remote team keeps getting better or just keeps shipping. We'll get to why. ## What makes a remote collaboration tool worth adopting Before the specific picks, it's worth being clear on what separates a genuinely useful tool from one that just adds noise. The best ones share a few traits. **They reduce friction, not add it.** If your team needs a 20-minute orientation before they can contribute to a session, the tool is already working against you. Low setup overhead matters most for async contributors and occasional participants. We've seen teams abandon tools within a sprint because the join experience was too clunky. **They fit your existing workflow.** A tool that pulls everyone into a separate system tends to get quietly abandoned. Integration with what your team already uses, Jira, Slack, GitHub, is the difference between a tool that gets adopted and one that sits unused after week two. **They support both real-time and async work.** Distributed teams rarely share a clean nine-to-five. The best tools let people contribute when they're online and catch up when they're not, without losing context. This matters most for retrospectives, where async input before a session often produces more honest feedback than live contributions alone. **They create outcomes, not just conversations.** Meetings without clear actions and owners are expensive chats. Tools that build in decision capture, action tracking, and summaries let you actually see whether the issues raised last sprint got resolved this one. With those principles in mind, here's how to think about each layer of the stack. ## Communication tools for remote teams Communication is the foundation. Get it wrong and everything downstream suffers: misalignment, duplicated work, and the slow erosion of team cohesion that's easy to miss until it's already a real problem. ### Slack The de facto standard. Channels keep conversations organized by project or topic, and Slack integrates with almost everything else on this list, so it doubles as a workflow hub. The trick is channel discipline; too many and the signal drowns. **Best for:** Day-to-day messaging, async updates, and workflow notifications. ### Microsoft Teams The natural choice if you're already in Microsoft 365. Chat, video, and files in one place, with deep SharePoint, OneNote, and Outlook integration and the governance controls enterprise IT asks for. **Best for:** Enterprise teams with existing Microsoft infrastructure. ### Zoom Still the most reliable option for video, especially larger meetings and workshops. Breakout rooms are genuinely useful for facilitation; we use them in retrospective kick-offs so small groups can discuss before bringing themes back to the room. **Best for:** Video meetings, workshops, and all-hands sessions. Once your team has a communication layer, the next challenge is organizing and tracking work across people and time zones, and keeping it visible to everyone. ## Project management tools for remote teams Project management tools bring structure to distributed work: who owns what, what's in progress, and what's blocked. Without this layer, coordination happens in chat and work quietly falls through the gaps. ### Jira The most widely used project tool for agile software teams: sprint boards, backlogs, and reporting built for scrum and kanban, at the cost of configuration overhead. Connect [Jira to TeamRetro](/integrations/jira/) and retrospective action items push straight into the backlog, so nothing gets lost between the retro and the next sprint. **Best for:** Agile software teams managing sprints and backlogs at scale. ### Linear Jira's structure without the bloat: fast, opinionated, and clean enough that issue tracking stops feeling like admin. If your team spends more time maintaining Jira than shipping, it's worth a look. **Best for:** Product and engineering teams who want lightweight, fast issue tracking. ### Asana Strong for cross-functional teams, product, marketing, design, and ops, where work spans functions that don't all think in sprints. Timeline views, workload management, and goal tracking keep it coordinated. **Best for:** Cross-functional teams coordinating projects across departments. With communication and project tracking in place, most remote teams think their stack is complete. It isn't. There's a third layer that's almost always missing, and it's the one that unlocks actual collaboration, not just coordination. ## Online whiteboard tools for remote teams Communication tools keep people connected. Project tools keep work organized. Neither gives your team a shared visual space to think together, to brainstorm, map complexity, or work through ideas as a group. That's where online whiteboards come in. For agile teams they earn their place across a range of sessions: sprint planning, retrospectives, team health discussions, and process mapping all benefit from a space where ideas can be surfaced, grouped, and prioritized visually rather than typed into a list. The teams who get the most out of a whiteboard are the ones using it *during* structured sessions, not just for open brainstorming. When a whiteboard is connected to a facilitation process, with a clear purpose, a way to vote on priorities, and a path to action, it produces better outcomes than a blank canvas everyone adds sticky notes to and then never revisits. ### Miro Miro is the most feature-rich online whiteboard available, with a vast template library covering everything from customer journey mapping to org design. A strong choice for teams that need a flexible visual workspace for many use cases. The trade-off is that without a structured facilitation workflow, boards get cluttered and hard to act on. **Best for:** Teams needing a versatile visual workspace for diverse use cases. ### FigJam FigJam is Figma's collaborative whiteboard, and it's popular with design-adjacent teams. If your team already works in Figma, FigJam offers low-friction visual brainstorming without leaving the ecosystem. Sticky notes, connectors, and voting stamps also make it usable for lightweight retrospective-style sessions. **Best for:** Design and product teams already working in Figma. ### TeamRetro whiteboard TeamRetro's built-in [whiteboard](/retrospectives/) is purpose-built for agile ceremonies: not a general-purpose canvas, but a focused space for structured team sessions. The difference is that it connects directly to the [retrospective](/retrospectives/) and [health check](/health-checks/) workflow, so your team moves from brainstorming to grouping to dot-voting to action capture in one tool, without switching tabs. This matters more than it sounds. Many teams run a whiteboard separately from their retrospective tool, which means two setups, two links, two contexts to manage. An online whiteboard for retrospectives that's built into the facilitation workflow lets people add sticky notes at the same time, group similar themes through affinity mapping, and vote on priorities privately. The structure is already there, so the facilitator can focus on the conversation instead of the logistics. Teams tell us that removing that one moment of friction is what keeps people in the flow of the session rather than dropping out at the tool switch. **Best for:** Agile teams running retrospectives, sprint reviews, and collaborative planning where structure and outcome capture matter. ## Retrospective and team health check tools This is the layer most "best collaboration tools" lists skip entirely, and it's arguably the most important one for sustained team performance. Communication tools help your team talk. Project tools help your team ship. But what helps your team *improve*? How do you catch friction before it becomes frustration? How do you make sure distributed team members feel heard, not just assigned tickets? It's a live problem: in [Owl Labs' 2025 State of Hybrid Work report](https://www.owllabs.com/state-of-hybrid-work/2025), 61% of hybrid workers said they feel left out in meetings. That feedback loop doesn't happen by accident on a remote team. It needs a deliberate, structured space to surface what's working and what isn't, sprint after sprint. ### TeamRetro TeamRetro is purpose-built for [agile retrospectives](/retrospectives/) and [team health checks](/health-checks/), designed for remote and hybrid teams. Instead of a blank canvas, it gives you guided facilitation, so whether you're running a Start, Stop, Continue, a Mad, Sad, Glad, or a model like the Spotify Squad Health Check, the structure is already there. Your team shows up and focuses on the conversation, not the setup. What surprises teams most when they switch is the quality of the feedback. Independent voting means everyone submits their ideas privately before anything is revealed, so the loudest voice in the room doesn't shape what gets discussed. We've seen teams surface issues that had been invisible for months, simply because people finally felt safe writing them down without worrying about being singled out. Picture the difference in practice. On an open board, the first person to speak anchors the discussion and quieter people tend to agree rather than add. With independent voting, everyone writes and votes before anything is revealed, so a blocker that three people were silently working around lands as a top-voted item instead of staying unsaid. Same team, same sprint, a very different retro. > "TeamRetro helped our teams effectively manage retrospective meetings, even in a remote setup, saving time." > > **Václav Nidrle**, Trigama ([more reviews](/compare/reviews/))
The features that make it work for distributed teams: - **Independent voting** prevents groupthink. Team members add and vote on items privately before results are revealed, surfacing more honest feedback than open-board formats. - **200+ retrospective templates** covering formats from mood checks and futurespectives to full agile maturity assessments, plus community and AI-generated ones. Browse the [retrospective template library](/retrospective-templates/) to find the right one. - **Team health check models** track sentiment across dimensions like psychological safety, happiness, and goal alignment over time, not just as a one-off snapshot. - **AI-powered insights** group similar themes and highlight patterns automatically, so facilitators spend less time organizing and more time on the conversation. - **Action tracking** carries items forward from retro to retro, keeping the team accountable between sessions without manual copy-paste into Jira or Slack. - **Presentation mode** syncs screens across the whole team, in-person or distributed, so a facilitator can walk through results together without losing the room. There are other retrospective tools out there, but few are built specifically for distributed agile teams.
## How to build your remote collaboration stack The tools above don't work in isolation; they're most effective layered intentionally across your workflow. Here's how we think about building a stack that covers all four stages. **1. Start with one communication tool and commit to it.** The biggest mistake distributed teams make is proliferating channels. More tools doesn't mean better communication; it means more noise and more places for information to get lost. Pick Slack or Teams, set channel conventions, and stick to them. **2. Match your project tool to your team's complexity.** Jira for larger engineering orgs running multiple squads. Linear for smaller or faster teams where speed beats configuration. Asana when you're coordinating across functions that don't all think in sprints. **3. Get a visual space connected to your retrospective workflow.** A standalone whiteboard is useful. A whiteboard built into your retrospective process is better: less setup, less context-switching, and a natural path from brainstorm to action. For agile teams this is one of the simplest, highest-value upgrades you can make. **4. Don't skip the reflection layer.** This is where most remote teams underinvest. Shipping fast without a regular feedback loop accumulates team debt the same way you accumulate technical debt: slowly, then suddenly. A retrospective practice, run consistently, turns lived experience into real improvement. **5. Keep the stack lean.** The best remote collaboration stack is the smallest one that covers all four layers. Tool sprawl is a real cost: [Owl Labs found 64% of employees juggle too many communication tools](https://www.owllabs.com/state-of-hybrid-work/). Every extra tool is a new onboarding burden, a new notification stream, and another integration to maintain. Fewer, better tools beat a sprawling toolkit every time. ## Quick reference: the remote collaboration stack | Category | Recommended tools | Primary use case | Best for | | --- | --- | --- | --- | | Communication | Slack, Microsoft Teams, Zoom | Messaging, video, async updates | All distributed teams | | Project management | Jira, Linear, Asana | Task tracking, sprint management, roadmaps | Engineering and cross-functional teams | | Online whiteboard | TeamRetro, Miro, FigJam | Visual brainstorming, retrospectives, planning | Agile and design teams | | Retrospectives & health checks | TeamRetro | Continuous improvement, health tracking, action follow-through | Agile teams running regular retros | ## Final thoughts The best remote collaboration stack isn't a single tool. It's the right combination working together across every stage of how your team operates: one for communication, one for managing work, one for thinking visually, and one that creates the space to reflect and improve. Most remote teams have the first three covered in some form. The fourth is where the gap usually lives, and where TeamRetro comes in. It's the layer that ties the rest together, giving your team a structured space to surface what's working, fix what isn't, and keep getting better at collaborating, not just at staying connected. ## Frequently asked questions **What are the best collaboration tools for remote teams in 2026?** A complete stack spans four layers: communication (Slack, Teams, Zoom), project management (Jira, Linear, Asana), visual collaboration (Miro, FigJam, TeamRetro), and continuous improvement (TeamRetro). The best stack is the smallest one that covers all four. **What are the four types of collaboration tools?** Communication, project management, visual collaboration (online whiteboards), and retrospective or team health check tools. Most teams cover the first three and skip the fourth. **Do remote teams need a separate tool for retrospectives?** A purpose-built tool adds what a general whiteboard can't: independent voting, ready-made templates, action tracking between sessions, and health trends over time. You can run a retro on a blank canvas, but a structured tool produces better outcomes with less effort. **What's the difference between an online whiteboard and a retrospective tool?** A whiteboard is a flexible blank canvas. A retrospective tool wraps that canvas in a facilitation workflow, format, anonymous voting, grouping, and assigned actions, so the team moves from ideas to outcomes. ## Build the layer your stack is missing Most remote teams have communication and project tracking covered. The reflection layer is where the gap usually lives. Run your next retrospective in TeamRetro and see what surfaces when everyone gets a private, structured space to be honest.
--- # What makes the best icebreakers for teams? URL: https://www.teamretro.com/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/ No matter how many times they’ve raced before, athletes warm up their muscles prior to heading to the starting block. They don’t take their warm-up lightly. In fact, it’s the cornerstone of their race; helping to ensure they deliver peak performance when it counts and avoids unnecessary injury. Similarly, anytime groups of people come together to meet, a warm up in the form of an icebreaker can increase their focus and efficacy. Importantly, they can create and support tiny but vital fibers of human interaction within the context of the workplace. They build neutral spaces for social calibration in which colleagues may emit and receive subtle signals of inclusion and trust thereby nurturing an atmosphere of psychological safety. ## Why use icebreakers? You’ve probably got a massive backlog that keeps getting bigger, a calendar full of back-to-back meetings and it’s your turn to cook dinner. Well, the value that an icebreaker can bring to the team is hard to ignore – - A lot has been [written](https://www.thecut.com/2016/09/back-to-school-icebreakers-are-awkward-but-they-work.html) about the safety of the environment icebreakers help foster; they nurture spaces in which people are happy to share and are therefore better positioned to collaborate. - In fact, [research](https://books.google.com.au/books?hl=en&lr=&id=4ITxDwAAQBAJ&oi=fnd&pg=PA293&dq=the+psychology+of+icebreakers&ots=ZiG6p1rp_w&sig=mziSScGDw1Qu-AWEP7BWktNtN8A#v=onepage&q=the%20psychology%20of%20icebreakers&f=false) points to the common ground established by icebreakers improving the efficiency of distributed teams. and let’s not forget they’re fun and – - A [fun workplace](https://www.businessnewsdaily.com/9640-fun-at-work.html) seems to be the gift that keeps on giving (to all involved) as they support team cohesion and learning. Let’s face it – a fun place is one where people want to be! So, if you’re looking for a simple tool that nurtures a positive, safe, productive work environment – using icebreakers is the way to go. ## So, what makes an effective icebreaker? An icebreaker is a simple activity, undertaking, or game that helps people foster connections and build rapport. Importantly, they can create and support tiny but vital fibers of human interaction within the context of the workplace. They build neutral spaces for social calibration in which colleagues may emit and receive subtle signals of inclusion and trust thereby nurturing an atmosphere of psychological safety. ## Effective icebreakers adhere to the 3E rule, they are: ### Easy Keep them so simple that people could respond almost instantly. Keep the playing field level. It’s not a demonstration of knowledge nor expertise. All answers are correct. There are no scoreboards – everyone wins! ### Enjoyable This is a chance to bask in positivity, play, and have fun! The key ingredient is inclusivity. Yep – it’s recess time on that playing field and everyone is welcomed! ### Explainable Almost every word that is shared during an icebreaker can help to build a connection. So, giving people a chance to explain is giving people a chance to connect. The great thing is – it doesn’t stop there! Allowing people this time to tell their story gives your team safe points to connect beyond the icebreaker and continue to foster a sense of team. ## Tip from TeamRetro - Go first! Model the behavior you’re keen to see. - Show how easy the icebreaker is. Have fun. Explain what you mean. - Let your words build connections with your team then allow their words to do the same. - Always let people know in advance when you plan to use an icebreaker. - Surprises (no matter how well intended) aren’t always everyone’s cup of tea. To help get you started, we created a collection of [free online icebreaker games](https://games.teamretro.com/games) that you can use to run your next agile retrospective meeting or health check. Remote teams love quick rounds of [Two Truths and a Lie](https://games.teamretro.com/games/two-truths-and-a-lie) and [guess the emoji](https://games.teamretro.com/games/emoji-guess) to warm everyone up. --- # Top planning poker software for agile teams in 2026 URL: https://www.teamretro.com/blog/best-planning-poker-tools-for-agile-teams/ When estimation feels more like guesswork than a team effort, it’s time to rethink your approach. Agile teams do their best work with clarity, speed, and shared context. When estimating means a mix of opinions, gut feelings, and scattered tools, even a strong team loses momentum. Planning poker software fixes the mechanics — private voting, a shared reveal, and a number the whole team agrees on — so the conversation, not the loudest voice, sets the estimate. The tools below all do the core job. Where they differ is everything around it: whether they plug into [Jira, GitHub, or Linear](/estimations/), whether they’re free, and whether estimation lives on its own or alongside your retros and planning. This guide compares the current options — pricing and features **verified in July 2026** — and gives a clear pick for each situation. New to the technique itself? Start with our [agile estimation guide](/guides/agile-estimation-guide/). ## What to look for in a planning poker tool The best estimation tools don’t just collect votes — they help the team make a better decision and keep that decision where the work already lives. - **Real-time collaboration**: live voting, a simultaneous reveal, and room for discussion when estimates split. - **Integration**: does it connect to Jira, GitHub, Linear, or Slack — and does it write estimates *back*, or only import them? - **Customization**: can you match the deck and scale (Fibonacci, t-shirt sizes, custom) to how your team estimates? - **Reporting**: can you see where votes diverged and learn from it over time? - **Cost**: is there a genuine free tier, and does paid pricing scale by user, facilitator, or a flat fee? ## The best planning poker tools for agile teams ### 1. Free Planning Poker by TeamRetro TeamRetro’s Planning Poker is a free, real-time estimation room built to remove friction: share a link and start, with no account required. Cards stay hidden until everyone has voted, so no one anchors on the first number they see. **Key features:** - No sign-up — share a room link and estimate straight away - Anonymous voting with a simultaneous reveal to avoid groupthink - Lightweight, browser-based, built for remote and distributed teams - Graduates into [full TeamRetro estimation](/estimations/) — import from Jira, GitHub, or Linear and sync agreed story points back **Best for**: teams that want a frictionless free room now, and the option to bring estimation alongside their retros, health checks, and backlog sync later. **Pricing**: free forever, unlimited participants, no account required. New to running sessions? Our [planning poker guide](/guides/agile-estimation-guide/) covers how to facilitate a round, size work in [story points](/guides/agile-estimation-guide/what-are-story-points/), and [compare estimation techniques](/guides/agile-estimation-guide/estimation-techniques/). ### 2. PlanningPoker.com PlanningPoker.com is one of the longest-running branded rooms, with a clean interface and Jira import/export. Players join free; the game organizer pays for the paid tier. **Key features:** - Customizable decks and timers - Anonymous, real-time voting - Jira import/export of stories, estimates, and notes **Best for**: teams that want the familiar, established planning poker room with Jira import/export. **Pricing**: free for players; paid organizer plans — confirm the current price on their site. ### 3. Planning Poker Online Planning Poker Online (by We Agile You) is a polished paid room with real integrations and compliance credentials. **Key features:** - Real-time voting with visual results and sidebar issue management - ISO 27001 and GDPR compliance - Jira, Linear, GitHub, and Azure DevOps import (plugin or CSV) **Best for**: teams that want a structured, compliant tool and are comfortable paying per facilitator. **Pricing**: free plan (9 votings and 5 issues per game); Premium $30 per facilitator/month (or $300/year). ### 4. Planning Poker for Jira (Atlassian Marketplace) If your backlog lives in Jira, native Marketplace apps keep estimation in-platform and write story points straight to the issue. Popular options include Agile Poker and Planning Poker by Appfire. **Key features:** - Runs directly inside Jira, against your real issues and story-point fields - Multiple estimation methods (planning poker, async, magic estimation) - Estimation history and insights on the board **Best for**: Jira-centric teams that want estimates written back to issues without leaving Jira. **Pricing**: commercial apps priced on Atlassian’s per-user tiers (small teams often free); check each app’s pricing tab. ### 5. PlanningPoker.live PlanningPoker.live is a free, open-source room with genuine two-way sync and an AI facilitation twist. **Key features:** - Free and open-source, no sign-up, sync and async voting - Two-way Jira and Linear sync; start sessions from Slack - “PokerBot” AI session summaries (some AI features are credit-metered) **Best for**: open-source or privacy-minded teams that want free real Jira/Linear sync. **Pricing**: free; certain AI features use refillable monthly credits. ### 6. Zenhub Zenhub builds planning poker into a GitHub-native project-management suite, so estimation happens on the board you already use. **Key features:** - Planning poker and estimates inside your GitHub workflow - Sprint automation and velocity reporting - Deep GitHub integration, plus Slack and Figma **Best for**: GitHub-native engineering teams that want estimation in their actual PM tool, not a separate room. **Pricing**: free ($0, up to 50 users, 2 GitHub repos); Teams from $4.99 per user/month billed yearly ($7.50 monthly). ### 7. PlanITPoker PlanITPoker is a straightforward tool with a flat paid tier, popular with small teams. **Key features:** - Shareable-URL rooms with story management - Voting stats and distribution graphs - Story import via Jira XML or CSV **Best for**: small teams that outgrow the free cap and want flat pricing rather than per-seat billing. **Pricing**: free for up to 7 participants; Premium $20/month (flat) for unlimited participants. ### 8. Estimioo Estimioo is a modern, AI-forward tool with cheap flat pricing that also covers retros and standups. **Key features:** - AI-assisted story-point suggestions - Anonymous voting with an instant reveal - Jira integration on the paid tier **Best for**: teams that want AI-assisted estimation at the lowest paid price point. **Pricing**: free plan; Team $7 per workspace/month (flat, not per seat), adding Jira and more AI. ### 9. scrumpoker-online.org scrumpoker-online.org is a no-frills, multi-language free room that runs in a tab next to Jira. **Key features:** - Instant no-sign-up rooms, unlimited participants - Fibonacci, t-shirt, half-point, and custom decks - Six-language interface and QR-code sharing **Best for**: teams that want the simplest possible free, multilingual browser room. **Pricing**: free; Premium $40/year removes ads and adds a timer, auto averages, and a reusable room ID. **Note**: no project-tool integrations — it’s deliberately standalone. ### 10. planningpokertool.com planningpokertool.com is a minimalist, privacy-first free room with no accounts. **Key features:** - Completely free, no registration, unlimited participants - Multiple scales (Fibonacci, t-shirt, powers of two) - Sessions auto-delete after 24 hours **Best for**: a throwaway, privacy-first estimation room for a single session. **Pricing**: free (no paid tier). ## Comparison table | Planning poker tool | Best for | Pricing | Jira | | :-- | :-- | :-- | :-- | | **[Free Planning Poker by TeamRetro](/free-planning-poker-for-agile-teams/)** | A frictionless free room that graduates into full estimation | Free forever, unlimited participants | Yes — import and sync via [TeamRetro estimation](/estimations/) | | **PlanningPoker.com** | The established, familiar branded room | Players free; paid organizer plans | Import/export | | **Planning Poker Online** | Compliant, structured estimation | Free tier; $30/facilitator/mo | Yes (plugin/CSV) | | **Planning Poker for Jira** | Teams that live in Jira | Atlassian per-user tiers | Native | | **PlanningPoker.live** | Open-source teams wanting real sync | Free (open source) | Two-way sync | | **Zenhub** | GitHub-native engineering teams | Free tier; from $4.99/user/mo | Via GitHub | | **PlanITPoker** | Small teams wanting flat pricing | Free (7 users); $20/mo flat | XML/CSV import | | **Estimioo** | Cheap, AI-assisted estimation | Free; $7/workspace/mo | Paid tier | | **scrumpoker-online.org** | The simplest free multilingual room | Free; $40/yr premium | None | | **planningpokertool.com** | A private, throwaway free room | Free | None | ## Which planning poker tool is best for your team There’s no single winner — the right tool depends on where your work lives and what you need beyond a vote. - **You want free with zero setup**: Free Planning Poker by TeamRetro, planningpokertool.com, or scrumpoker-online.org. All run in the browser with no account. - **Your backlog is in Jira**: a native Marketplace app keeps estimates in-platform, or [TeamRetro estimation](/estimations/) imports Jira issues, runs the session as a team, and syncs the agreed story points back. - **You’re GitHub-native**: Zenhub keeps estimation on the board you already use. - **You want estimation alongside retros and health checks**: TeamRetro brings planning poker into the same place as your other agile ceremonies, so the decision and the discussion stay together. The best tool is ultimately the one your team keeps using. If that means a free room for now, start there — and when you want estimates to live alongside the rest of your team’s work, [TeamRetro](/estimations/) is ready when you are. Need help improving your team’s overall process? See how [Reward Insight used TeamRetro to measurably increase their agile maturity](/case-studies/reward-insight/). ## Frequently asked questions ### What is the best planning poker tool? There isn’t one best tool for every team — the right pick depends on where your backlog lives and what you need beyond voting. For a free, no-sign-up room, Free Planning Poker by TeamRetro, planningpokertool.com, and scrumpoker-online.org all work well. For teams in Jira, [TeamRetro’s estimation](/estimations/) or a native Atlassian Marketplace app keeps points in sync. For GitHub-native teams, Zenhub builds estimation into the board. Match the tool to your workflow rather than chasing a single winner. ### What is the best free planning poker tool? [Free Planning Poker by TeamRetro](/free-planning-poker-for-agile-teams/) is free forever with unlimited participants and no account required, and it graduates into full team estimation with Jira, GitHub, and Linear sync when you need more. planningpokertool.com and scrumpoker-online.org are also genuinely free, no-sign-up browser rooms; PlanningPoker.live is free and open-source with two-way Jira and Linear sync. Zenhub’s free tier includes planning poker for GitHub teams of up to 50 users. ### What is the best planning poker tool for Jira? Two approaches work well. Native Atlassian Marketplace apps run inside Jira and write story points straight to issues, priced on Atlassian’s per-user tiers. Alternatively, [TeamRetro](/estimations/) imports the Jira issues you’re planning into an estimation session, runs planning poker as a team, and syncs the agreed story points back — useful when you also want the discussion, retros, and health checks in one place. ### Do planning poker tools integrate with Jira? Many do. TeamRetro, PlanningPoker.com, Planning Poker Online, PlanningPoker.live, PlanITPoker, and Estimioo all offer Jira import or sync in some form, and the Atlassian Marketplace has several native planning poker apps. Integration depth varies — some only import a CSV of stories, while others write agreed story points back to the issue automatically — so check the direction of sync before committing. ### How much do planning poker tools cost? Most offer a free tier. Free options with no account include TeamRetro, planningpokertool.com, and scrumpoker-online.org. Paid plans range widely: Zenhub is around $4.99 per user per month billed yearly, PlanITPoker is a flat $20 per month, Estimioo is $7 per workspace per month, scrumpoker-online.org is $40 per year, and Planning Poker Online is $30 per facilitator per month. Native Jira apps follow Atlassian’s per-user pricing. Always confirm current pricing on the vendor’s own page before you buy. Ready to try it? [Run a free planning poker session](/free-planning-poker-for-agile-teams/) — no sign-up, no limits — or [see how estimation works in TeamRetro](/estimations/). --- # The best team health check tools in 2026 URL: https://www.teamretro.com/blog/best-team-health-check-tools/ A team health check tool is software that lets everyone on a team anonymously rate the same set of dimensions — delivery, psychological safety, workload, and so on — then track how those scores move over time and turn the gaps into owned actions. The best ones are owned by the team rather than by HR, keep individual ratings private so the honest answers surface, and make the trend across quarters as easy to read as the first result. That definition matters, because "team health check" gets used for three very different things: a purpose-built agile tool, a published framework you facilitate yourself (the Spotify squad model), and an org-wide HR engagement survey. They solve different problems, and picking the wrong category is the most common mistake. This guide sorts the real options into those three groups, tells you what each is genuinely good at, and gives a clear best-for pick. We build one of these tools, so treat us as a party with a view — but the comparison below is written to be useful even if you pick someone else. Every competitor fact here was checked against the vendor's own live pages in July 2026; pricing and features change, so confirm the current details before you commit. ## What separates a real health check tool from a survey Before the picks, four traits separate a tool that changes how a team works from one that just collects opinions. **Anonymous rating.** The moment people sign their name to a low score, the low scores dry up. Anonymity is the single feature that decides whether you measure what people think or what they are willing to say out loud. **Stable dimensions you can trend.** A health check is only worth running repeatedly if the questions stay the same, so the scores are comparable quarter to quarter. A tool that makes the trend easy to see — often as a team radar tracked over time — is doing the job; a one-off snapshot is not. **Action follow-through.** Scores that don't lead to an owned, dated action teach the team that being honest changes nothing, and the numbers quietly converge on a safe, meaningless 4. The tool should carry actions from one check to the next. **Fit with how the team already works.** For agile teams that means living beside retrospectives and integrating with Jira, Slack, and the rest of the stack, not pulling everyone into a separate HR system once a year. ## Category 1: Dedicated agile team health check tools These are built for a team to run its own health checks on a rhythm. This is the category most people mean by "team health check tool", and where the four traits above actually show up. ### TeamRetro — best dedicated agile team health check tool TeamRetro is a retrospective and health check platform built around exactly the loop above: anonymous rating, dimension-by-dimension discussion, trends across quarters, and actions tracked through to done. It ships 40+ ready-made health check models — including the [Spotify squad health check](/health-check-templates/squad-health-check/) — plus custom and AI-generated models, and several rating formats (numeric, Likert, happiness, and matrix scales). Results plot onto a team radar you can trend over time, comments summarize automatically, and actions carry owners and due dates from one session to the next. For organisations running many teams, cross-team reporting rolls the picture up without turning scores into a league table. Where it fits: agile teams and coaches who want the whole health-check loop in one place, and who usually run retrospectives too. It is a paid product (with a free trial), so a team that only wants a one-off facilitated workshop with no software may be better served by the free framework in Category 2. **Best for:** teams that want a dedicated, anonymous, trend-tracking health check that lives next to their retrospectives. ### Echometer — best for a psychology-grounded approach Echometer (echometerapp.com) positions itself around psychology-based retrospectives and health checks, spun out of a university psychology faculty. Its health check draws on a large library of items (the vendor cites 200+) across dimensions like psychological safety, team maturity, agility, morale, and eNPS, and it records the long-term development of a team automatically. It also covers 1:1 meetings, which the others here mostly don't. **Best for:** teams that want a research-flavoured question bank and don't mind a smaller, more specialised tool. (Some of Echometer's impact figures are vendor-reported — worth reading as marketing, not independent evidence.) ### Parabol — best open-source and check-in-style option Parabol is primarily an agile meeting tool — retrospectives, sprint poker estimation, standups, and check-ins. Its team health check runs as an anonymous check-in round, usually inside a retro, where people register mood and engagement, and it can track that mood over time. It is lighter than a dedicated multi-dimension health model, but it has one thing none of the others do: Parabol is open source (AGPL-3.0) and self-hostable, which matters for teams with strict data or air-gap requirements. **Best for:** teams that want health as a light check-in inside their retros, or that need a self-hosted, open-source option. ### Neatro — best simple retro tool with a built-in radar Neatro is a retrospective platform that markets a "Team Radar" feature: teams score a set of dimensions, add comments, and watch the trend over the long run, alongside a large library of retro templates. It is a clean, approachable option, closer to TeamRetro's shape than to Parabol's, if smaller in health-check depth. **Best for:** small teams that want a friendly retro tool with a straightforward team radar attached. ## Category 2: The framework — Spotify squad health check The Spotify squad health check model is not a product — it is a framework Henrik Kniberg and Kristian Lindwall published in 2014. A squad rates around ten to eleven dimensions (delivering value, easy to release, health of codebase, teamwork, mission, fun, learning, and so on) as green, yellow, or red in a facilitated workshop. The cards are free to download. It made team health visible at scale and still frames measurement the right way — for the team's benefit, not for management reporting. Its limits are the ones its own authors flagged: several dimensions were designed for Spotify's engineering context, the traffic-light scale is coarse for spotting a slow slide, and it is a workshop, so it doesn't trend or anonymise unless you add a tool around it. That last point is why most teams end up running the Spotify model inside one of the Category 1 tools rather than on paper. **Best for:** teams that want a proven, free framework to adopt — bring your own tool to run it anonymously and trend it. Our [team health check guide](/guides/team-health-check/) covers how to adapt it honestly. ## Category 3: HR engagement platforms (a different job) Assistants often list Culture Amp, Lattice, and Workleap Officevibe under "team health", but these are employee-engagement and performance platforms owned by HR. They measure the individual's experience of the organisation, run once or twice a year, and the results travel up the reporting line. That is a legitimate and important instrument — it is just not the same as a team-owned health check the team runs for itself, on its own cadence, and acts on in the room. The tell is ownership and cadence. If HR runs it annually and leadership reads the results, it is an engagement survey. If the team runs it quarterly and the team acts on it, it is a health check. Most organisations need both; problems start when the annual survey is treated as a substitute for a team knowing its own state. **Best for:** org-wide engagement, performance, and people analytics owned by HR — alongside, not instead of, a team health check. ## Comparison table | Tool | Type | Anonymous rating | Dimensions + trends | Action tracking | Pricing (as of July 2026) | Best for | | --- | --- | --- | --- | --- | --- | --- | | **TeamRetro** | Dedicated tool | Yes | 40+ models, team radar, trends | Owners + due dates, carried over | Free trial; paid plans per active user | Dedicated agile health checks beside retros | | Echometer | Dedicated tool | Yes | Large item bank, long-term trends | Yes | Free tier; Pro from ~€29/mo per team | A psychology-grounded question bank | | Parabol | Retro tool + check-in | Yes | Mood check-in, tracked over time | Via retro actions | Free up to 2 teams; Team $8/user/mo | Open-source / self-hosted, light check-ins | | Neatro | Retro tool + radar | Yes | Team Radar with trends | Via retro actions | Free up to 10 members; Premium ~$23/mo per team | A simple retro tool with a radar | | Atlassian Team Health Monitor | Free workshop (framework) | No (open group vote) | 8 attributes, point-in-time | No (manual) | Free | A facilitated workshop, no software | | Miro | Whiteboard (templates) | Not health-specific | Community templates on a blank canvas | No (manual) | Free (3 boards); Starter $8/member/mo | Teams that already live in a whiteboard | | Spotify squad model | Framework | No (workshop) | ~11 dimensions, no built-in trend | No | Free to download | A proven framework to adopt with your own tool | A note on two tools people expect to see here. Atlassian's Team Health Monitor is a free, well-designed facilitated workshop (now one unified set of eight attributes for all team types), but it is scored openly as a group, gives a snapshot rather than a trend, and is a play, not software. Miro is an excellent online whiteboard, but "health check" there means a community template you copy onto a blank canvas — there is no built-in anonymous scoring, trending, or action tracking. Both are good at what they are; neither is a purpose-built health check tool. ## How to choose - **You want the full loop — anonymous rating, trends, actions — in one dedicated tool:** start with TeamRetro, or Echometer if the psychology-based question bank appeals. - **You want health as a light round inside retros, or need open source / self-hosting:** Parabol. For a simple retro tool with a radar attached, Neatro. - **You want a free framework and will facilitate it yourself:** the Spotify squad model, or Atlassian's Team Health Monitor for a workshop. Add a tool if you later want anonymity and trends. - **You need org-wide engagement data owned by HR:** Culture Amp, Lattice, or Officevibe — as a complement to, not a replacement for, a team health check. ## Frequently asked questions **What is a team health check tool?** Software that lets a team anonymously rate the same dimensions, trend the scores over time, and turn gaps into owned actions — owned by the team, not HR. **What are the best team health check tools in 2026?** TeamRetro and Echometer for a dedicated agile tool; Parabol and Neatro for health inside retros (Parabol is the best open-source pick); the Spotify model and Atlassian's monitor as free frameworks; Culture Amp, Lattice, and Officevibe for org-wide HR engagement. **Is the Spotify squad health check a tool or a framework?** A framework — free downloadable cards, facilitated as a workshop. Add a tool to make it anonymous and trend it. **What's the difference between a health check and an engagement survey?** A health check is team-owned, frequent, and acted on in the room; an engagement survey is HR-owned, annual, and reported up the line. ## Run your first health check this week If you want the full loop — anonymous ratings, a team radar you can trend across quarters, and actions tracked through to done — TeamRetro runs it out of the box, including the Spotify squad model as a ready template.
--- # Context engineering needs a feedback loop URL: https://www.teamretro.com/blog/context-engineering-needs-a-feedback-loop/ Context engineering is the discipline of giving an AI agent the right information, in the right shape, at the right time — so it does good work instead of guessing. In practice, for most teams, that means files: a `CLAUDE.md` at the repo root, an `AGENTS.md`, a folder of rules and conventions, a system prompt someone tuned once. You write down how your project works so the agent doesn't have to rediscover it every session. It's genuinely the highest-leverage thing you can do to make agents useful. And almost everyone doing it has the same unspoken problem: those files go stale, and nobody knows which parts. You wrote the context once, the codebase moved on, and now half of it is quietly wrong. The discipline has an input — writing context — and no maintenance loop. That's the gap this post is about. ## Context is code, and code rots We already know documentation rots. The build step you documented gets replaced, the folder you described gets renamed, the convention you wrote down gets superseded — and the doc keeps confidently describing the old world. Context files are worse than ordinary docs on this, for two reasons. First, **an agent reads them literally and acts on them.** A human skims a stale README, senses it's off, and asks someone. An agent takes `CLAUDE.md` at its word. If it says "run `make setup`" and that target was deleted last quarter, the agent doesn't shrug — it burns time trying to make the wrong thing work, or it invents a workaround and moves on, carrying the bad instruction into its output. Second, **incorrect context is worse than missing context.** A gap, the agent can sometimes reason around or flag. A confident wrong statement, it trusts. The most expensive lines in your context files aren't the missing ones — they're the ones that used to be true. So you need a maintenance loop. The trouble is the usual candidates don't work. You won't audit `CLAUDE.md` line by line on a schedule — nobody does. You won't notice it's stale from the outside, because it reads fine. The staleness only reveals itself at the moment of use, to whoever is using it. And increasingly, whoever is using it isn't a person. ## The one witness who knows Here's the shift. The agent that just ran a session against your project is the only participant that knows, concretely, which parts of your context helped and which parts lied to it. It just used the files. It hit the stale build command. It found the folder that doesn't exist. It followed the pattern that turned out to be three patterns. That knowledge exists — for about as long as the session does, and then it's gone. Nobody tells you which context is missing or wrong, except the thing that just suffered from it. That's the feedback loop, sitting right there, unclaimed. All you have to do is ask the agent to write down what it learned before the session closes — and structure the ask so the output points straight at the files that need editing. ## The session retro log is the maintenance loop This is exactly what an end-of-session AI retro produces. At the end of a working session the agent writes a short, honest entry: what went well, where it hit friction, and — the part that matters here — every friction item is tagged with one of ten fixed root-cause labels and ends with a ticket-sized "→ Fix:". Two of those ten labels are pointed directly at your context files: - **`missing-documentation`** — the agent needed something the project should have documented, and didn't. This is your context file's *to-write* list. Every one of these is a line you should add to `CLAUDE.md` or your docs. - **`incorrect-documentation`** — the docs existed but were wrong or out of date. This is your context file's *to-fix* list. Every one of these is a stale line the agent caught the only way it can be caught: by using it and hitting the wall. Add a third and you've covered most of the maintenance you'll ever need: **`ambiguous-instruction`**, where a brief or a rule could be read more than one way. That's the loop. You don't audit your context files on a calendar; you let the agents that use them tell you, in the moment of use, exactly which lines to change — with the evidence attached, because the practice is evidence-cited only. And there's a fourth signal that's easy to miss: **the guesses.** A good entry lists every point where the agent filled a gap with an assumption. Each guess is a place your context was thin enough that the agent had to invent an answer. Read a week of guesses and you have a to-do list for your context files that you could never have written yourself — because you already know the answers, and so you can't see where they're missing. Here's the shape of what comes back — an illustrative example, not real data: ```markdown ## Friction - CLAUDE.md says "run `make setup`" but that target was removed; the actual setup is `pnpm install && pnpm db:migrate`. Lost ~10 min. (incorrect-documentation) → Fix: Update the "Getting started" block in CLAUDE.md to the pnpm commands. - Nothing documents that integration tests need the worker running. Found it by reading the CI config. (missing-documentation) → Fix: Add a "Running tests" note naming `pnpm worker` as a prerequisite. ## Guesses I made - Assumed the `api/` package is the public surface and `internal/` is not, because nothing states it. Please confirm before I rely on it again. ``` Every line there is a specific edit to a specific file. That's a maintenance loop a person will actually run, because the work of finding the problem — the expensive part — is already done. ## Why this beats auditing by hand You could try to keep context files fresh the old way: schedule a review, read them top to bottom, check each claim against reality. It doesn't happen, and even when it does it's the wrong instrument. Reading a doc in the abstract, you can't tell which lines are stale — they all read plausibly. The staleness is only visible under use. The retro log is context maintenance *driven by real use*: only the lines that actually tripped an agent get flagged, so you fix what's genuinely broken instead of re-reading what's already fine. It's the difference between a smoke detector and walking the building sniffing for smoke. It also compounds. Fix the `incorrect-documentation` items this week and next week's sessions hit that wall less, so the log gets shorter and shifts to deeper issues. Your context files trend toward accurate not because anyone audited them, but because the people — and agents — using them had a cheap, structured way to report the drift. That's healthy human-AI collaboration: the agent surfaces the drift, the human decides the edit. ## Start the loop If you're already investing in context engineering, this is the missing half — the maintenance loop that keeps the investment from rotting. It's open source and MIT-licensed: - **Get the skills and prompt pack:** [github.com/TeamRetroHQ/teamretro-skills](https://github.com/TeamRetroHQ/teamretro-skills) — a Claude Code skill that writes the end-of-session entry, one that synthesizes entries into a brief, and a tool-agnostic prompt pack for Cursor, GitHub Copilot, or any agent you can prompt. - **See the full practice:** [how to gather feedback from your AI agents](/blog/gather-feedback-from-ai-agents/) covers all ten labels, the human sanity-check, and how the entries feed [a team retrospective](/retrospectives/) — not just your context files. - **Go deeper on the loop itself:** [agent feedback loops](/guides/ai-agent-retrospectives/agent-feedback-loops/) maps the whole landscape — the capture-to-fix loop, the tools that run it, and where a session retro fits. One nuance worth keeping. When an agent reports the docs are wrong, check before you edit — sometimes the docs are right and the agent misread them. That's still a useful signal (a line easy to misread is a line worth rewriting), but it's a different fix, and it's why a human stays in the loop. The agent is a participant flagging what tripped it, never the authority on what your project should say. Your context files are only as good as their last honest correction. The agents using them are handing you those corrections at the end of every session — you just have to write them down. And if your team wants those fixes to land somewhere people already look, the agent can prepare its recommendations and post them onto your board itself via the [TeamRetro MCP server](/mcp/) — confirmed by you, marked `[AI retro]`, next to the rest of your team's improvements. --- # Create your team’s social contracts with effective team agreements URL: https://www.teamretro.com/blog/create-social-contracts-with-team-agreements-that-improve-culture/ Often used by agile teams, a social contract paves the way for everyone in the team to work together better. They list the agreed ways a team will behave with each other. Typically, without a clear agreement, there’s often a lack of clarity as to how team members should interact. Let’s face it, working together is challenging. Whether your team is new (forming and storming) or a seasoned group (performing and adjourning), working with others requires effort. Different personalities, backgrounds, and the company’s ethos influence how a team performs. Innocent actions of one person can easily frustrate, distract, or annoy others. While one team member may be very chatty during meetings, another may find that rude. Even behaviors with positive goals such as recognition of effort might be missing the mark. How people interact in a meeting defines culture. From raising an opinion and being heard without judgment through to whether or not you turn the video camera on during the discussion. All form part of the norms that define the culture of a team. One of the ways to build a positive culture is to address issues and create team agreements. ## What are team agreements for agile teams? Team agreements are the behaviors that a team promises to demonstrate when working with each other on a daily basis. They can cover a number of workplace contexts including – - decision making - meetings - communicating - information sharing - supporting each other These are the ground rules for behavior. They make it psychologically safe for everyone to participate as a team. Here, psychological safety means that team members can share their ideas without the fear of judgment, bias, status, or authority. This allows people to focus on a project rather than worry about surviving socially. Team agreements are usually created at the start of the project by the team. They can include things such as: - Using the [agile retrospective prime directive](/guides/scrum-masters-retrospective-guide/what-is-the-retrospective-prime-directive/) as part of retros - Everyone has an equal voice and is a valuable contributor. - If you are assigned a job, you should own the task and keep it up to date. - Complex tickets should be discussed with the person before simply being assigned. - Use of code words to indicate a need. - Clear meeting cadence and purpose. - How the team communicates and works remotely, with flexible hours, or different time zones. ## The benefits of team agreements There are plenty of benefits of having team agreements. They – - help reduce team conflict. - help people better manage stress and anxiety. - lay the foundation for cooperation, collaboration, and continuous improvement. - build trust and help create belonging. - give the team a sense of control and security. - build relationships within the team - help move the team through the Tuckman team development model. So done right, team agreements can amplify the greatness of your team. ## How to create team agreements? Unsurprisingly, creating team agreements is best done with the team. It’s a collaborative process. It can be done manually in person with sticky notes. It can also be done online with a good retrospective tool. The advantage of an online retrospective tool is the ease with which input can be kept anonymous. Again, this is to foster a psychologically safe environment in which people can share their ideas. ### 1. Explain the need The first step is to explain the need for creating the team agreement. Most people will already understand the rationale but it’s a good reminder nevertheless. You can set aside some time at the start of your retrospective or have a specific meeting to talk about this. The benefits of having a team agreement include – - having a way to define and improve the team’s culture - having clear and defined ways of working with each other successfully - knowing the expectations of each other and having a working understanding - being generally happier at work when the team gels ### 2. Create individual accountability Next, ask everyone to type in a positive behavior they think aligns with the organization, their team, and themselves. This is what makes the agreement unique to their team and creates buy-in. When getting people to brainstorm and add ideas, it can be helpful to give them a few sentence starters. This helps ensure that the agreements are behavioral-based and are framed in a positive way. Here are a few suggestions – - You can count on me to ________________ - We can be a great team by ________________ - We can overcome some of our frustrations and issues by ________________ - One thing I love about this team is when ________________ - We can improve the way we work by ________________ Each point of the agreement should be a standalone concept to keep it simple. ### 3. Propose agreements for discussion Generally speaking, it’s a good idea to have people [propose an agreement](https://help.teamretro.com/article/266-team-agreements) before it is accepted. This ensures that everyone understands and genuinely accepts the agreement as opposed to it simply being a box-ticking exercise. An online tool such as TeamRetro allows you to have the option to either have people add agreements directly to a list or to propose them to the group. If an agreement is proposed everyone else can then choose to support it (thumbs up), not support it (thumbs down) or remain neutral. This allows you to quickly see if there is consensus within the group before it is confirmed as an agreement. ### 4. Facilitate group discussions Once the agreements have been shared, give everyone a chance to read through them and ask clarifying questions. You can group identical items if need be. Facilitate a discussion and allow concerns, questions, and comments to be explored. Objections should be noted. Then decide upon which to include by voting. Not all proposed agreements will be accepted. Talk these through with the group to ensure it’s understood why that was the case. The goal is to work through all the proposed agreements before closing the meeting. The proposed behaviors that are accepted are the team agreements that form the social contract. ### 5. Reflect on the agreements Once the agreements have been added to the list, it’s a good idea to review them. Get further comments and address any new concerns that may have come up. A good question to ask can be – “When looking at our team agreements, how do we think it will impact the way we work together, and how does that feel?” The feedback informs any final revisions the agreements may need. ### 6. Use the agreements Finally, at the start of future meetings, it’s a good idea to quickly reference the agreements to help set the tone for your session. Alternatively, you can use it as a reflection at the end of the meeting to see if the team stuck to their agreements. TeamRetro displays team agreements on your dashboard. This means they are always at your fingertips. ## Traps to avoid when creating team agreements ### 1. Lack of real consensus The most obvious trap is when not everyone in the team truly commits to the agreements. Head nodding at the collaboration meeting can simply be that. People first need to understand before they buy-in. This means that the agreement has to make sense to them, as well as align with their values. As we’ve touched on before, this is also why each team has to come up with its own set of agreements. Borrowing or piggybacking another team’s agreements does little to improve traction. It will only serve to reduce the sense of ownership. If the agreements are pushed down from top-level management, this can increase the disconnect. Having ample time to talk through concerns and address them before making them part of the final agreement is important. ### 2. No rituals The agreements then need to translate into actions and daily rituals. If not, they are simply words on a page. There may be different interpretations of the agreements. This would lead to differences in behaviors. One way our team has managed this is to come up with code words. The code words summarize our team agreements. Here’s a sneak peek at what we do. - Cross-check- Team members agree that for critical, customer-facing actions a cross-check is required. A colleague of a similar role and skill will quality check and vet the work to verify accuracy. - Sushi time – We love having fun at work. Sometimes a bit too much. If someone says ‘sushi time’ they are asking to have focussed work time. Because we have agreed to it, no one is offended, and we quickly quieten down. - Bikeshed – If a topic comes up that cannot be resolved immediately then that topic is parked. The topic is put in the “bikeshed” and taken out again later for discussion. ### 3. Blame and shame Team agreements can be used inappropriately. In other words, they can be used to attack or finger point. As a scrum master, it is important to ensure that people feel safe at work. Fear has no part to play. People need to be able to own their mistakes as part of their continuous improvement. There is an effective way to manage the misuse of the agreements. Ask people to pinpoint good examples where others have demonstrated positive behavior. However, have them reflect on themselves when asking which agreements they can improve upon. ## How to make team agreements stick? ### 1. Lead by example As a scrum master, it’s important for you to demonstrate the behaviors in the agreement. If you start to stray, so will the team. Make it clear that you would like someone to nudge you if you start to head off track and that you will do them the same for them. ### 2. Keep them in view Make the agreements as visible as possible. You can publish the list to Slack or MS Teams. It doesn’t matter how you do it, it’s all about reminding people of the behaviors they agreed to. ### 3. Revisit and revise Over time, your team will change and so will the environment you work in. So your agreement should change too. Having a regular cadence to revise and update the agreement will make the agreement more meaningful and keep it current. ### 4. Different teams, different agreements Don’t be fooled. Each team is different, even if they have similar roles. Make sure that each team has their own agreements that are unique and that works for them. ### 5. Acknowledge and recognize Teams that demonstrate the behaviors they committed to are worth their weight in gold. Recognizing the efforts of the team regarding the agreements will help reinforce that great behavior. ## Ready to create a team agreement? TeamRetro lets you run online agile retrospective and health checks easily and effectively. It lets you create [team agreements](https://help.teamretro.com/article/266-team-agreements) that you can refer to in future meetings. Agreements can be proposed by the team members anonymously and safely. Team members can indicate their support for agreements before they are accepted. Help make your teams go from good to great today! #### Create a team agreement now --- # Creating positive working relationships between the product owner and agile retrospective team URL: https://www.teamretro.com/blog/creating-positive-working-relationships-between-the-product-owner-and-agile-retrospective-team/ The relationship between the Product Owner, Scrum Masters and Developers is critical to an Agile Team’s success. It’s a symbiotic relationship that relies on clear communication, aligned goals, transparency, and is founded on trust. Building a product that is widely adopted or continuous improvement is the usual goal, but the cohesion and dynamics of the team can determine how smooth and pain-free that process is. We wanted to learn more, so we went out to find a Product Owner to share their insights and stories. Following his product roadmap presentation at the Perth Agile MeetUp, we sat down with Adam Mullett, author of the book [*From “No” to “How?: Get Buy-in and Lead Change*](https://from-no-to-how.square.site/) and a Product Owner to ask him for his take on the level of involvement a Product Owner should have in a retrospective. What we got was more than just an answer to a question, but a demonstration of the role of the Product Owner and a renewed appreciation of trust, transparency, and discipline. ## The relationship between Product Owner, Scrum Masters, and agile team Adam seemed somewhat taken aback when asked if a Product Owner should be involved in the retrospective. The question stemmed from the observation that some people involved in agile perceived the presence of the Product Owner at the retrospective as optional, or even a hindrance. After only a brief pause, his response was an emphatic “yes!” He went on to outline ‘why’ – One of the important aspects of Agile is that it is not about being fast, but about being adaptable- which leads to more success, such as better adoption of a product. When it comes to running a team’s retrospectives, not only is it important to facilitate the process but it’s equally important to manage the culture. The team relies so much on the direction and the input of the Product Owner as a subject matter expert. The Product Owner fosters an environment in which a can team can strive to be high performing, being responsible for outcomes, and self-managing so that they remain accountable to their stakeholders. ## Trust and transparency Adam perceives that fundamental to the fabric of a Product Owner is trust and transparency. “For me, being transparent is a gift because you are sharing what you think or what you know. If the team can’t get that out of you, then you aren’t giving them what they need to make them successful.” “There should be no secrets between the team, the Scrum Master, and the PO. For me, I would zero in on those things. I’d rather raise the issue and dive into conflict rather than leave it to fester.” “Being able to discover something that is stopping a team from going forward is really valuable.” Adam offered an example of two team members who weren’t talking to each other in a team he once coached. “It was unfathomable! So, if there was a comment connected to the issue made during the retrospective, I would keep diving in, drilling down into the ‘why’, until they realized that their lack of communication was the problem.” Although the approach was somewhat confrontational, once the issue was brought to the fore it was easier to address, and team members were later thankful the matter had been sorted. “Sorting out these types of issues could be as simple as offering different working hours. Not talking to another was simply not a good reason to not be a high-performing team. “ ## Bring people into the conversation A Product Owner should keep collaboration front of mind, which is why Adam aims to co-create. “If I’m doing something, I want to do it with you, not to you. No change will ever be successful if you’re doing it alone” “Because team collaboration is needed for co-creation to take place, it’s important to know how and when to bring people into the conversation. Choosing the way conversations happen can make a big difference.” “For example, it’s easier to show someone your work, rather than having to convince them. A one hour prototype that you can talk to is much more effective sometimes than a big planning session where you are trying to sell your idea. Other times it might be better to co-create.” ## Be disciplined with process and outcomes When discipline is viewed as a platform of support rather than a barrier to flexibility, it can act as a mechanism of team empowerment. Discipline can be as simple as starting a meeting on time, finishing on time, and having a strict definition of ‘ready’. They are the small, agreed behaviors to which team members adhere with a view to mindfully improving team cohesion and respect. It’s Adam’s view that with discipline, healthy habits can be fostered that support high functioning teams. “I was a Product Owner in a project where there were 23 teams and a general mindset of getting through this sprint, then another sprint, and another sprint, and so on, just get through the sprint however we could.” “Then we started to become more disciplined in the sprint.” “Yes, it was tough in the first month because we were trying to do two things at once. But after that, it was smooth sailing. And the team was able to continue improving and growing as a high-performing team. In fact, others in the organization were wanting to be part of that team.” It was also observed that the teams that lacked discipline would experience problems. So what should happen if team members didn’t embrace a disciplined approach? “If someone comes unprepared, then it’s important to make the purpose of the meeting clear and how their actions do not support that purpose.” “It’s about focus. During product grooming, for example, if people start to talk about a particular ticket, then it’s about bringing the focus back to why we are having this meeting and what we are aiming to achieve as an outcome for that ceremony.” Of course, the Scrum Master helps keep this discipline. In terms of their retro, Adam added that once a team understands and appreciates the structure their discipline has built, they are far more focused and efficient, without having to engage in System 2 thinking, as described in the book [Thinking Fast and Slow](https://mlsu.ac.in/econtents/2950_Daniel%20Kahneman%20-%20Thinking,%20Fast%20and%20Slow%20\(2013\).pdf) by Daniel Kahneman. “Having a clear process keeps things easy. Teams don’t want to have to worry about things such as which room or which technology they are using. Their focus is on the actual problem.” ## Build up your team as they build solutions As far as Adam is concerned, there is no lack of clarity as to the role of the Product Owner; if you are a Product Owner, you are part of the agile team. “I feel like it’s the Product Owner’s role, with support from the Scrum Master, to build the culture and create clarity for the team.” “Teams hate not knowing where they are going. They turn on each other, they get antsy, they try to look busy, and all sorts of other dysfunctions. If you can give people a reason, a ‘why’, a strategic direction, then they will say ‘okay, cool. Got it!’ So it’s about being loosely coupled but tightly aligned. That way we all know where we are going then allow the team to get there.” Adam has worked with fully in-person, remote, and hybrid teams. For 18 months, he worked with people spread from Sydney through to India. No matter the make-up, one of the success factors of a high-performing team was the understanding of what would happen next. “So if one thing happens in our retrospective, then someone would go off to create a ticket in Jira. People could still work together even if they weren’t always in the same room. Having strong ways of working helped to accommodate that”. ## The role of the product owner in an agile retrospective Circling back to the question of the role of the Product Owner in the retrospective, Adam noted the Product Owner is a participant. In his opinion, the retrospective itself can be run by anyone in the team, with his preference that the facilitation be rotated among team members so that those skills can be developed and appreciated by the team. “I think the team wants the PO to be honest and to be open as they participate” In terms of what a product owner hopes to help achieve at a retro, Adam’s response is simple – it’s for the team to get better at what they are doing. Why? “Because the PO is accountable for outcomes to the organization in terms of how long something took through to resources used. The team is responsible for delivering the outcomes. So the Smart PO will attend the retrospective to listen. They won’t tell people what to do, or that they should do it “this way”. If the team already knew, they would have done it.” Adam views the retrospective as an opportunity for the team to – 1. discover solutions 2. to find things out as they go in order to be a high performing team and 3. to move up the maturity ladder. The Product Owner wants to help build a high performing team for many reasons – 1. to improve predictability 2. to have good, solid, regular user story management 3. to improve overall confidence and quality as features get developed over time. ## Encourage and enable changes at your retros So why do retros work? “I think it’s because the team is empowered to come up with things that they can change. They can define SMART goals that they can put into effect over the next two weeks. They are coming up with the problem that impacts them, so they are self-directed to the change.” It was noted that some people may fear change because something is being done to them, and they don’t feel like they have the control. “Something I reference in From “No” to “How?”, is the sphere of influence and loci of control. It’s important to help the team focus their conversations on where their locus of control lies so that they are empowered and feel capable of making changes.” “They should feel they can lean on the PO to leverage their influence or social capital to influence beyond the team’s sphere of influence.” “In the meantime, if an agile team feels like they are in control of their destiny, then they can change their world and make things happen. They feel more empowered to do things and can then go ahead and get things done.” ## How a product owner can guide a team away from dysfunction We couldn’t let Adam go without asking for his advice as to how to transition a team from dysfunction to high performance. The key take-aways: 1. Ensure everyone knows where they are going, their purpose and ensure they are all on the same page. 2. Make sure there’s good communication; whether it be team member to team member, to Product Owner to Scrum Master, communication needs to be open and honest. 3. Discipline! Give people the platform for creativity. Start on time, focus on what the meeting’s about. It provides a structure so people can flourish. 4. Always tell them ‘why’ 5. Call out dysfunction. Identifying problems, conflicts and errors is great because something has been discovered. Do you have any other [insights](https://www.youtube.com/watch?v=bUtHQXm6HKY) or stories to share about how you have improved working relationships between your scrum team and product owner? We’d love for you to [share with us](mailto:info@teamretro.com). About [Adam Mullett](https://www.linkedin.com/in/adam-mullett-57250213/) [*From “No” to “How?: Get Buy-in and Lead Change*](https://from-no-to-how.square.site/) encourages the sharing of outcomes from failed improvement attempts with peers and the boss as a way of both cementing the lesson and sharing the learning with others. [Try a demo with our fun bots](https://secure.teamretro.com/demo/health-checks/0bd55a69-9990-46a9-ad28-15f012d5563a) or [Start Your 30-day Free Trial](https://secure.teamretro.com/login/new) --- # End of year retrospective: an exercise in gratitude URL: https://www.teamretro.com/blog/end-of-year-retrospective-an-exercise-in-gratitude/ There’s a lot to be said for [showing gratitude in the workplace](https://www.forbes.com/sites/forbescoachescouncil/2021/12/29/the-benefits-of-showing-gratitude-in-the-workplace/?sh=34031a3917dd); and with the end of 2025 in sight, it struck us as the perfect opportunity to reflect upon that for which we are grateful at TeamRetro. Of course, as passionate advocates of agile and shameless fans of retrospectives, we couldn’t help ourselves – with a blank template and a few clicks of a mouse, we whipped up a gratitude template. Here’s TeamRetro’s 2025 Retro, the people and things for which we are grateful, and what we’ll be taking with us into 2026. ## The people for whom we are grateful We are grateful for our ‘curious’ and ‘creative’ **clients** who allow us to do what we do (and it’s what we love doing!). It’s wonderful to see our clients quickly embrace and deliver value through TeamRetro and the new features we released throughout 2025. Our clients inspire us to continue to improve, to remain curious and to embrace new knowledge and experiences. We are grateful for our talented and supportive **colleagues** who create and curate TeamRetro. They walk the agile manifesto talk, and in doing so they make TeamRetro a pretty special place to work. We are grateful for the generosity of the **agile community** who are always open to share their knowledge and experiences with us. ## The experiences for which we are grateful It’s no surprise that those wonderful people mentioned above paved the way for the experiences for which we are most grateful. Connecting with our clients lets us hear first-hand, how we had helped them achieve their goals. It also informed our next steps and concepts for product improvement. Connecting with our team delivered all manner of happiness. Like teams across the globe, we made time to engage with each other, foster connections with each other, and strengthen our trust and respect for each other. When times got tough, we knew we had each other’s back. We got through it, and we got better. Improving, and improving and improving were awesome!!! From bug fixing to feature releasing, knowing the value we were offering to our clients was a real buzz! We were delighted to support the AgileAus conference and absolutely thrilled and honored to receive awards from SourceForce. 2025 gave us a lot to be grateful for. ## What we’ll be taking into 2026 Our team learned a lot in 2025. We learned about ourselves, and we learned about each other. 2025 reinforced the importance of our health and our team’s health, and the positive momentum good health delivers. 2025 delivered to us all manner of kindness and offered us some wonderful examples of the strength of kindness in the face of adversity. Finally, 2025 confirmed once and for all, it is possible to eat too much chocolate. ## Thank you! Everyone at TeamRetro is looking forward to next year – what we will do, who we will meet and what we will learn. Thank you to everyone for giving us so much for which we are grateful. [Try a demo with our fun bots](https://secure.teamretro.com/demo/health-checks/0bd55a69-9990-46a9-ad28-15f012d5563a) or [Start Your 30-day Free Trial](https://secure.teamretro.com/login/new) --- # Everything you need to know about futurespectives URL: https://www.teamretro.com/blog/everything-you-need-to-know-about-futurespectives/ ## What is a futurespective? A futurespective is a process agile teams can undertake at the start of a project. They help teams to shape a high-level strategy that supports the smooth delivery of their goal. During a futurespective a team will consider the project within the context of things such as – - the skills, expertise and experience of the team members - the resources they can access - the risks and obstacles they may encounter, and - the parameters within which they must work in order to produce - a shared understanding of the project trajectory, and - confirm the first steps the team needs to take to get started. While futurespectives and retrospectives follow pretty similar processes, they differ in a couple of important ways – - a retrospective looks back over a short period of time to review what happened. This is done so as to inform the team’s next steps. - a futurespective considers the whole project in order to anticipate what may happen. This is done to shape a project strategy and the first few steps needed to start the project. ## Why run a futurespective? There are two key reasons a Scrum Master may run a futurespective. The first is to kick start a new project, and the second is to restart an existing one. A futurespective gives a team a chance to create and grow the connections that are important for [team health](/blog/what-is-an-agile-team-health-check-and-why-are-they-important/). They are an opportunity to team build: the perfect time to explore your team’s motivations and fears, and share how members have worked well in the past. This presents a Scrum Master with – - valuable insight into how they can best support their team, and - the chance to start important conversations such as dealing with unpredictability. Additionally, they help the team build a vision and purpose. It’s no surprise then that futurespectives are a wonderful way to align newly formed teams or check the calibration of established ones. When it comes to the project, a futurespective is a brilliant planning mechanism. They can be used to identify things such as – - areas of concern or perceived risks - resources and tools needed - gaps in the team. This means shaping solutions to address such hurdles can start sooner than later. A futurespective can also be used to set the tone for a project. This is why Scrum Masters can also use the futurespective to – - include a warm up or [icebreaker game](https://games.teamretro.com/games) - draw upon Larson’s [Circles and Soup](https://www.lucidmeetings.com/glossary/circles-and-soup) - set [SMART goals](https://www.groupmap.com/portfolio/elementor-20134), and - add to [team agreements](/blog/create-social-contracts-with-team-agreements-that-improve-culture/) Importantly, futurespectives ensure that at the start of the project, all team members are on the same page. Futurespectives are also a great way to restart a stalled or stuck project. They can help reenergize an unmotivated team, shake up the repetition of retrospectives, and help a team revisit their goals. ## Futurespective Prime Directive A prime directive is popularly understood to be a guiding principle. Although it’s possible to find a number of Futurespective Prime Directives, [Caroli and Caetano’s](https://www.thoughtworks.com/en-au/profiles/p/paulo-caroli-and-taina-caetano) version is the one most widely cited. Underpinned by the [Agile Manifesto](/health-check-templates/agile-manifesto-values/), and like the [Retrospective Prime Directive](/guides/scrum-masters-retrospective-guide/what-is-the-retrospective-prime-directive/) it complements, Caroli and Caetano’s Futurespective Prime Directive is a mindset. It aims to foster a positive, collaborative context within which a team can deliver the best possible outcomes. The Directive sets an optimistic tone. It reinforces the importance of the involvement of the whole team and the shared ownership of the team’s vision of the future. For it to be most effective, the team must feel [psychologically safe](/health-check-templates/psychological-safety-check/). After all, trying to predict the future is a big ask! The safer the team feels, the more ideas they will be comfortable to offer. ## How to run a futurespective? There are currently two main approaches as to how to run a futurespective. 1. Consider the project as if it has been delivered 2. View the project as if it is to be delivered The first approach has participants imagining they are their future selves looking back at the project that has been successfully finished. This approach has participants imagining they are thinking back on all of the goals they have delivered and how they did so. They (creatively) reminisce about the things that went well, the hurdles they encountered, and how they overcame them. They are effectively doing a retrospective in the future (so, a futurespective). It’s possible for the team to have a great deal of fun with this approach. An end of project lunch could be held during the futurespective. A warm up can include reference to what their future selves did in the past year of which they are most proud, or the latest (future) trend or (future) film can be discussed. The second approach is a little more straightforward. Participants are invited to look ahead and offer their perspective of what the future has in store (so again, a futurespective). This approach is possibly better suited to a team who are new to agile, or simply less comfortable with the other. Regardless of which vantage point your team prefers to adopt for their futurespective, the purpose and the process remain the same. The five steps of a retrospective can be applied to a futurespective. The important thing to keep in view is the different mindset that is to be adopted. #### Step 1 - Set the futurespective stage Once you’ve embraced the Futurespective Prime Directive mindset and picked a point of view from which to examine the project, it’s time to choose a template. Online futurespective templates offer all sorts of benefits. They are an ideal tool when it comes to remote team engagement. They can also support the delivery of asynchronous futurespectives. An online template captures all input as you go so there’s no time wasted at the end of your futurespective rewriting ideas, input and action items. Best of all, they can [integrate](/integrations/) with your existing workflow to save you even more time. The best template to choose is one that will help your team produce their high-level project strategy, the way they want. With so many amazing templates available, we’ve built an [online futurespective template selector](/retrospective-templates/) to help you choose the right one for your team. As far as our team goes, we share our favorite futurespectives below. #### Step 2 - Gather futurespective data Using the template as a guide, participants are invited to offer their input. Allowing time for quiet, individual brainstorming where team members can contribute their ideas anonymously will help overcome such barriers as groupthink. The Scrum Master should encourage participants to draw on their past experience and knowledge to populate the template. Everyone is to be reminded to offer their best (informed) guess. It’s important to acknowledge that any predictions they make that don’t come true, won’t be held against them. #### Step 3 - Generate insights It’s at this stage of the futurespective that the team’s shared understanding of their project strategy will start to germinate. So it’s vital to make sure all ideas are understood and if not, clarity is sought. Again, reference to previous projects plays an important role here. It’s an opportunity for the team to learn about what they each bring to the table and how it can be used to support the project and team. #### Step 4 - Decide what to do to start the project It’s very easy to get swept up with team building and delivering high-level vision, but it’s important to make sure your futurespective produces what’s needed to get the project started. Shaping action items is the way to do this. Make sure you limit the number of actions to the number you need to get things started, and keep them SMART. Some actions may apply to the team more so than the project. Actions that support the team’s ability to work together can be included as a [team agreement](/blog/create-social-contracts-with-team-agreements-that-improve-culture/). #### Step 5 - Summarize and end the futurespective The last step is to summarize the futurespective. This ensures that all team members understand the action items before the meeting is closed. Ending the meeting with a [Return on Time Invested (ROTI)](/blog/return-on-time-invested/) is informative and a healthy habit to support. It helps the Scrum Master gauge the effectiveness of meetings and make adjustments if needed. Finally, the Scrum Master will share the outcomes of the futurespective and follow up on the actions. ## Examples of futurespectives Here are our top three futurespectives to help get you started. ### State of Nirvana futurespective The State of Nirvana futurespective sees team members define their version of nirvana. They step out what they expect to have achieved by the first, third, sixth and tenth month, with the ideas they share building an outline of their way forward. [Learn more about State of Nirvana futurespective.](/retrospective-templates/state-of-nirvana-futurespective/) ### Plus, Minus, Interesting (PMI) The PMI Futurespective helps a team view a topic from multiple perspectives. It ensures a broad view of the project is considered as team members cannot dismiss the variety of inputs that they themselves have put together. [Learn more about Plus, Minus, Interesting (PMI)](/retrospective-templates/plus-minus-interesting-pmi/). ### SCOR futurespective The SCOR Futurespective is a reimagining of the SWOT Analysis to include team empowerment. Weaknesses are reframed as challenges and participants identify risks rather than threats. This way, participants view them as less ominous and therefore more manageable. [Learn more about SCOR futurespective](/retrospective-templates/scor/). If these aren’t quite what you’re looking for, don’t forget, TeamRetro lets you customize your futurespective or create your own. We hope this run through of what a futurespective is has given you another tool in your kit and you have what you need to help your team experience success. Here’s to you and your team’s future! --- # The best retrospective tools for agile teams (2026) URL: https://www.teamretro.com/blog/find-the-best-tool-for-your-teams-agile-retrospective/ If you're choosing an online [retrospective tool](/retrospectives/), the hard part isn't finding one — it's matching the tool to how your team actually works. A distributed scrum team that needs anonymous input and health-check trends wants something different from a co-located team that just needs a quick board once a sprint. This guide compares the retrospective tools teams evaluate most often, with pricing, standout features and what each one is best for, so you can shortlist quickly and pick with confidence. We re-checked every tool's pricing and features against its own site in **July 2026**. ### What to look for in a retrospective tool - **Templates and facilitation** — enough formats to keep retros from going stale, with guided steps so anyone on the team can run one. If you want to try formats first, browse [retrospective templates](/retrospective-templates/). - **Anonymity and voting** — honest input depends on people feeling safe; check whether both come on every plan or only higher tiers. - **Health checks** — tracking [team health](/health-checks/) over time is what turns a retro board into a continuous-improvement habit. - **Integrations** — Jira, Slack and Teams, so the actions you agree on land where the work happens. - **Pricing model** — this matters more than the headline number. Most dedicated retro tools price **per team** (cost is flat no matter how many people join); Miro, Parabol and ScatterSpoke price **per user**, which is cheaper for a tiny team but grows with headcount. - **Security** — SOC 2 and SSO start to matter the moment more than one team is involved. ### Retrospective tools at a glance | Tool | Best for | Pricing model | Free plan | Health checks | | --- | --- | --- | --- | --- | | **TeamRetro** | Retros, health checks and estimation in one | Per team, from $250/team/year | 30-day trial | Yes | | **EasyRetro** | Simple board-based retros, big template library | Per team | Yes | Limited | | **Retrium** | Structured, facilitator-led distributed retros | Per team room, from $39/mo | Trial only | Yes (Team Radar) | | **Parabol** | Open-source, self-hostable retros plus poker | Per active user, free–$8/mo | Yes | Yes | | **Neatro** | Facilitation-first guided retros | Per team, from $23.20/mo | Yes | Yes (radar) | | **Miro** | Whiteboard-first teams who also run retros | Per user, from $8/mo | Yes | No (not a retro tool) | | **GoRetro** | Retros tied to sprint metrics | Per team, from $29/mo | Yes | Sprint analytics | | **Echometer** | Recurring team-health measurement, EU hosting | Per team, from €29/mo | Yes | Yes | Pricing was verified against each vendor's site in July 2026; plans change, so always check the vendor for current details. Here's each tool in more depth. ### In this guide 1. [TeamRetro](#teamretro) 2. [EasyRetro](#easyretro) 3. [Retrium](#retrium) 4. [Parabol](#parabol) 5. [Miro](#miro) 6. [Neatro](#neatro) 7. [GoRetro](#goretro) 8. [Echometer](#echometer) 9. [ScatterSpoke](#scatterspoke) 10. [RetroTool](#retrotool) 11. [TeleRetro](#teleretro) 12. [Reetro](#reetro) 13. [IdeaBoardz](#ideaboardz) 14. [Metro Retro (now Spreo)](#metro-retro-now-spreo) 15. [RetroTime](#retrotime) 16. [Retrospected](#retrospected) 17. [Frequently asked questions](#frequently-asked-questions) ## TeamRetro ### Overview TeamRetro runs guided [retrospectives](/retrospectives/), team [health checks](/health-checks/) and [estimation](/estimations/) in one place — so the conversation, the trends behind it and the follow-up actions live together instead of scattered across three tools. Retros are template-led with anonymous input and independent voting, and health checks let you track how the team feels over time, which is what turns a retro board into a continuous-improvement habit rather than a one-off meeting. It's SOC 2 Type 2 and GDPR compliant, offers SSO on every plan, can be hosted in the US or EU, and has a wide range of [integrations](/integrations/) including Jira, Confluence, Azure DevOps, Slack and Microsoft Teams. Pricing is per team, not per seat, so the cost stays predictable as the team grows. ### Top three features - Guided facilitation with anonymous input and independent voting. - Team health checks and Insights dashboards that track trends over time. - Estimation (planning poker) built into the same tool. **Trial:** Yes – 30 days, no credit card required. **Price:** Per team, from $250/team/year (about $20.83/month) for a single team of up to 25 members; organization plans start at $50/month. There's no free-forever plan, but the 30-day trial includes every feature. ### What customers say “There is no other product on the market that delivers this number of features at this level of quality at this price. It is extremely valuable for remote teams, but we also found value using it for in-person retros for its organization, anonymous capabilities, and reporting.” – [Source Forge](https://sourceforge.net/software/product/TeamRetro/) ### Great for **The best all-rounder** — teams that want retros, health checks and estimation together in one secure tool, and expect to add more teams over time. See [TeamRetro for enterprise teams](/enterprise/) for scaling across an organization. ## EasyRetro ### Overview EasyRetro is a lightweight, board-based retrospective tool with a large template library (200+) and a genuinely usable free plan. Its public-board model lets an unlimited number of participants join a single board, and it offers free team-building extras like a Kudos Generator and Icebreaker Bingo. It integrates with Slack and Confluence on paid tiers. ### Top three features - 200+ retrospective templates. - Public boards with unlimited participants. - Free team-building tools and surveys. **Trial:** Free plan available. **Price:** Free plan (2 public boards a month, plus the full template library); paid tiers add private and team boards. EasyRetro doesn't publish transparent pricing on its site, so check the vendor for current paid rates. ### What customers say “We began using this software before the pandemic, but it was critical during that period. We needed a lightweight tool to conduct retros, and it was nice to not have to figure it out with drawing tools or messy Notion pages. This tool does one job and one job really well. Very worth it.” – [Capterra](https://www.capterra.com.au/reviews/185134/easyretro) ### Great for Teams that want a simple, low-cost board with a big template library and a free tier to start. [Compare EasyRetro with TeamRetro](/compare/easyretro-alternative/) in our side-by-side breakdown. ## Retrium ### Overview Retrium is a facilitation-focused retrospective tool built around a library of guided techniques and its "Team Radar" health-check format. Anonymous feedback and real-time collaboration help teams surface honest input, and each Team Room holds an unlimited number of users. Retrium integrates with Jira Cloud on every plan. ### Top three features - Structured "Team Radar" health-radar retros. - Guided retrospective technique library. - Unlimited users per Team Room. **Trial:** Yes – 30 days. **Price:** $39 per Team Room per month; the Business plan is $715 per Team Room per year (about $59/month) and adds SAML SSO and SOC report access. There's no free plan. ### What customers say “I like how quickly you can get a meeting started with Retrium. When my team needs to start a retrospective, we can invite who needs to be there, select our format, and get started.” – [G2](https://www.g2.com/products/retrium/reviews#reviews) ### Great for Facilitators and coaches running structured, technique-led distributed retros where unlimited seats per team matter. [Compare Retrium with TeamRetro](/compare/retrium-alternative/) in our side-by-side breakdown. ## Parabol ### Overview Parabol is an open-source tool that runs retrospectives, sprint poker and standups, and emails a meeting summary to attendees afterwards. Because it's open source, the codebase is fully auditable, and Enterprise customers can self-host. It bills only for active users, so people who go quiet for a month aren't charged. It integrates with Jira, GitHub, Azure DevOps, Slack, Microsoft Teams and Google Calendar. ### Top three features - Open-source, fully auditable codebase. - Retros, sprint poker and standups in one tool. - Active-user-only billing. **Trial:** Free Starter plan (no separate trial needed). **Price:** Free Starter tier (2 teams, 10 meetings a month); the Team plan is $8 per active user per month. Self-hosting and single-tenant deployment are available on Enterprise. ### What customers say “We primarily use Parabol for running our retros. We love the intuitive UX, great design and lot’s of templates to use for your team’s retrospectives summaries emailed to the team are a great feature, too!” – [G2](https://www.g2.com/products/parabol/reviews#reviews) ### Great for Engineering teams that want open-source, self-hostable retros and estimation, billed only for active users. [Compare Parabol with TeamRetro](/compare/parabol-alternative/) in our side-by-side breakdown. ## Miro ### Overview Miro is a general-purpose infinite whiteboard where retrospectives are one use-case among many, run from templates rather than a dedicated retro workflow. It's strong when a team wants a single flexible canvas for ideation, mapping, planning and retros, and it has one of the deepest integration catalogues on this list. Miro integrates with Jira, Asana, Linear, ClickUp, Azure DevOps, Slack, Microsoft Teams and Google Workspace (250+ integrations in total), and is SOC 2 Type II and ISO 27001 certified. ### Top three features - Infinite freeform whiteboard. - 250+ integrations. - AI-assisted workflows. **Trial:** Free plan available. **Price:** Free plan (3 editable boards); paid plans from $8 per member per month (billed annually). Priced per user. ### What customers say “Miro is an invaluable tool for optimizing collaboration and project management. Its benefits in efficiency, communication and dynamism of meetings are widely productive. I recommend Miro to any team that wants to improve their work processes and collaboration.” – [Capterra](https://www.capterra.com.au/reviews/128955/miro). ### Great for Teams that want one flexible whiteboard for many activities, with retros as just one of them — not a dedicated retro workflow. [Compare Miro with TeamRetro](/compare/miro-alternative/) in our side-by-side breakdown. ## Neatro ### Overview Neatro is a facilitation-first retrospective tool that keeps psychological safety front of mind: people brainstorm privately first, then share anonymously. It offers 70+ templates and a team "radar" health check, with a polished guided flow that walks a team through each step. ### Top three features - 70+ retrospective templates plus a team radar. - Strong guided facilitation flow. - Unlimited custom templates and exports (paid). **Trial:** Yes – 14 days, no credit card. **Price:** Free plan (up to 10 members, 30-day history); Premium is $23.20/team/month and Pro $31.20/team/month (billed annually). Priced per team. ### What customers say “The tool is super easy to use. Also I really like the created templates as I can join my retrospective and choose with the team which one to use, depending on our topics.” – [G2](https://www.g2.com/products/neatro/reviews) ### Great for Small-to-mid teams that want a polished, facilitation-first retro at a low flat per-team price. [Compare Neatro with TeamRetro](/compare/neatro-alternative/) in our side-by-side breakdown. ## GoRetro ### Overview GoRetro ties retrospectives to sprint data, pairing anonymous feedback and templates with sprint monitoring and analytics. Its Sprint Pro tier adds planning poker and a capacity calculator, so retros sit alongside the numbers they're reacting to. It integrates with Slack and Jira Cloud, and is SOC 2 Type II and ISO 27001 compliant. ### Top three features - Sprint monitoring and analytics. - Planning poker and capacity calculator (Sprint Pro). - Advanced action-item tracking. **Trial:** Yes – 30 days, full features, no credit card. **Price:** Free plan plus a 30-day trial; Premium is $29/team/month and Sprint Pro $49/team/month (billed annually). Priced per team, with unlimited users. ### What customers say “My team and I use GoRetro for team retrospectives at the end of each sprint. It allows writing feedback anonymously, commenting on the cards, “likes” and even gifs for a touch of humor. It does its job perfectly.” – [G2](https://www.g2.com/products/goretro-goretro/reviews#reviews) ### Great for Scrum teams that want retros tied directly to sprint metrics. [Compare GoRetro with TeamRetro](/compare/goretro-alternative/) in our side-by-side breakdown. ## Echometer ### Overview Echometer pairs retrospectives with psychology-based team health checks, using scheduled surveys and a cross-team dashboard to measure how teams are doing over time. It's hosted in Germany, which makes it a natural fit for EU teams with data-residency requirements. Echometer is GDPR compliant with a DPA, and integrates with Jira. ### Top three features - Psychology-based health checks with automated scheduling and a cross-team dashboard. - Custom anonymous survey builder. - 50+ templates with a collaborative board. **Trial:** Yes – free plan available. **Price:** Free plan (one retro a month); Pro is €29/team/month and Business €49/team/month (billed annually). Priced per team, in EUR, with German hosting. ### What customers say “What we like best is usability, modern design and the basic attitude behind the tool – giving responsibility to the teams.” – [Capterra](https://www.capterra.com.au/software/213109/echometer#reviews) ### Great for Teams — especially in the EU — that pair retros with recurring team-health measurement and want German data residency. [Compare Echometer with TeamRetro](/compare/echometer-alternative/) in our side-by-side breakdown. ## ScatterSpoke ### Overview ScatterSpoke has repositioned itself as an AI feedback platform for engineering leaders. It still runs retrospectives, but the emphasis is on rolling up feedback from retros, standups and surveys into AI-synthesized themes, sentiment metrics and prioritized action items. ### Top three features - AI-generated themes and sentiment. - Prioritized action items across retros, standups and surveys. - AI "Agent Surveys". **Trial:** Yes – free plan available. **Price:** Free (1 seat); Pro is $29 per seat per month (up to 5 seats); Business is $149/month including 5 seats. Priced per seat. ### What customers say “I’ve tested several multi-purpose tools, but I like that this one is focused specifically on retrospectives. It’s awesome to see the data-driven approach!” – [Product Hunt](https://www.producthunt.com/products/scatterspoke/reviews) ### Great for Engineering leaders who want AI-synthesized insight across feedback, not just a retro board. [Compare ScatterSpoke with TeamRetro](/compare/scatterspoke-alternative/) in our side-by-side breakdown. ## RetroTool ### Overview RetroTool is a simple, whiteboard-style retrospective board you can start without signing up. It includes a private area to gather thoughts before sharing, drag-and-drop grouping, dot voting and a timer. It's functional but appears to be lightly maintained. ### Key features - Single-page retrospective. - Private area before sharing. - Zero-knowledge encryption (top tier). **Trial:** Yes – 90 days on paid plans. **Price:** Free (Anonymous plan, unlimited cards and participants); Individual $10/team/month; Company $20/team/month. Flat per-team pricing. ### What customers say “Easy to use – very intuitive – setup in just a few seconds – easy to share.” – [Capterra.](https://www.capterra.com.au/reviews/202624/retrotool) ### Great for A small team or one-off retro on a tight budget — though note it doesn't appear to be actively developed. [Compare RetroTool with TeamRetro](/compare/retrotool-alternative/) in our side-by-side breakdown. ## TeleRetro ### Overview TeleRetro offers polished, engaging online retrospectives with an AI retro bot, pulse/health checks and analytics. You can bring images and music into the session, vote with emojis, and keep things on track with a timer and icebreakers. ### Top three features - AI retro bot. - Pulse and health checks. - Icebreakers with music and video. **Trial:** Yes – free plan (1 team, 3 retros). **Price:** Team is £26/month (£21/month billed annually); Business is £72/month (£58/month billed annually). Priced in GBP. ### What customers say “Cool background images. Ease of customizing the board with different columns. Best tool to work on virtually. Helps running retrospection meetings online.” – [Capterra](https://www.capterra.com.au/reviews/214521/teleretro) ### Great for A single team that wants a polished, engaging facilitated retro with health checks. [Compare Teleretro with TeamRetro](/compare/teleretro-alternative/) in our side-by-side breakdown. ## Reetro ### Overview Reetro is an AI-assisted retrospective tool for agile teams. It offers AI meeting summaries, sentiment analysis and card grouping, customizable health checks and a happiness index, plus an action tracker. Retros can be run inside Slack or Microsoft Teams. Reetro integrates with Jira, Azure DevOps, Confluence, Slack and Microsoft Teams; it's ISO 27001 certified. ### Top three features - AI summaries, sentiment analysis and card grouping. - Customizable health checks and happiness index. - Action tracker with Jira and Azure DevOps export. **Trial:** Yes – free version available. **Price:** Free tier (3 teams, limited active boards); paid plans available. We couldn't verify Reetro's current pricing from its own site at the time of writing, so check the vendor. ### What customers say No reviews available at the time of writing. ### Great for Teams that want AI features and Jira/Azure action tracking with a generous free tier. [Compare Reetro with TeamRetro](/compare/reetro-alternative/) in our side-by-side breakdown. ## IdeaBoardz ### Overview IdeaBoardz is a dead-simple, shared-URL brainstorming board for collectively gathering input, reflecting and retrospecting. It's functional and free, but it's a legacy tool that's no longer actively developed, with no stated security or data guarantees. ### Top three features - Optional login. - Export as PDF or Excel. - Runs in any modern browser. **Trial:** Free to use. **Price:** Free. ### What customers say “It is one of the easiest tools to organize and manage ideas regarding anything that we want to implement in the future implementation.” – [G2](https://www.g2.com/products/ideaboardz/reviews#survey-response-7387852) ### Great for A free, no-login throwaway brainstorm or retro board when guarantees don't matter. [Compare IdeaBoardz with TeamRetro](/compare/ideaboardz-alternative/) in our side-by-side breakdown. ## Metro Retro (now Spreo) ### Overview Metro Retro has been rebranded as **Spreo** (after an interim stint as Ludi) — the old `metroretro.io` address now redirects on. The product itself lives on as a freeform, visual whiteboard for retros, planning and workshops, with playful templates and the illustrated stickies it was known for. ### Top three features - Infinite freeform whiteboard. - Playful retro templates. - Design mode and meeting mode. **Trial:** Yes – 30-day trial (the free plan was retired in 2024). **Price:** No free plan; paid plans are priced per member (a 10-license example works out to roughly $40/month billed annually). ### What customers say “The interface is very simple, and super easy for everyone to learn. Being able to see what others are doing/saying/commenting on in real time is priceless.” – [G2](https://www.g2.com/products/metro-retro/reviews#reviews) ### Great for Teams that want a visual, whiteboard-style retro canvas — though the repeated rebrands are worth weighing as a stability consideration. [Compare Metro Retro with TeamRetro](/compare/metro-retro-alternative/) in our side-by-side breakdown. ## RetroTime ### Overview RetroTime (at retroti.me) offers a very simple, real-time way for teams to collaborate: add a sticky note, align it to a category, and vote. You can hide comments during collection, assign action items, and export the summary to your sprint tool. ### Top three features - Real-time board. - Hide comments during collection. - Action items and summary export. **Trial:** Yes – free tier. **Price:** RetroTime offers a free tier and low-cost paid plans, but we couldn't verify its current pricing from the site at the time of writing — check the vendor before you commit. ### What customers say No reviews available at the time of writing. ### Great for A lightweight, real-time retro for small teams. [Compare RetroTime with TeamRetro](/compare/retrotime-alternative/) in our side-by-side breakdown. ## Retrospected ### Overview Retrospected is open-source software (MIT-licensed) for running simple retrospectives. Boards are public on the free plan and can be encrypted or made private on paid tiers, and the whole thing can be self-hosted. Retrospected includes integrations with Slack, GitHub, Microsoft and Okta. ### Top three features - Open source and self-hostable. - Encrypted, private sessions (paid). - Multilingual interface. **Trial:** Yes – free Basic plan. **Price:** Free Basic (40 posts); Pro $12.90/month; Unlimited $49.95/month; self-hosting is a $599 one-time license. Not SOC 2 certified. ### What customers say No reviews available at the time of writing. ### Great for Privacy-conscious or budget teams that want open-source, self-hostable control. [Compare Retrospected with TeamRetro](/compare/retrospected-alternative/) in our side-by-side breakdown. ## Frequently asked questions ### What is the best retrospective tool? There's no single best retrospective tool — the right one depends on your team. For guided retrospectives plus team health checks, estimation and reporting in one place, TeamRetro is the strongest all-rounder; for a quick free board, EasyRetro or Parabol's free tier work well. ### What's the best free retrospective tool? EasyRetro, Parabol, Neatro, GoRetro and Echometer all offer free plans that suit small or co-located teams. TeamRetro doesn't have a permanent free plan, but its 30-day trial includes every feature — health checks, estimation and reporting included. ### Are retrospective tools priced per user or per team? It varies, and it matters as you scale. Most dedicated retro tools — TeamRetro, Neatro, GoRetro, Echometer and Retrium — price per team, so cost is flat regardless of how many people join. Miro, Parabol and ScatterSpoke price per user, which is cheaper for a tiny team but grows with headcount. ### Which retrospective tools work best for remote teams? All the tools here run online. For distributed teams, look for anonymous input, independent voting and async support so people contribute honestly across time zones — TeamRetro, Retrium and Parabol are all built with remote retros in mind. ### Do I need a dedicated retrospective tool, or is a whiteboard enough? A whiteboard like Miro is flexible but unstructured. A dedicated retrospective tool adds guided steps, templates, voting, action tracking and health checks — which is what keeps retros consistent and turns them into follow-through, not a one-off discussion. All pricing and features were verified against each vendor's site in July 2026. Details change over time — check the vendor for the latest. --- # Free agile tools for better retros and sprints in 2026 URL: https://www.teamretro.com/blog/free-agile-tools-for-better-retros-and-sprints/ Running agile ceremonies effectively is key to team performance. Whether you’re planning a sprint, kicking off a retro, or looking to energize a meeting, the right tools make it easier. That’s why TeamRetro offers a set of free agile tools: RetroIdeas, the Icebreaker Generator, and Planning Poker. These browser-based, AI-enhanced tools are designed to help teams improve collaboration, estimation, and engagement – all at no cost. ## TeamRetro’s free agile tools ### RetroIdeas: AI-generated retrospective templates Looking to keep retrospectives fresh and relevant? RetroIdeas offers an ever-growing library of retrospective templates, generated by AI and categorized by theme and goal. Whether you’re focused on team morale, sprint delivery, or continuous improvement, there’s a template to match. Key ways to get the most from RetroIdeas: - Rotate templates each sprint to maintain engagement. - Choose based on your team’s vibe — serious, celebratory, or constructive. - Bookmark your favorites for easy reuse. If you’re looking for more guidance on facilitating great retrospectives, check out our practical guide on [how to run a sprint retrospective](https://help.teamretro.com/article/261-starting-a-retrospective). You can also explore our collection of [fun retrospective templates](/retrospective-templates/) to keep things creative and engaging. ✅ Explore it here: [ideas.teamretro.com](https://ideas.teamretro.com/) ### Icebreakers: kick off agile meetings with a turn-based icebreaker question Set a positive tone for your retros, stand-ups, or team check-ins with TeamRetro’s Icebreaker Tool. It delivers thoughtful, AI-generated icebreaker questions designed to spark connection and ease into the conversation. Cool features that make this tool stand out: - Categories like fun, personal growth, and work-related questions. - Built-in timer to keep the meeting on track. - [Name spinner](https://games.teamretro.com/games/random-name-picker) to randomize who answers next. - Ability to edit or add your own custom questions. Use it to: - Build rapport among team members. - Break the ice in hybrid or remote settings. - Encourage more open and engaging meetings. For teams also looking to measure engagement and team dynamics over time, our [Agile Health Check tools](/health-check-templates/) offer a structured way to assess and improve team culture and performance. ✅ Try it here: [free online icebreaker games](https://games.teamretro.com/games) ### Agile planning poker: estimate story points with confidence TeamRetro’s free Planning Poker tool helps Agile teams estimate user stories collaboratively and accurately. With this online version, each participant picks an estimate independently, and all cards are revealed at once. Top features include: - Multiple estimation scales (Fibonacci, T-shirt sizing, custom). - Supports hybrid and remote teams. - Instant visibility of results with quick rounds of discussion. - No sign-up or setup required. Here’s how it helps: - Avoids bias from early estimates. - Drives better consensus through discussion. - Simplifies sprint planning for any team setup. ✅ Use it here: [planning-poker.teamretro.com](https://planning-poker.teamretro.com) — or get up to speed first with [how to run a planning poker session](/guides/agile-estimation-guide/how-to-run-planning-poker/) and [how story points work](/guides/agile-estimation-guide/what-are-story-points/). If you’re new to estimation or want a refresher, our [beginner’s guide to Planning Poker](/blog/how-to-use-planning-poker-in-agile-estimation/) walks you through the process step by step. ## Why use these free agile tools? ### Accessible, intuitive, and AI-powered These tools are: - Free to use - Web-based and accessible from any device - No account creation required - Built for remote and face-to-face collaboration. You can go from idea to action in minutes—without sign-ups or learning curves. ## Make every agile ceremony count Here’s how to use these tools across your agile cycle: - **Before a retro**: Use RetroIdeas to find a fun, engaging template tailored to your team - **At the start of your meeting**: Use the Icebreaker Tool to set the tone and build engagement - **During sprint planning**: Use Planning Poker to estimate actions together and align as a team ## Small tools, big impact TeamRetro’s free agile tools were designed with one goal: to make your retrospectives, meetings, and sprint planning more engaging, inclusive, and effective. They’re intuitive, fast to use, and built for real-world team needs. Try them today, for free — no payment or sign-up required, no strings attached. 👉 [**RetroIdeas (Free AI-generated retrospective template)**](https://ideas.teamretro.com/) 👉 **[Free meeting icebreaker tool](https://games.teamretro.com)** 👉 **[Free planning poker for agile teams](/free-planning-poker-for-agile-teams/)** --- # Fun and easy retrospective ideas for 2026 URL: https://www.teamretro.com/blog/fun-and-easy-retrospective-ideas/ A retrospective is the meeting where your team looks back at the last sprint — what went well, what didn’t — and agrees what to change next. Run well, retrospectives are the engine of a team’s improvement; run on autopilot, they become the meeting everyone quietly dreads. (New to running them? Start with our [Scrum Master’s guide to retrospectives](/guides/scrum-masters-retrospective-guide/).) Here we share simple and effective ways to keep your retrospectives fun and easy. From choosing the right [retro template](/retrospective-templates/) and setting the stage to non-cheesy ice breakers and handy tips for remote or in-person meetings. It’s all about running a retro your team will love. ## What is a fun retrospective anyway? Running a fun retrospective doesn’t mean you have to hold it on a rollercoaster. They don’t need the Scrum Master to be a stand up comedian, nor do they need to trigger howls of laughter from the team. A fun retrospective is simply one that the team enjoys and finds rewarding. Importantly, fun retrospectives are **[safe and inclusive](/guides/scrum-masters-retrospective-guide/how-to-build-a-psychologically-safe-space/)**. This is simply because it is a lot easier to enjoy an experience when fear is absent and everyone can join in. Here’s how you can run a fun retrospective and avoid those boring, repetitive meetings. ## Sprint retrospective ideas ### 1. Reset and reframe your retros When you step into the room, switch on a smile along with the lights. The mindset you pick for the retrospective will set the mood for the meeting. If you’ve chosen a particular theme for the retro, dress the room, your background, or yourself to make a statement. If you’re using an online tool that includes a welcome message, sneak in a reference to fun. Turn up your own energy and model your sense of fun which will pave the way for others. ### 2. Vary your retrospective formats There are all sorts of themes and templates to choose from. From movies, food, hobbies and interests; if you can think of it, there’s probably a theme and template to match. If you’re more DC than Marvel, you can always change the template to what you want. Here are some of the fun retro templates our teams have used – #### Superhero retrospective Discover your team’s super powers and weaknesses, along with evil nemeses and sidekicks. It’s all in the name of working together to overcome the villainous challenges that may attempt to undermine your next sprint goal! #### Goldilocks retrospective Finally we have a reason we were told so many strange stories as a kid. It was so, when we grew up, we could use them to run retros! The Goldilocks retrospective is a fun way to help a team find how the team feels about the current state of play. By picking a topic, e.g. Deployment, you can then gauge which parts of the process are too hot (firefighting, running too fast, causing burn out), too cold (laggy, slow and lacking energy) or just right. #### Oscar academy Celebrating wins is fun, so is this retrospective. It focuses on the positives and celebrates those that helped make them happen. Use this at the end of an epic or major release to acknowledge your best actors, key moments and celebrate as a team. **Keen to try a different retrospective template?** Check out this nifty site that helps you **[choose the best template for your next retrospective](/retrospective-templates/)** or explore **[more retro formats](/guides/scrum-masters-retrospective-guide/retrospective-templates/)**. ### 3. Run a ‘non-corny’ icebreaker for team building An [**icebreaker**](/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/) is a great way to start a retrospective. Starting with a fun icebreaker is a great way to have fun. Don’t worry, even if the laughter gets loud, it will still count as work. Some of our favorite fun icebreakers include – - What piece of office equipment would you grab during a zombie apocalypse? - What is the most unusual kitchen utensil you have? - What would you do if you won the lottery? - Which supervillain do you most respect and why? - If you could go to a mythical place for your next holiday, where would it be? For more fun icebreakers, check out our **[funny icebreaker questions](/icebreakers/funny-icebreaker-questions/)**, or let our [free icebreaker questions game](https://games.teamretro.com/games/icebreaker-questions) pick one for the team. ### 4. Get feedback from the team At the end of the meeting, ask the team for feedback and if they enjoyed the retro. Ask a quick check out question, “like what did you think about today’s retro?”. A simple survey like a Return on Time Invested lets the team score the retro out of 5 and will also let you know if they found the meeting fun and productive. Adding a **[ROTI (Return on Time Invested)](/blog/return-on-time-invested/)** at the end of the retrospective is a handy way to get quick feedback. ### 5. Switch Scrum Master roles If your team has always had a dedicated Scrum Master, taking turns as to who runs the retrospective next is a great way of keeping things fresh. A [random name picker](https://games.teamretro.com/games/random-name-picker) takes the guesswork out of deciding who goes next. It’s also an easy way of increasing the team’s understanding of the role of the Scrum Master and seeing different styles of facilitation in action. ### 6. Introduce fun retrospective games An agile game is a fun, interactive activity that dives into an aspect of agile. The whole team works toward a common goal with their agile understandings helping to achieve it. They are a safe way of exploring agile that can be both fun and informative. Check out our list of **[agile games](/guides/scrum-masters-retrospective-guide/agile-games-facilitate-team-building/)** you could try at the start of your next retro. ### 7. Turn up the fun in your remote retros There are lots of ways to connect teams, even if they are miles apart. You can - Turn on the camera, and turn up the smiles. Smiles have a way of spreading when seen. - Use filters and backgrounds that match your meeting theme. - Get someone to be the DJ to play music during the meeting. - Run a funny **[virtual icebreaker](/blog/virtual-icebreakers-for-remote-teams/)** to get things started. ### 8. Get creative with in-person retrospectives Injecting fun into an in-person retrospective can start with the location. After all, meeting rooms tend not to be the most inspiring of places. Move to a different room, hold the retrospective outside or even head to a cafe. If moving to another location is off the table, pop some food on the table! Being in the same place means physical icebreakers can be used. Try kicking off with musical chairs, a knock out tournament of ‘rock, paper, scissors’, or a human knot. Park the post-its and use a digital tool instead. Your team will be able to use all the features they include that help build psychological safety as well as emojis and GIFs. ## Should I make my retrospectives fun? If you’re still not sure if you should add a little fun to your team’s retrospective, here are some final points (along with the research) to consider. - As well as increasing creativity, fun is an important factor in engagement. - Fun can help to increase [**productivity**](https://www.emerald.com/mrr/article-abstract/37/8/682/310239/Play-hard-work-hardFun-at-work-and-job-performance) in an agile team. - Fun also builds resilience in the workplace and supports **[employee retention](https://www.greatplacetowork.com/resources/blog/purpose-at-work-predicts-if-employees-will-stay-or-quit-their-jobs)**. - It can help team cohesion and foster [**workplace happiness**.](/health-check-templates/work-happiness-radar/) Fun and safety work hand in hand. Fun gently nurtures psychological safety by supporting team connectedness. Together they are able to help smooth over ripples of change such as transitioning from remote to hybrid or even in person models. For other fun formats, check out these suggestions from the [Agile Scrum Group](http://agilescrumgroup.nl/) – **[Retrospective ideas pdf.](https://agilescrumgroup.nl/wp-content/uploads/Retrospective-Ideas-ENG-1.pdf)** ## Ready to make your retro fun? [Run a fun retro now!](https://secure.teamretro.com/login/new) Head over to our blog and check out **[3 Nifty Ways to Keep Your Retros Fun and Exciting!](/blog/3-nifty-ways-to-keep-your-retros-fun-and-exciting/)** --- # How to gather feedback from your AI agents URL: https://www.teamretro.com/blog/gather-feedback-from-ai-agents/ An AI agent shipped code for you this week. It read your brief, dug through the codebase, hit a wall where the documentation was wrong, guessed its way past it, and moved on. Then the session ended — and everything it learned about where your project fights back went with it. Nobody asked the one participant who just spent an hour inside your repo what slowed it down. Retrospectives exist to close exactly that gap for people: the team meets, names what helped and what got in the way, and turns it into change. AI agents are now doing real work on your team — and they hit the same friction your people do, sometimes more of it. So the question is simple. If an agent does the team's work, why isn't it in the retro? This guide is about adding that voice. Not a new retrospective format, not automating your people's input — a new participant. The AI contributes feedback; your team still decides what it means. Here's how to gather it, and how to bring it into the retrospective you already run. This post is the quick start. The practice now has a complete guide — [AI agent retrospectives](/guides/ai-agent-retrospectives/) — covering the full loop from capture to the team ceremony; start here, go there for the full picture. ## Why your AI agent's experience is worth capturing The case for a human retro is that memory fades and lessons go unshared. With an AI agent the problem is sharper: its working memory doesn't fade, it evaporates. The moment a session closes, the context is gone. The missing README it wished existed, the environment variable that wasn't documented, the brief that could have been read three ways — none of it carries to the next session unless something writes it down. And agents accumulate a specific, useful kind of signal. Over an hour of work an agent notices things a person skims past because a person already carries the context in their head: - The onboarding doc that describes a build step that no longer exists. - The function that three call sites use differently, so "follow the pattern" points at three patterns. - The brief that said "clean up the config" without saying which config, or how clean. - The test suite that needs a service running that nothing tells you to start. A human developer hits these too, shrugs, works around them, and rarely files anything — the friction is beneath the threshold of "worth raising in the meeting". An agent, asked the right way, will report every one, with the evidence attached. That is the value: not that the AI is smarter about your process, but that it is a fresh pair of eyes with no ego and no accumulated tolerance for the papercuts. Human-AI collaboration works best when both sides can say what slowed them down. One guardrail before we go further, because it shapes everything below. **The AI is a participant, never a facilitator or a judge.** It contributes items to the retrospective the way any participant does. It does not run the meeting, score your team, or decide what to fix. Humans read its feedback, sanity-check it, and choose what matters. Keep that line and the practice stays healthy; blur it and you've handed your improvement process to a tool that can't be accountable for the outcome. ## The practice: an end-of-session retro The mechanism is small on purpose. At the end of a working session — a coding task, a research job, a refactor — the agent writes one honest retro entry to a file in the repo it was working in. It takes the agent under a minute. A human spends about the same again sanity-checking it. That's the whole loop. A good entry has four parts: 1. **What went well** — the moments worth keeping, cited to something concrete that happened in the session. Not praise, not filler. If it can't point to a specific moment, it doesn't go in. 2. **Friction** — where the work got harder than it needed to. Each friction item is tagged with one of ten fixed root-cause labels (below) and — this is the rule that makes it useful — **ends with a ticket-sized "→ Fix:"**. No finding without a fix. 3. **A "Do this first" top fix** — the single change that would have helped most. One item, surfaced to the top, so a busy reader who reads nothing else reads the thing that matters. 4. **Guesses made** — every point where the agent filled a gap with an assumption. These are gold. A guess is a place your context was ambiguous or missing; the agent is showing you exactly where it had to invent an answer. Two principles keep the entries trustworthy. **Evidence-cited moments only** — every point references something that actually happened, so nobody's reading generic advice. And **the honesty runs both ways**: the agent critiques the material it was handed *and* its own mistakes. An entry that only blames the codebase and never says "I misread this and wasted twenty minutes" isn't being honest; the practice asks for both. ## The ten root-cause labels Every friction item gets exactly one label. A fixed, small vocabulary is what turns a pile of individual gripes into a pattern you can act on: when the same label shows up across ten sessions, you know where to spend your next hour. The ten cover the ways real work gets blocked. | Label | What it means | Where the fix usually lands | | --- | --- | --- | | `ambiguous-instruction` | The brief could be read more than one way. | The person writing the task | | `missing-context` | Information the agent needed wasn't provided. | The brief, or the shared context | | `incorrect-context` | Information it was given was wrong or stale. | The brief, or the shared context | | `missing-documentation` | The repo doesn't document something it should. | The docs / CLAUDE.md / AGENTS.md | | `incorrect-documentation` | The docs exist but are wrong or out of date. | The docs / CLAUDE.md / AGENTS.md | | `work-material-friction` | The material being worked on made the change hard — tangled code, account, or template. | The work material / tech debt backlog | | `missing-access-or-tool` | A credential, permission, or tool wasn't available. | Ops / platform / access control | | `agent-error` | The agent got it wrong — misread, wrong turn, wasted effort. | The agent's own account, honestly | | `changed-requirements` | The goal moved partway through the session. | Planning / scope management | | `environment-friction` | The dev environment fought back — flaky build, slow setup, broken tooling. | Developer experience | *(v2 of the skills renamed `codebase-friction` to `work-material-friction` — older entries carrying the old label still count as the same cause.)* Notice how the labels split responsibility cleanly. Some point back at *you* — `ambiguous-instruction`, `missing-context`. Some point at the *project* — `missing-documentation`, `work-material-friction`, `environment-friction`. And `agent-error` points at the agent. That spread is the point: it stops the log becoming a list of complaints and makes it a map of where improvement is owed, on every side. ## The log: plain markdown, in your repo There is no product to install for the capture step. The agent writes to `docs/ai-retros/entries/` as plain markdown, committed alongside the code. That's a deliberate choice: - **It lives where the work happened.** The friction was in this repo; so is the record of it. Anyone reading the git history sees the feedback next to the change that prompted it. - **It's diffable and greppable.** Want every `missing-documentation` item from the last month? That's a `grep`. Want to see friction trend down after you fix the build? It's in version control. - **It's tool-agnostic.** Markdown in a folder works with any agent, any editor, any process. Nothing proprietary, nothing to migrate later. Here's an illustrative example entry — this is a made-up session to show the shape, not real pilot data: ```markdown # Session retro — add rate limiting to the public API Agent: Claude Code · 2026-07-13 · ~50 min ## Do this first → Fix: Document the Redis connection setup in CLAUDE.md — three of us will hit this same wall. (missing-documentation) ## What went well - The `middleware/` folder has a clear pattern; the existing auth middleware was a clean model to copy for the rate limiter. - Tests ran fast once the service was up. ## Friction - Nothing documented that the test suite needs Redis running locally. Spent ~15 min chasing a connection error before finding it by reading docker-compose.yml. (missing-documentation) → Fix: Add a "Running tests locally" section to CLAUDE.md naming the Redis dependency and the `docker compose up redis` command. - The brief said "add sensible rate limits" without numbers. I chose 100 req/min per key. (ambiguous-instruction) → Fix: Decide the real limits with the team and put them in the ticket. - `config/limits.ts` and `config/throttle.ts` both looked like the right home for the setting; I couldn't tell which was canonical. (work-material-friction) → Fix: Merge or clearly comment which config owns rate limiting. ## Guesses I made - Assumed 100 req/min because the payment endpoints use that. May be wrong for read-heavy public endpoints — please check. - Assumed rate-limit responses should be 429 with a Retry-After header. ``` Read that as a participant's note, because that's what it is. It's specific, it owns its own guesses, and every problem comes with a next step. ## Bringing it into your team retrospective Individual entries are the raw material. Before your retro, a companion synthesis step reads the entries since last time and produces a one-page brief for the meeting: the friction that repeated, the top fixes clustered by label, the guesses that keep recurring in the same place. It's held to the same standard as the entries — **no praise or filler, no finding without a fix** — and its honesty runs both ways too: it critiques the entries it was given (thin evidence, a fix that's too vague to action) as readily as it summarizes them. Then the human part, which doesn't change: 1. **Read the brief before the retro** — treat it as one more participant's pre-read, not the agenda. 2. **Put the top one or two items on the board**, next to what your people brought. Now the AI's `missing-documentation` note sits alongside a teammate's "onboarding took me a week" — and you can see they're the same problem. 3. **Discuss and decide as a team.** The agent surfaced the item; the humans in the room own what happens next. Some items you'll action, some you'll park, some you'll disagree with. All fine — that's a participant contributing, not a system dictating. There are two ways to close this last step, and the first one costs nothing: - **With any retro tool.** The brief is just a document. Read it before the meeting, add the top item or two to whatever board you run — sticky notes included. The whole practice works this way, end to end, without TeamRetro or any other specific product. - **With TeamRetro, the agent posts for itself.** If your team runs its retros in [TeamRetro](/retrospectives/), the agent can prepare its recommendations from the log and — with your confirmation on each item — post them through the [TeamRetro MCP server](/mcp/): parked items queued for your next retro, actions when a fix already has an owner, or ideas contributed straight onto a running board. Every posted item is prefixed `[AI retro]`, so the room can see which participant raised it. That's the difference in one line: instead of you carrying the AI's feedback to the meeting, the participant hands it in itself. ## Getting started in about 10 minutes The whole thing is open source under an MIT license. The [teamretro-skills repo](https://github.com/TeamRetroHQ/teamretro-skills) covers both paths: `ai-session-retro` (writes the end-of-session entry) and `ai-retro-brief` (synthesizes entries into the pre-retro brief) need no product at all, and `teamretro-post-recommendations` adds the posting path for TeamRetro teams. A tool-agnostic prompt pack rounds it out. To start: 1. **Clone the repo** and drop the skills into your Claude Code setup, or lift the prompt pack if you work in something else. 2. **Not on Claude Code?** The prompt pack is written to work with Cursor, GitHub Copilot, or any agent you can hand a system prompt — same four-part entry, same ten labels, same "no finding without a fix". 3. **Run one session with it on.** At the end, read the entry it wrote. That first read is usually the moment it clicks — the agent will have named something about your project you half-knew and never wrote down. Point the entries at a `docs/ai-retros/entries/` folder in whatever repo your agents work in, commit them, and you've started. ## Honest limitations This is a young practice and it earns trust by being straight about what it can't do. - **An AI can't see all of its own mistakes.** Some `agent-error` friction is invisible to the agent that made it — it doesn't know what it doesn't know. Human review isn't optional garnish; it's how the blind spots get caught. This is why the AI stays a participant and never the judge. - **One entry is an anecdote.** You need roughly five entries before the patterns mean anything. A single session's friction might be that session's bad luck; the same label five times is a signal. Give it a couple of weeks before you conclude much. - **The agent reports its experience, not the ground truth.** When it says the docs are wrong, check — sometimes the docs are right and the agent misread them. That's still useful (it means the docs are easy to misread), but it's a different fix. - **Garbage briefs make garbage entries.** The practice surfaces friction; it doesn't invent insight where there was none. A session with a clear brief and a clean repo produces a short, boring entry — which is exactly right. None of that undercuts the case. Your AI agents are already doing the work and already hitting the walls. The only question is whether you find out. Give them a minute at the end of the session to tell you, read what comes back with a human's judgment, and bring the honest parts into the retro you already run — right beside your people, where a participant's feedback belongs. We ran the whole loop on our own team, agents included — see what happened when [our AI teammates joined our retro](/blog/our-ai-teammates-joined-our-retro/). --- *Building context files for your agents? See why [context engineering needs a feedback loop](/blog/context-engineering-needs-a-feedback-loop/). And if you're new to running retros at all, start with [how to run an agile retrospective](/retrospectives/).* --- # How to get estimation consensus faster in agile teams URL: https://www.teamretro.com/blog/get-estimation-consensus-in-agile-teams/ Agile estimation meetings are meant to create clarity, not confusion. Yet many teams still struggle to reach estimation consensus efficiently. If you have ever watched a team debate a single story for 20 minutes, bounce between opinions, and still end with **“Let’s just go with 5”**, you are not alone. The good news is that you can get estimation consensus faster without rushing, forcing agreement, or turning estimation into a battle of confidence. In this guide, we will walk through practical ways to improve alignment, reduce friction, and run a smoother [**agile estimation meeting**](/estimations/) that actually helps your team plan with confidence. ## Why estimation consensus takes time and why it matters Consensus is not slow because your team is doing it wrong. It is slow because estimation involves different assumptions, different levels of context, different experiences, and different interpretations of risk. When teams do not surface those differences early, they get stuck in long, unproductive discussions. What a designer can validate quickly in a prototype may require significant engineering effort to build and maintain, which is why teams often estimate the same story differently. Alternatively, a user experience issue that requires workflow changes can be mitigated through improved user interfaces. Consensus matters because it is not just about choosing a number. It is about building a shared understanding of what the work involves and what it will take to deliver the outcome. ## Tips for reaching estimation consensus faster ### 1. Start with the goal: shared understanding, not perfect accuracy A fast meeting is not always a good meeting, and a slow meeting is not always bad. But if your team’s goal is **“pick the right number”**, you will end up arguing endlessly. Instead, guide the team toward this shared goal: **“We want enough alignment to move forward with confidence.”** Make this explicit at the start of the meeting through [**team agreements**](/blog/create-social-contracts-with-team-agreements-that-improve-culture/) or a visible reminder so everyone is aligned before estimating. ### 2. Agree on what “done” means before estimating A major reason teams cannot align is that they are estimating different outcomes. Before estimating, confirm: - What is included - What is explicitly excluded - What **“done”** means for this story - Whether there are dependencies or testing requirements This step improves estimation speed because it removes ambiguity early, and ambiguity is what slows everything down. Spelling out the [acceptance criteria](/guides/agile-estimation-guide/acceptance-criteria/) and a shared [definition of done](/guides/agile-estimation-guide/definition-of-done/) before anyone votes is the fastest way to be sure the team is estimating the same thing. ### 3. Use story points the way they are meant to be used Many estimation meetings drag because teams treat points like time. But **[story points](https://agilealliance.org/resources/experience-reports/estimates-terrible/)** are not hours. They are a relative way to compare work based on complexity, effort, and uncertainty. If your team keeps converting everything into **“how many days”,** consensus becomes harder because time estimates feel personal and risky. To speed things up, remind the team: - Points are comparative, not exact - You are estimating as a team, not defending a personal opinion - Uncertainty is part of the estimate, and that is okay When teams treat story points as shared signals rather than personal commitments, consensus forms faster. Strong estimation consensus is a foundation of effective agile estimating and planning, not a separate activity. For a deeper breakdown of why points measure relative effort instead of time, see [how story points actually work](/guides/agile-estimation-guide/what-are-story-points/). ### 4. Use reference stories to speed up decisions If every story feels like a fresh debate, your team will keep starting from zero. Reference stories from past sprints can establish a baseline. For example: - **“This is similar to the login validation story we estimated as a 3”** - **“This feels like the reporting feature we rated as an 8”** - **“This is smaller than the dashboard redesign, which was a 13”** [Reference stories](https://www.agile-academy.com/en/agile-dictionary/reference-story-scrum/#:~:text=Jan%20Neudecker,support%20agile%20transformation%20in%20organizations.) build context and speed up agreement by anchoring estimates to shared past experiences. ### 5. Keep user stories small enough to estimate quickly If the story is too big, you will never get a consensus quickly. A good rule of thumb is this: If you cannot estimate it in under 5 minutes, it is probably too large or unclear. During your agile estimation meeting, look out for warning signs like: - **“We will figure that out later”** - **“It depends”** - **“There are a lot of unknowns”** - **“This touches everything”** These are signals that the story needs to be broken down, clarified, or scoped before you estimate it. Smaller stories lead to faster discussions and more reliable user story points. ### 6. Timebox the discussion without shutting people down Consensus takes time, but it should not take forever. Try this structure: 1. Read the story (30 seconds) 2. Clarify requirements and discuss (1-2 minutes) 3. Estimate silently (15 seconds) 4. Reveal estimates (10 seconds) 5. Discuss only the outliers (2 to 4 minutes max) 6. Re-estimate if needed (30 seconds) Timeboxing works because it forces focus. Instead of letting every opinion turn into a debate, it keeps the team centered on the differences that matter. ### 7. Focus on the assumptions behind the estimates When people disagree, the goal is not to make everyone agree on a number. Here are some prompt questions that can help: **“What assumptions are creating this gap?”** **“What are you including in your estimate that others might not be?”** **“What might be something you see that the others don’t see?”** For example, one person might include edge cases while another assumes a basic workflow. Exploring those assumptions quickly aligns the team and helps achieve estimation consensus faster. It is also a great way for people to learn and understand what others might need to do in terms of their part of the job. (Remember: The estimate should be for the whole team, not just their own section.) ### 8. Make uncertainty visible instead of arguing about it Sometimes, the story is genuinely unclear. Instead of forcing agreement, consider: - Estimating with a **[confidence check](https://www.scrum.org/resources/blog/winning-estimation-tactics-agile-teams-calibration-confidence)** - Adding a **[spike to research unknowns](https://agileseekers.com/blog/managing-technical-spikes-and-discovery-work-in-agile-sprints)** - Splitting work into “known” and “unknown” tasks This supports better effort estimation techniques for software development by separating uncertainty from effort instead of mixing the two. When the team can name where a story sits on the [cone of uncertainty](/guides/agile-estimation-guide/cone-of-uncertainty/), consensus becomes easier. ## A simple structure to get estimation consensus faster If you want a lightweight way to apply the tips above consistently, this flow brings them together into a repeatable agile estimation meeting structure. It mirrors a live [planning poker session](/guides/agile-estimation-guide/how-to-run-planning-poker/) — estimate silently, reveal together, then discuss only the outliers. ### Step 1: clarify (2 minutes) This is where we align on what estimation means for the team, shared understanding over perfection and confirm the Definition of Done. It’s also where assumptions, constraints, and unknowns are surfaced so everyone is estimating the same thing. ### Step 2: estimate silently (30 seconds) This is where we use story points properly, estimating relatively rather than translating to time. Reference stories help anchor thinking, while silent estimation avoids bias and premature influence. ### Step 3: reveal together (10 seconds) This is where differences become visible without pressure. Revealing at the same time gives everyone an equal voice and turns variation into useful data rather than debate. ### Step 4: discuss outliers only (3 minutes) This is where estimation earns its keep. The highest and lowest estimates explain what they are factoring in unknowns, edge cases, dependencies, technical risk, or prior experience with similar work. This conversation exposes assumptions the rest of the team may not have considered, so everyone leaves with the same understanding of scope and risk. ### Step 5: re-estimate (30 seconds) This is where we test whether that shared understanding actually exists. If estimates move closer together, the work is likely clear and ready to plan. If they don’t, it’s a signal the story needs to be split, clarified, or de-risked before moving forward. ## Final thoughts If your estimation meetings feel slow, the solution is not to talk less. It is to talk about the right things: assumptions, scope, uncertainty, and shared understanding. When your team gets better at surfacing those details early, estimation becomes faster and more useful. You spend less time debating numbers and more time aligning on what it will take to deliver. That is what leads to stronger estimation consensus and better sprint planning. If you want to make estimation a structured, repeatable part of how your team plans and not just a quick voting exercise, TeamRetro’s estimation meetings guide teams through story-by-story estimation with anonymous voting, simultaneous reveals, and focused outlier discussions. It keeps conversations centered on assumptions and risk, helps teams reach genuine consensus, and connects estimates directly back to the tools your team already uses. Teams that improve estimation consensus spend less time debating numbers and more time making confident planning decisions. Try estimation meetings in the TeamRetro app and see how clearer conversations lead to faster, more confident sprint planning. [Learn more about agile meetings](/estimations/) --- # Giving kudos with Kudo Cards in retrospectives URL: https://www.teamretro.com/blog/giving-kudos-with-kudo-cards-in-retrospectives/ In an Agile world driven by metrics, velocity, and constant delivery, it’s easy to forget the simple power of saying “thank you.” Enter Kudo Cards—a small yet mighty tool from [Management 3.0](https://management30.com/practice/kudo-cards/) practices designed to nurture appreciation, amplify psychological safety, and reinforce Agile values within your team. If you are someone committed to team culture, it’s time to add this humble practice to your toolkit. ## Kudo Cards in Management 3.0 Kudo Cards, also known as appreciation or motivation cards, originated in the [Management 3.0 framework](https://management30.com/practice/kudo-cards/). They provide a structured yet lightweight way for team members to acknowledge each other’s contributions. The word ‘kudo’ comes from Greek, meaning ‘praise’ which is exactly what kudos is for. Unlike top-down rewards, Kudo Cards thrive on peer-to-peer recognition—making gratitude an everyday part of Agile ceremonies like retrospectives and health checks. They can be a simple, fun activity through to something more serious. ## Why give kudos? Imagine this: You’ve just wrapped a sprint. Bugs were squashed, blockers cleared, and the team navigated a tense stakeholder review. In your retrospective, there’s a brief silence until one team member says, “Hey, kudos to Priya for stepping in on the API issue—totally saved our sprint.” Smiles appear. The mood shifts. Recognition changes the room. Kudo Cards are a peer-to-peer recognition tool that gives team members a structured, positive way to acknowledge each other’s contributions. Psychology tells us that recognition plays a vital role in intrinsic motivation. A few reasons why kudos matter: - **Reinforce positive behavior**: Recognition strengthens the likelihood of repeated collaboration and supportive behaviors. - **Boost team spirit**: Simple acknowledgements create a sense of belonging and camaraderie. - **Foster a growth mindset**: By praising effort, learning, and persistence, kudos encourage continuous improvement. - **Encourage radical candor**: By mixing honest feedback with appreciation, teams create safe environments for growth. - **Keeps people engaged** – both during and outside of the meeting. According to studies on employee motivation, **peer recognition** can boost performance by up to 14%. In remote or hybrid Agile teams, these micro-moments of appreciation act as emotional glue. ## Practical implementation steps To put kudos into practice, here are a few suggestions: - **Set aside a few minutes** in retrospectives or health checks specifically for kudos. This can be at the very start or at the end of the meeting depending on your preference. - **Use a structured system** such as physical cards, a kudos wall, or TeamRetro’s built-in kudos feature that will help you keep a record of all kudos over time. - **Encourage specificity**—thank teammates for clear contributions or actions. - **Lead from the front** – Model the behavior with an example. ## Best practices for sprint retrospective kudos Want your kudos moments to really matter? Simple. Keep them clear, authentic, and balanced. Keeping it intrinsic is also important. Jurgen Appelo’s rules for intrinsic rewards, as detailed in Management 3.0, emphasize preventing negative motivation. These include not promising rewards in advance, keeping anticipated rewards small and to reward publicly and continuously. The goal is to focus on rewarding the process, not just the outcomes in peer to peer rewards. You don’t have to reward everyone who gets a card. For example you can reward the person with the most cards or draw from a random card and reward its recipient. Let your team decide who deserves the golden ticket. It’s also a nice idea to thank the person who writes the Kudo Cards too or to have different people read out kudos each time. ## Giving kudos in TeamRetro TeamRetro makes it easy to weave kudos into your retrospectives and health checks. Facilitators, meeting participants and guests in a meeting can give kudos to other members. (Only observers, as their name would suggest, cannot give kudos). Here’s how you can recognize your team: ([full help guide here](https://help.teamretro.com/article/464-giving-kudos "kudo cards in retrospective guide")) ### Types of Kudo Cards Not all kudos are the same. Here’s a quick breakdown of the different types of Kudo Cards: **Thank you** For showing appreciation when someone helped you out. *e.g.* “Thank you, Sam, for jumping in to debug the issue so quickly.” **Proud of you** For recognizing growth, courage, or stepping up. *e.g.* “Proud of you, Jen, for leading the client demo with confidence.” **Great job** For acknowledging solid, reliable contributions. *e.g.* “Great job, Chris, coordinating with QA to get the release out on time.” **Very happy** For celebrating something that made the team or you feel good. *e.g.* “Very happy with how you handled the feedback, David—it turned things around.” **Congrats** For celebrating milestones or achievements. *e.g.* “Congrats, Maria, on closing your first story this sprint!” **Impressive** For highlighting standout effort or impact. *e.g.* “Impressive work, Samuel, fixing that critical bug in just a few hours.” These moments of acknowledgment ripple outward, lifting not only the individual but the whole team atmosphere. In TeamRetro, enabling kudos ensures that recognition is seamlessly woven into your retrospectives and health checks, turning gratitude into a regular part of Agile life. ## Ready to build a culture of appreciation? Kudos is more than a nice-to-have—it’s an excellent way to acknowledge contributions, build team spirit, and boost overall team happiness. Whether you’re running retrospectives, health checks, or day-to-day chats, integrating kudos with TeamRetro turns recognition into an intentional practice. 👉 **Start your free trial with [TeamRetro](https://secure.teamretro.com/login/new?cc=kudosBlog "TeamRetro start free trial")** and see how easy it is to foster a culture of gratitude in your Agile team. --- # How online retrospective and health check build psychological safety URL: https://www.teamretro.com/blog/how-online-retrospective-tools-build-psychological-safety/ Running your retrospective with an online tool can be an ideal way to build [psychological safety](/guides/scrum-masters-retrospective-guide/how-to-build-a-psychologically-safe-space/) by providing a way for the team to share their ideas safely, celebrate success and find ways to improve, without playing the blame game. They provide a platform where ideas can be safely and anonymously shared about what went well, what did not, and what they want to improve. By choosing the right tool with features that support this such as independent input and voting, it can create the perfect setting for continuous improvement. Scrum Masters who properly facilitate meetings with these tools can help reduce fear of judgment or reprisal. By following up with any issues quickly, this lets the team know that they are being heard. While it can never replace the skills and traits of the servant leader that is the Scrum Master, having the right online retrospective tool that has safety in mind will establish agreed protocols in meetings, adapt to your needs, and keep track of agreed actions. Here’s our take on how to build psychological safety through the humble retrospective. ## Helps the team understand what psychological safety is Online retrospective tools that include team health checks can help people better understand what psychological safety means for them. The health checks offer team members questions to support individual reflection. The questions included in the [Psychological Safety health check](/health-check-templates/psychological-safety-check/), for example, connect to the indicators of safety used by researcher, [Professor Amy Edmondson](https://www.hbs.edu/faculty/Pages/profile.aspx?facId=6451). An online tool also offers a team the flexibility to decide and define what safety means for them with a custom health check. Scrum Values can also be explored using an online retrospective tool. The [Scrum Values health check](/health-check-templates/scrum-values-radar/) can help a team measure and track their value alignment. This can then help support conversations around development and growth as well as helping to improve relationships within the team. Importantly, team health checks can help measure and track psychological safety within the team. This means that decisions around actions made to support safety can be informed by data. The impact of those actions can be tracked over time. ## Helps you set the stage for your retro An online retrospective tool can provide templates that support the needs of your team. If that need is fostering psychological safety, it can inform the choice of template you make. Adding headings to your retro that ask people how they can build safety in their team means you are already providing a space for ideas to be heard. A Welcome Message can be used to help set the tone for the meeting. It can remind people of the helpful habits that build safety. Displaying the Retrospective [Prime Directive](/guides/scrum-masters-retrospective-guide/what-is-the-retrospective-prime-directive/) at the start of your retrospective reminds the team of the mindset needed to ensure the meeting is both positive and improvement oriented. Having a facilitated workflow that can be customized can also build psychological safety. Being able to set the stage includes - Making it anonymous or semi-anonymous to make it safer for people to share their ideas - Allowing independent voting on ideas that is not biased - Having a familiar and effective workflow from brainstorming to generating action items - Being able to propose and give feedback on ideas as well as actions ## Levels the playing field An online retrospective tool gives each person the chance to have the opportunity to contribute, rather than just about being the most dominant person in the room. Simply put this means that each person can share their own ideas, comment on others, have an equal number of votes for discussion, and to support specific proposed actions. All voices are heard at the same volume and are of equal importance. Anonymous input helps with this. Submitting ideas anonymously means team members aren’t influenced by the person who suggested it. Instead, the idea is viewed on its own merits. Using independent voting to decide on what is discussed and which actions are taken forward is an effective way of supporting psychological safety. Each person has a fixed number of votes with equal weight as part of a “dot-mocracy” The way in which an online retrospective tool allows for input to be captured also helps maintain a level playing field. All participants have the same opportunity to submit the same type of input at the same time. It’s not dependent on having room to stick ideas on a physical board, nor for people to wait their turn. People can record their questions, comments and feedback simultaneously while discussion is taking place. Again, this means that all ideas can be captured and the whole team can see all comments that have been offered. See [how Typewise’s distributed team uses online retrospectives](/case-studies/typewise/). ## Helps remove fear and bias One of the most effective ways online retrospective tools help to support psychological safety is by reducing the opportunities for judgment. When team members fear being judged, they are more likely to self edit their input in order to avoid it. This may result in fewer, less varied ideas being generated. When the retrospective is set to anonymous names are removed from all input. No one knows who submitted what; not even the Scrum Master (unlike handwritten notes). Such anonymity lets team members share their ideas without fear of judgment or retaliation. This means people are more likely to be more honest and more creative. ## Fosters feedback As well as capturing questions without the fear of interrupting discussions, online tools allow participants to visually reflect their thoughts. Emojis and GIFs can be used to offer a sense of what a participant feels without the pressure of going into detail. When it comes to deciding on proposed actions, using a thumbs up, thumbs down, or up and down, is a quick indication of a preference without having to offer a reason. Other features such as a [ROTI (return on time invested)](/blog/return-on-time-invested/) can also support psychological safety. As it is yet another simple way team members can provide feedback and feel heard. ## Creates a space for ideas to be shared openly – beyond space and time Online retrospective tools are particularly well placed to support asynchronous meetings. This is because members of the team are able to determine the time that best suits them to offer their input. It also means that one time zone isn’t being favored over another. Additionally, remote, hybrid and in-person teams have the same retro experience. ## Helps set ground rules for the team Online retrospective tools can also include a mechanism to build [Team agreements](/blog/create-social-contracts-with-team-agreements-that-improve-culture/). This helps psychological safety as such ground rules reflect the behaviors that a team promises to demonstrate when working with each other. They can cover what the team feels is important when working together. This can include a range of understandings such as how to deal with noise up to how conflicts are to be addressed. The clarity and shared understandings about behavior they deliver makes the workspace a psychologically safe one in which to participate. ## Helps build team connectedness An online retrospective tool can help build team connectedness. From sharing ideas, proposing and accepting actions, through to adding topics about acknowledgement and kudos. The tool gives each person their own space to think, and also the chance to share and listen. When it comes to remote teams, an online tool is a real game-changer. It overcomes the barriers of distance and puts everyone on the same virtual page. ## Allows you to identify anti-patterns Online retrospective tools are able to address a number of issues that can reduce the safety of traditional meetings. They are able to counteract bias by supporting equitable, inclusive input. Specifically, the anti-patterns they can help identify – 1. Teams are not holding retrospectives 2. Team members are not participating during the meeting 3. Action items are not being followed up Online tools can capture data that could be missed during the retrospective itself. They can reflect participation rates, with low rates pointing to the possibility of low levels of safety. They also facilitate transparent processes that foster divergence and encourage openness. ## Run a retro today [Test drive the range of retrospectives](/retrospective-templates/) TeamRetro offers or sign up for a [free trial](https://secure.teamretro.com/login/new) (without a credit card) today! --- # How to manage the BMWs in your retrospectives URL: https://www.teamretro.com/blog/how-to-manage-bmw-in-retrospectives/ There’s an acronym used in [Agile](https://en.wikipedia.org/wiki/Agile_software_development) – BMW – and we don’t mean Bayerische Motoren Werke, the German brand of luxury cars well known around the world. We’re talking about the “Bitching, Moaning, Whinging” session that can sometimes happen during retrospectives. As much as we would love to believe that retrospectives are always rainbows and sunshines with a focus on the agile manifesto and prime directive, not all teams and meetings will fall neatly into this paradigm. And look, we get why BMWs can happen during a [retrospective](/retrospectives/) – a time when a team reflects on what happened in the iteration and identifies actions for improvement going forward. While BMWs will exist, to varying degrees within retrospectives, the last thing you want is for it to hijack your retro and everyone leaving your meeting with the wrong focus. So how might we balance out giving the people the opportunity to share what the problems are without it turning into the next soap drama? Here at [TeamRetro](/), we’re sharing some ways to manage BMW in retrospectives. ## Activate the “spidey sense” They say prevention is better than the cure and we totally agree with this saying! We advise scrum masters to turn on their “spidey senses” and sense from the stand ups and one-on-ones if something is brewing. If it is, address those issues before the retro so you manage BMW in retrospectives by keeping them out and the constructive feedback in. ## Manage BMW in retrospectives with a timebox for a soapbox BMWs are pretty inevitable and instead of letting it all stew in, we suggest there is a way to let it stew out strategically. Here’s how: 1. Schedule one minute in your retro to “let go” – let your team air out something that’s made them mad, lose focus or just need to get off their chest. 2. You can use the [timebox feature](https://help.teamretro.com/article/168-timer) in TeamRetro to “fix” the amount of time. 3. And use the information as a way to focus actions / solutions or park it if it needs to be solved after the retro. ## Call an elephant an elephant The saying “there’s an elephant in the room” typically means that there is an obvious problem or difficult situation that people do not want to talk about. Giving this “elephant” space to be listed on the retro topics for discussion means there will be less hidden issues and agendas, giving your team confidence to say what they need to. ## Change the focus A typical [Agile Retrospective](/retrospective-templates/agile-retrospective/) asks 4 basic questions – what went well, what went less well, what do we want to try next and what puzzles us – that gets teams thinking about the outcomes of the last sprint, and what actions they should focus on next. If you are finding this style of retro is opening the BMW can, then why not look at putting on a different hat with your retros? There’s the [Starfish Retrospective,](/retrospective-templates/starfish-retrospective/) which is a data gathering activity to foster the thinking around practices and the value the team gets from it. It helps team members to understand each other’s perceived value on such practices. Or try the [mad sad glad retrospective](/retrospective-templates/mad-sad-glad-retrospective/) which frames discussion around the emotional journey of your team during the previous sprint, and is a great way to identify opportunities to improve team morale and job satisfaction. There are many more retro hats to put on and try with TeamRetro – [WRAP,](/retrospective-templates/wrap-retrospective/) [FLAP](/retrospective-templates/flap-retrospective/) and the [Four Ls](/retrospective-templates/4ls-retrospective/) – give them a go for something innovative and creative that will engage your team best! Another model to try out too is the [Circle and Soups](https://www.innovationgames.com/circles-and-soup/#:~:text=This%20game%2C%20introduced%20by%20Diana,wall%20of%20the%20unproductive%20blame.) model by Diana Larsen to help people reconcile what they can and can’t influence. Why not try some of these styles to not only manage BMW in retrospectives but also to have fun! ## Switch Scrum Master roles While a scrum master typically runs the retrospectives, it doesn’t mean they should be the only one doing this. Changing up the facilitators for retrospectives can have many advantages, including: - Different styles which might make retros more exciting as it changes with each facilitator; - Provides an opportunity for all team members to have responsibility to run a successful retro for their team members; - Professional development for all team members; - Less BMW because team members who you work and collaborate with are running the retros. ## Data don’t lie If you find your retrospectives become unfocused with too much BMW, one thing we can suggest and have seen work well is to allow for voting for items or learnings to focus on independently. Independent voting keeps things real allowing the team to decide on where the focus should be. Voting can be done by using the sticky dot methods if you’re running retros physically with the good old post-it notes. Or, if you’re doing your retros online, we at TeamRetro have created a + vote system, accessible by a click of a button. Once you have collected the data, talk to it. Use it as evidence to back up your retros or focus on improving data outcomes rather than people. With this data in hand you now know where to direct the conversation and move the thinking into problem solving and action planning. ## Follow up Following up on the retrospective action items involves delegating tasks to each team member. By agreeing to follow up either as a separate team meeting, with one-to-ones, or with other stakeholders, the Scrum Master can assist teams to own their retro items. ## Manage BMW in retrospectives with TeamRetro TeamRetro is an enterprise-ready online retrospective tool for remote teams. Our guided and creative retrospective techniques ensure your retros are worthwhile – each and every time! [Try it FREE](https://secure.teamretro.com/login/new?emailAddress=) for 30 days today and see if it can help you to manage BMW in retrospectives. --- # How to run a remote retrospective: by agile coach, Kelly Cook URL: https://www.teamretro.com/blog/how-to-run-a-remote-retrospective-by-agile-coach-kelly-cook/ A global pandemic has certainly placed many pauses in the way we do things and how we work. Remote retrospectives is a result of this trend. For Agile teams, retrospectives are a crucial part of their working methodology. Retrospectives provide the opportunity for a team to look back and see how they can improve. Retrospectives can be a catalyst for organizational change as well as team change. They can be a place to build and enable teams, or to help teams start their journey from the best possible place. So how do you make sure that retrospectives still occur during a global pandemic that’s made most teams work in a more distributed and/or remote way? We recently came across [this article on running remote retros](https://www.itproportal.com/features/life-in-lockdown-how-to-run-a-remote-retro/) from [Kelly Cook](https://www.itproportal.com/author/kelly-cook/), Agile Coach of [AND Digital](https://and.digital/), focused on sharing advice and guidance on how to run remote retros. Let’s summarize Kelly’s key points. ## Tip 1: fostering collaboration in remote retrospectives To foster collaboration through remote retros, it’s crucial to encourage team members to be explicit. Kelly offers some tips on this topic: - check in regularly. - conduct anonymous team [health checks](/health-checks/). - be visible. - choose the appropriate tools that will allow for easy remote collaboration and help facilitate open, honest and transparent communication. ## Tip 2: removing barriers As Zoom calls become the new favorite way to communicate, we now have a screen acting as a physical barrier between team members. Kelly offers the following tips for removing barriers: - clarify how your team wants to work together to achieve their objectives. Once done, make sure you stick to this way of working. - summarize throughout your retro. - facilitate better conversations. - manage conflicts. ## Tip 3: maximize engagement during your remote retrospectives Remote retrospectives can be successful when you maximize input from your team. Kelly again offers the following advice to maximize engagement: - start your retros by setting the scene. - minimize distractions and set clear roles, like timekeepers, and scribes. - keep team members focused through games, music, or something that keeps energy and focus high. - review the team’s actions and ensure that each person has ownership of specific tasks. ## Try TeamRetro for your remote retrospectives If you are still looking for the right tools to help you run remote retros, we’d like to help! TeamRetro is an enterprise-ready online retrospective tool for remote teams. Our guided retrospective techniques ensure your retros are worthwhile – each and every time. [Try TeamRetro FREE for 30 days](https://secure.teamretro.com/login/new?emailAddress=). --- # How to run an icebreaker for meetings, workshops, and training sessions URL: https://www.teamretro.com/blog/how-to-run-an-icebreaker/ To run an icebreaker, just three things are needed. The right mindset, a great question and someone to give a gentle nudge to get things started and move the icebreaker along. Before you know it, your icebreaker is done, and you have set the stage for a more effective retrospective meeting. Even with all the benefits that running an icebreaker can bring to a team and their meeting, sometimes it can be tempting to skip straight to the retrospective. This is especially the case when your backlog is overflowing and you just don’t have the head space to think of a question. That’s why we asked our team to design an [icebreaker tool for agile teams](https://games.teamretro.com) that would take the effort out of running icebreakers. TeamRetro’s [icebreaker tool](https://games.teamretro.com) makes running icebreakers easy. Designed with agile teams in mind, it can generate [icebreaker questions](https://games.teamretro.com/games/icebreaker-questions) and help you decide who goes next. It can even help you keep an eye on the time! So let’s look at how to run an icebreaker so you can help your team get more out of their retrospective. ## Step into the icebreaker headspace The first thing to do when running an icebreaker is to switch on the right mindset. - Be curious. - Be positive. - Be an advocate for icebreakers. Remember, icebreaker questions aim to foster connections between people so they work better together. Those connections come about when people share their stories with each other. The more people share, the greater the connections. People are more likely to share when they feel their stories are being received positively and with genuine interest. Keep in mind, there’s no such thing as a wrong answer to an icebreaker question, which is why they are so great at helping to create safe spaces. All answers are welcome and all input is valued. It’s a space where inclusivity and diversity is naturally celebrated. Lastly, don’t forget that by running an icebreaker you are delivering a lot of value to your retrospective meeting. You are helping to create a safe, positive, collaborative space. You are contributing to the productivity of the meeting. Best of all, you are making work fun. ## Choosing a great icebreaker question To choose a great icebreaker question head over to TeamRetro’s [icebreaker tool](https://games.teamretro.com) and click start. Yes, it really is that easy! If you would like your icebreaker question to have a little more focus, you can filter the questions by the following categories. ### Agile games An agile game is a fun activity aligned to an aspect of agile. They see the whole team work toward a common goal. As well as building connections between team members they also help to deepen their understanding of agile. ### Building safety These icebreaker questions help to explore and foster a safe workspace. They offer the team the chance to share stories of trust, empathy and growth. These questions help start supportive conversations that can continue long after the icebreaker is done. ### Deep and meaningful This category of icebreaker questions gives people the chance to share insights and ideas they may not have otherwise shared at work. They let people explore and predict possibilities, while the group gets to know more about each other. In doing so, they can help a team expand their perception of each other. These are great to use when a reminder is needed that we’re all human. ### Fun This group of [funny icebreaker questions](/icebreakers/funny-icebreaker-questions/) is pretty self-explanatory. They are deliberately creative and a little bit silly, all in the name of having fun at work. Rest assured, they will still deliver all the benefits of an icebreaker, even if the laughter gets loud. ### Get to know The ‘Get to know’ icebreaker questions have been shaped with new teams and teams with new members in mind. They support the very early stage of when people meet. They help to start inclusive conversations that form the foundation of connections. ### Quick/check-ins This set of icebreaker questions is your go-to when you feel you are pushed for time. They are short and fast, but they still deliver value. These save you time so you don’t have the excuse to skip the icebreaker. ### Team building These icebreaker questions help nurture your team. They create space for celebration. They showcase collaboration and teamwork. They boost morale, explore values and fuel productivity. If you are looking to actively support your [team’s health](/health-checks/), these are the icebreakers for you. ### Virtual or remote Remote teams will easily relate to this category of icebreaker questions. They reference their virtual context as a common point of discussion. These icebreakers also see team members share aspects of their homes as a reflection of themselves. ### Warm-ups Although not technically an icebreaker, we included this category for established teams. Warm-ups help people focus on the task at hand. These activities help your team direct their full attention to the retrospective and to switch off from other thoughts and tasks. You can read more about warm-ups here. ### Work focussed If your team isn’t too keen on running an icebreaker before their retrospective, this set of questions will help you navigate that resistance. These [icebreaker questions for work](/icebreakers/icebreaker-questions-for-work/) connect to what everyone in the team has in common – their place of work. They help the icebreaker habit to be established by exploring that common ground. ## How to facilitate an icebreaker Facilitating an icebreaker is very straightforward and comes down to just three steps – - Kicking it off - Making sure everyone has had a turn - Wrapping it up ### Kicking it off Kicking off an icebreaker starts with finding someone to go first. If you’re meeting a brand new team for the first time, and you’re the Scrum Master or facilitator, that person should be you. Going first lets you introduce yourself, set the tone, and model the kind of open, respectful sharing you want to see from everyone else. TeamRetro’s icebreaker tool includes a built-in [random name picker](https://games.teamretro.com/games/random-name-picker) that nominates who goes next, so you don’t have to choose people manually. That keeps the process transparent, fair, and free from any unconscious bias. ### Making sure everyone has had a turn It’s important that everyone gets a chance to answer the icebreaker question. Inclusive retrospectives start with making sure no one is left out, especially quieter or remote team members. Here again, TeamRetro’s [icebreaker tool](https://games.teamretro.com) does the heavy lifting. Each time someone answers, their name is automatically removed from the pool of people still to respond. You don’t have to remember who has already had a turn—the tool tracks participation for you and makes it easy to see who’s next. ### Wrapping it up Once everyone has answered the icebreaker question, it’s time to bring the activity to a close and smoothly transition into your retrospective. When the question is particularly engaging, conversations can run long and eat into your retro time. To help with this, TeamRetro’s [icebreaker tool](https://games.teamretro.com/) includes a timer so you can keep the activity within a set timebox. It gives you a clear, neutral reference point if you need to move the discussion along and make sure your retrospective starts on time. Before you wrap up, thank everyone for sharing and acknowledge the contributions they’ve made. For more, check out our [top 5 tips for running icebreakers](/blog/top-5-tips-for-running-effective-icebreakers/). You can also explore our blog where we share [what makes the best icebreakers for teams](/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/), along with [quick but effective icebreakers to launch your next retrospective.](/blog/quick-but-effective-icebreakers-to-launch-your-next-retrospective/) Or browse the full library of [icebreaker questions](/icebreakers/), grouped by use case. --- # How to run great retrospectives online with remote and distributed teams URL: https://www.teamretro.com/blog/how-to-run-great-retrospectives-online-with-remote-and-distributed-teams/ As [predicted](https://www.siliconrepublic.com/careers/remote-flexible-working-fixed-offices-future-of-work) some time ago and recently catalyzed, the popularity of remote working continues apace. Whether partially or fully remote, the benefits of such a workforce are hard to ignore – - increased productivity and reach - decreased costs - access to a diverse talent pool - better retention and employee satisfaction Within the context of agile, the retrospective is critical to the success of a team. So, given the increasing popularity of a remote workforce, it stands to reason it’s important for an Iteration Manager or Scrum Master to be able to facilitate an online retrospective as effectively as they would one that’s face to face. With this in mind, we’ve put together the following to share our tried and true tips for running effective online retrospectives. ## What makes an effective online retrospective? Here at TeamRetro, we practice what we preach, running regular retrospectives in order to improve our product and our team. From our perspective, regardless of the medium of their delivery, an effective retrospective has the following characteristics – - has a regular cadence - operates with a shared understanding of what’s expected of the team - allows all voices to be heard - occurs in a safe, judgment-free space - adheres to the allocated time - is easily and concisely documented - supports team morale - delivers a clear set of actions for the next sprint, and a shared understanding as to who is responsible for their delivery Ensuring these outcomes are delivered in an online environment boils down to two key elements - An online environment supportive of retrospectives - Appropriate online facilitation techniques Here’s how to do it. ## Step 1 – Prepare the online environment (set the virtual stage) Consider the space in which you and your team run your face-to-face retrospectives – - You may be using a whiteboard with team members taking it in turns to stand up and add to it, or perhaps sticking post-its onto a board. - Participants may offer a quick explanation or comment as they add each of their points, before the team discusses things more broadly. If an impasse is reached, it’s possible things are talked through until a consensus is reached. - It’s possible you know it’s time to wrap up when you see people heading for lunch, or hear a knock on the meeting room door. Clearly, while the above may work for those of the team based in the office, the same cannot be said for those working remotely; the above obviously needs to be translated into a virtual space. While this may require some investment, an environment that supports both co-located and remote participants equally, is a valuable risk mitigation treatment on many levels. ### Choose your online retrospective tool [Online retrospective tools](/retrospectives/) have been developed with both remote and co-located teams in mind, and offer an organized process for running a retrospective. There are a myriad of tools but overall they should be designed to – - make facilitation easy - be secure, fast and reliable - address common retrospective anti-patterns - shape a safe, equitable space - easily capture inputs from all participants - record and track action items - gauge meeting effectiveness - present ideas one by one to ensure everyone is focused - augments your video conferencing tool - integrates action items into your workflow ### Choose your communication tool Will you be using video conferencing, teleconferencing, or will you be relying on VoIP? The mechanism your team uses to complement your online retrospective tool will inform the facilitation techniques used to support the retrospective process itself. For example we use video conferencing and an internal messaging system such as Zoom and Slack to support our real time online retrospectives. - Our screens are on and microphones are unmuted (this means that our facilitator can see we are engaged). - From time to time, links to documents and other files are shared on a dedicated and secure messaging channel. - The scrum master may share their screen throughout the retrospective as needed. ### Consider a dry run Delivering retrospectives to a remote workforce is very difficult to do on the fly; without the convenience of co-location it can be difficult to convey last minute decisions, delegate the Scrum Master role, change times etc. These things are also incredibly frustrating and isolating for the team. The importance of planning and following through cannot be understated. While some discipline may be needed to deliver this, the return (saved time, focused retrospective, team alignment) will be worth it. In order to ensure the virtual space is suitable to facilitate retrospectives, it’s helpful to ensure – - all participants know how to use the technology, so a dry run helps. - the technology works, so home VPNs and low connectivity can be addressed beforehand. - there is an easy and agreed process for people to follow. The simplest way to achieve this is to rehearse or walk through a retrospective. This way your team can demonstrate both the retrospective tool and communication mechanisms work, and they know how to use them! ### Before your retrospective **Build cadence**, by locking in a regular time slot in everyone’s schedule. Ensure all team members have made the retrospective a priority by giving them plenty of time to organize their commitments (kids etc) and double check time zones are aligned. **Draft a** [**team agreement**](https://help.teamretro.com/article/266-team-agreements)**;** these are the ‘house rules’ for the retrospective meeting itself, and a worthwhile exercise to do with your team. This aligns to building the team culture and how people interact with each other. Things such as “we won’t multitask” (which is always tempting to do during internal virtual meetings), or “always laugh at jokes, even the bad ones” could be included. The agreement isn’t written in stone, and can be updated at any time. **Choose a template** that will support the needs of your retrospective and team. If you’re looking for a way to help your team re-frame challenges, the [Netball Retrospective](/retrospective-templates/netball-retrospective/) may be what you’re looking for; if your team works well with a direct approach, the [Working Not Working Retrospective](/retrospective-templates/working-not-working-retrospective/) will help them get straight to the point. **Confirm the options** you wish to apply to your template. Adding a [ROTI](/blog/return-on-time-invested/) can help gauge the effectiveness of the meeting, allowing participants to add reactions, comments, or GIFs can increase participation and add an element of fun to the retrospective. **Consider the psychological safety** of the space. If your team is new, looking to build up trust, or you wish to ensure personalities don’t influence the perception of ideas, having participants contribute anonymously or use an alias may help level the playing field. **Share the template** to counteract [recency bias](/blog/tips-to-overcome-recency-bias-in-your-retrospectives/). By sending the template out at the start of the sprint with the brainstorming page open, team members can add notes whenever they wish during the sprint. **(If it hasn’t already happened) circulate the action items** from the last retrospective in order to remind the team of what was previously agreed upon. This will ensure no one will feel they are being ambushed during the retrospective itself. ## Step 2 – Run the retrospective (collect data) **Warm up with an** [**icebreaker**](/icebreakers/virtual-icebreakers/), a simple activity, undertaking, or game that helps people foster connections and build rapport. Our [free icebreaker games](https://games.teamretro.com/games) run right in the browser — great for [remote teams](https://games.teamretro.com/use-cases/remote-teams) joining from anywhere. **Then kick off with an overview** of the retrospective to ensure everyone is on the same page. This can include quickly running through the team agreement and the process steps that make up the retrospective. **Keep an eye on the time**, this means starting on time and keeping an eye on the clock. [Timeboxing](/blog/timeboxing-for-scrum-teams-and-successful-retrospectives/) is a great way to do this. **Maximize** **engagement** throughout the retrospective with – - permission-based progression (questions such as ‘is everyone happy to move on?’, ‘can we head to the next step?’) - requesting clarification of ideas and responses - checking in with quieter participants **Leverage the online retrospective tool** to support the process and don’t be afraid to go back a step. The tool is there so there’s no need to remember what comes next, that’s not to say you can’t back track if needed. ## Step 3 – Look for ways to improve (decide what to do) With the key items prioritized and discussed, a key element of the retrospective, and indeed Agile is to determine what the next steps are to improve processes, increase value, solve problems or simply experiment on. **Give the team the space and time to** come up with potential solutions and proposed actions that the others can deliberate on. **Capture action items** as they are proposed, confirming they have been recorded correctly at the time. **Review all action items** (including those outstanding) and tick off those that have been delivered. Always align an action item to a date and person responsible for their delivery. This is a good time to talk about things that might be blocking an action or any impediments that might slow it down. ## Step 4 – Wrap things up (close the retrospective) **Finish up by summarizing** the main areas covered, the agreed actions, the time and date of the next retrospective, and **thanking** everyone for participating. **Share the summary** of the retrospective along with the agreed action items. **Follow up** with the team to help them stay accountable and to remove impediments If done properly, running remote retrospectives can bring an incredible amount of value to your team. ## Ready to run your retro? Using an online retrospective tool such as TeamRetro allows the Scrum Master or meeting facilitator to focus on the needs of the team rather than the mechanics of the online retrospective. Ideas and comments can be captured instantly and prioritized for discussions. Actions can be tracked, shared or integrated and followed up at the next meeting. Each person in the team has an equal opportunity to contribute in a psychologically safe space and can be time boxed to ensure everyone stays on task. TeamRetro takes care of the process so participants can focus on conversations and actions to take forward. There’s no need to take our word for it – you can [t](/retrospectives/)[est drive a range of retrospectives](/retrospectives/) or sign up for a [free trial](https://secure.teamretro.com/login/new) (without a credit card). Have a great retro! --- # How to tell if your team feels psychologically safe URL: https://www.teamretro.com/blog/how-to-tell-if-your-team-feels-psychologically-safe/ Psychological safety describes a workplace environment where individuals feel safe to take risks, share ideas, and experiment without fear of judgment or punishment. It’s not just a buzzword—it’s foundational to fostering creativity, collaboration, and innovation. Why does psychological safety matter? Because when team members don’t feel safe, they hold back. Fear stifles creativity and decision-making. In a retrospective, for example, the lack of psychological safety can lead to withheld ideas, silence during discussions, or resistance to feedback—all of which hinder the team’s ability to improve. ## The business case for psychological safety Psychological safety delivers value. It underpins key workplace outcomes like innovation, knowledge sharing, and productive conflict resolution—all of which are critical to high-performing Agile teams. Google’s landmark Project Aristotle revealed that psychological safety is the *most important factor* in team success. It’s the foundation that enables dependability, clarity, meaning, and impact—all crucial components of exceptional teamwork. Let’s explore how psychological safety (or the lack of it) shows up in your retrospectives and team dynamics. ## Signs of psychological safety in action ### 1. Conflict: how it’s managed matters | **In a Psychologically SAFE Space** | **In a Psychologically UNSAFE Space** | | :-- | :-- | | Conflict is observed and addressed. | Conflict is rare or entirely avoided. | | Conversations are candid and direct. | Conversations are overly diplomatic or brief. | | Concerns and alternative ideas are explored openly. | Ideas are rushed to consensus to avoid tension. | Psychological safety doesn’t mean the absence of conflict. Rather, it means conflict is embraced as a way to challenge ideas constructively and seek the best solutions. When teams feel safe, members raise concerns, suggest alternatives, and work toward meaningful resolutions. **What to Watch For**: - **Unsafe**: Few disagreements or overly cautious language (“Maybe we could…” or “Possibly…”). - **Safe**: Healthy dissent, open debate, and exploration of diverse ideas. **Why It Matters**: Retrospectives thrive on honesty and diverse perspectives. A team that avoids conflict may miss opportunities for breakthrough improvements. ### 2. Engagement: who’s at the table? | **In a Psychologically SAFE Space** | **In a Psychologically UNSAFE Space** | | :-- | :-- | | High and voluntary participation. | Low engagement or minimal input from members. | | Everyone contributes ideas. | The team leader dominates discussions. | | Questions and feedback flow freely. | Questions and feedback are rare. | When people feel safe, they focus on the work instead of self-preservation. They’re more likely to voice opinions, ask questions, and challenge assumptions—all critical behaviors in retrospectives. **What to Watch For**: - **Unsafe**: Silent team members, reluctance to ask questions, or passive agreement. - **Safe**: Robust discussions, enthusiastic contributions, and curious questions. **Why It Matters**: Engaged team members drive more effective retrospectives. Higher engagement leads to better decisions, stronger accountability, and actionable improvements. ### 3. Mistakes: are they discussed or hidden? | **In a Psychologically SAFE Space** | **In a Psychologically UNSAFE Space** | | :-- | :-- | | Mistakes and failures are shared openly. | Mistakes are hidden or denied. | | Problems are analyzed for improvement. | Problems are ignored or blame is assigned. | | Lessons learned are shared with the team. | Errors are avoided in discussions. | How your team reacts to mistakes can reveal a lot about psychological safety. In a safe environment, mistakes are viewed as opportunities for learning and growth. When safety is absent, mistakes are sources of fear—and blame. **What to Watch For**: - **Unsafe**: Reluctance to admit errors, finger-pointing, or silence about problems. - **Safe**: Open acknowledgment of mistakes, shared problem-solving, and learning moments. **Why It Matters**: Retrospectives are a prime opportunity to learn from mistakes. Teams that embrace errors as learning experiences improve faster and more consistently. ### 4. Team connectedness: trust and relationships | **In a Psychologically SAFE Space** | **In a Psychologically UNSAFE Space** | | :-- | :-- | | Team members know each other personally and professionally. | Interactions are limited to professional contexts. | | Help is offered and requested freely. | Help is limited to formal roles and responsibilities. | | Connections span across organizational levels. | Connections are siloed within the team. | Strong interpersonal connections are a hallmark of psychological safety. When team members trust and understand one another, they’re more willing to collaborate, give feedback, and embrace diverse perspectives. **What to Watch For**: - **Unsafe**: Limited personal interaction, rigid adherence to roles, or fear of “judgment from above.” - **Safe**: Genuine connections, mutual support, and a sense of belonging. **Why It Matters**: Trust and empathy foster collaboration, creativity, and resilience—key ingredients for productive retrospectives and team success. ### 5. Measuring psychological safety | **In a Psychologically SAFE Space** | **In a Psychologically UNSAFE Space** | | :-- | :-- | | Team uses surveys and tools to measure safety regularly. | Measurement is avoided or done superficially. | | Honest feedback is encouraged and received anonymously. | Feedback is rare, and team members fear reprisal. | How do you know if your team feels psychologically safe? Consider using structured tools and frameworks to measure safety levels: - **Amy Edmondson’s Psychological Safety Scale**: A [research-backed framework](https://hbr.org/2023/02/what-is-psychological-safety) for assessing team safety through targeted questions. - **TeamRetro’s Team Health Check**: A [quick, effective way](/health-check-templates/team-health-check/) to measure and track psychological safety over time, identifying specific areas for improvement. **What to Watch For**: - **Unsafe**: Ongoing and persistent low morale and team health scores that cannot be readily mitigated or a lack of engagement. - **Safe**: A balanced set of team health metrics with a relatively high level of engagement and participation. **Why It Matters**: Measurement ensures you’re making progress toward a safer and more productive team culture. ### 6. The role of leadership in psychological safety | **In a Psychologically SAFE Space** | **In a Psychologically UNSAFE Space** | | :-- | :-- | | Leaders admit mistakes and show vulnerability. | Leaders avoid admitting fault and appear infallible. | | All voices are actively invited into discussions. | Only a few dominant voices shape decisions. | | Empathy and support are demonstrated consistently. | Concerns are dismissed or minimized. | Leaders play a pivotal role in shaping a psychologically safe environment. Key behaviors include: - **Vulnerability**: Admitting their own mistakes to normalize imperfection. - **Inclusivity**: Actively soliciting input from all team members, especially quieter voices. - **Empathy**: Demonstrating understanding and support when team members share concerns or make mistakes. **Why It Matters**: When leaders model these behaviors, they set the tone for the rest of the team, creating a culture of openness and trust. ### 7. Psychological safety and innovation | **In a Psychologically SAFE Space** | **In a Psychologically UNSAFE Space** | | :-- | :-- | | Bold ideas and experimentation are encouraged. | Risk-taking is avoided due to fear of failure. | | Divergent thinking is celebrated and explored. | Teams default to groupthink or safe decisions. | | Knowledge is shared freely across the team. | Knowledge hoarding occurs to maintain control. | Psychological safety is a catalyst for innovation. When team members feel secure: - They are more likely to experiment and propose bold ideas. - They engage in divergent thinking, exploring multiple solutions to a problem. - They share knowledge freely, leading to better decision-making and collaboration. **Why It Matters**: Teams that innovate are better equipped to adapt to change and deliver value—a critical advantage in today’s fast-paced environment. ### 8. Psychological safety in remote teams | **In a Psychologically SAFE Space** | **In a Psychologically UNSAFE Space** | | :-- | :-- | | Team members use cameras to build connections. | Video is avoided, limiting trust-building cues. | | Clear norms support respectful and open dialogue. | Communication norms are vague or non-existent. | | Anonymous tools encourage honest feedback remotely. | Feedback mechanisms are missing or ignored. | Creating safety in virtual environments can be challenging but is entirely possible. Consider these tips: - **Use Video Calls**: Seeing facial expressions helps build trust. - **Set Clear Communication Norms**: Encourage open dialogue and respectful disagreement. - **Leverage Tools Like TeamRetro**: Facilitate anonymous input to make everyone feel heard. **Why It Matters**: Remote teams can thrive when they feel connected and secure, leading to more effective collaboration and retrospectives. ### 9. Psychological safety in retrospectives A retrospective is only as effective as the environment in which it takes place. When team members feel safe, they engage deeply, explore ideas fearlessly, and learn from mistakes openly. Conversely, an unsafe environment leads to superficial discussions and missed opportunities for growth. **How TeamRetro Can Help:** - **Check-in and Check-out Questions**: Begin and end retrospectives with thoughtful questions to gauge team mood and reflections, such as: - ***Check-in**:* “How are you feeling about this sprint?” or “What’s one thing you’d like to achieve today?” - ***Check-out**:* “What’s one thing you’re taking away from today’s discussion?” or “How are you feeling after this retrospective?” - **Independent Brainstorming**: Encourage team members to ideate privately before sharing, reducing the influence of dominant voices. - **Unbiased and Private Voting**: Use private voting tools to prioritize ideas or actions without bias or peer pressure. - **Anonymity**: Enable anonymous feedback and suggestions to ensure everyone feels secure in sharing their honest thoughts. - **Retrospective Templates**: Use tools designed to encourage open dialogue and structure meaningful conversations. - **Icebreakers**: Kickstart sessions with activities that build trust and break down barriers. - **Team Health Checks**: Monitor psychological safety regularly and identify areas for improvement. - **AI-Powered Insights**: Spot patterns and address issues before they escalate. ## Comprehensive overview: safe vs. unsafe behaviors | **Category** | **In a Psychologically SAFE Space** | **In a Psychologically UNSAFE Space** | | :-- | :-- | :-- | | **Conflict Management** | Conflict is observed and addressed constructively. | Conflict is rare or avoided entirely. | | | Conversations are candid and direct. | Conversations are overly diplomatic or brief. | | | Concerns and alternative ideas are explored openly. | Ideas are rushed to consensus to avoid tension. | | **Engagement** | High and voluntary participation from all team members. | Low engagement; discussions are dominated by a few voices. | | | Everyone contributes ideas and asks questions. | Questions and feedback are rare. | | | Robust, enthusiastic discussions. | Team members appear passive or reluctant to share opinions. | | **Handling Mistakes** | Mistakes and failures are shared and analyzed for learning. | Mistakes are hidden, denied, or met with blame. | | | Lessons learned are shared with the team. | Errors are avoided in discussions. | | **Team Connectedness** | Team members know each other personally and professionally. | Connections are limited to formal, professional interactions. | | | Help is freely offered and requested. | Help is limited to strict roles and responsibilities. | | | Relationships extend across organizational levels. | Interactions are siloed within the team. | | **Measuring Safety** | Team uses surveys and tools to measure safety regularly. | Measurement is avoided or done superficially. | | | Honest, anonymous feedback is encouraged and acted upon. | Feedback mechanisms are missing or feedback is feared. | | **Role of Leadership** | Leaders admit mistakes, invite all voices, and show empathy. | Leaders avoid admitting fault, dominate decisions, or dismiss concerns. | | **Fostering Innovation** | Bold ideas and experimentation are encouraged. | Risk-taking and divergent thinking are avoided. | | | Knowledge is shared freely to improve collaboration. | Knowledge hoarding occurs to maintain control. | | **Remote Work Dynamics** | Video calls are used to build connection and trust. | Video is avoided, limiting trust-building cues. | | | Clear norms support open and respectful dialogue. | Communication norms are vague or nonexistent. | | | Anonymous tools encourage honest remote feedback. | Feedback mechanisms are missing or ignored. | Ready to build a safer, more engaged team? [Start your free trial with TeamRetro](https://secure.teamretro.com/login/new) to run safe and easy retrospectives, measure team health and track actions for improvement over time. Sign up today and create a space where innovation, connection, and productivity thrive! --- # What is planning poker? A beginners guide for agile estimation URL: https://www.teamretro.com/blog/how-to-use-planning-poker-in-agile-estimation/ Estimating user stories can be tricky. Too often, discussions drag on or estimates feel arbitrary. That’s where Planning Poker comes in — a fun, structured way to bring your team together for accurate, team based estimates. Planning Poker, also known as Sprint Poker or Estimation Poker, is a collaborative technique that helps Agile teams estimate the effort required for user stories or tasks. It’s a structured, often gamified activity that typically takes place before sprint planning. Using a deck of estimation cards, each team member privately selects a card that represents their view of the effort involved. When revealed, the group discusses differences and works toward consensus. ## What is an online planning poker session? In an online Planning Poker session, teams use digital cards instead of physical ones. Estimates are cast anonymously and revealed simultaneously. It’s more efficient, inclusive, and free from bias. If the estimates differ, the team discusses why. A second round of voting may follow, or the team can adjust the final score by consensus. This can be really useful for remote and hybrid teams, but works just as well for people in the same room to save time. This ensures that estimates reflect a shared understanding of the work, not just the opinions of the most vocal team members…. And avoids all that manual mental math and decimal place calculations in a flurry of post it notes. 👉 *Try it with your team:* [*Run a Planning Poker Session Online*](https://planning-poker.teamretro.com/) ## Why use planning poker in agile estimation? Here are 5 great reasons! 1. **It builds shared understanding** – by revealing everyone’s estimate, it uncovers assumptions, dependencies and missing details early, leading to better defined stories. 2. **It removes bias and groupthink** – Everyone estimates privately, so it’s not influenced by the most senior, confident or vocal team member, allowing balanced accurate estimates. 3. **Estimates are collaborative, and even fun** – Structured, inclusive processes keep estimation session focused, time boxed and engaging. A game-like nature can boost morale and participation. 4. **It improves accuracy over time** – By comparing complex tasks to simpler ones, teams naturally calibrate their sense of effort and complexity to help create smoother sprint planning. 5. **It encourages continuous learning** – Differences represent an opportunity to learn. It highlights technical risks, unclear requirements or edge cases and may help the team get a better understanding of what “done” really means. ## How to run a planning poker session (step-by-step) 👉 *Try it with your team:* [*Run a Planning Poker Session Online*](https://planning-poker.teamretro.com/) 1. **Add or import your list of tasks or items for estimations.** The facilitator presents the user story or task. Everyone should have enough context before estimating. 2. **Select a deck.** Decide on the estimation scale (e.g. Fibonacci, T-shirt sizes, [Powers of Two](https://columbia.edu/~ask2262/Obsessions/KudinoorFibonacciStoryPoints.pdf)). Since Planning Poker practitioners shy away from estimating by time (turns out humans are pretty bad at it), you also need to decide what measure – often referred to as the scale – you will use to estimate a task’s effort. These are the numbers or units you will see on your playing cards. 3. **Start estimating.** Each team member selects their card independently. Estimates remain hidden until everyone has chosen. 4. **Review together.** All cards are revealed at the same time to prevent bias. 5. **Discuss differences.** If estimates vary, the team discusses why. Often, the highest and lowest estimators explain their reasoning. 6. **Redo if needed.** A second round helps the team reach consensus. 7. **Record the estimate.** The final score is added to the backlog item, ready for sprint planning. ## Benefits of planning poker for teams Planning Poker is a practical way to bring clarity, confidence, and collaboration to your sprint planning. It helps teams move beyond guesswork by focusing on meaningful conversations about why something is complex, not just how long it will take. Every card turned becomes a spark for discussion about assumptions, dependencies, and risks that might otherwise stay hidden. When teams estimate together, they uncover blind spots early, align on priorities, and build a shared understanding of what “done” really means. Over time, this consistency leads to better sprint forecasts, fewer last-minute surprises, and more predictable delivery. It also levels the playing field by giving everyone from developers to designers to testers an equal voice, creating a culture where all perspectives matter. By treating estimation as a team learning moment rather than a numbers game, Planning Poker turns planning into a collaborative rhythm that keeps teams connected, informed, and focused on delivering value. ## When NOT to use planning poker Planning Poker is a great way to build shared understanding and align on effort, but it’s not always the best fit. Here are a few times to consider another approach: - **Story is too vague or oversized** – Estimating work that isn’t well defined can cause confusion. Refine or break it down first. - **Trivial tasks** – Small items, like fixing a typo, don’t need a formal estimation session. ## Pro tips for better sessions Some Agile teams choose to skip estimations because they find them time-consuming, inaccurate, or unnecessary. Estimates can easily be misinterpreted as commitments, leading to pressure and frustration rather than collaboration. Others feel that discussions often take longer than the value they provide, especially when requirements aren’t clear or when real data from past sprints offers better insight. For teams focused on continuous delivery and learning, estimation can sometimes feel like a distraction from actually building and improving. That said, when done with the right mindset and structure, estimation can still be a powerful tool for building shared understanding and alignment. Here are some pro tips to make your estimation sessions more effective: - **Use a reference story** – Select one baseline item (e.g. “Implement login with Google authentication”) and compare other stories against it. - **Estimate effort, not time** – Focus on complexity, not hours. - **Split or park unclear stories** – If consensus isn’t reached after two rounds, break the story down or revisit later. - **Encourage open discussion** – Differing estimates often surface risks or overlooked details. - **Use best case, worst case, and ideal scenarios** – Consider optimistic, pessimistic, and most likely effort to balance estimates. Want to go deeper? Our agile estimation guide covers [how to run a planning poker session](/guides/agile-estimation-guide/how-to-run-planning-poker/), [story points](/guides/agile-estimation-guide/what-are-story-points/), and [worked estimation examples](/guides/agile-estimation-examples/). ## Embrace the power of collaboration Planning Poker is more than just an agile game. When used with intention, it becomes one of the simplest and most effective ways for Agile teams to stay aligned, reduce bias, and plan smarter together. 👉 Ready to give it a try? [Run your next Planning Poker session](https://planning-poker.teamretro.com/) and see how simple, inclusive estimation can transform your sprint planning. --- # 60+ icebreaker questions for agile and scrum teams URL: https://www.teamretro.com/blog/icebreaker-questions-for-agile-and-scrum-teams/ You know that awkward silence at the start of a sprint planning session? Everyone's on the call, someone's fiddling with their mic, and nobody quite knows how to kick things off. That's exactly what icebreaker questions are for — and when they're done well, they can shift the whole energy of a meeting in under two minutes. For scrum masters and agile practitioners, a good icebreaker isn't just a warm-up. It's what makes the difference between a meeting where people hold back and one where they actually show up. This guide covers icebreaker questions organized by agile ceremony — from daily standups to sprint retros — along with tips for running them well, a question of the day bank, and ideas for remote and hybrid teams. If you'd rather not pick by hand, our [free icebreaker questions game](https://games.teamretro.com/games/icebreaker-questions) serves one up for the whole team. > **⚡ Quick answer** > > Icebreaker questions help agile teams increase participation, build psychological safety, and improve collaboration. The best questions are short, optional, and matched to the ceremony being run. Use them at the start of standups, sprint planning, retrospectives, and team kickoffs to get people talking before the real work begins. ## Icebreaker questions by ceremony — quick reference Not sure which type of icebreaker fits your meeting? Here's the quick version: | Ceremony | Best icebreaker type | Time limit | Goal | | --- | --- | --- | --- | | **Daily standup** | Quick check-in | 30–60 sec | Get people talking | | **Sprint planning** | Reflection or curiosity | 1–2 min | Arrive mentally present | | **Retrospective** | Psychological safety | 2–3 min | Open up honest sharing | | **Team kickoff** | Personal connection | 3–5 min | Build team identity | ## What makes a good icebreaker question? A bad icebreaker can make people cringe, feel put on the spot, or quietly disengage. A good one takes about 60 seconds, gets a nod or a laugh, and opens people up before the real work starts. For a deeper look at the research behind this, check this article on [what makes the best icebreakers for teams](/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/). Here's the difference: | Good icebreaker | Bad icebreaker | | --- | --- | | Has no wrong answer | Puts someone on the spot | | Anyone can answer quickly | Requires deep thought or preparation | | Invites self-expression | Forces disclosure or vulnerability | | Fits the context and tone of the meeting | Same question used every week (gets stale) | | Passing is always allowed | Mandatory participation enforced | ## Five tips for running icebreakers well Before you dive into the question banks below, it's worth knowing what separates a good icebreaker from one that falls flat. These five things make the difference. 1. **Answer first.** Before asking your team, give your own answer. It models the behavior you want and creates psychological safety. As [Prof. Amy Edmondson of Harvard Business School](https://hbr.org/podcast/2019/01/creating-psychological-safety-in-the-workplace) has shown, safety starts with the person at the top of the room. 2. **Rotate who picks the question.** Don't let the scrum master own it every time. Rotating builds buy-in and gives people a reason to engage before the meeting even starts. A [random name picker](https://games.teamretro.com/games/random-name-picker) makes choosing who goes next fair and bias-free. 3. **Match the depth to the ceremony.** A standup gets a 30-second question. A retrospective can handle something more reflective. Don't use a deep team bonding question before a 15-minute standup. 4. **Time-box it explicitly.** Tell the team: "We're spending 90 seconds on this before we begin." Naming it makes it feel intentional, not chaotic. 5. **Make passing normal.** Some days are hard. Let people say "pass" without explanation. That's the difference between an icebreaker and an interrogation. For a full breakdown of each of these, see our guide on [top tips for running effective icebreakers](/blog/top-5-tips-for-running-effective-icebreakers/). ## What are the best icebreaker questions for agile teams? With the basics covered, here are the question banks. Each section is matched to a specific ceremony so you're not guessing which question fits which meeting. ### Standup icebreaker questions (keep it under 60 seconds) Standups are short by design. One quick standup icebreaker question, answered in a single sentence, is all you need. If you want a ready-to-go set, [TeamRetro has standup-specific icebreaker questions](https://games.teamretro.com/icebreakers/icebreaker-questions/for-standups) you can share as a link — no account required for participants. 1. What's one word that describes how you're feeling today? 2. If your current sprint were a weather forecast, what would it be? 3. What's one small win from yesterday — inside or outside work? 4. Tea, coffee, or something else — and why? 5. What song would be the theme tune for your day so far? 6. What's your current browser tab count? 7. On a scale of 1–5, what's your energy like today? 8. What emoji sums up your morning? 9. What is the most unusual kitchen utensil you have? 10. What would your out-of-office message say if you were being 100% honest? ### Sprint planning and backlog refinement These sessions require focused thinking. A slightly warmer icebreaker helps people arrive mentally before the work begins — without eating into planning time. 1. What's one thing you're genuinely looking forward to this sprint? 2. If this sprint were a film genre, what would it be? 3. What's one assumption you're holding about this work that you'd like to test? 4. What's the most useful thing you learned last sprint? 5. What's one thing you're hoping goes differently this sprint compared to the last? 6. If you could swap one item on the backlog for something completely different, what would you add? 7. What tool or process has saved you the most time recently? ### Sprint retrospective icebreakers 1. On a scale of 1–10, how would you rate your energy this sprint? What would have made it a 10? 2. What's one word you'd use to describe last sprint — and one word for how you want the next one to feel? 3. What's something outside work that went well for you recently? 4. If last sprint were a TV show, what would this episode have been called? 5. What's one thing you learned — about the work, the team, or yourself — this sprint? 6. What's one thing you wish you'd said out loud during this sprint but didn't? 7. If you could change one thing about how we work together, what would it be? (Great segue into the retro itself.) 8. What's a small, specific thing another team member did this sprint that you appreciated? ### Team bonding questions for kickoffs and new members When the team is new or someone just joined, team bonding questions need to do more heavy lifting. Give people a little more time here — these also work well as agile team building activities when you have a full team day or onboarding session. 1. What did you want to be when you grew up — and how close did you get? 2. What's a skill or hobby you have that most people here wouldn't guess? 3. Tell us your name, your role, and one thing that brought you genuine joy this week. 4. What's your remote work superpower? 5. What does your ideal workday look like? 6. What's something you've changed your mind about in the last year? 7. What's the best piece of professional advice you've ever received? ## Agile team building activities and icebreaker games Sometimes a question isn't enough — especially for kickoffs, team days, or when you want to do something a bit different before a retro. [Agile team building activities](/team-building-activities/) that double as icebreakers give everyone a chance to interact without anyone being singled out. Some formats that work well: - **Icebreaker Questions** — choose from a category, create your own, or let AI generate something new. Spin the wheel to see who goes next. - **Emoji Guess** — emojis appear one by one to reveal a hidden answer. Race to guess it first. Fast, competitive, and works great before a standup. - **Imposter Syndrome** — everyone gives a one-word clue based on a secret image, but one person saw something different. Use the clues to vote out the impostor. - **Franken-draw** — each person draws a hidden section of a creature without seeing the others. Stitch them together at the end for chaotic results. Great for team days and kickoffs. - **Teams Against Agility** — a cheeky card game where you submit your funniest answer to a prompt and the judge picks the winner. Perfect for end-of-sprint wind-downs. All free, no sign-up needed for participants — just share the link and play at [games.teamretro.com](https://games.teamretro.com/). ### Would you rather — agile edition 1. Would you rather have no sprint deadlines ever, or always have a perfectly clear backlog? 2. Would you rather pair-program all day or work in complete silence? 3. Would you rather have a two-hour retrospective with no action items, or a 10-minute one with three? 4. Would you rather never have another blocker, or have blockers that always resolve in under an hour? 5. Would you rather run every meeting as an async video, or never have another async update? 6. Would you rather be the best estimator on the team or the best facilitator? ### This or that — quick warm-ups 1. Kanban or Scrum? 2. Async standup or live standup? 3. Sticky notes or spreadsheets? 4. Two-week sprints or four-week sprints? 5. Verbose tickets or minimal tickets? 6. Story points or t-shirt sizing? 7. Sprint demo to stakeholders or skip it and ship? ## How to use a question of the day for work A [question of the day for work](/icebreakers/question-of-the-day/) is a simple recurring ritual: one rotating icebreaker question, answered by everyone, at the start of your regular meeting. Done consistently, it builds the kind of team knowledge that pays off in planning sessions, hard conversations, and the retrospectives that actually move things forward. The science backs this up: research from [Strategy+Business](https://www.strategy-business.com/blog/Why-the-first-five-minutes-of-a-meeting-shape-its-outcome) shows that the sooner someone speaks at the start of a meeting, the more they contribute throughout. Getting people talking in the first few minutes isn't a warm-up formality — it actively shapes the whole session. The question of the day works best when it's: - Owned by whoever is facilitating that day, not always the scrum master - Drawn from a shared bank the whole team contributes to - Time-boxed — 60 to 90 seconds maximum - Optional to answer — passing is always fine Consider building a simple rotation: each team member picks one question per week, posted in Slack before the standup. Over a few sprints, you end up with a team artifact that reflects your culture. For async teams, this works especially well — posting the question in Slack before the meeting gives quieter members time to think before they're asked to answer live. ## How do you use icebreakers in sprint retrospectives? A sprint retrospective icebreaker sits right at the start of the retro, before brainstorming begins. The goal isn't entertainment — it's to lower the emotional temperature in the room so people feel safe enough to be honest about what went wrong. Here's how to run one effectively: 1. **Pick a question that matches the tone of the retro.** If the sprint was rough, go warm and personal. If the team is in a good place, something playful works well. 2. **Answer it yourself first.** This sets the tone and models the openness you're hoping to see. 3. **Use a name spinner to decide who goes next.** TeamRetro's icebreaker tool does this automatically so no one is put on the spot. 4. **Time-box it.** Two to three minutes is usually enough. Set a visible timer and stick to it. 5. **Transition clearly.** Once everyone has answered, acknowledge it and move into the retro. The energy carries over. ## Should scrum teams use icebreakers every sprint? Yes, but keep them short and varied. The risk isn't overusing icebreakers, it's using the same one every sprint until it becomes a formality people zone out through. Here's what a healthy rotation looks like in practice: - Standup icebreaker questions every few days, drawn from a shared bank so it never feels repetitive - A new sprint retrospective icebreaker each retro, matched to the format you're running - Deeper team bonding questions and agile team building activities at kickoffs, team days, or when someone new joins Teams that do this consistently tend to have higher psychological safety, more honest retrospectives, and fewer people "on mute but not really there." It's a small habit with a compounding return. ## Icebreaker for remote and hybrid agile teams That applies to remote and hybrid teams too — arguably even more so. Without the casual hallway conversations and visible body language of an office, those two minutes at the start of a meeting often carry more weight than they would in person. Check out our dedicated post on [virtual icebreakers for remote teams](/blog/virtual-icebreakers-for-remote-teams/) for a full list of activities designed for the online space, and our broader guide on [running great retrospectives with remote and distributed teams](/blog/how-to-run-great-retrospectives-online-with-remote-and-distributed-teams/). ### Ideas that work well online - Visual prompts: "Hold up something on your desk that represents how you're feeling" gets people off mute and on camera. - Async questions of the day: post in Slack before the meeting so quieter team members can think and respond at their own pace. - Polls and reactions: "Beach or mountain cabin — drop an emoji" gets everyone interacting without putting anyone on the spot. ### Remote-specific icebreaker questions 1. What's your current background noise? 2. Show us something in your workspace that you actually like. 3. What's the best thing about working from where you work right now? 4. If your home office had a name, what would it be? 5. What's your go-to WFH beverage — and how many have you had today? 6. What's the strangest thing that has ever appeared on screen during one of your calls? 7. One skill that helps you work remotely that you didn't expect to need: ## Wrapping up: small questions, big impact Icebreaker questions aren't about forcing fun — they're about creating the conditions for real collaboration. People perform at their best when they feel safe enough to take interpersonal risks — and that starts long before the hard conversations happen. Start small. Pick one standup icebreaker question or a sprint retrospective icebreaker and rotate it. Watch what happens over a few sprints. The teams with the most honest retros and the healthiest sprint rhythms are almost always the ones that also take two minutes at the start of every meeting to actually connect as people. Want to go further? Here are the best places to start: - [How to run an icebreaker](/blog/how-to-run-an-icebreaker/) — step-by-step facilitation guide - [Virtual icebreakers for remote teams](/blog/virtual-icebreakers-for-remote-teams/) — activities designed for the online space - [Quick icebreakers to launch your next retrospective](/blog/quick-but-effective-icebreakers-to-launch-your-next-retrospective/) — matched to specific retro formats - [What makes the best icebreakers for teams](/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/) — the research behind why they work - [Top 5 tips for running effective icebreakers](/blog/top-5-tips-for-running-effective-icebreakers/) — practical tips for facilitators - [Fun retrospective ideas](/blog/fun-and-easy-retrospective-ideas/) — agile team building activities for when you want to mix it up - [TeamRetro icebreaker tool](/icebreakers/) — free tool with name spinner, timer, and AI questions built for agile teams TeamRetro makes it easy to run collaborative retrospectives with everyone contributing honestly — whether they're in the room or dialing in from the other side of the world. [Icebreakers are built in](https://help.teamretro.com/article/405-the-retrospective-process-icebreaker) so you never have to start from scratch. 💡 Ready to run your next icebreaker? [Try it free at games.teamretro.com →](https://games.teamretro.com/) --- # Ensuring top-tier data security with TeamRetro: our journey to SOC2 and GDPR compliance. URL: https://www.teamretro.com/blog/is-teamretro-soc2-compliant/ At TeamRetro, we understand the paramount importance of data security and compliance for our valued customers. We are pleased to announce that we are SOC 2 Type I and Type 2 compliant. You can also get a copy of our [SOC 3 report](/documents/groupmap-soc-3-final-report-2026.pdf). Specifically: TeamRetro is SOC 2 Type 2 accredited for Security, Confidentiality, Availability and Privacy. An independent auditor has evaluated our policies, product, platform, and infrastructure in accordance with the Standard on Assurance Engagements (ASAE 3150) and verified that TeamRetro complies with their stringent requirements. You can request a copy of our SOC 2 report via our [Trust Center](https://trust.teamretro.com/). Achieving this standard with an unqualified opinion provides a third-party industry validation that TeamRetro provides enterprise-level security for customers’ data. The independent audit was conducted by [Assurance Lab](https://www.assurancelab.com.au/?hsLang=en) following the SSAE 18, ISAE/ASAE 3402, and GS 007 standards. Their accredited reports were provided through their AICPA Partners, a leading association for accounting professionals. An unqualified opinion on a SOC 2 Type 2 audit report demonstrates to TeamRetro’s current and future customers that TeamRetro manages customer data with adherence to the highest security and compliance standard. Information security practices, policies, procedures, and operations meet the SOC 2 standards for security. We also uphold the principles of the General Data Protection Regulation (GDPR), providing our customers the choice to host in either the US or the EU. Here are some of the ways we keep your data secure and maintain your confidentiality and privacy. ## Secure personnel - TeamRetro takes the security of its data and that of its clients and customers seriously and ensures that only vetted personnel are given access to TeamRetro resources. - All TeamRetro contractors and employees undergo background checks prior to being engaged or employed by us in accordance with local laws and industry best practices. - Confidentiality or other types of Non-Disclosure Agreements (NDAs) are signed by all employees, contractors, and others who have a need to access sensitive or internal information. - We embed the culture of security into our business by conducting employee security training & testing using current and emerging techniques and attack vectors. - Our policies, internal systems, and access are based on role and function and are designed to ensure we can continue supporting customer needs without compromising data privacy. ## Secure development - All development projects at TeamRetro, including support services, follow secure development lifecycle principles. - All development of new products, tools, and services, and major changes to existing ones, undergo a development box review approval to ensure security requirements are incorporated into the proposed development. - Software development is conducted in line with [OWASP Top 10](https://owasp.org/www-project-top-ten/) recommendations for web application security. - We maintain documented Systems Development Life Cycle policies and procedures, as well as backups, availability, and change control. ## Secure testing - TeamRetro deploys third-party penetration testing and vulnerability scanning of all production and Internet-facing systems on a regular basis. - We perform static and dynamic software application security testing of all code, including open-source libraries, as part of our software development process. - Our applications are tested on staging environments using anonymized, aggregated, and non-identifying data before deployment and undergo a formal approval process. - We employ a web application firewall and security management platform to enable continuous and ongoing application protection. ## Cloud security - TeamRetro’s cloud ensures security with complete logical customer isolation in modern architecture. TeamRetro’s cloud leverages the native physical and network security features of the cloud service and relies on the providers to maintain the infrastructure, services, and physical access policies and procedures. - All data is also encrypted at rest and in transmission to prevent unauthorized access and data breaches. - We implement role-based access controls and the principles of least privileged access and revoke access as needed. The full TeamRetro Privacy Policy is published on the TeamRetro website at [teamretro.com/privacy](/privacy/) and addresses how personal information and intellectual property are collected, used, retained, disclosed, disposed of, and anonymized. The Privacy Policy also provides details of the assigned Privacy Officer, assigned EU and UK Representative, and contact information. Further information and requests for a Data Processing Agreement can be found at [teamretro.com/gdpr](/gdpr/). Enterprise clients interested in receiving a copy of our SOC 2 Type 2 or Type 3 report can do so at [teamretro.com/security](/security/). ## What is TeamRetro? TeamRetro is an enterprise-ready online retrospective tool for remote teams. Our guided retrospectives and health checks ensure productive and effective meetings – every single time. We’re SOC 2 Type 2, GDPR compliant, and ready to help agile leaders and teams drive continuous improvement. --- # Easy and fun remote retrospectives: insights from World Retrospective Day 2020 URL: https://www.teamretro.com/blog/making-the-most-out-of-remote-retrospectives/ ## Celebrating the power of remote retrospectives World Retrospective Day 2020 is a volunteer-based, globally coordinated effort to share stories and insights to improve Agile retrospectives. Two events held were the World Retrospective Day Lightning talks by Remote Forever and the Agile Club of Egypt monthly meetups. As teams become increasingly remote, running online team meetings that empower and drive continuous improvement is a key focus for Scrum masters. While there may be reduced travel costs and time, there are increased challenges in how remote meetings, especially retrospectives can be best run to ensure engagement and a sense of connection. [TeamRetro’s](/) CEO and Co-Founder, Jeremy Lu, spoke at both events on the topic of **“Making the most out of your remote retrospectives.”** We share some of the key messages as well as learnings and insights from both the events here. ## The pros and cons of running remote retrospective meetings Going digital does mean adjustments to how team meetings run. But there are some neat benefits. Removing production blocks, reducing bias and allowing independent brainstorming and voting for actions can improve the quality of data as well as build psychological safety. Time that would have been spent writing up reports, manual collation and recording can now be spent on team relationships or giving more time to deep dive into discussions that matter. On the other hand, reliance on an individual’s internet set up, security and the lack of accountability can negatively impact team trust. The increase of social dissonance as we lose the physical cues means that the role of the scrum master as the conductor of the social orchestra becomes evident. Building team culture from planned and explicit activities to setting ground rules for meeting hygiene are good practices to help to start to overcome these cons. At the same time, irrespective of whether or not the team is distributed, co-located, remote or some blended hybrid, individuals in a team want: - to be heard - to be valued - to be guided - to feel safe - to be resourced - to be grown So how can the humble retrospective play its role in helping address those team needs? Here are some ideas. ### 1. Develop a team social contract Setting the right focus and tone before you begin your retrospectives goes a long way to creating an engaging, safe and productive space for team members to speak up. The culture, group expectations, and agreed ground rules are more likely to stick and have an impact if they are created together and made visible. We grabbed a couple of balloons and all wrote down things that we heard but did not feel like it was useful for a meeting. We then “popped” these balloons in an audible and significant way if we noticed these behaviors and words in a meeting. We then wrote down a list of guiding behaviors that our team wanted to use as part of our retrospectives as well as any team meetings and frame this when we kick start our remote retrospectives. In fact, it appears on our remote retro. If you don’t want to go that far, then you can always rely on the Agile Prime Directive. However, addressing basic meeting etiquettes such as turning on cameras and audio, call signals to slow down, speed up, or make comments and other rituals can help make meetings more successful. If accountability and social dissonance are common in your meetings, then having processes like round-robin discussions, call-out facilitated conversations or liberating structure formats can help build that team engagement. **Takeaway**: Whether you do it formally or more of an informal ritual, understanding and managing the social contract for your team builds trust, psychological safety, and clear online meeting retrospective etiquette. **2. Pick the right retrospective format to fit your purpose – fun? easy? focussed?** With so many different retrospectives formats and questions out there, Scrum Masters are spoilt for choice when it comes to variety. However, to get the most out of the retrospective, it was suggested that the choice of retrospective format requires intention, thought, and consideration so that it serves the purpose of the meeting. This does mean the format will change from time to time which in its own right will lend itself to reducing the repetition fatigue. It will also mean that you are entering the meeting with intent and can focus the conversation. Take this example below. This team used the Mad Sad Glad approach to kick off their initial retrospective. This format has a more personal touch and requires people to consider their emotional responses to the last sprint. It helps to air out any potential issues and address any emotional barriers to help teams move past the storming stages of team formation. The next few retrospectives focused more on action-based, focusing on a Stop, Start, Continue retrospective and the StarFish retrospective. These formats lend themselves to more action-based brainstorming and allow teams to consider time trade-offs between tasks. As teams transitioned to working from home, they then focussed on changes in the process and how to work from home to talk through what they needed to do in a remote environment, followed by a standard agile retrospective at the end of the year. Using the 4L retrospective next allowed them to reflect on the activities to date to share learnings as well as what they have liked and longed for. Finally, a FLAP (Future considerations, lessons learned, Accomplishments and Problem areas) was a futurespective process to help the team decide what they wanted to see going forward. Of course, you can always create your own set, or choose topics that are seasonal or interest-based. There’s also the option to create retrospectives based on interest, festive seasons, famous TV shows, or a shared passion. **Takeaway**: While a variety of retrospective formats is great to break meeting fatigue cycles, choosing one that is aligned with your team and product’s current state can improve the focus, intention and outcomes of your retrospective meetings. **3. Power up your retro flow.** Beyond splitting groups into smaller breakout rooms, there are some additional ways that you can level up on your team meetings. At the start of each retro, run a short, sharp but friendly activity that allows people to check-in. Share a word, or facial expression that demonstrates how you felt about the last sprint, or even what was the last thing that made you smile is a great way to kick start the meeting. Remind them about the prime directive, social contract and remind them of why they are here to do. You can assign roles so that people can all contribute. The Co-pilot can help manage the tech and meet goals. The time police keep the meeting flowing and reminds people on time as they start to overrun. The energy monitor might run a quick check-in during the meeting or get a sense from people as to how the meeting is going and the Action Avenger can call out if there are actions that are not being discussed or captured. Using a range of facilitation methods that allow people to contribute throughout the process keeps people engaged and lets you sense the vibe of the room. For E.g. using reactions on comments helps to capture sentiment, and the pass the baton pattern means that one participant can pick the next speaker. Finally, if your meetings are longer than an hour then include a planned break. It just gives people time to breathe and re-calibrate. Take a break away from the screen or run an activity with the team that’s fun and can lift the energy. We call for lights out which means mics and cameras on (music on if they want) for a little focus time before coming back together. **Takeaway**: Team engagement strategies through powering up the process flow at the very start and throughout the meeting can lift energy and accountability. **4. Experiment with different time-box recipes.** One way we can make sure meetings don’t run overtime is to use time-boxing. There’s a [countdown timer](/blog/timeboxing-for-scrum-teams-and-successful-retrospectives/) in TeamRetro for each stage that can be used for example to give people a sense of how much time is left, as well as the I’m finished button to give you the heads up when people are ready to move on. Assuming you are running an asynchronous 60-minute meeting, here’s our time box recipe that seems to work. It may however be better to think of this in terms of a base recipe rather than a formal guide. Much like the pizza dough, the final pizza flavor is the combination and quantity of ingredients you decide to add on. If you think there’s a greater need for team bonding, then check-ins, appreciations, and check-outs might be important. Data can be gathered before the meeting asynchronously. Grouping of similar ideas can be done before the meeting and then ideas are voted on when read for discussion. Alternatively, if there is less need for rapport building, then this might be used more on building consensus for action items. For self-organizing teams, allow more time for them to group ideas that have come up. If there are lots of comments, then have them work in smaller groups under specific sections. While this might be good for a 60-minute meeting, you can simply change the ratios for a longer session. **Takeaway**: The end of the meeting time is the main constraint for teams who like to finish on time with clear outcomes. Trying out new time-box recipes can help keep meetings on track and be a good marker for guiding conversations. **5. Make your retrospectives easy, fun and human!** Remember bring a pet day? Crazy shirt/hat day? Share a meal day? Who says we can’t do that online? Adding a little fun and team-building activity can be a good way to relieve stress, learn a little more about your team and get insights you won’t find in your standard retrospective. Here are a few things we heard teams have been doing while remote. (Some of our teams actually do this at the end as a reward for a good retrospective.) - Use mood checkers. - Play a game – agile or just for fun. - Watch a movie together on Discord. - Run a team-building activity — for example, if you are in a plane that crashed into a desert, what 10 items you want with you in order to survive. - Story or picture telling: try asking everyone to tell a story about something, even something as small as a cup or a pair of shoes! Or to take a picture of something near them to share - Guess the song: test your scrum masters singing capabilities by asking them to sing songs for the team to guess! - Solve a random problem that someone else in the team has. - Share a recipe that everyone tries at home and tastes. **Takeaway:** Encourage compassion. It is not easy to move to a fully online team retro or remote working. We as humans are social beings after all. Having some fun, social activities can make it easier to build bonds and empathy that can make your retrospectives more meaningful and effective. ## Excited to level up your remote retrospective? We hope these insights provide a little inspiration. If you have others you’d like to share or would just like to swap notes, ask for advice or find out more, [just get in touch!](/contact-us/) We’d love to hear from you. TeamRetro. --- # Feature spotlight: define your retrospective templates URL: https://www.teamretro.com/blog/new-define-your-retrospective-templates/ Here at [TeamRetro](/), we’re excited to share features to make your online, hybrid or face to face retrospectives even more organized, accessible and creative. We’re pleased to introduce a feature where you are able to define your own retrospective templates either for your team, or at an organizational level for all teams! Save your favorites in your template library that you can then use to run again. Let’s find out how this works. ### Create retrospective templates for a team This feature is applicable for one team who might want to creatively customize their own retrospective but is only relevant or applicable to just that one team. For example, we created an [Avengers themed customized retrospective template!](/blog/3-nifty-ways-to-keep-your-retros-fun-and-exciting/) Creating Icons from Icons8, we went about representing different aspects of our online retro. Here’s what we came up with. - **Captain America**: What do we want to protect? - **Iron Man**: What experiments should we try? - **Hulk**: What do we want to change? - **Black Widow**: How can we improve our team? - **Thor**: What are our biggest strengths? - **Hawkeye**: What support do we need? #### You can create your own team retrospective templates when you create a new retrospective, or under your team settings. ### Create and share retrospective templates for the organization. This feature is very handy if you would like your teams across the whole of your organization to use the same retrospective templates so that it is consistent or aligns with your culture, language and values. If you create an organizational template, these will be accessible by all users associated with your organization’s accounts. It’s a creative way to share the love of good practice, successful retrospectives and even offering choice and alternatives for your colleagues and fellow scrum masters. #### You can create your own organizational retrospective templates when you create a new retrospective, or under your organizational settings tab. ### Questions about our new feature? Thank you to our community of TeamRetro users for this suggestion. This idea first came from a financial institution in France who had an extremely creative team. They created custom templates including the “Three Little Pigs” asking what would fit under a House of Straw, a House of Sticks and a House of Bricks. If you have any questions about this new feature, [reach out to us anytime.](/contact-us/) --- # 12 new retrospective ideas to break the rinse and repeat cycle URL: https://www.teamretro.com/blog/new-retrospective-ideas-to-break-the-cycle/ We're halfway through the year. If your retrospective has settled into the same three columns, the same five people talking, and the same quiet nod at the end, you already know what next sprint's retro will sound like. That predictability is the problem. When a team can guess the questions, they start giving you guessable answers, and the honest, awkward, genuinely useful stuff never makes it onto the board, let alone the action list. So I went looking. As our team's Scrum Master, part of my job is to keep the room alive, and over the last few months our team has worked through dozens of different retrospective formats from the [retrospective template library](/retrospective-templates/). Most were fine. Some fell flat. But a handful genuinely broke the cycle: they changed the questions, changed who spoke up, and surfaced things our usual format never would. These are the ones we have handpicked to refresh the palette as they say. One thing up front, because it matters: **this isn't about making your retro silly.** A themed board or a playful prompt isn't the point; it's simply the on-ramp. The goal is to lower the stakes just enough that people feel safe saying the real thing, in a format their brain hasn't already pre-answered. Fun is the mechanism; honest improvement is still the outcome. ## Why the same retro stops working There's nothing wrong with [Start, Stop, Continue](/retrospective-templates/start-stop-continue-retrospective/) or [Mad, Sad, Glad](/retrospective-templates/mad-sad-glad-retrospective/). They're classics because they work. But any format, run on repeat, eventually trains the team to autopilot. People learn the shape of the answer the format wants and give you that, not what they actually think. This isn't just my experience: Mike Cohn warns that the same thing happens to any retro [conducted "the same way each and every time"](https://www.mountaingoatsoftware.com/blog/overcoming-four-common-problems-with-retrospectives), and Retromat creator Corinna Baldauf [puts it plainly](https://retromat.org/blog/why-do-we-vary-activities/): "if you keep asking the same questions, you will keep getting the same answers." So here are the formats that did the unsticking for us. Each links to a ready-to-run template. Pick one for your next retro and see what surfaces. ## Break the format, not just the questions Changing the *questions* helps a little. Changing the *format* helps a lot. A new structure makes everyone approach the sprint from an angle they haven't rehearsed, which is exactly when the interesting stuff falls out. It's the same reason a change of scenery or a fresh metaphor unsticks a conversation: the brain can't coast. Atlassian makes the same case: [vary the technique, or retros go stale](https://www.atlassian.com/blog/teamwork/revitalize-retrospectives-fresh-techniques) and slide into glorified status meetings. Professional Scrum Trainer Stefan Wolpers files the never-changing retro as a named [anti-pattern](https://age-of-product.com/sprint-retrospective-anti-patterns/) he calls "Groundhog Day". And Aino Corry, author of [Retrospectives Antipatterns](https://metadeveloper.com/retrospective-antipatterns/), counts running every retro the same way among her antipatterns too; at the 2026 Online Scrum Master Summit she called breaking out of it "escaping the rinse". ### 1. Working, Not Working The [Working, Not Working retrospective](/retrospective-templates/working-not-working-retrospective/) strips everything back to two questions. No softening, no "glad", no metaphor, just *what's working* and *what isn't*. We ran this after a messy sprint where people were dancing around the real issue, and the bluntness of it gave everyone permission to be direct. Best when you want honesty over nuance and you're short on time. ### 2. KALM: Keep, Add, Less, More [KALM](/retrospective-templates/kalm-retrospective/) is the upgrade for teams who've outgrown Start/Stop. Instead of a binary "do it or don't", you get four dials: **Keep**, **Add**, **Less**, and **More**. That "Less / More" axis is the magic: most team problems aren't "stop doing this entirely", they're "we're doing too much of this and not enough of that". It surfaces the dial-turning conversations that Start/Stop forces into all-or-nothing. ### 3. What? So What? Now What? [What? So What? Now What?](/retrospective-templates/what-so-what-now-what-retrospective/) is built to fix the most common retro failure: lots of discussion, no action. You walk the team through three steps (what happened, why it matters, and what we'll do about it) so every observation is pushed toward a decision. If your retros keep generating the same complaints sprint after sprint without anything changing, this is the format that closes the loop. ### 4. Speed Car The [Speed Car retrospective](/retrospective-templates/speed-car-retrospective/) frames the sprint as a car: engines push you forward, parachutes hold you back, and there's a cliff ahead if you ignore the risks. It sounds light, but the metaphor does real work: people who'd never say "our process is slowing us down" will happily attach a parachute to the car. Great for surfacing friction without anyone feeling like they're pointing fingers. Unlike the [Sailboat retrospective](/retrospective-templates/sailboat-retrospective/), the key focus here is putting the team in the driver's seat. They accelerate, turn the wheel and move in the right direction... or not. ## Retros for the mid-year reset June is a natural checkpoint. Goals set in January have either drifted or quietly died, energy is different from where it started, and nobody's stopped to notice. These three are built for the halfway moment. ### 5. Mid-Year Goal Check-In The [Mid-Year Goal Check-In](/retrospective-templates/mid-year-goal-check-in/) is the obvious one to run this month, and most teams skip it. It pulls the team back to the goals you set at the start of the year and asks the honest questions: what's on track, what's slipped, and what's no longer worth chasing. Half a year of hindsight makes this conversation far more useful than it would've been in Q1: you're working with real evidence, not optimism. ### 6. Energy Levels The [Energy Levels retrospective](/retrospective-templates/energy-levels/) takes the team's temperature instead of the sprint's. Where's energy high, where's it draining away, and what's quietly burning people out? At the mid-year mark, when fatigue tends to creep in unannounced, this one catches the human signals that a velocity chart will never show you. Run it anonymously and you'll get the truth. ### 7. Appreciation Round The [Appreciation Round](/retrospective-templates/appreciation-round-retrospective/) is the simplest reset here, and the one teams underrate the most. Everyone calls out something a teammate did that made a difference. It's not filler: naming good work out loud refills the tank, builds the psychological safety that every other retro depends on, and reminds a tired team why the work matters. A great one to open a heavier session with. ## Retros for the AI era The way teams work has shifted fast, and the retro is a good place to make sense of it. These two are genuinely current; they didn't exist as conversations a couple of years ago. ### 8. AI Agents The [AI Agents retrospective](/retrospective-templates/ai-agents-retrospective/) gives the team space to reflect on how AI tools and agents are actually landing in your workflow: what's saving real time, what's creating new kinds of rework, and where the team needs clearer guardrails. If "should we be using this more, or less?" keeps coming up in side conversations, put it on the board. ### 9. AI Evolution The [AI Evolution retrospective](/retrospective-templates/ai-evolution-retrospective/) takes the longer view: how the team's relationship with AI has changed over time, and where it's heading. It's a good periodic check-in for teams who've moved past experimenting and want to be deliberate about how these tools fit their process. ## Themed formats that lower the stakes This is where the "fun" lives, and where I'll repeat the caveat. A theme isn't the point; it's a way to get a guarded team talking. Wrap a familiar reflection in an unfamiliar story and people drop their meeting-face. Pick a theme your team will actually enjoy, keep the questions real, and these earn their place. ### 10. Studio Ghibli Journey The [Studio Ghibli Journey retrospective](/retrospective-templates/studio-ghibli-journey-retrospective/) frames the sprint as a gentle adventure: the companions who helped, the obstacles along the way, the small moments of wonder. The calm, reflective tone is the opposite of a blame session, which makes it surprisingly good for teams that need to talk about a hard stretch without it turning tense. ### 11. KPop Demon Hunters The [KPop Demon Hunters retrospective](/retrospective-templates/kpop-demon-hunters-retrospective/) leans into a bit of pop-culture energy: the demons (problems) the team faced, the powers that helped you win, and the encore you're planning next. It's high-energy and a little ridiculous in the best way, ideal for a team that's been heads-down and needs the room to lift before it can reflect. ### 12. Among Us (Agile Edition) The [Among Us retrospective](/retrospective-templates/among-us-agile-edition-retrospective/) reframes the sprint around tasks completed, "impostors" (the hidden blockers that sabotaged your flow), and emergency meetings (the moments you had to regroup). The game framing makes naming blockers feel collaborative rather than accusatory: you're hunting the impostor together, not blaming a person. **And that's just the start.** Between themed boards, structured formats, and seasonal one-offs, there are 100+ ready-to-run options in the [retrospective template library](/retrospective-templates/), so you can keep rotating long after these twelve. ## How to introduce a new format without losing the room A new format only works if the team's with you. A few things I've learned the hard way: - **Say why.** Open with one line: *"We're trying a different format today to shake loose some new thinking."* People go along with novelty far more easily when they know it's intentional, not a gimmick. - **Match the format to the moment.** A bruising sprint wants [Energy Levels](/retrospective-templates/energy-levels/) or an [Appreciation Round](/retrospective-templates/appreciation-round-retrospective/), not a comedy theme. A coasting team can handle something playful. Read the room first. - **Keep the questions real.** The theme is the wrapper; the reflection underneath should be as serious as ever. If a prompt is only fun and surfaces nothing useful, cut it. - **Use anonymity for the honest stuff.** A fresh format lowers the social barrier; anonymous input lowers it further. For anything touching workload, trust, or morale, let people [contribute without attribution](/retrospectives/) so you get the real picture. - **Don't change every single time.** Novelty works because it's a break from the norm. Rotate formats every few sprints, not every sprint, or the "new" one becomes the new autopilot. ## Keeping it fresh *and* serious Here's the thing I want to leave you with. Bringing energy to a retro and taking the retro seriously are not opposites; they're the same job. A team that's relaxed, curious, and a little bit entertained will tell you things a tense, bored team never will. The format's job is to create that safety; your job as facilitator is to turn what surfaces into real, owned action. So this mid-year, break the cycle. Pick one format off this list that your team would never expect, run it at your next retro, and watch what comes out when people aren't on autopilot. Then do the serious part: capture the actions, assign the owners, and follow through. That's the whole game: a fresh way in, a serious way forward. ## Frequently asked questions **How often should you change your retrospective format?** Every few sprints, not every sprint. Variety works because it breaks the routine; change too often and the variety itself becomes the new autopilot. **Do fun retrospective formats actually improve outcomes?** Yes, when the questions underneath stay serious. The playful wrapper lowers the social barrier so people share honestly; the reflection and the action items are still the point. **What's a good retrospective to run at the mid-year point?** A Mid-Year Goal Check-In, ideally paired with an Energy Levels retro to catch fatigue before it spreads. **How do you introduce a new format without resistance?** Say why you're changing it, match the format to the team's mood, keep the questions genuine, and use anonymous input for the sensitive stuff. ## Break your team's retro cycle this month You don't need a hundred new ideas; you need one that your team won't see coming. Browse the [retrospective template library](/retrospective-templates/), pick a format that fits where your team is right now, and run it at your next retro. Fresh way in, serious way forward.
--- # Nine top agile retrospective ideas and games to keep your team engaged URL: https://www.teamretro.com/blog/nine-top-agile-retrospective-ideas-and-games-to-keep-your-team-engaged/ We all lose focus from time to time. As retrospectives get repeated and stale, people start to hit auto-pilot and get side-tracked or distracted in the retrospective. They start getting vague with their responses, put on their grumpy pants, or simply disengage altogether due to boredom. That’s why we have pulled together this list of nine of the best agile retrospective ideas and games to help keep your team engaged. These can help to support team connectedness, safety and fun. They bring focus to the room without singling anyone out. They can even help bring some fun to your meeting! ### 1. Energy levels Before the team jumps into the retrospective, ask everyone to call out, type or use their hands to indicate their current energy level. You can quickly see how the team feels and what energy is being brought into the retrospective. 5 means you are fully charged and ready to go. 1 means you are here but drained and running flat. This game is a perfect warm up for the [Energy Levels](/retrospective-templates/energy-levels/) retrospective idea which helps people share what charged them up, and what drained them from the last sprint. For more quick warm-ups before a retro, browse our [free icebreaker games](https://games.teamretro.com/games). This game can highlight what is motivating your team. Their responses give you insight into things that give them energy so that you can aim to replicate this going forward. Likewise knowing what they need to re-charge can set the next sprint off in the right direction. ### 2. Statement orbit Statement Orbit is a fun retrospective game that can get an agile team moving…literally! This can be used interactively for both online and in-person meetings. An object is placed in the middle of the room with the team members standing around it. If you are online, the camera can act as the object. Statements are read aloud, with team members invited to move toward the object if they agree with it and away from the object if they disagree. The size of the step they take should reflect the degree to which they agree or disagree. Here are some examples or you can have people go round and call out their own statement. - The last sprint went off without a hitch. - Everyone was able to complete their tasks to the right quality and at the right time. - We were able to demonstrate improved velocity. - There were no errors, rework or impediments. - We worked well as a team and created value. - We acted according to our Scrum Values. - We are working and acting according to our team agreements As people move back and forth, this lets you see where people are far apart. This can be followed up with a discussion. Then, you can align this with a retrospective theme. For example, you can build team cohesion and battle epics with the [Superhero retrospective](/retrospective-templates/superhero-retrospective/). If values and team agreements are not being experienced, then the [Scrum Values retrospective](/retrospective-templates/scrum-values/) may well be the way to go. ### 3. Sailboat retrospective If your last sprint left the team feeling all at sea and hoping for some plain sailing with their next one, then get onboard with this fun retro idea. The [Sailboat](/retrospective-templates/sailboat-retrospective/) retrospective is designed to help your crew reflect on their last sprint, and plot a successful course going forward. This can help them remember the vision and plan ahead based on what they have already learned and to develop a more positive mindset. Like all good sailors, they need to consider their conditions. The wind (what moves them forward), rocks (the risks they may face), the sun (what makes them feel good), anchors (what can slow things down or stop them completely) and, of course, where they are heading. This retrospective idea can be useful when your team is having trouble seeing the big picture or are kick starting off a new epic or project. It helps them focus on their goal and plot a course to achieve it! ### 4. Starfish retrospective If you are finding your retros a bit of a talk fest, with no action or commitment, then this action oriented format might be the way to go. The [Starfish](/retrospective-templates/starfish-retrospective/) retrospective idea helps teams to think about the degree to which actions and activities are most effective in creating value and team cohesion. It’s different from more traditional retro ideas because rather than just listing down what happened in the last sprint, the team is encouraged to be more specific and think about practices that are generating value. It can also help the team members gain insight into each other’s perception of those practices. As well as thinking about what they should start and stop doing, the team thinks about what they could do more and less of. They also define what they should keep doing. This way, the Starfish retrospective idea can help a team decide which of their practices should have more or less energy directed toward them. It can be a great way of helping a team step away from unhelpful practices without them feeling like they are going cold turkey. It’s best to run a Starfish after a few retrospectives have happened. This way the team has a period of activity to look back on and compare. ### 5. ESVP How do you ask people how they are feeling without asking people how they are feeling? You run an ESVP. The ESVP is designed to engage and focus on those involved in the retro. At the same time, it gains insight into the participants’ attitudes toward the agile retrospective meeting itself. ESVP stands for ‘Explorers, Shoppers, Vacationers and Prisoners’. Participants indicate which of four personas they most relate at that point in time. They are invited to choose from – An explorer – Will dive in and discover new things A shopper – Will see what can be procured A vacationer – Will relax and switch off A prisoner – Does not want to be there Setting the stage with an ESVP can help a Scrum Master gauge the attitudes of the people in the room. This lets them shape their next steps and helps everyone make the most of their meeting time. An ESVP can give everyone insight into the current motivations of the group. This means you’ll get more out of your meeting because you can see the attitudes and expectations of the people there and adjust your approach. ### 6. Rose bud thorn Roses aren’t just for Valentine’s Day or special occasions. The sweet scent of the rose can sometimes mask the thorns that serve to protect them. The [Rose, Bud, Thorn](/retrospective-templates/rose-bud-thorn-retrospective/) retrospective idea plays on this metaphor. It helps a team identify the positive outcomes (Rose), the opportunities (Bud), and the pains (Thorn) from their last sprint. This game reminds your team to approach challenges as manageable obstacles that come along with delivery value. Getting past the thorns, nurturing buds and then harvesting the blooms is the goal of this game. ### 7. The retro anti-pattern bingo This game has the team being made aware of things that can negatively impact a retro and to be on the active look out for them during a retro. Inspired by [Ben Linders](https://www.benlinders.com/), this game could be just the thing to help address issues without making people feel singled out. Each team member is given a bingo board that includes retro anti-patterns. This includes things like distractions, jumping to solutions, blaming the process, lack of action items. The center square is a wild card, or you can add your own anti-pattern. As the team goes through the retro, they can mark off things they noticed on their board. At the end of the retro, people can see if they scored 5 in a row. You could have people shout out “Bingo!” during the game but this could also serve as a distraction. This retrospective game is great for helping teams reset their behaviors, or simply introduce good meeting etiquette. It can also be a fun way to teach new teams what habits they should avoid. ### 8. Sherlock retrospective If you have a team of mystery buffs, try the [Sherlock](/retrospective-templates/sherlock-retrospective/) retrospective idea for your next meeting. It’s especially helpful if the team needs to unravel the cause of a particularly puzzling sprint. Engaging a team might not always be about fun. It could be the problem solving, logical aspects and feeling the sense of achievement when solving a tough problem. The team looks at their last sprint like a mystery. They list what cases were closed, and the clues that helped them. They define what they found to be elementary, as well as what puzzles remain. This way, like Sherlock, team members are encouraged to put emotion aside and just look at the facts. This easy retro can be a helpful way of encouraging teams to unpack tricky problems with calm and logic as they generate ideas. ### 9. GIF me a break! This retrospective game is simple, fast and fun. It works especially well with remote online agile teams. Just before the team jumps into the retro itself, each person is asked to find and share a GIF that represents the last sprint. The GIF they share could be quite topical, use a classic such [https://giphy.com/](https://giphy.com/). Each person picks a gif and then shares their screens to explain why they picked that gif. GIF Me a Break is a fun way a Scrum Master can gain insight into what the team thought of the last sprint without having to ask them directly. It’s also a way of injecting some fun into the meeting following a particularly challenging sprint. ## Bonus tips for running great retrospective ideas and games **Keep them inclusive** When choosing a retrospective idea make sure it’s one the whole team can enjoy. Keep language, accessibility and people’s backgrounds in mind. The simplest way of doing this might be to ask them which one they’d like to try. **Book end the retro with fun** Using games is a great way to build team connectedness. Making sure they are limited to the start and end of the retro is a great way to make sure they don’t become distracting and that your retrospective is still meaningful and worthwhile. **Timebox** Whether it be a great retrospective idea or fantastic game, timeboxing the game is an important principle in agile that can also be practiced while still making the retro valuable and fun. **Keep it relevant** Picking a theme, topic or issue that is relevant to your team is what keeps them engaged. Don’t simply rely on a theme. At the end of the day, making sure that people are able to relate to the discussion is what will drive engagement. ## Want more? Check out our [Scrum Master’s Retrospective Guide](/guides/scrum-masters-retrospective-guide/) where we look at [what agile games teams play to help them learn and grow](/guides/scrum-masters-retrospective-guide/agile-games-facilitate-team-building/). You can also head to our [agile blog posts](/blog/) for some [fun and easy retrospective ideas](/blog/fun-and-easy-retrospective-ideas/). TeamRetro lets you create engaging and effective Agile Retrospectives. Create and customize your own templates, explore team happiness and create actions for continuous improvement. [START A RETROSPECTIVE](https://secure.teamretro.com/login/new) --- # Online Retrospective Games vs. Formats: What Actually Works URL: https://www.teamretro.com/blog/online-retrospective-games/ A retrospective game isn't there to be fun. It's there to lower the guard that keeps remote teams polite, vague, and quiet, so you get the honest signal a retro depends on. That's why online retrospective games matter more than they look. On a video call, the usual cues that pull people into a conversation are gone. The confident talkers fill the silence and the quiet thinkers check out. A good game cuts through that, giving everyone the same low-pressure way in and surfacing the issues that would otherwise stay unsaid. But there's a catch: most of what gets called a “retrospective game” is really just a format with a nice picture on it. This guide draws a clear line between the two. On one side are the proven formats that structure most retros. On the other are the genuine games, the ones with an actual mechanic, that get a quiet team talking. We'll cover both, when to reach for which, and where even a good game hits its limit. ## Games vs. formats: why the difference matters A quick word on labels first, since they get used loosely: retrospective games, formats, techniques, templates, often interchangeably. Here's how this guide uses them: a **format** is the structure (the prompts people respond to), a **template** is that format pre-built and ready to run, and a **game** adds a mechanic, something like a surprise, a reveal, or a guess, that changes how people behave. So Sailboat is a format and a template, but calling it a game is generous: you're still filling in columns. Don't confuse any of this with [agile games](/blog/the-best-agile-games-for-building-teams-learning-and-creativity/) either. That's a broader category of activities spanning the whole delivery process, and its own topic. Why does it matter? Left to their own devices, most retros default to open discussion. Someone asks “So, how did the sprint go?” and waits. A long pause, then the same two people talk while everyone else stares at their thumbnail. A format replaces that blank prompt with structure. A game goes further: it gives people something to react to before they've had time to self-edit. Both have their place, and the payoff is the same: better data. Retros only work if people tell the truth about what's slowing them down, and online that rarely happens by accident. The rest of this guide is about making that happen on purpose. ## Start with a solid retrospective format Most online retrospectives should still start from a proven format, the reliable structures your team already recognizes. For a routine sprint they're all you need to get a useful conversation going. Pick the one that fits the job: - [Mad, Sad, Glad](/retrospective-templates/mad-sad-glad-retrospective/): emotional signal after a rough or high-stakes sprint. - [Start, Stop, Continue](/retrospective-templates/start-stop-continue-retrospective/): the fastest route from feedback to action items. - [Sailboat](/retrospective-templates/sailboat-retrospective/): risks, goals, and what's holding the team back. - [Rose, Bud, Thorn](/retrospective-templates/rose-bud-thorn-retrospective/): a balanced read on what's working and what's emerging. - [4Ls](/guides/retrospective-games/): liked, learned, lacked, longed for. Strong after a milestone. Each is a free, ready-to-run [template in TeamRetro](/retrospective-templates/). But a format only structures the conversation. It doesn't guarantee anyone opens up. When your team is quiet, tired, or going through the motions, that's when you reach for an actual game. ## The retro games we played There's real evidence behind this, not just facilitator folklore. A study in [*Empirical Software Engineering*](https://link.springer.com/article/10.1007/s10664-021-10043-z) tracked six Scrum teams running game-based retrospectives and found the games directly countered the problems that make retros worth skipping in the first place: lack of structure, dull repetition, and a handful of people carrying the whole conversation. Worth remembering next time a busy sprint makes the retro feel optional. Those are usually the sprints that need one most. So we put it to the test. Over the last couple of months we ran a game in every one of our own team's retros. The honest reason was that attendance had gone quiet, and we wanted to see if a game would pull people back in. Here's what we played, with the real screenshots from each session: 1. **Your sprint in three emojis:** three emojis each, then everyone unpacks their own. 2. **Describe your sprint, and let AI draw it:** everyone uses TeamRetro's built-in image generator to turn the last few weeks into a picture. 3. **Guess who wrote which card:** the same idea, kept anonymous, then guess who made each one. 4. **Team Spectrum:** place yourselves on a spectrum, then guess where your teammates landed, with scores. 5. **The AI-generated sprint artifact:** feed the finished retro's summary into an AI image generator for a newspaper, poster, or Sprint Wrapped card. ### 1. Your sprint in three emojis Before any discussion, everyone drops three emojis to sum up the sprint, then explains them. The shorthand is faster and more disarming than prose. Someone will admit in a skull, a fire, and a sob emoji what they'd carefully hedge in a full sentence. _We ran ours as a quick mood check straight in the chat. Three emojis, then everyone unpacks their own._ Prefer a GIF? That works just as well as an alternative format: a single well-chosen GIF (a burning building, say) often says more than a paragraph. Either way it's a quick, low-effort opener, especially when time is tight. ### 2. Describe your sprint, and let AI draw it Ask everyone to describe their sprint experience over the last few weeks, then let TeamRetro's built-in image generator turn that into a picture. Each person shares what came back and talks through why. Reacting to your own weird little image is far easier than answering "so, how did the sprint go?", and the picture usually says the quiet part out loud. _Our "June Mood" board. The prompt was simply: create an image that describes what the sprint felt like._ The board filled up fast: a wide-eyed monkey losing its grip on a fistful of flying tasks, someone at their desk staring into a screen full of lightning. Every image became a way into a conversation we would otherwise have had to drag out of people. ### 3. Guess who wrote which card Run the same board, but keep every submission anonymous, then have the team guess who made each card. It turns a passive review into a game and surfaces assumptions along the way: "I was sure that was you" says as much as the image itself. _The guessing in action: teammates dropping their guesses in the comments under each anonymous image._ One honest warning: this only works if your team already has high trust and good camaraderie. Guessing "who's the burnt-out one" is fun when people feel safe and pointed when they don't. If you're not sure where your team sits, save this one and start with something lower-stakes. ### 4. Team Spectrum This is the one that got the most buy-in of the lot, and it's a proper game with scores. [Team Spectrum](https://games.teamretro.com) (one of our free Icebreaker Games) puts a reflection prompt on a spectrum, then makes everyone guess where their teammates landed. We used it for the sprint itself. The prompt was "how well did the sprint stories align with the bigger picture?", running from "everything fit" on one end to "felt disconnected" on the other. Everyone privately placed themselves, then the team guessed each other's positions, scoring points for getting it right. _A real reflection prompt, played as a spectrum. You score by guessing where teammates put themselves._ The guessing is what makes it work. Predicting where someone landed forces you to actually consider their sprint, not just your own, and every wrong guess is a small, safe surprise that gets people talking. The leaderboard turns a reflection nobody was excited about into something they wanted to win. _Round one done. The scoreboard did more for attendance than any calendar reminder._ Use it when you want a genuine reflection but the team keeps treating retros as a chore. The scoring is the hook; the alignment conversation is what you actually walk away with. ### 5. The AI-generated sprint artifact This one isn't an opener. It's what we did with the retro once it was over. We took the output, TeamRetro's [AI Meeting Summary](/blog/ai-tools-that-make-agile-retrospectives-easier-and-smarter/), which already pulls the key themes, sentiment, and outcomes, and fed it into an AI image generator with a strong style prompt: a 1960s newspaper front page, a wartime propaganda poster, an 80s movie one-sheet, a Spotify Wrapped-style recap card. Then we shared the results back with the team. We ran a few prompts on one month's summary. Here's what came back, no cleanup and no cherry-picking. Click through the deck: Every one of those came from the same meeting summary. Seeing the sprint retold in a new form makes it stick, and the gap between the artifact and reality (the "that's not how it actually felt" moment) often surfaces a point the retro glossed over. The "octopus-level multitasking" headline did more to open up a workload conversation than any check-in question we've tried. Use it to close out a milestone or end-of-quarter session you want people to remember. **Want to try these without the setup?** Every game here runs on a free template in TeamRetro, and the AI Meeting Summary that powers the sprint artifact is built in, so you can run the retro and generate the artifact in the same place. ## Facilitating retro games remotely The activity gets you started. Remote facilitation is what decides whether online retrospective games actually work, and it's where most online retros quietly fail. Three things make the biggest difference. **Timebox tightly.** Online attention is short and silences feel longer. Put a visible timer on each phase: a window to add input, another to group and vote, a hard stop for discussion. Tight boxes create urgency and stop one topic eating the whole hour. **Make input anonymous.** Hierarchy travels down a video call fast. When people contribute anonymously, the junior engineer raises the concern the tech lead was tiptoeing around. It's also what makes a game like Guess Who work at all. Anonymous entry defangs rank and gets you the real feedback, not the safe version. **Let people pre-enter async.** Don't make everyone think on the spot with their camera on. Open the board beforehand so people can add thoughts in their own time. The quiet, deliberate thinkers contribute properly instead of being steamrolled by the fast talkers, and you start the live session with raw material already there. Get these three right and almost any activity above lands. Get them wrong and even the cleverest game turns back into an open discussion with a scoreboard on top. ## When a game won't fix the problem One honest caveat: a game won't fix an unsafe team. If people don't trust each other, no clever format will pull out the real issues. Neither will an AI-generated newspaper. They'll fill in the safe cards, laugh at the artifact, and save the real conversation for the DM afterwards. Anonymity and playfulness help at the margins, but they're a patch, not a cure. When the same problem resurfaces sprint after sprint with no one willing to own it, that's a signal a template can't answer. If you're not sure which one you're dealing with, don't guess from tone on a video call. A quick health check before the retro tells you in minutes whether you're looking at a flat team or an unsafe one. It's a numeric read on trust, safety, and morale. If the numbers are low, that's the actual agenda item. No game fixes that. Only the follow-through does. That work sits underneath all of this. It's facilitation and leadership: following through on action items so people see that speaking up changes something, modeling that it's safe to disagree, and dealing with the behavior that makes people go quiet. Online retrospective games are a powerful tool for a team that trusts each other enough to be honest. They're not a substitute for building that trust. ## Match the game to the sprint The best online retrospective game is the one that matches what your team needs this sprint: a solid format when the conversation needs structure, a genuine game when it needs unsticking. Match it to the job, run it with tight timeboxes and anonymous input, and watch whether the honesty is real or performed. Every format here is a free template in TeamRetro. Anonymous input, async pre-entry, timeboxing, and the AI summaries that power the remix game are all built in, so you focus on the conversation, not the setup. Browse the [retrospective template library](/retrospective-templates/), warm up with [Icebreaker Games](https://games.teamretro.com), or pull fresh prompts from [RetroIdeas](https://ideas.teamretro.com/activities) when a format feels stale. For more on keeping retros engaging, see [3 nifty ways to keep your retros fun and exciting](/blog/3-nifty-ways-to-keep-your-retros-fun-and-exciting/) and [how to run an icebreaker](/blog/how-to-run-an-icebreaker/). --- # Online whiteboards for retrospectives: templates and techniques that work URL: https://www.teamretro.com/blog/online-whiteboards-for-retrospectives/ Most teams use an online whiteboard the same way. Someone opens a blank canvas, people drop in sticky notes, and then everyone stares at a wall of disconnected ideas trying to work out what to do with them. It is better than nothing, but it is a long way from what a structured visual session can do. The teams that improve fastest are not the ones with the most tools. They are the ones who run sessions with a clear flow: think privately, group by theme, vote on what matters, dig into the causes, and leave with actions someone owns. That is a method, not a feature. So instead of pointing teams at a separate whiteboard and hoping the method survives the tool-switching, we built the whiteboard into the session. This guide covers where a visual canvas earns its place across retrospectives, health checks, and estimations, and the templates that make it useful. ## Why a blank canvas is not enough for a team session A blank canvas is a starting point, not a method. For a retrospective, a health check, or a planning conversation, what a team actually needs is a flow that protects honest input and ends in something concrete. Three things break down on a general whiteboard without that structure: - **Ideas stay disconnected.** Sticky notes pile up with no way to surface the relationships between them. The team discusses individual points instead of the pattern underneath, treating symptoms rather than causes. - **The loudest voice still wins.** Without independent input, where everyone adds their thoughts before anything is visible to others, the first few contributions anchor the conversation. Quieter people self-edit before they have even typed a note. - **Actions do not survive the session.** When the board is the only artifact, the actions live on a canvas that gets closed at the end of the call. There is no carry-forward, no owner, no accountability. This is where [psychological safety](/blog/how-to-tell-if-your-team-feels-psychologically-safe/) and structure meet. A session that supports private input, guided steps, and visible action capture does not just run more smoothly. It creates the conditions where people say what they actually think, which is the only version of a retrospective worth running. Harvard's Professor Amy Edmondson, [whose research on psychological safety](https://www.library.hbs.edu/working-knowledge/psychological-safety-is-an-asset-not-a-luxury) underpins how high-performing teams operate, found that people speak up more honestly when they are protected from immediate judgment. Independent brainstorming, private until the facilitator reveals the board, is how that protection gets built into the session by default. ## The gap a facilitator pointed out A senior agile practitioner on a large, distributed team described the gap precisely. Her team follows the standard flow of brainstorming, grouping, and voting. Where she got stuck was right after the team aligned on the topic they most wanted to discuss. *Real feedback from a facilitator on a distributed team, and one of the requests that shaped how we built whiteboards into TeamRetro (personal details redacted).* Before jumping to solutions, she wanted to do some root cause analysis, to make sure the team was solving the real problem rather than a symptom. With a separate whiteboarding tool she would spin up a quick working space and run a technique like a Fishbone diagram or 5 Whys. Inside a retrospective, there was no good home for that. In her words: > "What I find myself wishing for is an additional optional workflow step after voting that provides a dedicated collaborative space for root cause analysis. Essentially, something that helps teams explore and document the causes behind an issue before moving into action planning." > > *A senior agile practitioner, distributed software team* This is exactly the kind of feedback the whiteboard was built for. Rather than send teams out to a separate tool, we put a dedicated, collaborative space for root cause analysis right where she wanted it: after voting, before actions, without leaving the retrospective. Here is what it looks like in practice. Say the team votes up "the mobile checkout shipped three weeks late." The easy reaction is "estimate better next time." Open a Fishbone against that idea instead, and the real picture appears: the staging environment was down for four days, scope expanded mid-sprint, and the product owner was unavailable for two key decisions. The fix that follows is specific, and the whole team can see the reasoning behind it, rather than one person's hunch. ## Whiteboards, built into the session TeamRetro's collaborative whiteboard is a shared visual canvas that lives inside the meeting. Everyone can sketch, map a framework, and draw together at the same time, with each person's cursor visible live, and without leaving the retrospective to do it. You can add a whiteboard wherever the discussion needs one: - **Against an idea**, to dig into a specific item the team voted up (this is the root cause analysis step the facilitator above was missing). - **Against a comment**, to expand on a single point. - **At the meeting level**, as a standalone canvas the whole team can browse. A few things make it work as a facilitation surface rather than a free-for-all. The facilitator or creator can **lock** a board so only they can edit while presenting or once it is finalized. **Presenting** broadcasts a board to every participant, so nobody is scrolling on their own. And every whiteboard can be **exported** as PNG or SVG, and is **included in the session report**, so the thinking is captured rather than lost when the call ends. It works the same way across retrospectives, health checks, estimations, and maturity assessments. ## The templates, and when to reach for each A blank canvas is still there when you want it. But most of the time you want a structure to work into, so the team spends its energy on the thinking rather than drawing boxes. TeamRetro ships nine templates, which fall into three jobs. **For getting to the root cause:** - **5 Whys.** Ask "why" in sequence until you reach the underlying cause rather than the first visible symptom. Reach for it when a single problem keeps recurring and you suspect the team is fixing the wrong layer. - **Fishbone (Ishikawa) diagram.** Map the possible causes of a problem into categories so the team can see cause and effect at a glance. Reach for it when an issue has several contributing factors and you want to sort them before discussing fixes. To build a whole session around this kind of root cause analysis, there is also a full [Fishbone (Ishikawa) retrospective template](/retrospective-templates/fishbone-ishikawa-retrospective/). **For deciding and prioritizing:** - **Impact/Effort matrix.** Plot options by the value they deliver against the work they take, so the quick wins and the time-sinks are obvious. Reach for it when the team has more ideas than capacity. - **SWOT.** Lay out strengths, weaknesses, opportunities, and threats. Reach for it in a planning conversation or a quarterly review. - **North Star.** Align the team around the one guiding metric that matters. Reach for it when priorities are scattered. - **The Golden Circle.** Work outward from why, to how, to what. Reach for it when the team needs to reconnect a piece of work to its purpose. **For mapping people and time:** - **Stakeholder map.** Place the people involved in a decision by influence and interest. Reach for it before a change that touches teams outside the room. - **RACI.** Set out who is responsible, accountable, consulted, and informed. Reach for it when ownership of a follow-up action is unclear. - **Timeline.** Lay events out in sequence. Reach for it when the team is reconstructing what happened over a sprint or an incident. ## Using whiteboards in retrospectives A TeamRetro retrospective runs in steps: everyone brainstorms privately, ideas are grouped, the team votes, and the top issues get discussed and turned into actions. The whiteboard slots in after voting and before actions, the moment the team has agreed on what matters and needs to understand it before fixing it. Open one against the top-voted idea, pick a template, and dig in together. Reach for a whiteboard when: - **A problem keeps coming back.** Run a 5 Whys or Fishbone on the top-voted issue to find the root cause, not the first fix that comes to mind. - **The sprint is a blur and people remember it differently.** A Timeline rebuilds what actually happened, event by event, before the team draws conclusions. - **The discussion is going in circles.** Sketching the process or the system on a shared canvas gives everyone the same thing to point at. - **An action needs a clear owner.** A quick RACI settles who is responsible, accountable, consulted, and informed before the session closes. **Picture it.** You are running the sprint retro. The team votes up "we keep missing the sprint goal," and the room's first instinct is "commit to less next time." Instead of taking that at face value, you open a whiteboard on that idea and drop in the 5 Whys template. A few whys down, the real cause is not over-commitment at all: stories are being pulled in without clear acceptance criteria, so work bounces back late in the sprint. The action writes itself, and the whole team watched how you got there rather than taking your word for it. ## Using whiteboards in health checks A health check gives you the numbers; a whiteboard turns them into a conversation. People rate each [team health check](/health-checks/) dimension privately, the results are revealed as a radar or bar chart, and then the real work starts, because a rating on its own does not explain itself. Reach for a whiteboard when: - **A dimension scores low and the reasons are tangled.** Map the causes on a Fishbone so the team debates the causes, not the number. - **Scores are split.** When some people rate "communication" a 2 and others a 5, put the reasons side by side and find out why the same team sees it so differently. - **A theme runs across dimensions.** Sketch how "delivery," "process," and "fun" feed into each other instead of treating each score in isolation. Because health check data is tracked over time, whatever the team uncovers is there to revisit next session, so a dimension that is quietly sliding back is hard to miss. ## Using whiteboards in estimations When a team estimates together and the numbers come back far apart, that spread is information: someone is seeing complexity, a dependency, or an edge case the others are not. A whiteboard makes that hidden picture shared, so the re-estimate rests on the same understanding rather than on who argued hardest. Reach for a whiteboard when: - **Estimates are far apart.** Break the story into its parts on the canvas until the reason for the gap shows itself. - **The work depends on other teams or systems.** Map the dependencies and unknowns before anyone commits to a number. - **Scope is fuzzy.** Sketch the flow or the acceptance criteria so the team is sizing the same thing. - **There is more to do than capacity allows.** An Impact/Effort matrix sorts what is worth doing against what it will cost. Across all three ceremonies the move is the same: when the conversation gets stuck, a whiteboard turns it into a shared picture, and because it lives inside the session, whatever the team draws is captured in the report rather than lost on a separate canvas. | Ceremony | Where a whiteboard helps | What the team leaves with | | --- | --- | --- | | Retrospective | A deep dive on the top-voted issue, with a 5 Whys or Fishbone | The real cause named, not just the symptom, and owned actions | | Health check | Unpacking a low or split rating into the reasons behind it | A shared understanding of why a dimension scored the way it did | | Estimation | Breaking a story down when estimates come back far apart | A re-estimate grounded in the same picture of the work | ## Why built-in beats a separate whiteboard tool Plenty of teams stitch their session together across tools: a whiteboard for brainstorming, a separate retro board for voting, a Jira ticket or Slack message for actions. It is a common setup, and it is where follow-through quietly dies. Every tool switch mid-session costs focus. People open the wrong link, lose the thread, or check out during the transition, and the facilitator spends energy on logistics instead of the conversation. Sticky notes on a general whiteboard do not become tracked actions on their own. Someone has to go back after the call, read the board, translate ideas into tasks, and assign them, and that step is where most retrospective actions are lost. Building the whiteboard into the session removes the switch. The canvas, the voting, the root cause analysis, and the actions all live in one place, and the actions carry forward into the next session's Open Actions step automatically. Health check ratings, retrospective themes, and follow-ups build up in the same place over time, so you can see how the team is actually developing, not just whether one meeting went well. ## Try it in your next retrospective The blank canvas was never the problem. The missing piece was a structure around it, and a place to dig into the real cause before the team commits to a fix. Run your next retrospective in TeamRetro, add a whiteboard where the discussion needs one, and see what surfaces.
## Frequently asked questions **What is a collaborative whiteboard in TeamRetro?** A shared visual canvas inside the meeting. Several people can sketch, map a framework, and draw together in real time, with each person's cursor visible, without leaving the session. It sits alongside private brainstorming, grouping, voting, and action tracking rather than being a separate tool. **Where can I use a whiteboard?** Across retrospectives, health checks, estimations, and maturity model meetings. You can open one against a specific idea, against a comment, in the chat, or as a standalone board at the meeting level. **Which templates does the whiteboard include?** Nine, plus a blank canvas: 5 Whys and Fishbone for root cause analysis; Impact/Effort matrix, SWOT, North Star, and the Golden Circle for deciding and prioritizing; and Stakeholder Map, RACI, and Timeline for mapping people and events. **Can I run root cause analysis like 5 Whys or Fishbone in a retrospective?** Yes. Once the team has voted on the issue that matters most, open a whiteboard against that idea, pick the 5 Whys or Fishbone template, and work through it together before moving into action planning. **Can I present, lock, and export a whiteboard?** Yes. A facilitator can present a board so everyone follows the same view, and lock it so only they can edit while presenting or once it is final. Boards export as PNG or SVG and are included in the session report, so the thinking is captured rather than lost. --- # Our AI teammates joined our retro URL: https://www.teamretro.com/blog/our-ai-teammates-joined-our-retro/ We build retrospective software, so our team's retro board is a fairly ordinary place: Start, Stop, a column of open actions, the usual Friday arguments. Last week it gained some new contributors. Six of the cards weren't written by anyone human — they were filed by the AI agents we work with every day, summarizing the friction from their own working sessions with us. Let's be precise about what this is, because the phrasing matters. This is not an AI sitting *in* the retro: no bot facilitating the meeting, no AI feature summarizing the humans' cards. The agents that do real work on our team (the ones writing code, editing content, running audits) showed up to the ceremony the way any teammate does: with their own account of how the work went. Participants, not facilitators; the meeting stayed ours. This wasn't a stunt, either. The push came in one of our own retros: someone said the onboarding docs were out of date (again) and someone else mentioned an agent had flagged exactly that to them mid-session that morning, in passing, before the context scrolled away. The agent had known; nothing in its world said the observation was worth keeping. So for the past few weeks we've been running an experiment on ourselves: the practice is the one we described in [how to gather feedback from your AI agents](/blog/gather-feedback-from-ai-agents/). At the end of each substantial AI-assisted working session, the agent writes a short, structured retro entry of its own work: what went well, what dragged, what each drag cost, one root-cause label per item, and a proposed fix. The entries accumulate in the repos the work happened in. When enough had built up, a companion process read them all and filed the recurring patterns straight onto our retro board, prefixed `[AI retro]` so nobody mistakes the author. Here's what our newest teammates had to say about working with us. ## What they found **The headline they led with was about themselves.** The top card read: *"Start verifying before acting — agent execution error is 38% of friction (2× the next cause); the recurring cost is asserting a cause, pushing, or retargeting before checking live code, data, or branch state."* The single biggest source of friction in our AI-assisted work, by the agents' own accounting, was the agents, specifically the habit of acting on an assumed state of the world instead of checking the live one first. We'll take honesty like that from any colleague. **The biggest team-shaped theme crossed every boundary a person wouldn't.** Git and branch-state errors under concurrent-agent work showed up in eight sessions across two repos: stale bases, unread branch targets, one agent moving a branch another was using, a PR retargeted without verification. No single session would have ranked this anywhere near the top; each instance was a shrug and a few lost minutes. Ranked across eight sessions, it was unmissable. **It caught us shipping on partial checks.** Four sessions where something was pushed or merged after a narrower check than CI actually runs: a bare type-check instead of the full build, targeted tests instead of the suite. Twice in one repo, on the same day. **And the most uncomfortable cards weren't about the work at all; they were about follow-through.** One card noted that a testing-convention gap had let a reproducible crash slip past two rounds of review, and that the fix document had been *proposed the day before and never written*. Another noted the same tool stall had now cost two sessions, "no standing fix shipped between them." A third: the same requirements-creep pattern, three consecutive sessions, "each noting it recurring from the last." The agent, it turns out, remembers what we said we'd do. ## The two things worth staring at **First: none of this was visible to any individual.** That's not a failure of attention; it's the shape of the problem. AI-session friction is chronic and minor, so it never triggers a postmortem, and it evaporates when the session ends. Each of us had absorbed our share and moved on. The ranking (*this* pattern costs the team most) only exists in the aggregate view, and the aggregate view only exists because the entries were comparable: same schema, same small set of root-cause labels, every claim citing a dated session. This is the aggregation idea at the center of [the guide this post accompanies](/guides/ai-agent-retrospectives/), and it's the part we most wanted to test on ourselves. **Second: the agents didn't blame anyone, including themselves, loosely.** The entries follow two rules that turned out to matter more than we expected. Friction items describe the gap and what it cost, never who caused it: no names, no "X's brief." And "the agent made a mistake" is a *residual* label, only used when the inputs were genuinely adequate, which is exactly why the 38% figure got our attention: it survived that discipline. The result read like a good retro contribution: specific, evidence-cited, blameless, and slightly embarrassing for everyone equally. ## What the room decided We decided to act on all three of the proposed actions, each at the altitude it named. The "confirm live branch and PR state before mutating" rule goes into each repo's agent docs, a documentation fix for the eight-session theme. The pre-push hook that runs the CI-equivalent build and tests goes into the repos that got burned by partial checks, an environment fix, so it doesn't depend on anyone remembering. And the testing-convention doc that was "flagged the day before and never written" is being written, with the crash that slipped through as its worked example. No grand reorganization, no new process: three ticket-sized fixes with owners. The modesty is deliberate: the whole bet of this practice is that small fixes, aimed at the right level and actually checked next cycle, compound. Whether these three stick is precisely what the next brief's adoption check will tell us; the same mechanism that caught us last time will be grading us on it. It's early days, and we're saying so plainly. But we walked out of that retro more interested in our own working patterns than we've been in a while — and a little competitive with a colleague who doesn't even get tired. ## The honest footnotes This is our first synthesized brief, weeks of data, not months, so we're treating the rankings as attention allocation, not accounting. The costs in the entries are the agent's own estimates and are marked as such. The practice's harder claims (that labels stay consistent between raters, that the trend line actually bends after fixes land) are experiments we're running rather than assumptions we're making, and we'll publish what they say either way. But the core payoff already showed up: a set of patterns nobody on the team could see individually, ranked, evidenced, and filed into the ceremony where the people who own the fixes were already sitting. Rahul Garg's [Feedback Flywheel](https://martinfowler.com/articles/reduce-friction-ai/feedback-flywheel.html) includes in its cadence list "an agenda item in the existing sprint retrospective: what worked with AI this sprint?" We can now report that the agenda item is considerably more interesting when your AI teammates file their own items. ## Try it on your own team Everything we used is free and documented in [the guide](/guides/ai-agent-retrospectives/): how the entries work, the root-cause labels, the never-log rules (no secrets, no customer data, and never anything that identifies a person), and the facilitator's 15-minute agenda item, plus the two skills that implement the capture and synthesis ends. It works with any capable agent and a text file; our product is one place the results can land, not a requirement. Next cycle, the brief's adoption check will tell us whether we actually wrote that testing doc this time. We'll let you know. So will they. *Tried it? Disagree with it? We mean it about wanting to be argued with: [ai-discussion@teamretro.com](mailto:ai-discussion@teamretro.com).* --- # Planning poker decks: which options best accelerate agile team velocity? URL: https://www.teamretro.com/blog/planning-poker-deck-that-is-best-for-accelerating-team-velocity/ Estimation plays a critical role in agile planning, but it’s not just about assigning numbers or sizes to user stories. At its core, estimation is about building shared understanding, setting expectations, and enabling teams to plan and deliver work more reliably. It’s a surprisingly human exercise that blends structured guessing with group psychology, with just enough math to keep everyone honest. Choosing the right deck improves agile story point estimation, team alignment, and boosts team velocity. It can simplify complex work and add structure to abstract ideas during backlog refinement or sprint planning. It can directly influence how easily you reach consensus, how confident people feel about their estimates, and how accurately you can forecast future sprints. And who wouldn’t want that? So here’s the crunch. I’ve got an estimation meeting coming up with my team. – “How do I choose the right deck?” Here we explore the common choices for planning poker card decks, share our top tips and things you need to think about when choosing a deck, and use a case in point example to compare two common methods. In this case Fibonacci versus T-Shirt size. > #### Fun origin fact > > [Planning poker](https://athena.ecs.csus.edu/~buckley/CSc231_files/Introduction%20to%20Planning%20Poker.pdf) is based on Wideband Delphi, a forecasting method invented by the RAND Corporation sometime between the 1940s and 1968 (even historians can’t agree 😄). It was modernized for Agile teams in 2002 and made mainstream by [Mike Cohn](https://www.mountaingoatsoftware.com/agile/planning-poker). ## Choose your planning poker deck: why the numbers matter? When it comes to planning poker decks, the numbers are doing more work than you think. (Our estimation guide breaks down each option in [which deck should you use?](/guides/agile-estimation-guide/how-to-run-planning-poker/#which-deck-should-you-use).) Some of the most common card decks include: - **Scrum**: Based on the traditional Scrum values (0, 1,2,3,5,8) this deck helps standardize estimates across agile teams following Scrum methodologies. - **Fibonacci**: A sequence (1, 2, 3, 5, 8, 13…) a sequence that intentionally gets less precise as numbers grow to represent increasing levels of effort and complexity. - **Sequential**: A linear progression of numbers (e.g., 1, 2, 3, 4, 5…) for teams who want more consistent, evenly spaced estimates. A popular choice where projects have less variations. This can also be used for estimating based on Ideal days or time based. - **Half card**: Allows for finer granularity between common estimates by including values like (1, 1½, 2, 2 ½, 3) – a more precise estimation sequence that further refines estimations. - **Power of two**: Exponential sizing (1, 2, 4, 8, 16…) is a variation on the fibonacci sequence that emphasizes uncertainty when it comes to the larger tasks. - **T-shirt sizing**: Abstract labels like XS, S, M, L, XL that work well for high-level planning, relative ranking or when collaborating with cross-functional teams. It can be a useful discussion point to get a general team definition of each t-shirt size. There are some other variations out there including weighted averaging and weighted shortest job first, but they tend to over complicate something which cannot be so precisely calculated and leads to an over reliance that the final output must be accurate simply due to its complexity. ## Factors for choosing the right planning poker card deck When selecting a deck, the goal isn’t perfection — it’s clarity and consistency. The right deck should support productive conversations and fit naturally into how your team already works. A few factors can help guide the decision: ### Workflow alignment Choose a deck that fits naturally with the tools, ceremonies, and processes your team already uses. The best deck is one your team doesn’t have to think about. ### Team experience T-shirt sizing is often easier for newer or mixed-discipline teams, while Fibonacci estimation works well for teams comfortable discussing relative complexity and trade-offs. ### Level of precision Numeric decks support more detailed estimates, while abstract sizing keeps early planning lightweight and avoids false precision. ### Planning goals T-shirt sizing works well for discovery and roadmap conversations. Fibonacci and similar numeric decks are better suited to sprint planning and tracking team velocity over time. ### Risk and uncertainty If work items vary widely in unknowns, decks like Fibonacci or Power of Two help surface uncertainty by spreading estimates further apart as size increases. ### Nature of the work Routine or repeatable tasks may suit linear or time-based decks, while exploratory or creative work benefits from relative or abstract sizing. ### Speed of decision-making Abstract or bucket-style decks encourage faster consensus and reduce over-analysis when working through large backlogs. ### Cross-team consistency If multiple teams collaborate or compare estimates, using the same deck can reduce confusion and make shared planning more effective. ### Cognitive load Simpler decks reduce mental overhead, helping teams focus on discussion and shared understanding rather than debating numbers. The decks that are in our estimation set are chosen for a simpler approach. ### Change tolerance Switching decks mid-project can disrupt velocity tracking. Consider whether your team values continuity or is comfortable experimenting with new approaches. ### Remote collaboration For remote teams, decks with fewer options and clearer distinctions often work better, reducing friction and decision fatigue during online sessions. Ultimately, the best planning poker card deck is the one that encourages meaningful conversations, builds shared understanding, and supports how your team works day to day. While there are some default or go to – popular models, it’s (excuse the pun) not a one size fits all scenario. ## Planning poker card deck decision matrix **Legend**: ★★★ = Strong fit ★★☆ = Can work ★☆☆ = Not ideal | Card deck → / Decision factor ↓ | Scrum | Fibonacci | Sequential | Half card | Power of two | T-shirt sizing | | --- | --- | --- | --- | --- | --- | --- | | **Early discovery / roadmap planning** | ★☆☆ | ★★☆ | ★★☆ | ★☆☆ | ★☆☆ | ★★★ | | **Sprint planning & delivery** | ★★★ | ★★★ | ★★☆ | ★★★ | ★★☆ | ★☆☆ | | **New or mixed-discipline teams** | ★★☆ | ★☆☆ | ★★★ | ★☆☆ | ★☆☆ | ★★★ | | **Experienced agile teams** | ★★★ | ★★★ | ★★☆ | ★★★ | ★★★ | ★★☆ | | **High uncertainty / unknowns** | ★★☆ | ★★★ | ★☆☆ | ★☆☆ | ★★★ | ★★☆ | | **Predictable, repeatable work** | ★★☆ | ★★☆ | ★★★ | ★★★ | ★☆☆ | ★☆☆ | | **Needs high precision** | ★☆☆ | ★★☆ | ★★☆ | ★★★ | ★☆☆ | ★☆☆ | | **Avoid false precision** | ★★☆ | ★★★ | ★☆☆ | ★☆☆ | ★★★ | ★★★ | | **Fast consensus needed** | ★★☆ | ★★☆ | ★★☆ | ★☆☆ | ★☆☆ | ★★★ | | **Encourages discussion & alignment** | ★★★ | ★★★ | ★★☆ | ★★★ | ★★☆ | ★★☆ | | **Remote-first teams** | ★★☆ | ★★★ | ★★☆ | ★☆☆ | ★★☆ | ★★★ | | **Cross-team consistency required** | ★★★ | ★★★ | ★★☆ | ★☆☆ | ★★☆ | ★☆☆ | ## Case study: Fibonacci vs t-shirt sizing for an internal product team An internal product division at a mid-sized organization was responsible for building and maintaining several shared tools used across the business. They regularly collaborated with stakeholders from operations, finance, and customer support. While the work wasn’t customer-facing, the impact was significant — small delivery delays often created ripple effects across the business. The development team was experienced and stable, working in two-week sprints with a predictable release cadence. However, planning sessions were starting to feel strained. As the product matured, the team needed a clearer approach to estimation that could support both longer-term planning and day-to-day delivery. ## The challenge The team faced two distinct planning contexts: - Early-stage work, where requirements were still evolving and input from non-technical stakeholders was essential - Sprint-level work, where stories were well-defined and the team needed reliable estimates to track velocity and forecast delivery To address this, the team compared two commonly used estimation approaches: Fibonacci estimation and t-shirt sizing. ### Option 1: Fibonacci estimation Fibonacci estimation uses a non-linear number sequence where each value represents a meaningful increase in effort and uncertainty. This helped the team recognize that larger stories were harder to estimate precisely and encouraged deeper discussion when estimates diverged. The team found Fibonacci particularly effective for: - Sprint planning - Tracking velocity across iterations - Improving forecasting accuracy over time Once work items were refined and ready for delivery, Fibonacci supported consistent planning and helped the team understand their capacity from sprint to sprint. **Trade-offs** - Slower during early backlog discussions - Less accessible for non-technical stakeholders during planning sessions ### Option 2: T-shirt sizing in agile T-shirt sizing takes a more abstract approach by using relative sizes instead of numbers. This made it easier for stakeholders outside the development team to contribute during planning and kept conversations focused on relative effort rather than precision. The team found T-shirt sizing especially useful for: - Early backlog refinement - Roadmap planning - Cross-functional or remote planning poker sessions By removing numbers from the conversation, the team moved faster through early-stage ideas and avoided overcommitting too early. **Trade-offs** - Not detailed enough for sprint-level forecasting - Required translation into numeric estimates before delivery ## The decision Rather than choosing a single deck, the team aligned each approach to a specific planning goal: - T-shirt sizing for early backlog refinement and roadmap planning - Fibonacci estimation for sprint planning and delivery This allowed the team to maintain clarity and consistency without forcing precision too early in the process. ## How planning poker card decks influence team velocity Team velocity isn’t about speed—it’s about consistency. Reliable velocity allows teams to plan with confidence and make better delivery commitments. (More on [how story points roll up into velocity](/guides/agile-estimation-guide/velocity/).) Numeric estimation decks like Fibonacci support velocity by helping teams: - Compare completed work across sprints - Identify delivery trends - Improve long-term forecasting T-shirt sizing influences velocity more indirectly. By keeping estimation lightweight, teams often: - Plan faster - Spend more time clarifying scope - Align earlier before committing to detailed estimates Both approaches can boost team velocity when used consistently and at the right stage of planning. There’s no universally “correct” way to estimate. The most effective teams choose an approach that supports clear communication, alignment, and predictable delivery. As teams grow, their estimation practices often evolve too. Revisiting how you estimate—and why—can be a simple but powerful way to improve planning outcomes and long-term team velocity. ## Start estimating in seconds The planning poker deck your team uses shapes how you plan, collaborate, and deliver. Some teams need numerical precision, while others benefit from fast, lightweight sizing—especially in remote or async planning poker sessions. Choosing the right deck isn’t just a preference; it’s a strategic decision that affects how clearly your team communicates and how reliably it delivers. Try [TeamRetro’s free planning poker tool](https://planning-poker.teamretro.com/) today. No sign-up needed, just open your browser and get started. [Learn more about free planning poker](/free-planning-poker-for-agile-teams/) Looking for templates, tips, or a walkthrough video? We’ve got more resources coming soon. --- # Quick but effective icebreakers to launch your next retrospective URL: https://www.teamretro.com/blog/quick-but-effective-icebreakers-to-launch-your-next-retrospective/ Starting your retrospective with an icebreaker is a great way to help your team focus, engage with each other, and get the most out of the meeting. If you want one ready to go, our [free icebreaker questions game](https://games.teamretro.com/games/icebreaker-questions) picks a prompt for the team in seconds. An icebreaker will help your team members – - focus - strengthen rapport - build relationships An icebreaker will give you the chance to – - model supportive behavior - set a positive tone for the meeting - foster a psychologically safe space A good icebreaker will follow the [3E Rule](/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/), and linking it to your retrospective will allow you to leverage the momentum of focus and connection it has established so when you start your retrospective, you’ll hit the ground running. The best thing is, to save you time, we’ve paired each of our retrospectives formats with 3 quick and easy ice breaker questions that you can use to open up your meeting with flair – just like a good wine to each course at a degustation. We’ve also included an example of how you could rehearse the retro with your team. These may take a little more time but can help improve understanding and engagement in the rest of your retro. Check out each of these icebreakers and retro rehearsals in our retrospectives below. [Agile Retrospective](/retrospective-templates/agile-retrospective/) [Anchors and Engines](/retrospective-templates/anchors-engines-retrospective/) [Drop Add Keep Remove](/retrospective-templates/daki-retrospective/) [Family Circle](/retrospective-templates/the-family-circle-retrospective/) [Flap Retrospective](/retrospective-templates/flap-retrospective/) [Four L’s](/retrospective-templates/4ls-retrospective/) [Hero’s Journey](/retrospective-templates/the-heros-journey-retrospective/) [Hopes and Fears](/retrospective-templates/hopes-and-fears-retrospective/) [KALM](/retrospective-templates/kalm-retrospective/) [Mad Sad Glad](/retrospective-templates/mad-sad-glad-retrospective/) [Must Should Could Won’t](/retrospective-templates/mscw-retrospective/) [Oscar Academy](/retrospective-templates/oscar-academy-retrospective/) [Pathfinder](/retrospective-templates/pathfinder-retrospective/) [Personal Growth](/retrospective-templates/personal-growth-retrospective/) [Roller Coaster](/retrospective-templates/roller-coaster-retropective/) [Scrum Values](/retrospective-templates/scrum-values/) [Seasons of the Year](/retrospective-templates/seasons-of-the-year-retrospective/) [Snakes and Ladders](/retrospective-templates/snakes-and-ladders-retrospective/) **[Social Media](/retrospective-templates/social-media-retrospective/)** [Starfish Retrospective](/retrospective-templates/starfish-retrospective/) [Stop Start Continue](/retrospective-templates/start-stop-continue-retrospective/) [Superhero](/retrospective-templates/superhero-retrospective/) [The Good Gardener](/retrospective-templates/the-good-gardener-retrospective/) [The Master Baker](/retrospective-templates/the-master-baker/) [Three Little Pigs](/retrospective-templates/three-little-pigs-retrospective/) [Vacation](/retrospective-templates/vacation/) [Weather Report](/retrospective-templates/weather-report-retrospective/) [Witches and Warlocks](/retrospective-templates/witches-and-warlocks-retrospective/) [Working, Not Working](/retrospective-templates/working-not-working-retrospective/) [WRAP Retrospective](/retrospective-templates/wrap-retrospective/) #### We hope you love trying out some of these ideas with the team. #### If you had any other ideas you wanted to share, reach out to us at info@teamretro.com. #### Ready to kick off with an icebreaker? [Start a Retro Now](https://secure.teamretro.com/login) or warm up the room first with our [free icebreaker games](https://games.teamretro.com/games). --- # 100 retrospective questions that actually improve your team (2026) URL: https://www.teamretro.com/blog/retrospective-questions-sprint-agile-teams/ Tired of asking the same retrospective questions sprint after sprint? Every retro guide tells you to ask "What went well? What didn't? What should we change?" And if you've been running retrospectives for more than a few sprints, you already know the problem — the same questions get the same answers. People go through the motions, the energy drops, and nothing new surfaces. The questions you ask determine the insights you get. In this guide, you'll find 100 retrospective questions organized by category — opening questions, sprint questions, team health questions, icebreakers, and more. Whether you're running a standard sprint retro, a mid-project pulse check, or a quarterly retrospective, there's something here for every format and team mood. And if you want to shake things up beyond questions alone, TeamRetro's [retrospective template library](/retrospective-templates/) gives you 100+ formats to choose from. **In this guide:** - What makes a great retrospective question? - Opening and icebreaker retrospective questions - Classic sprint retrospective questions - Start, Stop, Continue retrospective questions - Agile retrospective questions for Scrum teams - Team health retrospective questions - Retrospective questions for remote and hybrid teams - Closing retrospective questions - How to choose the right questions for your retro - Run better retros with TeamRetro ## What makes a great retrospective question? The questions you ask shape the conversation you get. And the conversation you get shapes whether anything actually changes. The best retrospective questions share a few things in common: - They're open-ended — "How did we handle scope changes?" beats "Did scope creep affect us?" - They invite honesty without creating blame — [psychological safety](https://hbr.org/2023/02/what-is-psychological-safety) first - They're specific enough to generate action, not just conversation - They rotate — using the same questions every sprint breeds autopilot thinking A quick rule of thumb: if the question can be answered with a yes, a no, or a shrug, rephrase it. ## Opening and icebreaker retrospective questions The first few minutes of a retro set the tone for everything that follows. These warm-up questions lower defenses, invite participation, and signal that this is a safe space — not a blame session. Use one or two at the start. For more ideas on starting your session well, check out TeamRetro's guide to [retrospective icebreakers](/icebreakers/). ### Check-in questions - On a scale of 1–10, how are you arriving at this retro? What's your number? - What's one word that describes how this sprint felt? - If this sprint were a weather forecast, what would it be? - What emoji best describes your week? - What's one thing outside work you're looking forward to this week? - If you had to give this sprint a movie title, what would it be? - What's something small that went better than expected this sprint? - How full is your tank right now — and what's draining it? ### Icebreaker questions - What's a superpower you wish your team had right now? - If our team were a sports team, what sport would we be playing? - What's one thing a teammate did this sprint that you didn't get to thank them for? - If you could fix one thing about our process overnight, what would it be? - What's the biggest assumption we made this sprint? ## Classic sprint retrospective questions These cover the essentials without being prescriptive — leaving room for the team to surface what actually matters. If you want a structured starting point for your session, TeamRetro's [sprint retrospective template](/retrospective-templates/sprint-retrospective/) has you covered. ### What went well? - What's one thing you're genuinely proud of from this sprint? - Where did the team perform above expectations? - What made collaboration easier than usual? - Was there a moment in this sprint where things just clicked? - What process or tool saved us time or prevented a problem? ### What didn't go well? - Where did we feel most blocked or frustrated? - What slowed us down that we could have anticipated? - Were there any surprises that derailed our plans? How did we handle them? - Where did our estimates fall short, and why? - What's a recurring problem we keep talking about but haven't fixed? ### What should we do differently? - If we ran this sprint again with the same team, what's the first thing we'd change? - What experiment could we run next sprint that's low risk but high potential? - What's one concrete thing we could do to improve team communication? - Is there a meeting, ceremony, or process we could cut or simplify? - Who do we need to involve earlier in our work? ## Start, Stop, Continue retrospective questions The [Start-Stop-Continue format](/retrospective-templates/start-stop-continue-retrospective/) is action-oriented by design. Here are questions that work well within each column. ### Start questions - What's something we've been avoiding that we know would help? - Is there a practice from another team we've seen work that we haven't tried? - What one habit, if adopted next sprint, would make the biggest difference? - What feedback are we not collecting that we should be? - Are there conversations we keep postponing that we need to have? ### Stop questions - What's something we're doing out of habit that no longer adds value? - Where are we creating unnecessary work for ourselves or each other? - Is there a meeting we could make shorter, less frequent, or cancel entirely? - What are we tolerating that we shouldn't be? - Where are we over-engineering or over-documenting? ### Continue questions - What's working so well that we need to protect it from change? - What practice from this sprint deserves to become a permanent team norm? - Which team behaviors have made the biggest difference to delivery? - What's something a teammate does that you'd like the whole team to adopt? - Where have we made a recent improvement that's starting to pay off? **Tip:** Anchoring bias is real — the first voice in the room shapes everyone else's thinking. TeamRetro lets you control this directly: choose Anonymous mode to hide all names even from the facilitator, Aliases to give each participant a unique avatar and name, or Named if full visibility suits your team. You can also keep ideas hidden during brainstorming and only reveal them in the next step, so everyone contributes independently before the group discusses. It's one of the simplest ways to get more honest, diverse responses from your Start, Stop, Continue retro. ## Agile retrospective questions for scrum teams These questions are designed to bridge reflection and action within a [Scrum framework](https://www.scrum.org/resources/what-is-scrum) — useful for Scrum Masters, agile coaches, and self-organizing teams alike. For a deeper look at where retrospectives sit within the Scrum process, the [official Scrum Guide](https://scrumguides.org/scrum-guide.html) is worth bookmarking. TeamRetro also has a dedicated [Scrum retrospective template](/retrospective-templates/) built around the sprint ceremonies. ### For Scrum Masters and facilitators - Were our sprint goals clear and achievable at the start of the sprint? - How well did we protect the sprint from scope changes? - Did our Definition of Done serve us well this sprint, or does it need updating? - Were blockers surfaced early enough in daily standups to resolve quickly? - How effective was our sprint planning — were estimates realistic? ### For agile teams - Where did we honor our [agile values](https://agilemanifesto.org/principles.html) this sprint? Where did we slip? - Did we involve the product owner at the right moments? - How well did we balance technical debt against new feature work? - What would make our next sprint planning session more efficient? - Did we demo work we're genuinely proud of in the sprint review? ## Team health retrospective questions Sprint velocity matters. But so does the health of the people delivering it. These questions surface the human side of your team's performance — [psychological safety](https://rework.withgoogle.com/guides/understanding-team-effectiveness/steps/foster-psychological-safety/), workload balance, trust, and morale. Good to use quarterly, or whenever team energy feels off. ### Psychological safety - Do you feel comfortable raising concerns without fear of how they'll land? - When was the last time someone on the team changed their mind based on feedback? - Is there anything you've been wanting to raise in retros but haven't? What's stopping you? - Do we disagree well — can we challenge ideas without it becoming personal? ### Workload and wellbeing - Is anyone feeling close to burnout right now? What would help? - Do you feel your workload is sustainable? If not, what would need to change? - Are we saying yes to too many things? What should we push back on? - Is your work energizing you or draining you right now? ### Trust and collaboration - Do you feel you can rely on your teammates to deliver what they commit to? - Is there anyone on the team you haven't connected with enough this sprint? - Where do we collaborate well — and where do we work in silos? - Are there unresolved tensions on the team that are affecting our work? ## Retrospective questions for remote and hybrid teams The energy and spontaneity of an in-person retro doesn't transfer automatically to video — you have to design for it. These questions work well for distributed teams because they invite openness without relying on body language or room dynamics. If you're looking for a tool built for this, TeamRetro is an [online retrospective tool](/retrospectives/) designed specifically for remote and hybrid teams. - What's something that's harder working remotely right now — and what would make it easier? - Are we over-relying on async communication where a quick call would work better? - Does anyone feel like they're losing visibility or recognition working remotely? - What's the best virtual collaboration moment we had this sprint? - Are our meetings well-facilitated for people in different time zones? - What tools or processes have improved our remote collaboration lately? - Do you feel connected to the rest of the team? If not, what would help? - What's something you miss about in-person work — and can we recreate any of it? ## Closing retrospective questions How you close a retro shapes whether people actually follow through on commitments. These questions help the team leave with clarity, not just conversation. ### Commitment and accountability - What's the one thing you personally commit to doing differently next sprint? - Who's owning each action item — and do they have enough context to make progress? - Is there anything from our action list last retro that we should carry forward? - What would "done" look like for each action item we've agreed on? ### Retro health check - How useful was this retrospective — and what would make the next one better? - Did we spend time on the right things today? - Was everyone's voice heard? If not, who do we want to hear more from next time? - How confident are you that we'll actually act on what we discussed? - What format or structure should we try next time? **Tip:** Check-in and check-out questions aren't just conversation starters — they're data. TeamRetro tracks how your team answers questions like "How would you rate your energy level coming into this meeting?" and "Was this meeting worth your time?" across every sprint, giving you a visual timeline of team mood and retro effectiveness over months. Spot when energy consistently dips before a retro, or whether your team finds retrospectives genuinely worthwhile — and act on it before it becomes a problem. It's the kind of longitudinal insight most teams never get because they treat check-ins as throwaway warmups rather than signals worth measuring. ## How to choose the right retrospective questions ### Match questions to where the team is at A team coming off a bruising sprint needs different questions than one that's been coasting. If energy is low, start with lighter icebreakers and move toward actionable themes. If trust is fraying, lean on the psychological safety questions before jumping to process. ### Rotate formats, not just questions Changing your retrospective format — not just swapping out a few questions — is the most effective way to keep retros fresh. Team Radar, [4Ls](/retrospective-templates/4ls-retrospective/), [Sailboat](/retrospective-templates/sailboat-retrospective/), [Mad-Sad-Glad](/retrospective-templates/mad-sad-glad-retrospective/) — each format surfaces different things. Use our [retrospective template library](/retrospective-templates/) to find one that fits your team's current focus. ### Don't ask more than you can act on A focused retro with five great questions and three strong action items beats a sprawling one with fifteen questions and no follow-through. Pick what's most relevant to this sprint and leave the rest for next time. ### Use anonymous input for sensitive topics For questions touching on burnout, team dynamics, or trust — anonymity unlocks honesty. When people can respond without fear of attribution, you get the real picture. ## How to use retrospective questions effectively Having a strong list of retrospective questions is useful — but knowing when and how to use them matters even more. The best Scrum Masters don't simply ask more questions. They choose the right questions for the team's current context, create the conditions for honest answers, and turn the discussion into meaningful action. ### Know when not to ask certain questions Some retrospective questions are powerful, but only when the team feels safe enough to answer honestly. For example, a question like "Do you feel comfortable raising concerns without fear of how they'll land?" can surface important issues around psychological safety. But if the team does not trust the facilitator, each other, or the wider organization, people may give safe answers instead of honest ones. For sensitive topics — burnout, conflict, team trust, leadership concerns, workload pressure — consider using anonymous input, private brainstorming, or a lighter question first. The goal is not to force vulnerability. It's to create enough safety that useful truth can emerge. A good rule of thumb: if the question could make someone feel exposed, make sure anonymity, facilitation boundaries, and follow-up safety are clear before asking it. ### Turn answers into experiments, not just discussion Better questions only improve the team if the answers lead somewhere. A retrospective should not end with a long list of observations and no clear next step. As Atlassian notes in their [retrospective guide](https://www.atlassian.com/team-playbook/plays/retrospective), the value of a retro comes from insights that actually get implemented. Once the team has identified an issue, turn it into a small experiment, assign an owner, and agree how you'll check whether it helped. Instead of ending with "We need better communication," turn it into something testable: - "For the next sprint, we'll add a five-minute dependency check after daily standup." - "The Scrum Master will review whether blockers are being raised earlier." - "We'll revisit this in the next retro and decide whether to keep, change, or stop it." Once the team agrees on an improvement, capture it as a visible action item with an owner and revisit it in the next retrospective. TeamRetro makes it easy to [track retrospective action items](/retrospectives/features/) so nothing slips through the cracks between sprints. ### Use question combinations to avoid overwhelm With 100 questions to choose from, newer facilitators may wonder where to start. You do not need to use many questions in a single retro. In most cases, five well-chosen questions are better than fifteen loosely connected ones. To avoid anchoring bias — where the first voice in the room shapes everyone else's thinking — consider structuring your retro so participants submit answers independently before group discussion. The [1-2-4-All method from Liberating Structures](https://www.liberatingstructures.com/1-1-2-4-all/) is a great technique for this: individuals reflect first, then pairs, then groups of four, before the whole team discusses. Here are a few simple combinations: **Low-energy sprint** - 1 check-in question - 2 workload or wellbeing questions - 1 improvement question - 1 closing commitment question **High-performing sprint** - 1 celebration question - 2 questions about what worked well - 1 question about what to protect or continue - 1 action question to reinforce the behavior **Tense or difficult sprint** - 1 neutral check-in question - 1 question about blockers or friction - 1 anonymous psychological safety question - 1 question about what support the team needs - 1 small next-step commitment **Remote or hybrid team retro** - 1 connection question - 2 remote collaboration questions - 1 visibility or communication question - 1 action question for improving team rhythm The best retrospective questions are not the most clever ones. They are the ones your team is ready to answer — and act on. ## Run better retros with TeamRetro The right questions are only as good as the space you create to answer them. TeamRetro is an [agile retrospective](/retrospectives/) tool built for agile teams — with 100+ templates, anonymous idea submission, real-time voting, and built-in action tracking so every retro leads somewhere. Ready to run a retro your team will actually look forward to? [Try TeamRetro free](/) — no credit card required. --- # Return on time invested (ROTI) in agile meetings URL: https://www.teamretro.com/blog/return-on-time-invested/ We all value our time and the meetings we attend can either be a positive or negative use of that time. Irrespective of whether our meetings are face to face or online with our teams, the time we spend in them can leave us with a sense of whether or not the meeting was worthwhile. The Return on Time Invested, or ROTI for short as suggested by [Esther Derby](https://www.estherderby.com/calculating-meeting-roti-return-on-time-invested/) is a great way to help teams discover how much value is coming out of those meetings. ### What is the return on time invested (ROTI) in agile retrospectives? A ROTI is an easy way of gauging how much value each meeting participant perceives their meeting delivered. Just prior to the close of the meeting, attendees are invited to rate their experience using a simple 1-5 rating method to assess whether they feel that the time they spent in the meeting was worthwhile. Just as icebreakers are a great way to open meetings, ROTIs are a great way to close them; they help wrap up the session and draw focus on what could be done better next time. Generally, it’s best to give participants the opportunity to provide their response anonymously and independently, as this creates a psychologically safe space in which they are more likely to be honest and their feedback is less likely to be influenced by others. ### Why should we rate the ROTI for our retros? Rating your meeting’s ROTI allows you to monitor [meeting effectiveness](https://www.agileconnection.com/article/roti-method-gauging-meeting-effectiveness) and value. Time, whether spent or borrowed, is a valuable commodity; it can therefore be frustrating for team members if they feel the time they spend on their retrospectives could be better directed elsewhere – especially when retrospectives are a core practice of agile methodology! Rating a meeting’s ROTI gives each team member a platform to offer their opinion on the value of the meeting and present ways to improve it. Team members are therefore given a voice and contribute to the continuous improvement of their retrospectives and health checks. This empowers the team and helps them feel more engaged in the current and future meetings creating greater participation and buy-in. The rating of a meeting’s ROTI provides Scrum Masters with [feedback](https://www.inc.com/john-eades/why-you-should-be-more-worried-about-your-return-on-time-instead-on-investment.html) they may otherwise have missed. That in itself is a great reason to find out your meeting ROTI. ### How do we rate the ROTI of the agile meeting? TeamRetro offers you the choice to add a ROTI poll at the end of your retrospective or health check. Each person evaluates the ‘Return’ on their own ‘Time Invested’ in the agile retrospective or health check on a scale of 1 to 5 by responding to a simple question.  **Was this retrospective worth your time?** **1\. Definitely not.** A waste of my time. **2\. Not really.** Useful, but not worth all of time. **3\. Somewhat.** I gained enough to spend my time on it. **4\. Mostly.** I gained more value than the time spent on it. **5\. Absolutely.** I gained a lot of value and it was absolutely worth my time. ## Scrum Master tips for using the ROTI ### How do team members rate the ROTI of the meeting? The value that each team member gets out of their agile retrospective or health check will vary from meeting to meeting, but there are a few decision criteria that can guide the rating. **Information sharing** Value can be obtained by receiving answers to questions or hearing information that can help you move forward with a task, avoid rework, improve the way you work or overcome an obstacle. **Decision making** There may have been a person, process or piece of information that was blocking progress so having this at the meeting can help move the needle in making a decision. **Problem solving** If the meeting highlights, addresses or explores options around improving the meeting, then there can be a clear sign of value. **Work planning** Prioritizing, re-prioritizing or even redefining future work may seem like a non-productive exercise but is a value-adding activity if it can create alignment, focus and direction. **Team building and agreements** An often neglected aspect of work meetings is building rapport, communication and team spirit. The value may not be as extrinsic as an output or artifact, but more intrinsic in terms of agreeing on the way the team works together. ### How can you introduce ROTI to your agile team? Here are a couple of key messages worth sharing with the team when introducing ROTI. - The ROTI is independent and anonymous. Be honest about what value you obtained. - Results are not tracked. It should reflect the time and space of the meeting rather than an ideal score. - Ratings should be sincere, fair and honest. This is your opportunity to share now. - The goal is for continuous improvement rather than using it to pinpoint individuals, create blame, or criticize. - Use a future-based statement such as, *In future meetings, I would get more value if we did X.* **As the Scrum Master, you can help guide the quality of the ROTI by saying something like…** *“I’d like to ask/invite you to indicate the value of the time spent on this meeting, in other words, was this meeting valuable for you? We’ll then look at the group results to see how we can improve the return on our time invested for future meetings.* *Please be open and honest about how much value there was for you today. We will be doing this anonymously and independently.* *In considering your score, ask if this meeting has added value by helping us:* - *move forward with our work* - *make decisions* - *create appropriate actions* - *solve a problem* - *clear up confusion* - *improve the way we work as a team* *…we’ll then come back to review the scores”* ### How do I use ROTI to improve meeting effectiveness? The results from the team signal the overall perceived value that the group gained from the meeting. Of course this will vary from meeting to meeting depending on the content and relevance, but in any case, the goal is to explore ways to improve the facilitation and meeting outcome process. **Let’s say scores are in the 4’s and 5’s…** Congrats! This meeting sounds like a resonating success. It may have been the meeting design, the content, the quality of facilitation or all of the above. **Let’s say there are a few 2’s and 3’s…** Okay, there was still some value gained, but certainly not on the positive side. What could we do to improve our ratings? **Let’s say there are a few 1’s…** Don’t worry! This doesn’t mean that you have done a poor job. It could have simply been that someone did not care about the topic or whose job was not impacted by it. *“When people get really negative I’ll say ‘it sounds like you have a vision of how you want things to be’ or ‘if you can imagine a really effective meeting, what would it look like?” – Esther Derby* ### Closing off retrospectives… and this article. Ready to do a Return on Time Invested with your team? Add it to your TeamRetro retrospective meeting or team health check and it will be displayed at the end of the meeting. You can capture the feedback and reveal the results in real-time or you can review the results later. Get started with a free trial or [Login Now](https://secure.teamretro.com/), or do a [practice run with our fun robots.](https://secure.teamretro.com/demo/) --- # Scrum paradigms: chickens vs pigs — the Observer Role in agile meetings URL: https://www.teamretro.com/blog/scrum-paradigms-chickens-vs-pigs-the-observer-role-in-agile-meetings/ The Scrum framework has long been a beacon for teams striving for increased collaboration and efficiency. One of the most well-known metaphors within Scrum is the tale of pigs and chickens, which serves as a guiding principle for team involvement. We have introduced a new meeting enhancement feature – the Observer Role – designed to bring a new dimension to your agile meetings. This will now allow you to have people join any meeting as a “view only” participant. This is a really useful feature for agile coaches, new recruits, cross team collaborations or for the supportive and empathetic leader. You can [find out more about the observer role](https://help.teamretro.com/article/416-observer-role). ## The pigs and chickens story in scrum methodology Before delving into the Observer Role, let’s revisit the classic metaphor of pigs and chickens in Scrum methodology. This metaphor originates from a simple but profound story illustrating the levels of commitment within a Scrum team. In the story, the roles of pigs and chickens are used to differentiate between team members. Pigs are considered fully committed – they are the ones “in the game,” responsible for the project’s success. On the other hand, chickens are involved but not committed. They might provide input, but it’s the pigs who have skin in the game. Think of it as Eggs Vs Bacon. To illustrate, here’s a funny ditty: — ***Scene:** A cozy barn where Cluckington and Porkington are having a chat.* **Cluckington (Chicken):** Hey Porkington, I’ve been thinking about this whole pigs-and-chickens thing in Scrum. What’s the deal with that? **Porkington (Pig):** Ah, Cluckington, it’s quite simple. In the world of Scrum, we’re all on a team, working toward a common goal. But the pigs and chickens metaphor helps distinguish the level of commitment each member has. **Cluckington:** Commitment, you say? I’m committed to laying eggs every day; isn’t that enough? **Porkington:** It’s more about being fully invested, Cluckington. You see, in our Scrum team, the pigs are the ones with skin in the game. They’re the folks committed to the project’s success, contributing directly to the end result. **Cluckington:** So, what does that make me, then? Am I not contributing? **Porkington:** Of course, you contribute, Cluckington! You’re like a chicken in the metaphor – involved, offering ideas and feedback, but not entirely committed like the pigs. It is not about the quantity of contribution; it is about the level of skin in the game. **Cluckington:** Fair enough. But sometimes, I feel left out. Is there a role for someone like me who wants to be part of the process but isn’t a pig? **Porkington:** Funny you should ask, Cluckington. Recently, in our agile meetings using TeamRetro, they introduced an Observer Role. Observers are like chickens – present and contributing by being a fresh set of eyes without actively participating in the discussion. **Cluckington:** That sounds intriguing. It’s like being part of the process without being in the frying pan, right? **Porkington:** Exactly! **Cluckington:** I like the sound of that. It’s like having the best of both worlds – involvement without the pressure. ***End Scene:*** *Cluckington and Porkington continue their barnyard banter, embracing the diversity of roles within their Scrum team.* ## The importance of observers in team meetings Observers play a vital role in providing fresh viewpoints without actively participating in the discussion. Their outsider perspective can bring new insights, identify blind spots, and foster a more inclusive environment. This is especially important in complex projects where diverse perspectives can lead to better decision-making. For the safety and acknowledgment of all team members, observers will always be named in TeamRetro. This transparency ensures that everyone understands their role and contribution to the meeting. It also fosters a culture of trust and openness within the team. ## Value for the team, Scrum Master, and the observer Whichever way you look, inviting a trusted observer into your agile meeting can serve up a buffet of benefits. - **For the team** - Improved collaboration: Including observers fosters an open and inclusive team culture, encouraging collaboration beyond the core team. - Opportunity to get new perspectives: If wanted, the team can have the observer look at their process, their dynamics or ask for any feedback after the meeting. - **For the Scrum Master** - Enhanced facilitation: The Scrum Master can leverage the observer role to facilitate more insightful discussions and guide the team toward better outcomes. - Risk mitigation: Observers can identify potential risks or challenges that the team might overlook, contributing to more comprehensive risk management. - **For the observer** - Learning opportunities and onboarding: Observers gain valuable insights into the team’s dynamics, processes, and challenges, providing a unique learning experience. - Networking and acknowledgment: By being named and acknowledged, observers feel a sense of belonging and appreciation, fostering positive relationships within the organization. - Bridge gaps: Observers can act as conduits for knowledge transfer between different teams or departments, fostering cross-pollination of ideas and practices. - Guidance from afar: Seasoned team members can take on the observer role to mentor less experienced colleagues, providing guidance without directly intervening in the discussion. These discussions can happen after the meeting. - **For the leadership** - Holistic perspective: While leaders may have a broad strategic view of the organization, they can gain a nuanced understanding of team dynamics and ground level processes in the observer role. This can contribute to more informed decision-making. - Understanding team challenges: Observing without actively participating allows leaders to empathize with the daily challenges of the team which can lead to more empathetic leadership and breaking down silos. ## Rules and considerations for the observer role One of the key conditions is that the observer must do just that… observe. So, here are the rules of engagement (or non-engagement as the case may be). This is important for all observers, no matter which level or role you have! 1. **No active participation (Hands-off approach)** Observers should refrain from actively contributing ideas, comments, or votes during the meeting. Their role is to observe and absorb without influencing the team’s decisions in any way. It might be tough, but resisting the temptation to intervene while still actively observing to make this role work. 2. **Named and acknowledged** Observers will always be named during the meeting for transparency and accountability. This ensures that their presence is known to everyone, promoting openness and trust. 3. **Respect team dynamics** Observers should be mindful of the team’s dynamics and avoid disrupting the natural flow of the meeting. They are there to enhance, not detract from, the team’s collaborative process. 4. **Confidentiality and safety** Observers must adhere to the same confidentiality and safety standards as other team members. Any information shared during the meeting, including discussions and decisions, should be treated with utmost confidentiality. 5. **Limited frequency** To maintain the integrity of the observer role, team members should rotate through the position to ensure that everyone has an opportunity to benefit from the fresh perspective without becoming a permanent observer. 6. **Feedback channels** Establish channels for observers to provide constructive feedback if requested, outside of the meeting. This allows them to share their insights and suggestions without disrupting the flow of the team and respecting boundaries. 7. **Clear communication** Team members and observers should communicate openly about expectations and boundaries. This includes clarifying the purpose of the observer’s presence and any specific areas they should focus on. For example, you could ask the observer to take notes on what behaviors helped to progress the meeting positively or which parts of the process did the team get stuck on. By sticking to these rules, the Observer Role becomes a powerful tool for enriching team dynamics, fostering learning, and promoting a culture of continuous improvement within agile teams. So, as you embrace this new feature, remember the essence of the pigs-and-chickens metaphor and how the Observer Role complements it by bringing external insights into your agile meetings. Perhaps it’s the new recruit joining the company and you want to show them how an agile meeting works. Perhaps it is the leadership wanting to be more understanding of how the team operates, or perhaps you have an agile coach whose role it is to help guide and develop the team as they embark on their agile journey. TeamRetro is here to empower your team with the tools you need to thrive in an ever-evolving agile landscape. Happy observations! --- # Season’s greetings from TeamRetro URL: https://www.teamretro.com/blog/seasons-greetings-from-teamretro/ We are incredibly grateful for the many people around the world who looked to our [retrospectives](/retrospectives/) and agile [team health checks](/blog/what-is-an-agile-team-health-check-and-why-are-they-important/) to support their agile journey in 2025. Thank you for choosing TeamRetro. As we approach the end of the year, a number of our team will be taking a well-earned break. However, our Help Center services will continue over the festive period. We look forward to supporting your agile journey in 2026. Until then, from our team to yours, we wish you the very best for the festive season. All the very best for the New Year. Jeremy Lu / Brad Ward Co-Founders --- # Sprint retrospective vs. release retrospective URL: https://www.teamretro.com/blog/sprint-retrospective-vs-release-retrospective/ Retrospectives are like the pit stops of Agile practices—a chance to refuel, check the tires, and maybe even grab a snack. But not all retrospectives are built the same. Two popular types—sprint retrospectives and release retrospectives—each have their own role to play in a project’s journey. In this post, we’ll break down the key differences between the two and share a step-by-step guide to running a great release retrospective. Spoiler alert: no actual snacks provided. ## Sprint retrospective vs. release retrospective: key differences Both sprint and release retrospectives are designed to promote reflection and improvement, but they differ in their scope, timing, and focus. Here’s a breakdown of the key differences: | Aspect | Sprint Retrospective | Release Retrospective | | :-- | :-- | :-- | | Scope | Focuses on a single sprint (1-4 weeks) | Focuses on the entire release cycle (multiple sprints) | | Timing | Held at the end of every sprint | Held after a major release or milestone | | Audience | Development team, Scrum Master, and Product Owner | Broader audience, including stakeholders and clients | | Goals | Immediate process improvements for the next sprint | Strategic insights for future releases | | Outputs | Actionable tasks for the next sprint | Comprehensive lessons learned and recommendations | | Focus Areas | Team dynamics, sprint execution, process efficiency | Product quality, user feedback, team collaboration | | Formality | Can be formal or casual | Tends to be formal, structured and well prepared | **Sprint Retrospective:** Sprint retrospectives are tactical. They emphasize short-term process improvements, collaboration, and delivery within a sprint cycle. These meetings are typically brief and focus on identifying what worked, what didn’t, and what to improve immediately. **Release Retrospective:** Release retrospectives are strategic. They look at the broader picture, including the product’s success, alignment with business goals, and long-term process improvements. These sessions involve a wider audience and delve into more comprehensive feedback and outcomes. ## Key steps to run a successful post-release retrospective Conducting a release retrospective is vital for analyzing a project’s successes and challenges throughout its lifecycle. Below, we outline the main steps to ensure your retrospective is productive and actionable. ### 1. Set the stage Create a welcoming environment and clearly outline the retrospective’s objectives. Given the audience, duration, and amount of time required, it’s also important that people are comfortable and that the venue or technology is suitable. - **Welcome Participants**: Introduce all attendees and explain their roles. - **Define the Goal**: Clearly state the purpose, such as reflecting on the release’s performance, learning from challenges, and planning improvements. - **Encourage Open Communication**: Set a tone of psychological safety where participants feel comfortable sharing honest feedback. ### 2. Reflect on achievements Celebrate successes and build a positive foundation for the discussion. - Highlight key milestones and achievements. - Showcase metrics or data that illustrate success (e.g., user adoption, performance metrics). - Recognize individual and team contributions. **Guiding question**: What were the major wins and outcomes from this release? ### 3. Identify challenges Pinpoint obstacles and areas for improvement. - Discuss what didn’t go as planned, using specific examples. - Explore the root causes of these challenges. - Gather input from diverse perspectives to uncover blind spots. **Guiding question**: What difficulties did we face, and how did we handle them? ### 4. Evaluate processes Examine the effectiveness of workflows and tools. - Review how well the team followed established processes. - Identify inefficiencies or bottlenecks. - Discuss the effectiveness of tools and technologies used during the release. **Guiding question**: What processes, tools, or methods were useful or not useful? ### 5. Reflect on team dynamics Assess how well the team collaborated and communicated. - Highlight instances of strong collaboration. - Identify areas where communication could improve. - Discuss team morale and workload management. **Guiding Question**: How did team dynamics affect the overall success of the release? ### 6. Gather stakeholder and user feedback Incorporate external perspectives to assess the release’s impact. - Present feedback from stakeholders, clients, and users. - Analyze whether the release met their expectations. - Discuss any gaps between the delivered product and the initial vision. **Guiding question**: How well did we meet stakeholder and user expectations? ### 7. Identify lessons learned Extract insights to guide future projects. - Reflect on both successes and failures. - Highlight transferable lessons for future releases. - Document key takeaways. **Guiding question**: What did we learn that can help us in the future? ### 8. Create actionable improvements Turn insights into concrete actions for improvement. - Brainstorm ideas for process, tool, or communication improvements. - Prioritize actions based on impact and feasibility. - Assign ownership for each action item. **Guiding question**: What key actions should we take going forward? ### 9. Close with gratitude End on a positive note by appreciating the team’s efforts. - Thank participants for their contributions to the release and retrospective. - Reinforce the importance of their work and input. **Guiding question**: What or who are we thankful for? Sprint and release retrospectives are both powerful tools for fostering continuous improvement, but their effectiveness hinges on understanding their differences and tailoring each session to its purpose. Sprint retrospectives are focused and tactical, while release retrospectives are broad and strategic. By following the steps outlined above, you can run a successful release retrospective that delivers actionable insights, strengthens team dynamics, and sets the stage for future success. Need a simple way to share and capture ideas? Check out TeamRetro’s Release Retrospective Template today. --- # Team Spectrum: a 'Would You Rather' team building game for meetings URL: https://www.teamretro.com/blog/team-spectrum-icebreaker-game/ Every team has opinions. Strong ones. Quietly held ones. Ones nobody knew existed until someone asked. If your team enjoys "Would You Rather", Team Spectrum is the team-building game that takes the same idea and turns it into a window into how well you actually know each other. ## What is Team Spectrum? Team Spectrum is a team-building game — sometimes called a *human barometer* or a *"where do you stand"* activity — where a topic is placed on a spectrum and each team member must **guess where their colleagues would place themselves** before the big reveal. Think: The twist? You're not just sharing where you stand — you're testing how well you actually know your teammates. Surprises are guaranteed. It works brilliantly for [remote teams](/blog/virtual-icebreakers-for-remote-teams/), in-person [retrospectives](/retrospectives/), or as a warm-up before any meeting where you want people to feel relaxed and present. ## Why Team Spectrum works Most icebreakers ask people to share something about themselves. Team Spectrum flips that — it asks people to **think about others first**. That small shift creates a completely different dynamic: - **It sparks genuine curiosity.** Trying to predict someone else's answer means you're actually thinking about them as a person. - **The reveal is the fun part.** When someone places themselves far from where the group expected, the conversation that follows is priceless. - **It's low-stakes but high-engagement.** There are no wrong answers, no expertise required, and no pressure — just a fun window into how your team thinks. - **It builds empathy.** Discovering you misjudged a colleague's view on something opens a door to understanding them better. ## How to run Team Spectrum ### What you need - A whiteboard, virtual whiteboard (Miro, FigJam, etc.), or the ready-to-play [Team Spectrum game](https://games.teamretro.com/games/team-spectrum) - A list of spectrum topics (see below for ideas) - 5–15 minutes ### Step-by-step 1. **Draw the spectrum.** Create a horizontal line with two opposing labels at each end — for example: 2. **Everyone secretly guesses.** Each team member privately notes (or places a marker for) where they think *each of their colleagues* falls on the spectrum. Give people 60–90 seconds. 3. **Teammates reveal themselves.** One by one, each person places themselves on the spectrum and explains why. 4. **Compare with the guesses.** See who predicted correctly — and celebrate the surprises. 5. **Debrief briefly.** Ask: *"Did anything surprise you? What does that tell us about how well we know each other?"* Repeat with a new topic, or move into your main meeting with the energy already flowing. Prefer a ready-made version? The free [Team Spectrum game](https://games.teamretro.com/games/team-spectrum) does the setup for you — pick a theme, and AI will generate a whole bunch of topics for you, or you can always customize your own. Then everyone guesses where each teammate lands before the reveal. No whiteboard, no prep.
--- # TeamRetro templates now available in multiple languages! URL: https://www.teamretro.com/blog/teamretro-templates-now-available-in-multiple-languages/ We’ve got some exciting news to share here at [TeamRetro.](/) Our standard retrospective templates are now available in multiple languages, including French, Spanish and German. Thank you to our TeamRetro subscribers who suggested this, upvoted and made our online retrospective tool more accessible. With our platform used in over 40 countries worldwide we will continue to make common translations in TeamRetro in various languages. For now, let’s look at how to access this new feature. ### Step 1: sign in to TeamRetro Sign in to your TeamRetro account and then click create team. ### Step 2: create your retrospective in your chosen language Once you’re in your team space, click on Retrospectives and Create Retrospectives to view all the available templates. On the top right hand corner you will see options for multiple languages that you can choose for your retrospective templates. ### Step 3: start your retrospectives Conduct your retrospectives like you would normally in the language or multiple languages that you and your team prefer. This new feature of the TeamRetro retrospective templates is also available on the mobile app version. We hope that you enjoy this new added feature to TeamRetro. ### Have suggestions for other languages? If you have any suggestions for other languages, make sure you add them in the request feature in your account. If you don’t have an account with TeamRetro as yet, the good news is that you can try it out [FREE for 30 days.](https://secure.teamretro.com/login/new) ### Have questions about our multiple languages templates? Please get in touch with the TeamRetro team if you have any questions or suggestions for improvements for this new feature. Thank you again to our global TeamRetro agile and scrum teams for suggesting this new feature and making our templates more accessible for teams around the world. We look forward to releasing more languages soon. --- # TeamRetro’s newest integration with Microsoft Teams URL: https://www.teamretro.com/blog/teamretros-newest-integration-with-microsoft-teams/ Thanks to our supportive TeamRetro users and Customer Advisory Group who recently requested for “Integration to publish to [MS Teams](https://www.microsoft.com/en-au/microsoft-365/microsoft-teams/group-chat-software),” we’ve been able to make this newest integration possible. Let’s take a look at what this new integration with Microsoft Teams means and how you can access it for your retrospectives. ### What is the MS Teams integration? We have deployed our Microsoft Teams integration, which means you can now invite your team and publish action items to your MS Teams Channels. ### Why do we need this new MS Teams integration? Integrating TeamRetro with your existing workflow and communications means that you can easily use TeamRetro with other popular engagement and task platforms. Being able to move from one platform to another seamlessly or import data and reports together helps to improve productivity and quality of your operations and, in this case, retrospectives. In addition to this new integration with MS Teams, [TeamRetro](/) also works with these other existing task management tools so nothing falls off the radar: - Jira - [Asana](https://asana.com/) - [Trello](https://trello.com/) - [Github](https://github.com/) ### When is a good time to use this integration feature? With remote working and distributed teams on the rise, we see many more teams meeting virtually, and using Microsoft Teams to facilitate conversations, brainstorming and of course, retrospectives. We’ve made this integration a priority to meet this trend and to support teams all over the world do their retros. ### Who can access this MS Team integration? Whoever is your TeamRetro facilitator, they will be able to create the TeamRetro activity and get the invite code/link to post in MS Teams chat. Everyone else in the team can then access the TeamRetro activity through and in the chat. ### How does the MS Team integration work? To access this new integration with MS Team, simply follow these steps: 1. Create your TeamRetro [space or activity](/retrospectives/) and then on the invite team screen click on code/link. 2. Copy the URL for your TeamRetro activity and then post the invite in Microsoft Teams. 3. Once your team members click on the link they will be able to view the TeamRetro activity you have created. 4. You can also then post your team action items into your MS Teams channel so that you can keep on top of your retrospective or [health check action items.](/integrations/microsoft-teams/) Thank you again to our active TeamRetro users and Customer Advisory Group for suggesting this new integration. We hope this new feature will help all teams run retros successfully in an online or distributed environment. ### Try TeamRetro today! Want to try TeamRetro for your next team retrospectives? [View a demo with our fun bots](https://secure.teamretro.com/demo/retrospectives/scrum-retrospective) to check all the features of TeamRetro. Or [Try it FREE](https://secure.teamretro.com/login/new?emailAddress=) for 30 days today. --- # 50+ teamwork quotes to motivate and inspire your team URL: https://www.teamretro.com/blog/teamwork-quotes/ Great work is rarely a solo act. The right words at the right moment — at the start of a standup, in a retrospective, or pinned in a team channel — can remind a group why they are better together. Below are more than fifty teamwork quotes, grouped so you can grab the right tone fast, followed by a few simple ways to put them to work. ## Motivational teamwork quotes - *"Alone we can do so little; together we can do so much."* — Helen Keller - *"Talent wins games, but teamwork and intelligence win championships."* — Michael Jordan - *"Coming together is a beginning, staying together is progress, and working together is success."* — Henry Ford - *"None of us is as smart as all of us."* — Ken Blanchard - *"The strength of the team is each individual member. The strength of each member is the team."* — Phil Jackson - *"Individually, we are one drop. Together, we are an ocean."* — Ryunosuke Satoro - *"Teamwork is the ability to work together toward a common vision… It is the fuel that allows common people to attain uncommon results."* — Andrew Carnegie ## Famous quotes about teamwork - *"If you want to go fast, go alone. If you want to go far, go together."* — Proverb - *"Great things in business are never done by one person; they're done by a team of people."* — Steve Jobs - *"Individual commitment to a group effort — that is what makes a team work, a company work, a society work, a civilization work."* — Vince Lombardi - *"It is literally true that you can succeed best and quickest by helping others to succeed."* — Napoleon Hill - *"I can do things you cannot, you can do things I cannot; together we can do great things."* — Mother Teresa - *"The way a team plays as a whole determines its success."* — Babe Ruth ## Quotes about collaboration - *"Many ideas grow better when transplanted into another mind than the one where they sprang up."* — Oliver Wendell Holmes - *"Cooperation is the thorough conviction that nobody can get there unless everybody gets there."* — Virginia Burden - *"Unity is strength… when there is teamwork and collaboration, wonderful things can be achieved."* — Mattie Stepanek - *"Snowflakes are one of nature's most fragile things, but just look what they can do when they stick together."* — Vesta Kelly - *"Talent is a gift, but teamwork is a decision a team makes every day."* — Anonymous - *"A boat doesn't go forward if everyone is rowing their own way."* — Proverb ## Funny teamwork quotes - *"Teamwork is important — it helps to put the blame on someone else."* — Anonymous - *"There is no 'I' in team, but there is a 'me' if you look hard enough."* — Anonymous - *"Teamwork: simply stated, it is less me and more we."* — Anonymous - *"A team is a group of people who all blame each other when something breaks in production."* — Anonymous - *"Together Everyone Achieves More — except, perhaps, on a Monday morning."* — Anonymous - *"Coming together is a beginning. Staying together through a four-hour planning meeting is a miracle."* — Anonymous ## Short teamwork quotes - *"Teamwork makes the dream work."* — John C. Maxwell - *"Many hands make light work."* — Proverb - *"Two heads are better than one."* — Proverb - *"Unity is strength."* — Proverb - *"Strength in numbers."* — Proverb - *"Together we win."* — Anonymous ## Teamwork quotes for remote and distributed teams - *"Distance means so little when a team means so much."* — Anonymous - *"You don't need to share a room to share a goal."* — Anonymous - *"The best remote teams over-communicate the small things so the big things take care of themselves."* — Anonymous - *"Trust is the bandwidth a distributed team runs on."* — Anonymous ## How to use teamwork quotes with your team A quote on a slide is forgettable; a quote that opens a conversation sticks. A few easy ways to use them: - **Open a meeting or standup.** Lead with one quote and ask, "Where did we live this — or fail to — last week?" It turns a platitude into a real check-in. Our [check-in questions](/icebreakers/check-in-questions/) work the same way. - **Theme a retrospective.** Pick a quote about collaboration or trust and use it as the lens for the session — a light framing that focuses the discussion. See more [icebreaker questions](/icebreakers/) for openers by use case. - **Recognize good teamwork.** Pair a quote with a specific shout-out ("this is exactly what 'together we are an ocean' looked like this sprint") so praise lands as genuine, not generic. - **Pin one in your team channel.** A rotating weekly quote is a small, low-effort culture ritual — the same idea as a [question of the day](/icebreakers/question-of-the-day/). The point is never the quote itself — it is the moment of reflection it creates. Used well, these few words give a team a shared language for the kind of collaboration that makes good work possible. --- # Learn about agile principles with the Coin, Paper Airplane, DevOps games and more. URL: https://www.teamretro.com/blog/the-best-agile-games-for-building-teams-learning-and-creativity/ Agile Games are a great way to get your team familiar with and to practice the key principles of agile software development. They create a safe space for teams to explore their creativity, problem-solving, and communication in a fun way. Want to know more about what makes them tick? [Read more here.](/guides/scrum-masters-retrospective-guide/agile-games-facilitate-team-building/) Here are some of the best agile games you can run with your Scrum team. There are options for face-to-face, remote, or hybrid teams. Each comes with a recipe set designed to help you facilitate the game and to draw out key learnings from the team. We’ve broken down the games into particular areas to help you better choose the one that best fits your team. ## Best agile games for agile principles ### Ball Point Game Experiment and play in multiple teams while learning about continuous improvement. Learning goals: Agile production process and iterative working Time to play: 60 minutes In person or Virtual: Both Number of players: 4+ players Resources required: Ping pong balls – multicolored can be fun. How the game works: The objective of Ball Point is to help the Scrum team navigate agile projects better. By understanding the agile production process, the team can appreciate the importance of self-organization, flow, and iterative working. **Agile ball game rules** The goal is to, as one team, get as many balls through the system as possible in 3 sprints. The rules are as follows - There are 3 minutes per iteration and 5 iterations - In between, there is a 1-minute retrospective - The ball needs to start and end with the same person - The ball must have passed through everyone in the team - The ball must have air time - It can’t be passed to the person next to them. - If the ball is dropped, it does not count. Gather the team and provide the goals and instructions. Ask them to estimate how many balls they will get through each iteration. You can do one estimation at the start of the cycle and another short estimation in between each iteration. Start the process and time the activity. Let them play it out, and then record the number of balls transferred. Record the score and then time their retrospective, allowing them to change how it is played. They can then come up with new strategies as well as new estimates. Repeat the above process for as many iterations as possible, recording the score. Once all iterations are completed, run a debrief. You can ask questions such as - What was your experience like in the game? - How did the iterations differ? - What changes did you make, and what effect did they have? - How important were the retrospectives? What would have happened if there was none, more or less time to reflect? - How different was the last iteration from the first? - Did you experience the concept of flow? - Which iteration stood out? - How did you feel like working as a team? - Did leadership change during the iterations? - What did you learn from playing this game? **Variations to the Agile ball point game** You can add to this challenge by - Grouping the large groups into smaller ones and creating zones where people can stand. - Having rules around which colored or numbered balls have to go first - Creating a little chaos by having a call for people to have to switch positions ### Paper Airplane Game A good game that explores continuous improvement and Lean workflow. Learning goals: Lean workflow, value stream mapping Time to play: 60 minutes In person or Virtual: Both Number of players: 4+ players Resources required: Recycled or scrap paper How the game works: The goal of the paper airplane game is to fold as many airplanes as possible in a given timeframe, but only one person can make a fold at a time. **Paper Airplane game rules** The goal is to, as one team, make as many paper planes of the same design. The rules are as follows - There are 3 minutes per iteration and 5 iterations - In between, there is a 1-minute retrospective - The airplanes folded must be of the same design and quality. - Only one person can fold at any one time. Others can do other things as needed for their design. Gather the team and provide the goals and instructions. Ask them to agree on the design of the airplane. It can be a simple design with a few drawings that can fly one meter. This includes an element of design, production, and quality testing. Start the process and time the activity. Let them play it out and then record the number of airplanes that have met the quality requirements. Record the number of airplanes created. Now time the retrospective, allowing people to change how they work in the next round. They can provide a new estimate if they wish. Repeat the above process for as many iterations as possible, recording the number each time. Once all iterations are completed, run a debrief. You can ask questions such as - Where did you notice you were waiting (waste)? - How often was everyone engaged? - What changes were made, and how did they affect the production process? - What design aspects could make the flow slower or faster? - How would this game differ if it was played virtually versus in person? - How did quality controls play a part in this process? - Did you experience the concept of flow? - Which iteration stood out? - How did you feel like working as a team? - Did leadership change during the iterations? - What did you learn from playing this game? **Variations to the Paper Airplane game** You can vary to this challenge by - Timing how long it would take the team to create a set number of planes. - Increasing or decreasing the complexity of the design of the airplane. - Introducing quality control at the midpoint of the game rather than at the end. - Increase the difficulty, e.g., the airplane must fly at least 2 meters to count. ### Chocolate Bar Game Become a product owner and get feedback on your ultimate chocolate bar. Learning goals: Product ownership, iterative feedback, customer value Time to play: 60 minutes In person or Virtual: Both Number of players: 3+ people Resources required: Recycled or scrap paper How the game works: The goal of the Agile Chocolate Bar game is to create the most attractive chocolate bar to your customers as possible. Agile Chocolate Bar game rules The goal is a Scrum simulation where you have to create a chocolate bar that is the most attractive to your customers within a certain set of constraints. The rules are as follows - For each team, there should be a designated Product Owner. Otherwise, for a small group, each person is also a product owner. - There is an iteration round (3 minutes) and a feedback round (1min) for each phase. - There are at least 3 phases. Gather the team and provide the goals and instructions. Set a timer for 3 minutes and each team or person creates an example of a chocolate bar they think their customers would love. They can draw this out with as much or as little detail as possible for the “Plate of DOD (Definition of Done, or Done and delivered).” Then they have 1 minute to present what they have on their plate and get feedback from the rest of the group, who will act as customers. Customers can request changes or simply provide feedback. Based on the feedback, they then redesign the chocolate bar to be presented on the “Plate of DOD”. Each phase is repeated until the allotted time elapses. Once all phases are completed, run a debrief. You can ask questions such as - How did you decide how to design your chocolate bar in each phase? - How useful was the feedback from customers, and how did you improve the feedback asked for from each round? - How did you measure the value of the chocolate bar to the customer each time to make improvements? - If you didn’t measure customer value, why not? - How did the feedback you received influence the design of the chocolate bar? - What trade-offs did you have to find in the design? - What proportion of the customers did you satisfy at the end? - Would you have personally bought this chocolate bar? - Were there any features that were added that did not come from customer feedback? - Were any agile processes applied in the game, such as backlog, dot voting, or prototyping? - What else did you learn from this activity that you wanted to share? **Variations to the Chocolate Bar game** You can vary to this challenge by - Adding a score from each customer each round on their likelihood to buy the chocolate bar. - Allowing or not allowing the design team to listen to customer feedback sessions (e.g., just the product owner gets the feedback). - Adding constraints to the design of the chocolate, such as materials or size. ### Coin Game Get flipping with a kanban workflow challenge that will help teams stay active. Learning goals: The first principle of the Agile Manifesto, Continuous deployment Time to play: 15 minutes In person or Virtual: Both Number of players: 3+ people Resources required: 20 coins – They don’t have to be the same. How the game works: The goal of the coin game is to learn about the first principle of the agile manifesto, which is “ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” **The Coin Game rules** The goal of this game is to work out the fastest way to deliver value to the customer as a team. Essentially this means comparing agile to traditional approaches and determining the best batch size. The rules are as follows - There is a set number of coins representing value to the customer. - Each coin needs to be flipped by each person along the value chain before it is given to the customer. - The process is timed to see how long it takes to deliver value to the customer. - There will be 3+ iterations that are timed. Gather the team and provide the goals and instructions. Separate them into teams of 5 or 6 people. They can represent different roles in the value chain. Have people decide the fastest way they can take turns flipping the coins and stacking them at the end of the process, ready for delivery to the customer. After a minute of discussion, start the timer and let them play it out. Stop the timer when all the coins have been flipped by each person and stacked. Allow a one-minute retrospective to see how they might change the strategy and then repeat the activity above. Re-run the activity, recording the time taken for each iteration. Once all iterations are completed, run a debrief. You can ask questions such as - Which batch sizes did the best in terms of time? Why do you think that is? - Was there anything that surprised you in the game? - How do you think it would change if the distance between people were increased? - How do you think things would change if you had to wait 10 seconds each time there was a handover of coins? - If you introduced a change request during the game, how did that impact the process? - If you had compared it to the traditional waterfall approach, what differences did you notice? - How good were the team’s time estimates? - What else did you learn from this activity that you wanted to share? **Variations to the Coin Agile Game** You can vary to this challenge by - Having the teams start off by completing the task in a traditional waterfall approach where every coin was flipped by one person before it was moved to the next person. This acts as a baseline. - Introducing one or more change requests to the process – e.g., I only want $2 coins or Coins with a picture of an animal. - Have teams estimate how long it would take to complete the task at different batch times. ### Marshmallow Game Explore problem-solving strategies and builds that require learning from failures and timeboxing. Learning goals: Creativity, problem-solving, collaborative teamwork. Time to play: 20 minutes to build the tower, then debrief. In-person or Virtual: Both Number of players: 3+ people Resources required: For each team, 1 large marshmallow, 30 dry spaghetti sticks, 1 meter of tape, 1 meter of string, 1 pair of scissors. Measuring tape. How the game works: This game allows you to challenge teams to be creative and collaborative. It involves teamwork, listening, and working together to build the best-performing structure. **The Marshmallow Game rules** The goal of the marshmallow challenge game is to build the tallest freestanding tower with a marshmallow at the top. The rules are as follows - The marshmallow must be intact. No tearing or biting. - You can break or tear any of the other items. - Once time is up, everyone must back away from the structure. You cannot hold onto it. - The structure must be free-standing. Gather the team and provide the goals and instructions. Set the time that you have allowed for the exercise and let the teams go. Once time is up, teams back away from their structure. Now record the maximum height of each of the marshmallow towers. Celebrate and congratulate all teams as well as the winning team. It’s now extra important to debrief on the exercise. You can ask questions such as: - How would you rate the overall performance of the team and your tower? - What factors contributed to the success? - What factors contributed to failures? - What failures did you experience on the way? - How did your team communicate? - Were there any aspects of the challenge that you thought helped with the tower’s creation? - What roles did each person play, and did it change? - How much planning did you do? - What was the impact of the resource constraint? - If you were allowed to double just one of those resources, which one would it be and why? - Did you use all of your resources? Why or why not? **Variations to the Marshmallow Tower Game** You can vary to this challenge by - Allowing teams to trade resources between teams - Adding a second marshmallow into the challenge ### How long does it take to make a cup of tea Enhance and explore estimations and the impact on the team outcomes. Learning goals: Estimations and task sizing Time to play: 30 mins In person or Virtual: Both Number of players: 3+ people Resources required: Tea, plus whatever tools, gadgets, and items each person decides to use to make their cup of tea. How the Make a Cup of Tea game works: This game helps teams understand estimations of tasks and being able to develop the right ability to ask questions and consider factors that will improve estimations in agile. **The Make a Cup of Tea Game rules** The goal is to estimate how long it would take everyone in the team to make a cup of tea and to be ready to drink altogether. There is a round of questions that allows people to guess, and then they then head off to make the cup of tea. The timer stops when the last person returns, and everyone is ready to sip their cup of tea. The rules are as follows - You have 1 minute for people to ask questions to the team to allow them to estimate how long it would take to make a cup of tea. - Each person then writes down their own estimate. (By Minutes and Seconds) - As a whole, the team then comes up with a final estimate. (By Minutes and Seconds) - The timer stops when everyone is back and ready to take the first sip of tea. Gather the team and provide the goals and instructions. Ask each person to ask questions to the group and listen to the response. After a minute, ask each person to share their estimate. Based on this, ask the team to create a final group estimate and record this. (Minutes and Seconds). Start the timer and let everyone head off to make a cup of tea. When everyone comes back, they are ready to take their first sip. Stop the timer and write down the time. Have teams compare their individual, group, and real-time. The important part of this game is then to debrief this. You can ask questions such as - How close were your estimates to the real-time? - How different are your estimates from the group estimates and the real-time? - What factors caused your estimates to be wrong? Or right? - What events surprised you and you did not expect or plan for? - What would have helped you make a better estimate? - What questions should you have asked that would improve your estimations? - What do you think is the value of good estimations – why did we just do this exercise? - What are the impacts of getting estimations too wrong? - How did it feel being the first person back versus the last person back? - If you run the same activity again next time, do you think your estimates would be the same or different? Why? **Variations to the Make a Tea Game** You can vary to this challenge by - Keeping personal estimates unknown. - Using different ways to calculate the group estimate – by average time, most common, by consensus. ### The Multitasking Name Game (Henrik Kniberg) Which is better, single-focus or multi-tasking? Take the challenge and find out. Learning goals: Limiting WIP, Kanban, task planning Time to play: 10 mins In person or Virtual: Both Number of players: 5+ people Resources required: Pen, Paper and timer **How the multitasking name game works** This is a short, simple but powerful game that highlights the effects of multi-tasking and context shifting. In a busy world, people are often doing multiple projects, open tabs in the browser, or trying to switch between tasks. This game highlights how effective people actually are at multitasking. This game was introduced by [Henrik Kniberg](http://coach-agile.com/wp-content/uploads/2018/07/Multitasking-Name-Game-agile.pdf). **The Name Game rules** The goal is to write down everyone’s names as fast as possible so that all names are written out in full. The rules are as follows - There are 2 phases. - In the 1st phase, you can only write one letter of each person’s name at a time. E.g. all the first letters, then all the seconds and so on. - Every time a name is completed, record the time of completion. - When all names are completed, record the time of completion. - In the 2nd phase, you can only write one name at a time. At the end of each name, complete the time of completion. When all names are completed, record the time of completion. - Compare the 2 results. Gather the team and provide the goals and instructions. Create a list of all the names of the people in the room. You can either have someone act as a scribe for the team and have someone else time each name and list completion. Ask teams to estimate how long it would take to write all the names one letter at a time per name versus one name at a time. Start phase one and record the times. Run phase two and record the times. Calculate the difference in times – what was the proportional change? The important part of this game is then to debrief this. You can ask questions such as - How close were your estimates to the real-time? - What made phase 2 easier than round one? - Would it make a difference if the names were scientific words or uncommon words instead of names? - What made it easier to uni-task rather than multi-task? - In reflection, which activities do you multitask? - Do you think it would be faster to write 2 names at a time rather than one? - What other learnings did you want to share? **Variations to the Name Game** You can vary to this challenge by - Changing it from names to a set of numbers, scientific terms, or formulas. - Try having paired scribes in both phases and see if it makes a difference. ### LEGO Flow Role-based workflow game that will be sure to get a few neurons firing. Learning goals: Backlogs, Kanban, inspection and adaption. Time to play: ~60 minutes, based on 3 rounds of 5 minutes In person or Virtual: Virtual Number of players: ~5 people per team Resources required: Lego pieces of any color, sticky tape or 4 pieces of paper. You can download [printable resources](https://www.organizeagile.com/app/themes/organizeagile/assets/uploads/2019/12/OrganizeAgile_LegoFarmAnimal_KanbanGame.pdf) here thanks to Organize Agile under the Creative Commons. **How the LEGO Flow game works** This game highlights differences between existing processes and using a kanban system to help optimize workflow and output. It uses assigned roles for each person, a backlog of orders, and other game theories to help teams experiment with ways to optimize their workflow. **The Lego Flow Game rules** The goal is to create as many lego animals as possible each round (3). With each round, the process is timed and the teams get to see how long it takes them to construct as many animals as possible. The team should manage their flow (left to right) and create explicit agreements to work together. Points are earned for each completed animal and points are deducted for unused parts or undelivered animals. The rules are as follows - This game is played in 3 rounds. - There are 4 types of animals to be built based on a set of resources. - In each round, points are earned for each completed animal built and delivered to the right specification. They must be 2 blocks high and the color does not matter. - The roles are as follows: - Analyst (Leg builder): gathers the legs. - Developer (Body builder): puts 2 blocks on top of each other - Designer (Head builder): builds the head - Delivery (Transporter): puts the animal in transport for 30 seconds - Tester (Quality Assurance: checks output, keeps score and takes the animal apart). - Animals are built and then transported for delivery. - There is a 30-second delay for transportation. The animal stays in the transport zone during this time. - There are a maximum of 3 animals transported at the same time. (ie. 1 animal per truck) - Once the animal is checked, it is then disassembled and put back into a starting pile. - Points are scored as follows: - +10 points for each fully delivered animal - \-1 point for every unused leg - \-4 points for every unused body - \-4 points for every unused head - \-10 points for every completed animal not yet arrived. **Round 1** Gather the teams and provide the goals and instructions. Simply give them a pile of lego bricks. There is no backlog, or visualization of workflow. The team chooses what animals to build. Set the timer for 5 minutes and ask people to start building. At the end of the round, record the final score and allow a minute for reflection of the task. **Round 2** Now introduce a workflow system. Ask the team to create a visual workflow either with tape on the table or pieces of paper, going from left to right. Unassembled pieces are then pulled from one pile and moved from leg builder to body builder to head builder, then transport/testing. Set the timer for 5 minutes and ask people to start building. At the end of the round, record the final score and allow a minute for reflection of the task. **Round 3** Keep the visualized workflow and this time introduce the backlog or order of production. E.g Cow Cow, Sheep Sheep, Duck Duck, Horse Horse. Set the timer for 5 minutes and ask people to start building. At the end of the round, record the final score and allow a minute for reflection of the task. Now ask the following debrief questions - How did your scores change from round to round? - What went well? - When and where did the work pile up (bottleneck)? - What improvements did you introduce and what impact did it have? - What was the differences between the first and third round? - Did you experience flow? When did this happen? - Did your WIP limits change after each round? - Was there any rework that needed to be done? - What else would you change to improve the overall results? **Variations to the Lego Flow Game** You can vary to this challenge by - Introducing some limits to a specific type of lego blocks. - Allowing the teams to come up with their own backlog. ### Lego Retrospective Game Each team member builds and talks about their experience of the last sprint through their lego design. Learning goals: Creativity, Retrospective Time to play: 3-minute build and 1 minute per person In person or Virtual: Both Number of players: Any Resources required: Assorted Lego pieces **How the Lego Retrospective game works** This is a free-style, easy game that lets people talk through a lego design about their experience of the last sprint. It can help break down communication barriers by using each piece, or the whole shape for people to use as a talking point. **The Lego Retrospective Game rules** The goal is to create a simple Lego design that reflects your experience of the last sprint. There are no right or wrong answers. Place an assortment of legos or give each person a pile of legos and give them a few minutes to build anything they like that represents their experience of the last sprint. Then, give each person a turn at describing what they have created. You can ask questions such as - Why did you use the pieces you used? - Tell us more about a particular experience? - What did you love most or think was missing in your design? **Variations to the Lego Retrospective Game** You can vary to this challenge by - Posing a particular scenario and having people build their version of it. Examples include: - What would good/bad communication look like? - What is your vision for this team or project? - How would a perfect user story be represented? - How would you portray our teams culture? ### Kanban Pizza Learning goal: Practice using a whole Kanban system including understanding the effects of limiting the team’s Work in Progress (WIP). Time to play: 2 to 3 hours In-person or virtual: In person Number of players: 4-8 per team Resources required: Sticky notes in three colors: yellow (mozzarella), pink (pepperoni) and green (herbs), paper (for pizza bases), red markers (for tomato sauce), glue or transparent tape, masking tape, scissors (one small and one large per team), paper plate (oven) and a stopwatch. **How the Kanban game works** Players step into the role of pizza chefs. They are divided into teams and given the materials they need to make a version of a pizza. They must create as many of the same pizzas as the one created by the facilitator. At the end of each round, the team counts the number of pizzas delivered and aims to reduce the amount of waste. **Kanban Pizza game rules** - The team must create as many pizzas as possible in the allocated time. - The pizza must be exactly the same as the one created by the facilitator. (5 points) - Each pizza must be ‘cooked’ for at least 30 seconds. - The oven can only hold three pizzas at a time. - Wastage should be kept to a minimum. (- 1 point for each waste item) - Unused resources created from one round can be used in the next. **Getting started** **Round one – Create your own process** - Have an example ‘pizza’ made up to show the group – A white circular base using the printing paper that is colored red with the marker for tomato sauce. Add six yellow (mozzarella) squares, six pink (pepperoni) squares and three green (herbs) squares. - Show them the paper plate as the oven. - After five minutes, count how many pizzas were made, assess the level of wasted food, and calculate scores. **Round two – Introduce Kanban** - Introduce Kanban and the core practices of Kanban. (Visualize the Workflow, Limit your Work in Progress (WIP), Manage the Flow, Implement Feedback Loops, Make Process Policies Explicit, Improve Collaboratively). - Have teams visualize the workflow and make the process explicit by introducing storage for production materials (pizza bottoms, slices of ham, etc.) directly on the table. The teams can use the materials at hand (masking tape, post-its and paper). - Advise the teams to limit their Work in Progress (WIP). - Run a new round with the newly established Kanban system. At the end of five minutes run a debrief and calculate scores. **Round three – Extend the system** - Introducing a new pizza type. Customer orders can now contain pizzas of two different kinds. - The team can only count the pizzas when the whole order is fulfilled. - A team can pull several orders at once. - Allow the teams five minutes to discuss how they will extend the system. - Run a new round . At the end of five minutes run a debrief and calculate scores. **Round four – Iterate and improve** - Give the teams five minutes to discuss and improve their system. Have them focus on the workflow and different WIP limits. - At the end of five minutes run a debrief and calculate scores. - Finally debrief on all four rounds to see what the team learned. [Agile 42](https://www.agile42.com/en/agile-teams/kanban-pizza-game) offers resources to support their game. Shared under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/). ### Agile Battleship An activity created by [James Scrimshire](https://www.linkedin.com/in/jamesscrimshire/) that takes the classic game of [Battleship](https://anthonycoppedge.medium.com/agile-games-using-battleship-for-demonstrating-pivoting-based-on-learnings-5a982dc63ab6) and gives it an agile twist. Learning goal: To understand the importance of communication, collaboration, and the benefits of the iterative development process. Duration: 30 minutes. In-person or virtual: Both. Number of players: 4-12 Resources required: Battleship game set **How the Agile Battleships game works** Teams play rounds of Battleships. The first is played without any feedback. Subsequent rounds gradually introduce more feedback. Agile Battleships game rules Each team can see their own board but not their opponent’s board. Teams take turns firing at their opponent’s board, calling out the coordinates of their target. The game ends when one team successfully sinks all of the opposing team’s ships. **Getting started** Divide the group into two. Set up the battleship boards and fleet pieces. The teams take turns to sink each other’s ships. **Round one – No feedback** - Begin the game with teams taking turns to call out coordinates. - After 5 minutes, stop the game. Count how many hits the team made. - Debrief by discussing how the players felt, and how their experience could apply to their work. **Round two – Limited feedback** - This time, after every five shots, the team is told if they ‘hit’ or ‘missed’ a ship. - After 5 minutes, stop the game. Count how many hits the team made. - Debrief by discussing how this iteration differed from the first. **Round three – Real time feedback** - This time, after every shot, the team is told if they ‘hit’ or ‘missed’ a ship. - After 5 minutes, stop the game. Count how many hits the team made. - Debrief by discussing how this iteration differed from the first. - Ask teams how they get and receive feedback in their workplace. **Variations to the Battleships game** - Watch [a pen-and-paper version of Battleships](https://www.youtube.com/watch?v=1aAQaGxCpCg). - A virtual version is offered by [BoxUK](https://www.boxuk.com/battleships/) - Play without timeboxing the rounds. Instead, stop when one team has sunk all of the ships of the other. Use this to inform discussions around the influence of feedback on time management. - If time allows, additional rounds can be included that more gradually increase the amount of feedback the teams receive. Shared under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/). ### XP Game A game designed by [Vera Peeters and Pascal Van Cauwenberghe](https://www.agilecoach.net/index.php/about/) to introduce participants to the principles and practices of Extreme Programming (XP) methodology. Learning goal: Increase understanding of concepts such as velocity, story estimation, yesterday’s weather and the cycle of life of both developers and customers. Time to play: 2-3 hours In-person or virtual: In-person Number of players: 5-12 Resources required: [Pre-filled story cards](https://www.agilebelgium.be/xpgame/download/), planning and scoring sheets, pencils, playing cards, dice, balloons, other small props to perform stories, a timer per team. **How the XP Game works:** The XP Game makes the players act as either a developer or customer, so that they understand each other’s role. **XP Game rules** - The aim of the game is to earn as many business points by delivering value with a timeframe or budget. - Value is delivered by completing stories that have been accepted by the customer. - Stories are found on story cards. These are simple activities to be done. - Players provide an estimate for each story card and decide what the team should attempt to deliver within an iteration. Not all time needs to be used. - An iteration is three minutes. - Teams with the most points are the most successful. Getting started Participants are divided into teams and assigned the roles of developers or customers. **Round one – Determining velocity** - Allocate each team 12 story cards. - Players estimate the stories from one to six, or impossible. Players may ask the coach questions about each story. - Customers choose the stories they think can be implemented by the developers in three minutes and then order the cards. - Developers implement the stories one at a time, in order. - Start the timer when a developer starts a story. Stop the timer when they think the story is finished. - The customer accepts or rejects the story. If rejected, the timer is restarted and the story is done again. If successful, the developer picks up the next story. - At the end of the round, tally up the business points of all fully delivered stories and add to the score sheet. Calculate velocity based on the time used. **Round two – Determining business value** - Have the team debrief the first round. - Give each team seven more story cards. The team estimates the new cards. - Customers choose stories to equal the team velocity from round one and orders them. - Developers implement the stories, in order, until the timer runs out. - At the end of the round, tally up the business value and calculate velocity. - Compare it to the first round and debrief. Run as many iterations as you would like to improve iteration planning. Shared under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/). ### DevOps Dream A simulation [game](https://devops.games/pages/aboutTheGame.html) from the team at [Mechanical Rock](https://mechanicalrock.io/). It’s designed to introduce participants to the principles and practices of DevOps methodology in a fun and interactive way. Learning goal: To help participants reflect on how they develop and run software. Time to play: Flexible In person or virtual: virtual Number of players: 1 Resources required: [DevOps Dream](https://dream.devops.games/?utm_source=devops.games_website&utm_content=orangebtn_cta) **How the DevOps Dream game works** Players step into the role of the CIO of a company. They need to pick the right combination of initiatives and actions to lead their team to success. **The DevOps Dream game** The game offers a guided tutorial. The steps include – - Choosing a company - Deciding on initiatives - Examining performance metrics Different scenarios are present along with a choice of steps that can be taken in response. The player is assessed on four key results over a 3 year period. - People - Productivity - Customer Satisfaction - Stability --- # From awkward to awesome: the science to good check-in questions URL: https://www.teamretro.com/blog/the-science-behind-good-check-in-questions/ Ever started a retrospective with, “How’s everyone doing today?”—only to be met with silence or a shrug? You’re not alone. While [check-in questions](/icebreakers/check-in-questions/) and check-out questions might seem like small talk, they’re actually powerful tools for creating engagement, psychological safety, and continuous improvement in Scrum teams. That’s why [TeamRetro](/) has built-in features to help Scrum Masters bring intention to how they open and close every meeting. In this post, we’ll explore: - The psychology behind check-in and check-out questions. - TeamRetro’s built-in options and how to use them. - How to turn one-off responses into long-term insights. - Tips for getting more value from your retros. ## The science behind good check-in questions What makes check-in questions so powerful in Agile retrospectives? It comes down to the science of human behavior and team dynamics. ### 1. Priming for participation A small early contribution makes people more likely to speak up later—this is known as the **foot-in-the-door effect**, a well-documented psychological phenomenon. Freedman & Fraser, 1966. ### 2. Cognitive framing The way a conversation starts frames how people think, speak, and respond throughout. A focused check-in sets the tone for constructive dialogue, feedback, and idea generation. ### 3. Belonging and trust Simple questions that invite open, honest input create space for team members to feel seen, heard, and valued. Agile thought leaders like [Esther Derby](https://www.estherderby.com/), [Lyssa Adkins](https://www.lyssaadkins.com/), and [Johanna Rothman](https://www.jrothman.com/blog/mpd/) all emphasize the role of team connection and psychological safety in effective retrospectives. ## Check out questions: the counterpart At the same time, a check-out question also offers its own benefits. ### 1. Closure and cognitive framing Check-out questions create a clear endpoint, allowing participants to mentally “package” what they’ve learned. According to Gestalt psychology, humans naturally seek closure. Offering a moment to reflect enhances information retention. ### 2. Shared experience and group cohesion Asking everyone to share a final thought reinforces a sense of belonging and psychological safety. Social identity theory (Tajfel & Turner, 1979) shows that shared rituals—like closing rounds—can strengthen group identity. ### 3. Reflection and meta-cognition Check-out questions prompt people to think about their own thinking. This encourages deeper learning and helps participants retain what was discussed. This deepens learning and self-awareness—key principles in Agile coaching as highlighted by [Lyssa Adkins](https://lyssaadkins.com/) and [Jurgen Appelo](https://www.management30.com/). ### 4. Priming for action A well-crafted check-out can subtly prepare the brain for future behavior. Asking what people will apply or do next builds a sense of accountability and encourages follow-through. In either case, the key aspects of a good question are that they are: - Short and to the point – this is not to open up or facilitate deep discussions. - Fast and quick – we are just collecting some quick data points in order to get a quick pulse check- not an ideation. - Designed to give feedback – not to solve a problem. Together, these questions can transform your retrospective from a checklist item to a meaningful team ritual. > “The most powerful tool we have as leaders is the question.” – Brene Brown ## TeamRetro’s built-in check-in questions—and what they reveal TeamRetro offers five built-in check-in questions to help you set the tone at the start of your meeting. Each one taps into a different aspect of team health and collaboration. | **Check-In Question** | **What It Captures** | **Why It Matters** | | :-- | :-- | :-- | | **Energy level** | Team’s physical or mental energy coming into the meeting | Helps gauge readiness and informs pacing or tone of the session | | **Weather Report** | Team’s mood or sentiment about the last sprint | Highlights morale and signals potential issues needing attention | | **Safety Check** | Comfort in sharing thoughts and concerns openly | Promotes psychological safety – key to open, honest communication | | **Team Collaboration** | How well the team worked together last sprint | Reflects teamwork dynamics and surfaces process or role gaps | | **Sprint Happiness** | General satisfaction with the last sprint or iteration | Reveals engagement and flags deeper issues behind delivery work | ## Close the loop: TeamRetro’s built-in check-out questions At the other end of the meeting TeamRetro includes four built-in check-out questions: | **Check-Out Question** | **What It Captures** | **Why It Matters** | | :-- | :-- | :-- | | **Return on Time Invested** | Whether the meeting was valuable and worthwhile | Tracks **meeting effectiveness** and ROI (shown in TeamRetro’s **Insights**) | | **Pulse Check** | Emotional or mental state at the end of the meeting | Indicates psychological engagement and overall team sentiment | | **Delivery Confidence** | Confidence in achieving sprint goals | Surfaces blockers or misalignments in team readiness | | **Retrospective Process** | Satisfaction with how the retro was facilitated | Direct feedback on facilitation style and structure—supports continuous improvement | Adding these questions to your retrospective is as easy as toggling them on as a step in your retrospective and then choosing the question you would like to ask the team. [See how.](https://help.teamretro.com/article/395-check-in-check-out-questions) ## Turn once-off responses into insights By using check-in and check-out questions regularly, you can track the emotional and cognitive pulse of your team over time. For example: - Monitor **energy levels** at the start of each meeting to detect burnout early. - Use the **weather report** to correlate mood with **delivery confidence.** - Track **retrospective process feedback** to improve your facilitation style. All this data is automatically captured in TeamRetro’s Insights tab, giving Scrum Masters and Agile coaches a clear view into **team engagement trends**. ## Turn insight into action Use what you learn from your insights to: - Adjust your facilitation style. - Acknowledge and refine what works. - Follow up 1:1 with quiet or outlier voices. - Change the format or timing of meetings. - Celebrate wins or address dips in morale. - Spot recurring blockers impacting team engagement. ## Tips for Scrum Masters Want to get the most from check-in and check-out questions? Try this: - Rotate questions weekly to keep them fresh or if you sense a need to change the question. - Alternatively, use the same question set if your goal is to track one metric over a period of time. - Create a team health check to dive deeper into a specific area. - Use the trends or results as a data point for future retrospectives. Have a new team member? Throw in an [icebreaker question](/icebreakers/) into your retrospective to help open up doors for communication. ## Final thoughts Check-in and check-out questions aren’t just nice-to-haves—they’re simple but powerful tools that help teams connect, reflect, and grow. Whether measuring energy, morale, or meeting value, TeamRetro gives you the structure and insights to do it with ease. So next time you launch a retro, don’t skip the opening question. Start strong, finish thoughtful—and watch your team open up. 👉 **Try adding a check-in to your next retrospective in [TeamRetro](/)**—it takes seconds and can spark conversations that matter. --- # Timeboxing for scrum teams and successful retrospectives URL: https://www.teamretro.com/blog/timeboxing-for-scrum-teams-and-successful-retrospectives/ We’ve all been in at least one meeting where we come out and say “well that was a waste of time.” This graph summarizes the truth about human attention span in meetings. One way we can make sure teams and participants don’t leave meetings unhappy because it runs out of time and ineffective is to use the timeboxing methodology. Scrum teams have used timeboxing as a way to maintain efficiency and productivity, so let’s find out more! ## What is timeboxing? Timeboxing is a simple time management technique which involves setting a fixed, maximum unit of time to complete an activity. That unit of time is referred to as a timebox. You then work on the activity during the fixed time period and stop working on it once the time is up. Then, you assess whether you’ve reached your planned goals. Timeboxing was first introduced by James Martin, the author of the book [Rapid Application Developmen](https://www.iro.umontreal.ca/~dift6803/Transparents/Chapitre1/Documents/rad_wp.pdf)t, as part of agile software development. Scrum teams and many project managers use timeboxing to keep everyone focused on accomplishing the task at hand. ## Let’s see how timeboxing is used by scrum teams ***Sprint**:* timeboxing can be used to define the length of the Sprint for scrum teams to deliver the Sprint goals. ***Sprint planning**:* when a team launches, they establish a timebox for the Sprint Planning meeting. The [Scrum Guide](https://www.scrumguides.org/) suggests that a Sprint Planning meeting should be timeboxed at 8 hours or less for a one-month Sprint. ***Daily scrum**:* a shorter timebox, for about 15 minutes for each day can help scrum teams synchronize activities and make any challenges to achieving the Sprint goal obvious. ***Sprint review**:* during the review, sprint backlog items delivered during the sprint are discussed and inspected. You can timebox the review to make sure you go through the backlogs efficiently and effectively. ***Sprint retrospectives**:* as you would know, retrospectives are our jam! Retrospectives are a time for the team to inspect itself and identify a process improvement that they can implement for a new sprint. Timeboxing retrospectives is important, [to avoid BMWs](/blog/how-to-manage-bmw-in-retrospectives/), to make sure that every team member’s opinions are valued, and to keep discussions constructive. ## Timeboxing with TeamRetro If you want to keep things moving quickly and on time with your retrospectives, you can set a countdown timer in TeamRetro through the stopwatch in the top right-hand corner of your screen. When your time is up the timer will go red and pulse to grab your attention. Or people can click the button functionality to say “I am finished” signaling they are ready to move on. Other ways to do this if you are using Zoom is to click “yes” or “no.” ## TeamRetro timeboxing recipe TeamRetro has a Timeboxing recipe for synchronous meetings for a 60-minute retrospective (just to make sure you finish on time). Note, you can proportionate this recipe for a longer meeting to suit your team’s needs. For example if your team health checks show that you need more connectivity, then you might need to allocate more time. Check it out below. ## More timeboxing tips and tricks - Allocate a specific time for each person in the team e.g. 1 minute per person - Roman voting: thumbs up or down if they need more time at the end of the timer - Think “pair share” – think for 30 seconds, pair with another person for 1 minute, and then share with another pair before final sharing with the whole group. ## Try it for your next retrospective or meetings Want to try the timeboxing methodology? [Try TeamRetro for free for 30 days](https://secure.teamretro.com/login/new/) and start using our meeting facilitation tool – the TIMER – to facilitate timeboxing easily for your next retrospectives or meetings. --- # Tips for actionable sprint retrospectives URL: https://www.teamretro.com/blog/tips-for-actionable-sprint-retrospectives/ At [TeamRetro](/), we know that teams can face a number of challenges in their retrospectives. This includes working through disagreements and complaints, keeping employees engaged, and ensuring goals aren’t too unrealistic, to name a few. So when we came across this article by [BuiltIn](https://builtin.com/) on [“How to make sprint retrospectives more actionable,”](https://builtin.com/articles/sprint-retrospective) we had to share! The best part of this article is the knowledge sharing from scrum masters, Agile directors, through to marketing managers. Each share their tips for running actionable retrospectives. So let’s check them out. #### Lionel Luchez, Software Engineering Manager — Snapsheet “As we move through the three phases of the retrospectives, we come up with resolutions, which then become our action items.” “Phase one is reviewing closed gaps since the last meeting.” “Phase two is where the meeting becomes an open dialogue.” “The format of phase three is fairly similar to the previous phase, except that we brainstorm on topics from open questions like recent changes, current projects and any issues we encountered.” #### Emily Erdman, Marketing Manager — TopstepTrader “Our marketing team recently switched over to a [“stop, start, continue”](/retrospective-templates/start-stop-continue-retrospective/) [retrospectives] model” These meetings are designed to understand learnings from the perspective of each team member and identify any ways the leadership team can help them improve. #### Eric Voetberg, Program Manager — Outrider “There are three keys to successful sprint retrospectives. First, provide advance notice of at least one week.” “Second, collect feedback in a methodical manner by using a standard template.” “Lastly, check egos at the door. Retros go well when team members are humble, honest and forthcoming.” #### Neil Sproul, Director of Agile — Billtrust “Start with understanding the team and organizational culture, as it will influence how to approach retrospectives. “ “Leading up to the retrospective, confirm the team’s understanding of the event’s purpose and the format that will be used.” “During the event, contextualize coaching to the team: ask questions, keep people focused, seek clarification and move the conversation toward possible solutions for the things that surface.” #### Share your actionable sprint retrospectives Have other tips to share on creating actionable sprint retrospectives? Share them with us below. You can also read the full [BuiltIn article](https://builtin.com/articles/sprint-retrospective) here for more in-depth tips and advice. --- # Tips to overcome recency bias in your retrospectives URL: https://www.teamretro.com/blog/tips-to-overcome-recency-bias-in-your-retrospectives/ Have you and your agile teams heard of the term recency bias? Even if you haven’t you might be experiencing it when you conduct your retrospectives without even realizing it. [Recency bias](https://en.wikipedia.org/wiki/List_of_cognitive_biases) is a psychological phenomenon where a person can remember something which has happened to them recently compared to the thing that has happened to them a while back. Here’s a little test to “experience” recency bias: try to recall the name of the ten or more people that you’ve met in the last week. You will easily tend to remember the names of the people that you’ve met recently compared to the ones you met a long time back, right? So what role does recency bias play in retrospectives? ### Your feedback is influenced by what happened recently! If during your sprint you experienced great things at the beginning but nearer the retro time things might have broken down a bit influencing your feedback. This can be detrimental to retros because then you might spend more time going through the “what went less well” rather than “what went well?” and “what do we want to try next?” OR If your recent experience was so good that you forget about everything else that you thought “this can be improved for next time,” you might not add anything in the “what went less well” column! ### A hotspot for BMWs Again, when you are focused on your most recent experience, it might result in the impulsiveness to do more [BMWs](/blog/how-to-manage-bmw-in-retrospectives/) rather than constructive feedback sessions. How can we mitigate recency bias? ### Make retros asynchronous One way to make sure we mitigate recency bias is to have a place where team members can add things that they want to suggest, bring up or discuss in retrospectives. Even better would be if it’s something that can be accessed easily while you’re working, be anonymous if you want it to be, and is recorded directly so that you can view it all in one space when it comes to your retro. In [TeamRetro](/) you can create asynchronous retrospectives by creating a retrospective or [using one of our templates](/retrospectives/) and then leave the brainstorming page open for team members to add notes whenever they want to during the sprint. ### Encourage sharing, anywhere and anytime! When you have your retro spot available and accessible for team members during any stage for a sprint, you’d need to remind them, remind them again and many more times to use the available retro board. You can do this via email, or your internal IM platform such as Slack. ### Avoid the open box! Much of the unconscious bias in retros stems from the “open box”. Retrospectives that lack structure and simply provide teams with a few open-ended questions and a large blank space to fill is breeding ground for recency bias. One way to add structure to your retro is to create a timeline-based retrospective that looks at getting feedback from the start, midway, and end of sprints. You can create this easily using the custom retro feature and here’s one we prepared earlier. ### Look at past retrospectives By looking at your past retrospective notes and action lists, you and your team can jog your memory on what happened last time and what’s important to follow up on. ### Use data to spot the bias When it comes to the very human problem of bias, analytics is useful! It can be easy to spot potential bias from the data, like when teams decide on an action from a previous retrospective as essential but in the current situation don’t even mention it as their recent experiences alter previous experiences. With TeamRetro, features such as voting to decide on priorities and actions that everyone has suggested and agreed upon can then be emailed or shared to [Trello](https://trello.com/), Jira, [MS Team](https://www.microsoft.com/en-au/microsoft-365/microsoft-teams/group-chat-software), [Slack](https://slack.com/) means that everyone can refresh and re-read before upcoming retros. ### Try TeamRetro today! Need to keep recency bias out of your retros? We’d be happy to help with our [30 days free trial](https://secure.teamretro.com/login/new?emailAddress=) and a [demo](https://secure.teamretro.com/demo/retrospectives/scrum-retrospective) on how our digital tool can help run retros in a coordinated and engaging way. --- # Top 5 tips for running effective icebreakers URL: https://www.teamretro.com/blog/top-5-tips-for-running-effective-icebreakers/ Effective icebreakers build safe, positive, collaborative spaces. Better yet, they enhance the productivity of all types of meetings, including retrospectives. On the flip side, a bad icebreaker can have the opposite effect. An ineffective icebreaker may make people feel excluded, anxious or frustrated. They may even reduce meeting productivity. So how do you make sure you’re getting the most out of your icebreaker activity? Here are our top five tips for running effective icebreakers. 1. Be prepared 2. Set the scene 3. Go first 4. Make sure everyone has a go 5. Keep it positive ## Be prepared A little preparation makes a big difference to the effectiveness of an icebreaker. Taking just a couple of minutes to get things in order before the meeting will deliver big returns. ### Choose a good icebreaker question Good icebreaker questions follow the [3E Rule](/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/). They are easy, enjoyable and explainable. They prompt people to share their stories so connections can be formed. Remember, if a question can be answered with a quick yes or no, it’s not a good icebreaker. The great thing about a good icebreaker question is that there are no right or wrong answers. They are inclusive, simple and fun. To help you get started, we’ve built a [free icebreaker games tool](https://games.teamretro.com/games) that can generate questions for you! You can even [browse icebreaker questions by category](/icebreakers/) if you wish to focus on a specific aspect of your team. Try a quick favorite like [Two Truths and a Lie](https://games.teamretro.com/games/two-truths-and-a-lie) or [This or That](https://games.teamretro.com/games/this-or-that) to get everyone talking. ### Allocate time to the icebreaker Allocating time for the icebreaker is important for two reasons. Firstly, it lets everyone know what they can expect when they step into the room. Secondly, it helps to manage the flow of the icebreaker activity itself. A timer has been included on the icebreaker widget. It helps you keep an eye on the time and you can refer to it if you need to move the conversation along. It also helps to make sure your retrospective starts on time. ### Grab a list Make sure you have a list of participants. It’s always helpful to know who you’re talking to. [](https://games.teamretro.com/) ## Set the scene Setting the scene means giving people an overview of the icebreaker before it starts. It will help things run smoothly. This can cover the mechanics of the icebreaker, for example how long it should take, as well as the benefits an icebreaker can deliver. This time can also help to reduce any anxiety in the room. People can ask any questions they may have and, importantly, this is a chance to remind people that there are no right or wrong answers. Setting the scene will only take a couple of minutes, but it helps to support the effectiveness of the icebreaker. ## Go first Going first is especially important if your team is new or if you have new people in the team. It lets you show people how to answer an icebreaker question. It also helps to set the tone of the activity (and the retrospective that will follow). People will follow your lead. There’s no need to worry who follows you. TeamRetro’s icebreaker widget can be used to nominate who goes next. ## Make sure everyone has a go This tip is linked to effective icebreakers being inclusive. Nothing makes someone feel less important than being overlooked. The significance of making sure everyone has had a chance to have a turn can’t be stressed enough. There are three quick ways you can confirm everyone has had a turn. First of all, the list of participants can be checked. The icebreaker widget can also help; each time someone answers the icebreaker question their name can be removed from the list of people still to answer. It’s also perfectly alright just to ask the group if everyone has had a turn. Bonus tip: Let people ‘pass’. If someone is clearly very nervous or simply can’t think of something, give them the option to ‘pass’. Everyone has good days and bad, and this is a chance to show empathy. ## Keep it positive A positive icebreaker is a gift that keeps on giving. People are naturally drawn to optimism. They want to connect with something that will make them feel good. Positivity is also contagious. When you connect with positive people it’s likely you will enjoy making that connection and view that connection in a good light. It will probably put you in a good mood! Keeping an icebreaker positive is fantastically simple. Thank people for their input. Listen to what they say and celebrate the diversity of input your icebreaker inspires. For more about icebreakers, you can also head over to our blog where we share [what makes the best icebreakers for teams](/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/) along with [quick but effective icebreakers to launch your next retrospective.](/blog/quick-but-effective-icebreakers-to-launch-your-next-retrospective/) --- # Top 7 habits of highly successful Scrum Masters and agile teams URL: https://www.teamretro.com/blog/top-7-habits-of-highly-successful-scrum-masters-and-agile-teams/ Sometimes, the simplest gestures carry the most profound insights. The heartfelt letter of appreciation from an Agile team to their Scrum Master shared above, illustrates the transformative impact a great Scrum Master can have. It’s these traits that create thriving teams, foster collaboration, and deliver continuous value. The role of a Scrum Master goes far beyond facilitating meetings and enforcing Agile practices. It’s about creating an environment where teams can thrive, adapt, and deliver value. Let’s dive into these key habits and explore how you can cultivate them to become an outstanding Scrum Master. ## Habit 1 – Honoring the agile principles The best Scrum Masters know that living Agile principles matters more than just following practices. Without a shared understanding of Agile principles, even the most meticulously executed practices can become hollow routines. Teams with a strong foundation in principles like collaboration, adaptability, and continuous improvement can consistently deliver value. **How to Foster Agile Principles:** - Revisit the Agile Manifesto to emphasize the “why” behind the work. - Leverage retrospectives to reflect on how principles are being upheld. - Align team goals with customer and organizational priorities. **Example in Action:** An Agile team struggling with prioritization shifted their approach after their Scrum Master facilitated a session on the principle of delivering value early and often by using the ping pong ball game, and refining the sprint planning process. The result? A more streamlined backlog and a noticeable improvement in stakeholder satisfaction. ## Habit 2 – Being a scrum “master of many hats” A Scrum Master wears multiple hats to meet the evolving needs of their team and organization. Understanding when to shift between these roles is critical to fostering a high-performing team. **Key Roles of a Scrum Master:** - **Servant Leader**: Supports team members and stakeholders to achieve common goals. - **Mentor**: Shares Agile expertise to upskill the team. - **Conflict Navigator**: Resolves tensions that hinder team collaboration. - **Coach**: Guides the team in embracing Agile mindsets and aligning behaviors. - **Facilitator**: Ensures productive collaboration during Scrum events. **Key practice:** Balance your involvement by observing when the team can self-organize versus when intervention is needed. Letting teams solve their own challenges fosters ownership and growth, but at the same time, there might be a need to step in to offer guidance. Some opportunities include: - Involve the team in setting up processes, such as scheduling Scrum events at times that suit everyone. - Assigning different people to be the Scrum Master so that you can be an observer and guide from the side. **Example in action:** A Scrum Master noticed that their team often waited for directives. By gradually delegating planning tasks and asking, “How would you solve this?” the team became more proactive and confident in their decision-making. ## Habit 3- Creating strong sprint rhythms and powerful retrospectives Successful teams rely on steady rhythms and structured retrospectives to maintain focus and adapt effectively. The retrospective should be a safe space for sharing, exploration and ideation that doesn’t become yet another whinging festival. **How to Build Rhythm and Improvement:** - Define the sprint cadence and ensure people adhere to it consistently. - Ensure clear roles and responsibilities, as well as sprint goals for each cycle. - Ensure Scrum events occur at consistent times, creating predictability for the team. - Experiment with new retrospective questions to keep the sessions engaging and productive. - Identify patterns in feedback to proactively prevent recurring challenges. **Example in action:** A Scrum Master established a 2-week sprint cycle for a mobile app team working on a user registration feature by ensuring clear planning, effective daily standups, and proactive issue resolution. During Sprint Planning, the team committed to realistic goals with a clear Definition of Done. Daily standups kept progress aligned, and mid-sprint, the SM resolved a testing delay after a blocker was identified at stand up. The sprint ended with a successful demo, incorporating stakeholder feedback for future improvements in the UI/UX. In the retrospective, the team identified actionable steps to optimize their workflow, creating a foundation for consistent, predictable delivery in future sprints. ## Habit 4 – Fostering a culture of continuous learning A successful Scrum Master and Agile team never stop learning. They understand that growth comes from reflecting on experiences, embracing feedback, and staying updated with industry trends. **Key Practices**: - **Regular Retrospectives**: Retrospectives, as mentioned earlier, are also crucial for continuous learning. - **Training and Certifications**: Invest in professional development for team members, such as Scrum certifications or specialized Agile courses. - **Knowledge Sharing**: Hold regular lunch-and-learn sessions or internal workshops to share new insights and skills. **Example in action**: A team at a mid-sized tech firm struggled with sprint velocity until their Scrum Master initiated a bi-weekly “tech talk.” These sessions boosted cross-functional learning, leading to noticeable improvements in team performance and morale, encouraging both individual and group learning. They would also check in on the effectiveness of the retrospective with a quick check-out question. If the score was 3 or less, instead of general feedback, they would ask retrospective questions like, ‘What small change could have made the retrospective more effective?’ to inspire actionable improvements. ## Habit 5 – Prioritizing outcomes over outputs Agile teams focus on delivering value rather than merely completing tasks. A successful Scrum Master steers the team toward outcome-based thinking, ensuring that every sprint delivers meaningful results, rather than ticking off tasks. **Key Practices**: - **Define Success Metrics**: Use key performance indicators (KPIs) such as customer satisfaction or time-to-market rather than task completion rates. - **Customer Feedback Loops**: Integrate customer feedback into sprint reviews to align deliverables with user needs. - **MVP Approach**: Prioritize developing a Minimum Viable Product (MVP) to validate ideas early. **Example in action**: An Agile team working on a mobile app avoided feature bloat (scope creep) by focusing on user feedback for each sprint. This ensured every release added measurable value to the product. ## Habit 6 – Empowering self-organizing teams Successful Agile teams take ownership of their work. They thrive in environments where they’re empowered to make decisions, experiment, and solve problems independently. Google’s research on high-performing teams highlights psychological safety as a critical factor. When team members feel safe to express themselves without fear of judgment, they innovate and collaborate more effectively. **Key Practices**: - **Delegation**: Allow teams to choose their sprint tasks and decide how to tackle them. - **Encourage Accountability**: Make team members responsible for achieving sprint goals while providing the necessary support. - **Create Psychological Safety**: Cultivate a culture where mistakes are seen as learning opportunities. **Example in action**: A Scrum Master noticed that their team often waited for directives. By gradually delegating planning tasks and asking, “How would you solve this?” the team became more proactive and confident in their decision-making. Every 2 months, they would also run a Team Health Check on psychological safety and discuss attitudes and behaviors based on the outcome that would help everyone in the team feel like they could participate. ## Habit 7 – Embracing adaptability and resilience The Agile manifesto emphasizes responding to change over following a plan. Successful Scrum Masters and teams embody this mindset by adapting to challenges without losing focus. **Key Practices**: - **Flexible Sprint Planning**: Adjust sprint goals based on changing priorities or unforeseen roadblocks. - **Risk Management**: Anticipate potential challenges and have contingency plans in place. - **Experimentation**: Use spikes to explore solutions to complex problems during sprints. **Example in action**: When a last-minute regulatory update required changes to an ongoing project, a resilient Agile team quickly re-prioritized their backlog. This adaptability prevented delays and ensured compliance. ## Your call to action: build your own success habits It’s clear that the best Scrum Masters and Agile teams don’t rely on luck or happenstance—they cultivate habits that drive continuous growth and collaboration. By embracing Agile principles, balancing diverse roles, empowering team ownership, and fostering a culture of improvement, you can unlock your team’s full potential. Now it’s your turn: Which of these habits will you cultivate next? Whether it’s improving your retrospectives or empowering team ownership, start small and grow from there. Need a starting point? Why not take this [self-assessment quiz](/scrum-master-self-assessment-quiz/) to identify your strengths and areas for growth. --- # Transitioning to native AWS services, December 2022 URL: https://www.teamretro.com/blog/transitioning-to-native-aws-services-december-2022/ ### Current state As you may be aware, TeamRetro is currently hosted on the Salesforce Heroku Platform-as-a-Service (PaaS), which in turn is hosted on Amazon Web Services (AWS) Infrastructure-as-a-Service (IaaS) in Amazon’s Northern Virginia (us-east-1) and Frankfurt (eu-central-1) data-centers. While the Heroku platform has served us well over the last few years, TeamRetro has reached a point where we’ve outgrown it and we are looking to set ourselves up for future growth and to improve our product services and security. ### Migrating to AWS native service We are planning to transition off Heroku to AWS-equivalent native service platforms (within the same data centers) in late December 2022. This migration will be transparent to you, although we hope you notice the improved performance and availability. As part of this migration: - **Heroku Server Dynos** will be replaced with **AWS ECS Fargate** services - **Heroku Postgres** will be migrated to **AWS RDS Aurora Postgres** clusters - **Heroku Redis** will be migrated to **AWS Elasticache** clusters To further reduce our data footprint we’ll be replacing a number of current third-party processors with their AWS equivalents. - **Sqreen (DataDog Inc.)** web application firewall will be replaced with **AWS Web Application Firewall** - **ImgIX (Zebrafish Labs Inc.)** asset resizing and CDN will be replaced with **AWS S3 + AWS CloudFront** ### Preparation Over the last two months we’ve been shaking and performance testing the new AWS environments in parallel to maintaining our existing Heroku environments. We have been working with our SOC2 auditors to ensure compliance is maintained during the transition phase. We’d like to thank our friends at Mechanical Rock Inc, Assurance Lab and Amazon Web Services for their assistance in the planning and implementation of this migration! ### Migration process Migration will be completed outside of business hours over a weekend, and will involve approximately 2 hours of planned downtime as data is transferred. Advance notice of this scheduled outage will be sent to account owners 48 hours prior to commencement. ### Questions If you have any questions – please let us know at [info@teamretro.com](mailto:info@groupmap.com) --- # Understanding team health data and next steps URL: https://www.teamretro.com/blog/understanding-team-health-data-and-what-to-do-next/ Running regular health checks sets the culture and tone for your team. It signals that you value and want to hear their voice about how they feel about their work. It is a valuable exercise that gives everyone insight into where problems might exist and to become the focus of the sprint retrospective. TeamRetro’s health check comes in either a radar or emoticon formats depending on how you like to collect and visualize data. ### So now you have the data – what do you do? This blog gives you a starting point to leverage the data you have generated to guide the conversation with the team. While we have used the extreme cases for illustration purposes, the same rules of engagement apply for an individual dimension. ### All signs point to green. - **Identify what might be the causes of success**– Lessons learned are not limited to just failure. Ask teams what is creating this success, recognize it, then feed the beast. - **Ask the question**– What would hinder or stop this success going forward? Identify the risks and potential issues that might come up in the future. - **Challenge the team** – What would happen if you extended the health check to product owners, scaled teams or leadership stakeholders? - **Change the dimensions** – If these areas seem to be working well over a period of time, experiment with changing one or two dimensions. - **Don’t rest on your laurels** – Just because you’ve worked out at the gym and the results have shown doesn’t mean you should neglect it. Continue to validate the status of the team even if all is does is allow you to celebrate successes. If over time your team’s health continues to hold true, this becomes a great communication story to share with others in your organization (We’d love to hear about this story too). ### There’s a lot of mellow yellow. - **Look for variation in responses** – ie. some people are very happy and others not (Use TeamRetro’s sort by mixed responses first to look at the dimensions that have the most mixed responses). Explore what might be causing the divide. - **Check for psychological safety** – If responses are all very neutral, it could be that people are too scared to speak the truth and have gone for something neutral. - **Look for opportunities to move the needle** – this is a perfect time to talk through what people think we need to do to shift the needle and to move us into the 5’s and in the greens. - **Check for understanding of health dimensions**. Clarify with the team that they know what the dimensions mean (or mean to them). Redefine or rescope the dimensions and try again to see if that makes a difference if need be. - **Watch out for [Unhealthy Peace](https://www.ted.com/talks/priya_parker_3_steps_to_turn_everyday_get_togethers_into_transformative_gatherings?language=en&fbclid=IwAR0Tzh4PBe040JW_umGDGN6-D9judZtmvFEPtkx4Hn6ttfw18p1dYbKPRP8)** – this basically means people are avoiding conflict which in its own right can be detrimental to the overall goals of the project. ### Oh dear the red is here. - **Call out the elephant in the room.** Find out what is causing the biggest issues and have team members air it out, straight away. If the culture isn’t quite there yet, then try using anonymity to help. Remind people it’s not about placing fault but looking for the way forward. - **Identify the root cause.** Use the 5 why technique to drill down into what might be causing the issue then ask the team to address the root cause. - **Use the circle and soups model** (or circles of influence to help address those issues). What can they individually change or control, what can they do as a team, and what is beyond their control. - **Look for quick wins if possible**. Run a retrospective such as the DAKI or the StarFish retrospective that focuses heavily on actions to take forward so that concerns can be quickly addressed. - **Talk to people. Be vulnerable**. With signs of bad health it can be cathartic (but also empowering) to be the first to shoulder the blame, take some responsibility or just open up to people to listen as to what is on their minds. ## Some final team health tips for scrum mastery TeamRetro lets you automatically re order the group’s responses by original order, most positive, most negative or most mixed responses first. Whichever order you choose, make sure you honor each dimension. Only focussing on negatives can make gatherings a glum, moody experience. Looking at the most mixed responses highlights the division in the room so giving each side an opportunity to share their perspective can give insight to others. Looking at data from one health check is certainly useful for short-term planning and focussing retrospective topics to get the biggest bang for buck. Long-term data shows progress and can be a great way to celebrate and acknowledge team effort and success. One last note. Data is important. Conversation with people is vital. Taking action and following through, however, is what causes the shift. Knowing which battles to fight as a scrum master, which need to be left to be self-directed by the team, and which requires the wisdom to accept and let go is part of the skill. Don’t stop listening and keep up the great work! Ready to discover your team’s health? --- # Beyond the surface: unearthing valuable metrics from retrospective and health checks URL: https://www.teamretro.com/blog/unearthing-valuable-metrics-from-retrospective-and-health-checks/ Welcome to the Insights feature of TeamRetro. [Insights](/enterprise/) brings metadata from your meetings to the surface. This will help identify trends and gaps, give you a sense of team mood, health and sentiment, and understand the rate of continuous improvements through action tracking. It does something that most other retrospective tools don’t. It shows you everything from the cadence of team meetings and the general themes, through to team happiness and sentiment over time. We really appreciate when our customers share their experiences, so we thought we would do the same. So rather than another blog article on how important agile retrospectives are, this post focuses on how we used the outcomes of our retros and health checks to help support our team. We share Insights into our own team and how it has helped us to improve. We hope it does the same for you. — Hi everyone, I hope all is traveling well. As promised, here’s a little run down on our own teams based on the new Insights feature we released. It’s always really informative to examine these things through our own lens as our customers do the same. ## Insights into our meeting activity Over the last year our 4 teams have run 27 retrospectives and 3 health checks, resulting in 102 action items and 29 team agreements. It’s great to see a bit of regularity happening as we improve our agile practice and meeting cadence. At each of our retros, we’ve had 13-47 ideas shared and anywhere from 0-6 actions that come out of those meetings, based on an 89% participation rate. For those who have been attending, we see a growing healthy Return on Time Invested which continues to remain steady. Well done to the teams and Scrum Masters for keeping our meetings relevant and meaningful for those attending. Generally, we run a retro once per month per team and a few times a year for everyone. Sometimes we bring them earlier before a weekend or to account for public holidays, and other times we have had to push them back. 1 team has really consistently met each month. We tend to have a wide spread of agile retrospective formats from meeting to meeting which means lots of variety and different perspectives being gathered. Our most frequently used template is the standard agile retrospective format, as well as the 4L retrospective. Of course, we continue to support teams trying out different formats and styles that work for you, while we keep our all hands meeting format very consistent each time to make it easier to compare. Based on the retrospectives, here is a word cloud of our most common themes across all our teams. Team, Working, project, Great, Thank, New, Feedback have been some positive sentiments over the last year. On the negative sentiment side, we are seeing things like Need, Agreements and Deadlines as some common ones which we have reflected on. -  -  -  Having said that, team sentiments are generally well spread and a relatively balanced approach when reflecting on sprints, although we tend to come from things from a more positive perspective. As a point of note, each of our retrospective formats has questions which have a negative sentiment in nature i.e- what did not go well, or what should we improve, or things that slowed us down. These are still necessary as part of our process so having negative sentiment is not actually an issue. Now to our team health. Since we only run these 3 times a year for all of us, we seem to have a relatively good participation rate and overall our team health dimensions are looking very strong. Looking at the individual health dimensions, it’s really great to see that we have been addressing some issues of communication. It looks like breaking down into smaller teams and having some clear guidelines about how, when and how much we communicate has been a worthwhile investment. I’m curious though. Does this mean that there are other areas that we should potentially be exploring (maybe a different type of health check)? Or should we simply talk about what we should do to keep these sorts of results positive going forward? More of those lunchtime competitions, hackathons or outcome based meetings perhaps? When it comes to actions, we’ve certainly been busy. Many of our actions from our September retrospective last year were big ticket and epic style actions which pushed our average days to completion to 77 days. But more recently, we are seeing a pretty good flow from actions created, through to actions published and completed. This means that our open action and action maturity is reasonably good. Finally, we have our team agreements. This is the “how we do what we do” part of the process. What was really interesting was how agreements were split up between teams. Using the filter, it looks like marketing focused on Feedback, use of Linear, managing project tasks and scope and becoming an agile marketing team. The Development team looked more like it was about knowing, sharing ideas, documentation and communicating ideas between people. Our ops team only had 1 team agreement so there was insufficient data for the word cloud. However our all hands meeting agreements still hold true for us today. Some of the agreements across all the teams that we thought were worth highlighting are : - We raise concerns with each other. - Work hard, have fun and recognize each other. - If someone is waiting on something from you, communicate where it is at. - 10%, 70%, 20% feedback rule - Any feedback is constructive, not an attack or disregarding an idea - If there is something you see that needs to be done, or something you’d like to do (or learn, or explore!) let the team know! In closing, we wanted to acknowledge the great work you are all doing. These retrospectives are a great way to see those continuous improvement ideas having a place to be shared and brought to life! --- # Why virtual icebreakers work for remote teams URL: https://www.teamretro.com/blog/virtual-icebreakers-for-remote-teams/ Icebreakers are simple activities held at the start of a meeting that can increase productivity and support team wellness. They help build small but powerful connections between people that nurture psychologically safe spaces. They are also a quick and easy way to help a team get to know each other. Best of all, icebreakers help to bring focus to a room and therefore increase the effectiveness of the meeting that follows. When it comes to remote teams, icebreakers offer even greater value. This is because they help address issues that can sometimes result from working online. They can make the online space feel more human. They can also counteract feelings of isolation. Here we take a look at [virtual icebreakers](/icebreakers/virtual-icebreakers/), and share those that have worked for our remote team. ## What is a virtual icebreaker? A virtual icebreaker is one that has been designed to be delivered in an online environment. Like all good icebreakers, they will follow the [3E Rule](/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/); that is, they are easy, enjoyable and explainable. Icebreakers that are delivered remotely can include more elements than those in a face to face setting. This is because virtual icebreakers can make the most of the technology that is being used to deliver the meeting. Virtual icebreakers can, for example, include – - virtual meeting backgrounds - digital images, emojis and GIFs - music and sound effects - video - messaging platforms and apps They can also tap into aspects of remote team members’ home environment. ## How can virtual icebreakers help remote teams? Virtual icebreakers give remote team members a chance to connect with each other they may otherwise not have. This is important because a feeling of connectedness is important for a team’s wellbeing. While their colocated counterparts have the opportunity to catch up in a coffee line or chat while walking together to their next meeting, the same cannot be said for remote team members. The great news is that icebreakers are an easy and effective way to offer similar such chances. The benefits don’t stop there. Icebreakers help to build supportive work environments. They encourage spaces in which people are happy to share. Icebreakers also help teams work better. In fact, there is [research](https://books.google.com.au/books?hl=en&lr=&id=4ITxDwAAQBAJ&oi=fnd&pg=PA293&dq=the+psychology+of+icebreakers&ots=ZiG6p1rp_w&sig=mziSScGDw1Qu-AWEP7BWktNtN8A#v=onepage&q=the%20psychology%20of%20icebreakers&f=false) pointing to icebreakers improving the efficiency of remote teams. Finally, icebreakers are fun. Not only do fun workplaces support team cohesion and learning, they retain team members for longer. ## Our top 20 icebreakers for remote teams Our top virtual icebreakers have been built with the benefits of remote work in mind. They leverage the variety of environments from which team members are working, the technology they have at their fingertips, and the shared experience of remote work. ### Quick shares As the name suggests, these icebreakers prompt remote team members to share something simple that is then explained. The chance to offer an explanation allows people to decide upon the level of insight they present to the team. 1. Share the last emoji you used; explain why you chose it. 2. Share a GIF that represents your current mood; what does it show about how you feel? 3. Share an image that represents what you will be doing in 10 years time. 4. Change your background to reflect an aspect of your personality; what does it show about you? 5. Play a sound grab that lifts your mood; why do you like it? ### Quick tours Our environment is a reflection of ourselves, and showing what’s around us offers insight into our world. These icebreakers are very effective in gaining focus as they tap into our natural curiosity to learn more about each other. 1. Show us what’s on your desk; what should and shouldn’t be there? 2. Show us around the room; why are you working from that spot? 3. Take us to your favorite spot; why do you like it? 4. Show us your view; what can you see? 5. What’s under your desk? ### Grab it These icebreakers are a bit like a scavenger hunt. Allow 30 seconds for team members to quickly grab the nominated item. These icebreakers give people the chance to move as well as share. To run this as a game, [Scavenger Sprint](https://games.teamretro.com/games/scavenger-sprint) does the timing and scoring for you, free in the browser. 1. Show us something you regret buying. 2. What is the most unusual kitchen utensil you have? 3. Grab something blue. 4. What do you own that has no purpose, and yet you still love it? 5. Introduce us to your pet (if you have one), or share a photo of a pet you wish you had. ### Celebrating our remote work experience There are quite a few advantages to working remotely and from home. Asking icebreaker questions that prompt people to identify those benefits are a great way of fostering connections while setting a positive tone for the meeting that will follow. 1. What does working remotely allow you to do that couldn’t happen if you were working face to face? 2. What do you do instead of commuting to and from work? 3. Be honest – how often do you work in your pajamas? 4. What have you learned about yourself by working remotely? 5. Describe your ideal remote work space. ## Want more? If you’re keen to get started but don’t know how, head over to our post on [how to run an icebreaker](/blog/how-to-run-an-icebreaker/). Ready to run your icebreaker? [Try our free online icebreaker games](https://games.teamretro.com/games) — including [Two Truths and a Lie](https://games.teamretro.com/games/two-truths-and-a-lie), a [guess-the-emoji game](https://games.teamretro.com/games/emoji-guess), and [Team Spectrum](/blog/team-spectrum-icebreaker-game/), built for [remote teams](https://games.teamretro.com/use-cases/remote-teams). Designed with agile teams in mind, you can pick a question, randomize who goes next and even keep an eye on the time! --- # Warm-up or icebreaker. Which one should you use? URL: https://www.teamretro.com/blog/warm-up-or-icebreaker-which-one-should-you-use/ If you’re working with a new team, or you have a new team member, use an icebreaker. If you’re working with an established team, it’s likely a warm-up will be more effective. When it comes to kicking off a meeting, icebreakers help connect people to each other, while warm-ups help connect people to the topic at hand. When deciding which one you should use, it all boils down to one simple question: how well do you know each other? So if it’s so simple, why are the two so often confused with each other? Well, this is because they have a number of things in common – - They are both great activities to kick off meetings. - They both help set the stage for productive, focussed sessions. - They both can help build a group’s energy. - They are both an opportunity to model supportive behavior. Importantly, both icebreakers and warm-ups can help build psychologically safe spaces. It’s no wonder they are often used by Scrum Masters to help kick off retrospectives. Now, having things in common doesn’t mean they are the same. In fact, understanding the differences between the two will help you deliver more effective meetings for your team. ## What is an icebreaker question and what makes it good? An icebreaker is a simple activity that helps connect people. They foster tiny, but important interactions that build rapport. [Research](https://research.com/careers/productivity-meeting-icebreakers) has confirmed that the connections icebreakers help build are valuable. They help lay the foundation for more effective meetings. They remove barriers that come from a lack of familiarity. They nurture psychological safety. The fewer such barriers, the greater the level of trust, safety and, therefore, productivity. Good icebreakers follow the [3E Rule](/blog/best-icebreakers-for-starting-conversations-with-online-teams-2021/), they are Easy, Enjoyable and Explainable. They give everyone in the room a chance to say something without the pressure of having to be right. Icebreakers are a chance to have fun. They do not have to be connected with the meeting at all. They can be creative, clever, silly or any combination of the three. The main thing is, they are inclusive so everyone in the group is invited to contribute and could easily respond. Icebreakers are the perfect activity to help people get to know each other. They are really valuable for people who’ve not worked together before. They are a great way to start retrospectives for new teams, or teams with new members. Icebreakers can be the difference between a good meeting and a great one. That’s why we’ve shared all sorts of examples of [Quick But Effective Icebreakers to Launch Your Next Retrospective.](/blog/quick-but-effective-icebreakers-to-launch-your-next-retrospective/) ## What is a warm-up and what makes it good? A warm-up is an activity that helps people focus on the task at hand. They help people direct their full attention to the topic of the meeting. They also help them to switch off from other thoughts and tasks. A warm up can be a co-operative task, a challenge or even a game. They can help build teamwork and camaraderie while focussing the group. They help people limber up before the meeting which leads to the session being faster, more focussed and efficient. Generally speaking, a warm-up is used for a team that already knows each other, and where good relationships exist between participants. Warm-ups tend to connect people to the meeting rather than with each other. Instead of finding common ground between participants by encouraging personal reflections, they aim to connect people to their common purpose at a shared moment in time. People could, for example, be asked what people think of the task. They could be asked what they need to stop thinking about in order to actively engage. Participants could simply be asked how they feel at that moment in time. A more creative example of a warm-up is Countdown. The aim of the activity is to count down from 20 with each person taking a turn to say one number out loud. No one is nominated to coordinate the order in which people speak. No one can speak at the same time (or the group starts again). This exercise requires everyone to pay attention to what’s happening in the room. They need to listen and carefully observe in order to deliver success. [](https://games.teamretro.com/) ## Run your own icebreaker now! Need help choosing the right ice-breaker? We’ve got you covered! Find the [best icebreaker questions for your next team meeting.](/icebreakers/icebreaker-questions-for-work/) Or jump straight into a [free online icebreaker game](https://games.teamretro.com/games) — try [This or That](https://games.teamretro.com/games/this-or-that) for a fast, low-effort warm-up. --- # We used TeamRetro’s health check as a mood meter and safety check — this is what we found. URL: https://www.teamretro.com/blog/we-used-teamretros-health-check-as-a-mood-meter-and-safety-check-this-is-what-we-found/ If you are anything like us, you value the happiness of the team of people you work with. Ensuring everyone can grow and feels supported is essential. Fostering a safe and fun environment is key to this. However, monitoring a team’s mood and safety levels can be a challenge. We recently held our annual work retreat. Our core team members from four countries come together to reflect, plan and get to know each other better. Understanding the sentiment of individual team members was vital. It helped us plan sessions to address concerns and explore areas of interest and opportunity. This post shares how we used the [Team Health Check,](/health-check-templates/team-health-check/) the data we captured and what that data meant to us. ## Using our health check as a mood meter We love our team. They are the people who help build, deliver and improve TeamRetro. A health check allows us to check in with them from time to time, and over time. It provides people the opportunity to share how they feel. It’s a quick survey that lets them easily indicate how happy they are across various health dimensions. As a Scrum Master or leader, it gives us insight into areas of concern that we want to address as a team. As a team, the data points allow people to get a sense of how everyone else is and what they can do to support as needed. We run our health checks every quarter. It means we get a quick pulse check of the team throughout the year. It’s also far less demanding than a daily or weekly mood check. Beyond just having a mood check, the TeamRetro health check also provides statistical insight into the data. Beyond the pretty graphs, it acts as an enabler for encouraging discussion. ## How we define team happiness and safety Every organization will define team happiness differently. For us, these dimensions cover a range of team dimensions that impact on the culture or mood of the team. In summary these are: - **Ownership** — How much ownership someone feels they have over their task or job. - **Value** — Whether or not someone feels they are delivering value that can be measured. - **Goal Alignment** — Whether their goals match those of the team and the wider company. - **Communication** — Whether conflict is minimal and communication is easy, open and smooth. - **Team Roles** — How well roles are defined and understood. - **Velocity** — The efficient delivery of agreed outputs at the right quality. - **Support and resources** — The level of support and resources available. - **Process** — Whether or not processes support or hinder workflow. - **Fun** — Whether there is engagement and fun. We ran our team health check asynchronously over two weeks, allowing people to input their responses (happy, neutral or sad emoticons) at any time. They could also provide specific comments if they wanted to. ## Keeping psychological safety in check One of the key considerations was safety. There were a few ways we did this. The first was to be open at meetings about the purpose of the surveys. We wanted the engagement to be high, but also honest. We made sure to let people know that they should indicate things that bother them and that it is okay. At the same time, we mentioned that we would not share comments but would follow up individually to address concerns. We also ran the check semi-anonymously in order to build a sense of safety, giving people space to say how they feel with far less pressure. This meant that their score was anonymous, but that we could follow up on their comments to ensure they were not ignored. Finally, the scores were discussed in aggregate and no one was pin-pointed. Unless they volunteered, there was no disclosure about individual responses, just that of the team. ## Evaluating team mood data We posted the survey on Slack, which we already integrated. Results were encouraged and reminded a few times and we had a 100% response rate. Here’s what came out on the radar. This radar shows the mean and range. While most of the scores were predominantly positive, the minimum range was still neutral in other dimensions, and negative in communications. This can also be seen if we overlay individual scores, the thicker lines represented where there were more of the same responses. E.g. Goal alignment through to process. The standard deviation showed that there was less deviation in process and ownership but that it was wider in communication and velocity. This suggests greater alignment in the responses around process through to team roles which gets wider as you go around the radar. The mode shows the most common response. So in other words, the vast majority of the team had positive responses and maybe just a few individuals may have issues that required personal attention. This is also reflected in the median (the middle score). While presenting statistical data can stimulate a lot of questions, discussion and deliberations, it is just as important to look at the trends over time. ## Looking at team mood and safety over time While a snapshot of a team’s health is valuable, so is looking at trends over time. Each column below represents a 6 monthly health check with the team. In essence, our overall team’s mood was upbeat and strong, but it was clear that communication, value and velocity had room for improvement. Or at least it did in this cycle. On a positive note, it was great to see that velocity and process issues previously addressed were sustaining, and that no one dimension had a high number of concerns. We previously dedicated a [Goldilocks Retrospective](/retrospective-templates/goldilocks-retrospective/) to our process flow to streamline everything from customer service to internal provisioning requests. Having said that, it was still important for us to look at the areas of communication, velocity and value. This ensures that they don’t slowly develop into issues later on down the track. Some insights did come through via comments, in addition to a good old fashioned chat. ## The follow-up actions Here’s what we did based on what we saw: - We looked at specific comments and reached out to the individuals who shared their thoughts. We invited them to discuss and share solutions and to alleviate concerns. Some of this was very simple and easily fixed. Others just said they were having a bad day. Finally, others required further process changes. - We shared the results with the team. Velocity, value and communication is not just down to management, or just the team but with everyone. Sharing the results openly and honestly was done to create visibility around the problem and having people think about what they can do to help improve the situation. - We played some [agile games](/blog/the-best-agile-games-for-building-teams-learning-and-creativity/) . Specifically, these were the Agile Ball Point Game and Agile chocolate game. These games were designed to create a safe space where the team could experiment with ideas in a time-boxed way. Special thanks to [Alexandrina Danifeld](https://www.linkedin.com/in/alexandrinadanifeld/), for facilitating one of our sessions. - We made changes to our kanban. For example, addressing value and velocity through a co-designed kanban workflow. By agreeing on process and deliverables, this helped to improve the smoothness and speed of output. ## Final thoughts on team mood and safety checks Our modus operandi aims to have a happy and productive workforce. One certainly feeds into another. Running surveys and health checks can be confronting, especially when results are not perfect. However, without these [data points](/blog/understanding-team-health-data-and-what-to-do-next/) generated from a culture of safety, there is little opportunity for improvement. Would we do another health check in the future? Absolutely. The only thing we would change is to ask people to suggest improvements, and why they feel a certain way. At a whole group level, we’d certainly like to understand what made people give positive feedback and responses. Knowing what elements make people happy means that we can repeat, replicate and reward going forward. How do you gauge the health of your team’s mood and safety? What questions would you have asked, or what actions would you have taken? We would love to hear your thoughts or questions. Reach out to us at [info@teamretro.com](mailto:info@teamretro.com) --- # We’ve made choosing the right retrospective format for your agile team easy URL: https://www.teamretro.com/blog/weve-made-choosing-the-right-retrospective-format-for-your-agile-team-easy/ We all know we’re meant to use the right tool for the job. We all know it can make the difference between getting the job ‘done’, and getting the job ‘done right’. Most of all, we all know just how easy it is to ignore this pearl of wisdom. For some reason, we’ll find ourselves doing something like reaching for a knife to open a can. Sure, we may get the job done, but when we use the wrong tool we may end up breaking the tool, damaging the goods or even ourselves. The same can be said of retrospective templates. Using the right retrospective template will help you deliver the outcomes you hope to achieve more effectively. Using the wrong template may – - undermine its effectiveness - cost the team valuable time, or even - negatively impact the engagement of the team The great news is, we’ve made it much easier for you to pick the right template for your next retrospective meeting! The templates are all remote friendly for distributed teams and just as useful for face-to-face sprint retrospective meetings. They can help focus your team on the product, the process, and they can even help make the meeting fun. ## How have we made choosing retrospective templates easy? The short answer is we’ve built a [widget](/retrospective-templates/) that overcomes the main barrier to making that choice; finding time. When it comes to choosing a retrospective format, a lack of time can often mean you don’t explore the other templates and the benefits they deliver. Instead, you stick with the same format or the one that is most familiar. This means that your team doesn’t get to benefit from the value changing retrospective templates can bring. Even worse, it could actually be helping antipatterns to take hold. This includes meeting fatigue, repetition and boredom, or asking the wrong questions. The widget helps you to quickly hone in on the template most likely to help your team. It has been designed to align the focus, context or behavior you wish to address to the best template for the job. It offers a quick summary of the template, along with the dimensions it includes. Of course, you can test drive that template with our team of friendly bots, and get more detail on it and how we’ve used it in the past. ## How have we sorted the retrospective templates? We have categorized each of the templates based on their purposes and intended outcomes. While a retrospective does not have to be solely focussed on just one aspect, each has a major theme it will support. Here’s the rundown. ### Check-ins As well as supporting the retrospective itself, these can also be used to bring the team into the meeting headspace. They can help warm up the team, help to build rapport, and they can make sure everyone’s focus is on the meeting at hand. It’s easy to get distracted by emails and other work items, so a check-in that uses an easy, round robin style of questions helps people focus on the retrospective. They tend to be simple questions that have no right or wrong answer, so they build safety by giving each person a chance to chime in. ### New to retros These are designed for a Scrum Master who may be new to Agile, or for a team who are just starting to dip their toes into the Agile water. They are tried and true formats that have become industry standards, and offer a solid array of questions to help the team learn and grow. ### Team building Have a new team? Maybe just a new team member? These team building retrospectives aim to help people work more collaboratively on a particular issue or theme. They can help to create [social contracts](/blog/create-social-contracts-with-team-agreements-that-improve-culture/). They can help grow understanding as to how each person works, thinks, and solves problems. There are no high rope courses here. Instead, it’s a discovery of the way your team members think and how they might work together. ### Product management These retrospectives templates help the team focus on the elements that will deliver the best possible product. They include dimensions that keep sprint and product goals in mind based on feedback from product owners, data and overall user stories. They look at the features of the product. They also look at how the team coordinates and is supported while delivering their goals. ### Process These templates focus on how a team works. They examine the environment in which they work and the stage they find themselves in the development life cycle. The goals of the templates might be to remove impediments, increase productivity and throughput, or simply to ensure that the team has a shared understanding of the process. Whether it’s continuous delivery or paired work, the process focus means that you can more easily examine what the team needs by way of support. ### Futurespectives These templates support the delivery of [futurespectives](/blog/everything-you-need-to-know-about-futurespectives/). While it is generally known that retrospectives are based on the last sprint cycle, a futurespective takes a different tack. They help teams shape a high-level strategy that supports the smooth delivery of their goal. They do this by having a team draw on their past experiences to shape a shared vision that will guide them forward. ### Fun and novel Is your team suffering from meeting fatigue? Can you sense their disengagement? Is there a chorus of groans when it comes to your retros? These fun and novel agile retrospective formats encourage people to think differently by offering them a fresh perspective. They bring smiles, energy and vibrancy to the meeting. Warning: It may lead to laughter or a wild idea that just might work! ### Deep dives These are the agile formats to use when it’s time to get deep and meaningful. The questions here help you delve further into a topic. The conversations themselves may be more intrinsic or personal in nature. Some of them require a little soul searching while others may require an analytical approach to solving a problem or issue. ## How to find a retrospective template for your next agile meeting Finding the right template can be done in three easy steps. 1. Head over to our [widget](/retrospective-templates/). 2. Pick the category that applies to your theme or purpose. 3. Choose the retrospective template you want, and start brainstorming. Want to know more about choosing a retrospective template? Check out [Chapter 8](/guides/scrum-masters-retrospective-guide/retrospective-templates/) of our [Scrum Master’s Retrospective Guide](/guides/scrum-masters-retrospective-guide/). In it, we offer more detail on how a team’s focus, context and behavior can shape the template you choose, as well as sharing some of our favorite templates. Do you have another idea for a retrospective format? We’d love to hear about it and to add it to our community library of templates. [Get in touch.](/contact-us/) --- # What is a Scrum Master and why is their role so important in a retrospective? URL: https://www.teamretro.com/blog/what-is-a-scrum-master-and-why-is-their-role-so-important-in-a-retrospective/ Retrospectives play a vital part in Agile; the opportunity they provide for a team to adapt and improve is core to the delivery of value through continuous improvement. The [Scrum Guide](https://scrumguides.org/scrum-guide.html) states that the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. “The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved. The Scrum Team identifies the most helpful changes to improve its effectiveness.” Given the critical nature of the retrospective, it seems eminently sensible to allocate resources to ensure its effectiveness is maximized. Enter the Scrum Master. ## What is a Scrum Master? When it comes to building agile teams that deliver value using the Scrum framework, a Scrum Master is fundamental to the mix. They act as a servant leader as well as an influencer and change agent, facilitating meetings and removing obstacles to help the team succeed. They serve as a bridge between product management and development. Along with the Product Owner, the Scrum Master is a member of the leadership group, and is generally responsible for creating an environment in which their team operates. From planning to retrospectives, the Scrum Master facilitates the sprint. They guide, coach and lead the team, keeping them on-track and focused, while managing the process, culture and overall vibe of the team. ## The Scrum Master’s responsibilities So what does a Scrum Master actually do? In broad terms, the Scrum Master – - Sets up and facilitates agile meetings - Coaches and encourages the Scrum principles and values - Solves logistical and meta problems - Supports the team and addresses team dynamics - Works as an interface between the team and the product owners as well as others outside the team - Protects the team from outside interruptions and distractions - Reports on team progress Besides the retrospective, they also facilitate daily stand ups, sprint planning meetings, sprint reviews and team member 1 on 1’s. A great Scrum Master should be just as comfortable discussing the team’s priorities and processes with senior management as they are ordering the team pizza for a tough final push. ## How does a Scrum Master differ from a Product Owner? The Scrum Master can be thought of as an intermediary. They can insulate the team from minor changes, revisions or confusion that could derail the sprint. What this means is that the purview of the Product Owner is external to the organization (product value, the market, customers and the competition); that of the Scrum Master is internal. Additionally, with the Scrum Master’s focus on enabling the Team to *do* work, the Product Owner may better focus on the big picture—rather than the day-to-day. Ultimately, the Product Owner has the final say over the product direction and strategy but will work closely to manage the backlog, understand the trade off and to find ways to deliver value. ## Does every team need a Scrum Master? When it really boils down to it, Scrum isn’t possible without the Scrum Master. Without one, you are doing something like a watered down version, often called scrum-but. They foster the required environment and serve as a buffer between the team and the rest of the organization. At its core, Scrum works well because of the clear focus it gives to each member of the team; without the Scrum Master, that focus is compromised. With that said, it *is* possible for a Scrum Team to be self organizing once things are rolling. This is also one of the goals of a scrum master. With the initial foundations laid and appropriate environment created, the team can get by without a Scrum Master if absolutely necessary. Some teams also rotate the Scrum Master role within their team, or have access to a community of practice (group of Scrum Masters), external consultants or independent agile consultants. ## Does the Scrum Master actually do the work? Generally speaking—no. Unless you are in a small team where one person simply acts as Scrum Master for the team, the actual development and tasks fall under the mandate of the agile scrum team. They don’t and should not interfere with the technical issues of the team. The Scrum Master on the other hand helps to solve problems and provide assistance, guidance and seek clarification as needed. If the sprint is progressing smoothly, they should never *need* to do work. The role of the Scrum Master is to help every member of their team realize some serious gains by ensuring they are free to focus on what they do best. Strategy is left with the Product Managers, writing the best code is left to the developers and Jason from sales can focus on getting those leads! ## What is the Scrum Master’s role in the sprint retrospective? ### Facilitate and moderate agile meetings There’s a reason orchestras have conductors; they ensure each group of musicians play in such a way so as to deliver a harmonious performance. Similarly, the Scrum Master conducts the retrospective to ensure it stays on track, remains unbiased, free of groupthink and is a psychologically safe space. Scrum Masters ensure the meeting is organized from choosing a [retrospective template](/retrospectives/) based on a theme or area of focus, ensure cadence and also run the meeting to ensure that the team stays focused. They move the team through the processes of brainstorming, prioritizing key discussions items, then generating actions for continuous improvement that are followed through. This ranges from hosting the daily stand up meetings all the way through to the sprint retrospective. ### Encourage transparency and honest communication For a [Sprint Retrospective](/retrospective-templates/sprint-retrospective/) meeting to work well, there needs to be open, unbiased and clear communication and feedback. The Scrum Master ensures this happens, and makes sure all voices are heard equally. Meetings are often prone to groupthink and bias, and a Scrum context doesn’t magically solve this. The entire Scrum Team needs to be aware of this potential, with the Scrum Master actively supporting them so they deliver honest, critical feedback for the benefit of the team. It’s common for people to have different opinions. When those opinions clash, it’s the Scrum Master’s responsibility to ensure both sides are heard, issues are resolved and the meeting continues. This can be a complex, delicate task and one with which the Scrum Master needs to be highly adept. ### Coach team members For organizations that are new to Scrum, a key part of the role is to ensure that team members understand and employ Agile processes on a day to day basis. They help to create self-managed teams and to promote a sense of ownership and utility. This could be mentoring new team members to teach them about the Scrum Values and principles and how to integrate this into their daily practice. ### Document, capture and follow through on actions Appropriately documenting the retrospective ensures – - feedback, issues, and action items are captured and tracked - notes are available for those unable to attend the retrospective - notes can be referenced throughout the sprint to ensure shared understanding - memory does not distort facts Ensuring accountability could be a follow up after the meeting or going through the list from previous meetings at the start of the retrospective. Helping remove impediments during the sprint will help the team be more successful when it comes time to reflect at the retro. ### Keep time Timeboxing is widely acknowledged to be an effective technique to increase productivity. With the big picture in view, tasks are prioritized, in order to make the most out of the time allotted to them. The retrospective is the perfect opportunity for the Scrum Master to model timeboxing; not only is it important to lead by example, it ensures time isn’t wasted and team members remain engaged with the task at hand. A useful end of meeting evaluation is the [Return on Time Invested or ‘ROTI’](/blog/return-on-time-invested/) available in all of TeamRetro’s templates. In under a minute, you can quickly gather whether or not there was value gained by the team in the meeting. ### Act as the intermediary with the rest of the organization Outside of the retrospective, the Scrum Master can report on actions that the team has generated and can bring ideas and suggestions to the relevant stakeholders. They may create visuals such as Scrum Boards to communicate progress, or simply share feedback from the Team Health Checks to highlight potential blockages for the team. They work with others to ensure that the team members are not in too many unimportant meetings and work with product owners and other stakeholders to redistribute the workload. Ultimately their goal is to remove distractions and blockages in order to help the team focus. ## In summary An effective Scrum Master can significantly enhance the value delivered by a retrospective. By employing strong facilitation skills, acting as the intermediary between the product owner and the development team, and focusing on the processes, environment and culture of the team, the scrum master can set the team up for success. The value they bring to the organization through outcomes, continuous improvement and helping to create self organizing teams is just some of the reasons why Scrum Masters are such a valued team member. Using an [online retrospective tool such as TeamRetro](/retrospectives/) allows the Scrum Master to focus on the needs of the team rather than the mechanics of the retrospective. Ideas and comments can be captured instantly and prioritized for discussions. Actions can be tracked, shared or integrated and followed up at the next meeting. Each person in the team has an equal opportunity to contribute in a psychologically safe space and can be time boxed to ensure everyone stays on task. --- # What is an agile team health check and why are they important? URL: https://www.teamretro.com/blog/what-is-an-agile-team-health-check-and-why-are-they-important/ A team health check is a simple tool that helps you measure and track team health and happiness over time; the data they capture can inform actions that drive continuous improvement. Team health relates to the factors that contribute to team success. There’s been considerable effort dedicated to defining those factors thereby paving the way to enhancing them. [Google’s research](https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/?utm_source=google&utm_medium=cpc&utm_campaign=team-health-checks&utm_content=agile-health-check&utm_term=team%20health%20check&gclid=CjwKCAjw-sqKBhBjEiwAVaQ9ayhjwYxHbWSTo4NAHiLYFt5PozZy_j4R8p6qpdiK1bn5fNAxU45gXBoCo2gQAvD_BwE), cites five factors that are pivotal to team success. Spotify’s work in this space informed their [Squad Health Check](/health-checks/). Having evolved over time, the 11 dimensions of their check reflect the factors they perceive as key to team health. The great thing is, you don’t have to launch a research program to measure and nurture your team’s health. Agile team health checks are exceptionally valuable mechanisms for two key reasons – - The information they capture can help inform data-driven actions designed to improve team health. - The effectiveness of those actions can be tracked over time. TeamRetro *offers a number of health check models from which you can choose. Each model has different question sets that can be tailored to suit the needs of your team. TeamRetro also lets you create your own team health check model to help ensure the individual needs of your team are met.* ### Why is team health important? A healthy, happy team can benefit – - Employers - Employees - An employee’s family We know our health is important. We know our health relates not only to our physical selves and what we can do, but also our emotional selves and how we feel. We know if we feel good, we can do more. Well, the same can be said of team health. The health of the team is a culmination of the quality of their communication, culture and camaraderie which then impacts upon productivity, velocity, and ease of collaboration when it comes to hitting team goals. Taking some time to understand and measure the health of your team can therefore lead to insights regarding what might be impacting their systems and what drives continuous improvement. TeamRetro *quickly and meaningfully collates health check data to help you identify areas of improvement and strength. This spider chart, for example, offers an easy-to-understand snapshot of responses to a health check, that can be used to support data-driven conversations with your team.* ### Team health is important to employers Healthy teams are happy teams. Much has been written regarding the direct link between team happiness and productivity; pointing to the fact that the happier the team, the more productive they are. The way a team feels can strongly influence what that team can do; this is particularly relevant for the organization that has employed that team. The organizational benefits don’t stop there! - Healthy teams are resilient - Healthy teams are innovative - Healthy teams contribute to a healthy workplace culture What, there’s more – the great news is organizations aren’t the only ones to benefit from healthy teams. ### Team health is important to employees Members of healthy teams benefit from their positive team traits. Members of healthy teams are more likely to – - Be supportive of each other - Trust each other - Embrace opportunities to learn - Have an optimistic outlook - Have fun at work Just like pot plants that thrive in the right conditions, if we are part of a healthy team, we are more likely to thrive. Additionally, people who demonstrate the above-mentioned characteristics are more likely to attract others with similarly positive traits. The positive momentum of healthy teams keeps going! TeamRetro *is here to support you as you help your team in their pursuit of continuous improvement. Features such as our heat maps (above) are designed to reflect your team’s health over time. We focus on tracking your team’s health data so you can focus on your team.* ### Team health is important to the families of employees The benefits of healthy teams extend beyond the workplace. The pay check you take home isn’t the only thing that can make a difference to your family. The ripples of the experiences that you had at work can also have an impact. Kansas State University’s [research](https://www.sciencedaily.com/releases/2009/08/090824115911.htm) found that people who have positive experiences at work, carry that positivity over to their home life. If you are a member of a healthy happy team, it’s likely some of that health and happiness will go home with you! ## How can you improve your team’s health? The first step to improving team health is to measure it, and TeamRetro has made it easy for you to do just that. ### Decide on your dimensions It’s important to determine what matters most to you and your team (within your context), as this will inform the dimensions you choose to use in your health check. A great way to define these dimensions is to speak with key stakeholders – this includes your team. TeamRetro offers a range of models with preloaded dimensions to get you started. From Remote Team Happiness, Spotify or Atlassian Models, through to the Scrum Values health check, you can use these models as they are or edit them to suit your team’s needs. TeamRetro lets you apply your dimensions to build your own health check models. You can, in fact, create multiple models and set a default model. Most importantly, TeamRetro helps you track your team’s response to those dimensions over a period of time thereby capturing the evolution of your team’s health. ### Create a cadence You could set a health check schedule that could range from daily through to annually but it’s important to set some sort of regular cadence that informs how you want people to respond and share. Keep in mind that faster, shorter health checks will let you see trends and validate team health in a more timely and relevant way. You can run your health checks synchronously or asynchronously. If you choose to facilitate asynchronous checks, it’s a good rule of thumb to ensure – - That the health dimensions are understood - You have set the tone for how you want people to respond to health checks - What happens with the data is known and understood Making team health checks a regular occurrence and with the right message, helps build trust and psychological safety, thereby creating a space in which – - Feedback is embraced as constructive rather than perceived as a criticism - Issues are identified and quickly addressed - The positive relationships between team members are reinforced - Conversations are open, honest and supportive ### Measure and manage The last step is all about connecting your team and transparency is key. 1. Share the results of that first health check with your team. 2. Acknowledge and celebrate successes. 3. Explore any issues the health check may have identified. 4. Ask your team for their input as to how team health could be improved. 5. If relevant, use the artifacts of your health checks as the theme for your next retrospective. 6. Capture actions or team agreements that the team would like to take going forward. For more help, check out our 5 handy hints for running team health checks. If you think it’s valuable to explore the health and happiness of your teams, test-drive our health checks with our team of friendly bots. [Try Health Check Live Demo](https://secure.teamretro.com/demo/health-checks) Happy health checking! TeamRetro --- # Which of the scrum values is most demonstrated by your team? URL: https://www.teamretro.com/blog/which-of-the-scrum-values-is-most-demonstrated-by-your-team/ Scrum Values are the **“how we work together”** side of agility. When they show up as day-to-day behaviors, teams deliver more consistently and learn faster. The challenge then? How do we get each person in a team to demonstrate more of the Scrum Values and create more happiness, productivity and common ground in our daily interactions. In this post, we explore how we can get team members to reflect on the values, pick one value to strengthen and plan an action item. ## What makes scrum values essential for agile teams? The Scrum Values of **Commitment**, **Focus**, **Openness**, **Respect** and **Courage** keep teams aligned when work becomes complicated. They guide how teams work under pressure, how conflicts are resolved, and how goals are achieved. When lived daily, they reduce friction, surface blockers earlier, and make tough conversations easier. Think it’s a little corny to talk about values? Imagine the opposite. What would it be like working with an uncommitted, directionless, siloed, rude and avoidant team? Nobody speaks up. You can’t rely on others and soon you lose direction and your own drive. Moving teams from paper based values to lived practice therefore remains a goal for Scrum Masters, Agile Coaches and Agile Teams. ## The five scrum values in practice So what do the values look like in practice? ### 1. Commitment **“*The Scrum Team commits to achieving its goals and to supporting each other*.”** What does it look like? Keeping promises every sprint. E.g. Aligning around a one-sentence sprint goal and adapting together when things slip. ### 2. Focus **“*The primary focus is on the work of the sprint to make the best possible progress toward these goals*.”** What does it look like? Protecting what matters most. E.g. Prioritizing work and reducing noise so the sprint goal stays on track and the product backlog is managed and groomed. ### 3. Openness **“*The Scrum Team and its stakeholders are open about the work and the challenges*.”** What does it look like? Sharing early and often. E.g. Being transparent about progress, challenges, and blockers at daily standups. ### 4. Respect **“*Scrum Team members respect each other to be capable, independent people, and are respected as such by the people with whom they work.*”** What does it look like? Valuing others. E.g. Respecting teams to self manage and to determine how they do the work to achieve the Sprint Goal and following the prime directive. ### 5. Courage ***“The Scrum Team members have the courage to do the right thing, to work on tough problems.”*** What does it look like? Speaking up for the Sprint Goal. E.g. Raising issues early, challenging scope creep and pushing back to stay aligned. ## Scrum values health check Getting a picture of where your team measures up is the next step in moving forward. A **[Scrum Values health check](/health-check-templates/)** in TeamRetro makes them visible, measurable, and actionable. It’s a quick pulse check that can provide some quick data points, independent /anonymous commenting and a way to get new ideas from the team, or from context driven AI that can suggest some actions based on the results. It provides an easy way to identify low hanging fruit, lowest individual and team scores and to then discuss ways to address some of those issues individually or as a team. These can all be done in a psychologically safe way, yet reflect how individual perceptions and responses contribute to the team as a whole. Seeing the spread of responses in this case is just as insightful as aggregated scores. ## Turning data into action Here’s a quick cheat sheet on some generic action improvements for each value. However, we suggest that you use actual scores and feedback from your team and their survey responses to come up with actions, team agreements and takeaways that are valuable to you. Using TeamRetro’s AI feature, you can get more context driven action suggestions for your team to discuss. | **Value** | **Action Improvements** | | :-- | :-- | | **Commitment** | - Keep the Sprint Goal visible on the board and review progress daily. - Each team member states their commitment to their tasks during sprint planning. - Log an action for mid-sprint check-ins to ensure alignment with the Sprint Goal. - Rotate a **“goal champion”** role to remind the team of the goal. - Capture learnings about missed commitments and agree on process adjustments. | | **Focus** | - Set and maintain a team WIP limit, revisiting its impact in the next retro. - Block out **“focus time”** slots on the shared calendar. - Limit unplanned work by requiring explicit trade-off discussions. - Agree on clear daily priorities (e.g. top 3 tasks to unblock first). - Use sprint board filters to highlight items closest to completion. | | **Openness** | - Log blockers as retro items with owners for follow-up. - Introduce regular **“demo-in-progress”** sessions for transparency. - Add uncertainties as backlog refinement items. - Rotate facilitation so all members lead discussions at least once. - Document key decisions in a shared space (wiki, board). | | **Respect** | - Enable anonymous input or round-robin speaking to ensure all voices are heard. - Give and receive constructive feedback using a structured framework. - Actively acknowledge contributions during daily stand-ups. - Enforce a **“no-interruptions”** rule in meetings. - Celebrate small wins or improvements at the end of each sprint. | | **Courage** | - Challenge scope creep by requiring team agreement before adding work mid-sprint. - Create a visible risk register with owners and due dates. - Use **“spike”** tasks to explore unknowns rather than deferring them. - Raise impediments early, even if solutions are unclear. - Review failed experiments in retrospectives as learning opportunities. | At the end of the health check, ask each team member to identify which one they’d most like to strengthen. This creates personal ownership without overwhelming people. Have them come up with one action that they can commit to and share with the team. By combining TeamRetro’s Scrum Values health check with practical team behaviors, those values shift from abstract ideals into measurable habits that drive continuous improvement. Whether you run it once just to get a baseline and to create a set of team agreements, or something that you want to monitor and track as your team changes or evolves, coming up with a list of agreed behaviors sets the vibe for your team. ## From scrum values into scrum habits If you are running your health check in TeamRetro, you can capture, track and keep account of the action items and team agreements from your team. You can then refer to these at the next retrospective or health check. It’s a good reminder, improves accountability and can continue to motivate good habits with the team. You could integrate this into your one on one discussions, pop it onto a poster on the office wall, or run it as part of your retrospectives to keep it on everyone’s radar. For example, at the end of your retrospective or icebreaker question, you could ask ***“How did you demonstrate one of the Scrum Values this sprint? How did it help us?”*** This reinforces progress and normalizes experimentation. You could even take this further by running a **[Scrum Values retrospective](/retrospective-templates/scrum-values/)**. Finally, don’t forget to acknowledge and celebrate small wins. Highlight when values do show up in practice. Use the kudos feature in TeamRetro to **[give team members a shout out](/blog/giving-kudos-with-kudo-cards-in-retrospectives/)** when they have demonstrated one of the Scrum Values. It’s not just a warm cozy feeling you give, it’s a way to build resilience and examples of how values appear in your team. Scrum Values aren’t just posters on the wall—they are the daily habits that make teams resilient, aligned, and effective. By reflecting on the values, choosing one to strengthen, turning it into a micro-behavior, checking in on progress, and celebrating wins, teams create the conditions for trust, learning, and sustainable delivery. Small, consistent actions compound into big cultural shifts. 👉 Ready to see where your team stands? Run a **[Scrum Values health check](/health-check-templates/)** in TeamRetro to get a baseline, spark meaningful discussions, and capture practical action items that turn values into habits. --- # The power of regular retrospective meetings in agile teams URL: https://www.teamretro.com/case-studies/alchemer/ It’s always appreciated when we get feedback from our clients; it’s their input that helps guide us as we learn, grow and evolve TeamRetro. Their stories are why we do what we do. That’s why we are delighted to share with you this piece written by [Mel Fox](https://www.linkedin.com/in/mel-fox-01587323/), Digital Product Manager, entrepreneur and TeamRetro user. She shares tips and tricks she uses with her team when conducting retrospective meetings that are engaging and productive. ## Impactful retrospectives In the fast-paced world of agile development, it’s crucial for teams to continuously improve their processes, communication, and overall performance. One of the most effective ways to achieve this is through regular and productive retrospective meetings. These gatherings provide a chance for the team to reflect on their work, celebrate successes, address challenges, and make actionable improvements. Unfortunately, some teams find themselves dreading their post-Sprint retrospective and are trapped in a cycle of creating stale bullet points without ever revisiting them. As someone who takes pride in running and managing impactful retrospectives, I wanted to highlight the importance of hosting impactful retrospectives, emphasizing the significance of tools like TeamRetro that enable intentional and effective retrospective sessions. ## Create a safe space for emotions with your retrospective While it’s no secret that engineers are highly analytical and logical individuals, it’s essential to acknowledge that they also have emotions. A productive retrospective encourages team members to express their feelings openly and honestly. By providing a safe space for emotional discussions, teams can address any frustrations, concerns, or conflicts that may be hindering their progress. Recognizing and validating these emotions fosters empathy, understanding, and a stronger team bond. ## Establish actionable insights and ownership A successful retrospective not only provides a platform for open dialogue but also results in tangible outcomes. By identifying and discussing areas for improvement, teams can generate actionable insights. These insights can then be translated into concrete action items that are assigned to relevant stakeholders on the team. As a Product Manager, I put a lot of the action items on my shoulders, but there is just as much accountability for the Engineering Manager and team leads, as well. This clear assignment of responsibilities ensures that the team’s concerns are heard and acted upon, driving real change and continuous growth. > #### Quick Tip! > > #### At the beginning of each retrospective, address the open action items from the last retro — what was done, what still needs to be addressed, and what could have been done differently. Oh, and guess what, you can add those items right into your current retrospective. > > #### Boom! ## Select the right tool for your retrospective meetings To maximize the effectiveness of retrospective meetings, leveraging appropriate tools can be immensely valuable. TeamRetro, in particular, is a powerful tool designed to enhance the retrospective experience. With its user-friendly interface and comprehensive features, TeamRetro enables teams to conduct intentional and productive retrospective sessions. Here are some key aspects of TeamRetro: ### Customizable templates TeamRetro offers a wide range of pre-designed [retrospective templates](/retrospective-templates/) tailored to different goals and objectives. These templates provide a structured framework for discussions and help teams focus on specific areas such as process improvement, team dynamics, or individual growth. I, personally, enjoy selecting a different template for each meeting to spice things up a bit. ### Collaboration and remote accessibility In today’s distributed work environments, TeamRetro facilitates collaboration regardless of team members’ physical locations. The tool allows participants to contribute their ideas and feedback asynchronously, ensuring that all voices are heard and considered. ### Action item tracking TeamRetro streamlines the process of capturing action items by providing a centralized platform for tracking and monitoring progress. This feature ensures that the outcomes of retrospective meetings are not lost or forgotten but rather integrated into the team’s workflow. Our team has the [Asana integration](/integrations/asana/) turned on, as well, as that is where the Product Team manages their action items. > #### Quick tip! > > #### TeamRetro allows retrospectives to be anonymous or you can leave your team members’ names on the cards. Our team finds that anonymity is actually less productive for our team, but that’s because we have built up a significant amount of internal trust. To start earning your team’s trust, try out the anonymous feature. ## Run better retrospectives and build a healthy team culture Regular and productive retrospectives play a vital role in nurturing a healthy team culture. By encouraging open and honest communication, retrospectives help foster psychological safety within the team. When difficult topics can be discussed in a healthy manner, trust and collaboration flourish. This positive team culture, supported by retrospectives, leads to improved morale, increased innovation, and a stronger sense of shared ownership over the team’s success. Want to check out TeamRetro for yourself? They offer a [30-day free trial](/plans/). **Thanks to our writer – [Mel Fox](https://www.linkedin.com/in/mel-fox-01587323/)** Mel Fox is currently the Principal Product Manager at SalesRabbit, where she manages both iOS and Android Mobile applications. With 5+ years of Product Management experience, Mel has managed both B2B & B2C Mobile apps. She is passionate about creating a customer-obsessed culture while focusing on nurturing her product development team. --- # Appsfactory turns to online retrospectives for engaging distributed teams URL: https://www.teamretro.com/case-studies/appsfactory/ ## Introducing Appsfactory [Appsfactory](https://appsfactory.de/en/) is one of Germany’s leading agencies for software development. The agency has over 15 interdisciplinary teams consisting of developers, QA and design staff as well as project managers. The company provides end-to-end [software development services](https://appsfactory.de/en/en-services/), including: - implementing individual software - creating responsive websites - implementing individualized back-end solutions for the real-time transmission of machine data - chatbots implementation - cloud services and hosting with Azure - internet of things to control various devices via an app - machine learning - design thinking - VR and AR development and many more Appsfactory was founded in 2009 by Dr. Alexander Trommen (CEO), Dr. Roman Belter (COO) and Dr. Rolf Kluge (CTO). Jan Nowak, the VP Projects and Technology, is leading the Project Department as well as the AI Department within Appsfactory. The team consists of more than 200 team members, who are distributed across [four offices](https://appsfactory.de/en/contact/) around Germany – Hamburg, Leipzig, Munchen and Erfurt. ## Face to face vs online retrospectives With four offices and sites across Germany, and most of the team members working with multiple clients at the same time, Appsfactory has found it challenging to find the right time and place where everyone can meet together for an engaging and regular retrospective. With COVID-19, this challenge has escalated even more as teams work remotely and face to face gatherings are more restricted. ## Finding the right online retrospective tool CTO Rolf Kluge decided to look for options to run online retrospectives so that all team members can get involved wherever they are located or working from. They came across [TeamRetro](/) as one of their options for an enterprise-ready online retrospective tool for remote teams. The Appsfactory team [trialed TeamRetro](https://secure.teamretro.com/login/new?emailAddress=) before deciding to continue with the platform to run their subsequent online retrospectives. ***“Retrospectives are an important part of our team’s culture and work methodology. We recognize retrospectives as enablers for change for the better, improvements to the way we work and stronger collaboration with each other and our clients.”*** ***“We are pursuing the goal of making retrospectives in all teams more efficient by using the TeamRetro tool.”*** ## Using TeamRetro for agile retros & team health checks The Appsfactory team enjoyed the easy to use interface of the TeamRetro platform, with both the [agile retrospective](/retrospectives/) and [team health check](/health-checks/) functionalities being stand out features that helped them run successful and efficient online retrospectives. ***“The feedback from our evaluation was quite impressive. All participants were amazed by the easy to understand design and the significance of time being saved by running the entire process digital from the beginning to the end.”*** ***“The agile retrospective feature is amazing, when it comes to fast collaborative retrospectives.”*** ***“The team health check is a very insightful tool for our team leads, so that they can monitor the team happiness level closely.”*** ## Online retrospectives increase productivity & satisfaction Jan Nowak commented that the standout benefits of using TeamRetro have been the ability for the AppsFactory teams to reduce the time spent on their online retrospectives vs. conducting a face-to-face format. Of course, with time savings also comes cost savings as team members are able to be part of the online retrospectives wherever, whenever they need to join, eliminating elements such as travel costs and time away from doing client work. This in turn helps to create more satisfied and engaged teams throughout the organization. ***“We could reduce our average time spent on retrospectives by more than 50%, while increasing the satisfaction level of the team at the same time.”*** ***“We are also very happy about the very supportive sales team and the flawless on-boarding procedure.”*** ## Try TeamRetro If you are also looking to solve issues of distributed teams or remote working when it comes to running engaging and effective retrospectives, why not give TeamRetro a go? We offer a [FREE 30 days trial and demos](https://secure.teamretro.com/login/new?cc=TeamRetroBlog) to help make your online retrospectives a success for you, your teams and the whole organization. --- # How Attus transformed team engagement with better retrospectives URL: https://www.teamretro.com/case-studies/attus/ [Attus](https://www.attus.ai/), a Brazil-based legal-tech company, offers a specialized platform designed to streamline operations for public sector legal departments. Powered by artificial intelligence and automation, Attus manages petitions and court rulings, classifies and distributes cases, drafts documents, monitors deadlines, and integrates with government systems like tribunals, Receita Federal, SEI, and debt collection services. By adapting to each institution’s unique workflows, Attus enables legal teams to focus on strategic decision-making rather than repetitive administrative tasks. As Development Coordinator, [Clávison Zapelini](https://www.linkedin.com/in/clavison-zapelini/) leads the orchestration of multiple development squads. His responsibilities include task prioritization, sprint planning, KPI tracking, and perhaps most importantly, keeping teams engaged and motivated. ## The challenge of creating standardized, high-impact retrospectives across 8 development squads While many agile ceremonies such as daily standups and reviews were running smoothly, retrospectives were proving inconsistent and less impactful. “Each tech lead used a different tool, some took more time and others less, and I didn’t see the results of this very important ceremony,” Clávison explains. Attempts to formalize retrospectives with other tools hadn’t helped, resulting in low engagement and fragmented outcomes. ### The turning point: trialing TeamRetro Looking for a better approach, Clávison introduced TeamRetro to one squad during a two-sprint trial. The difference was clear from the start. “We immediately noticed much higher engagement, thanks to the methodology the tool allows,” he recalls. > *“We immediately noticed much higher engagement, thanks to the methodology the tool allows.”* Team members echoed the sentiment in surveys, describing them as the best retrospectives they had experienced. Encouraged by the feedback, Clávison expanded the use of TeamRetro to all eight development squads, covering around 40 developers. “The engagement fostered by the various facilitation methods and the available templates were the main reasons for choosing it,” he confirms. > *“The engagement fostered by the various facilitation methods and the available templates were the main reasons for choosing it.”* ## How TeamRetro supports the Attus process Attus runs bi-weekly sprints across its development teams, and TeamRetro quickly became a staple for their retrospective ceremonies. Its pre-designed templates made preparation significantly easier for tech leads and helped standardize the experience across squads. What was once a challenge became a strength. > *“Our sprints are bi-weekly, and we have 8 development squads. We use TeamRetro for the retrospective ceremony. It greatly facilitates the management of this ceremony by providing well-designed templates, which significantly help the tech leads prepare an effective retrospective.”* ## Measurable outcomes: engagement, agreement, and alignment According to Clávison, the biggest win was team engagement. With everyone contributing meaningfully, retrospectives became an opportunity to surface important insights and turn them into clear, actionable agreements. Using TeamRetro, the team could also monitor progress on those agreements over time, improving accountability and follow-through. -  -  ## Features that made a difference Two features made the biggest impact. Firstly, the structured templates are tailored to our different retrospective goals. Secondly, the built-in agreement-tracking capabilities. “It provides peace of mind knowing that the agile methodology is being implemented correctly and consistently across all squads,” Clávison shares. Leadership feedback was equally positive. “The request to acquire the tool was unanimous after the tests were conducted,” he continues, “The technical leadership noted that both engagement and team relationships improved.” > *“It provides peace of mind knowing that the agile methodology is being implemented correctly and consistently across all squads.”* ## Advice to fellow Scrum Masters Reflecting on his experience, Clávison offers a few words of advice to others facilitating retrospectives. “Use open-ended questions to encourage reflection and identify concrete actions for improvement. Value diverse opinions and consistently strive for process and team enhancement.” What started as a need for consistency evolved into a more engaged, aligned, and empowered development culture. TeamRetro helped turn retrospectives into a high-impact, high-participation ceremony across the organization. > *“Use open-ended questions to encourage reflection and identify concrete actions for improvement. Value diverse opinions and consistently strive for process and team enhancement.”* ## Make the switch to TeamRetro today Attus Procuradoria Digital’s experience shows how TeamRetro can revolutionize retrospectives, boost team engagement, and streamline agile processes across multiple squads. Whether you’re looking to unify teams, surface meaningful insights, or implement agile best practices more effectively, TeamRetro provides the tools to make it happen. [Try TeamRetro today](https://secure.teamretro.com/login/new) to transform your retrospectives! --- # How Big Give runs smarter, more impactful retrospectives with TeamRetro URL: https://www.teamretro.com/case-studies/big-give/ At Big Give, small means mighty. [Big Give](https://www.thebiggive.org.uk/) is the UK’s largest match funding platform, helping thousands of UK-registered charities raise millions of pounds through match-funded campaigns. With just 12 people driving that outsized impact, every process, every conversation, and every lesson learned counts. For a team this size, finding the right online retrospective tool wasn’t a nice-to-have, it was essential to staying sharp. We’re genuinely proud to support Big Give and the work they do, and even prouder that they’ve trusted us to share their story here. This case study was contributed by [Dominique Standring](https://uk.linkedin.com/in/dominique-standring-91940749), Chief Operating Officer (COO) at Big Give, who has over 12 years of experience designing systems and processes in the charity sector. Dominique shares how TeamRetro helped transform Big Give’s retrospective practice from a fragmented, time-consuming exercise into a reliable engine for continuous improvement. ## The challenge: lost data and no central home for reflections For a team that prizes learning and constant improvement, running effective retrospectives wasn’t optional — it was baked into the culture. Big Give uses the retrospective format not just for sprint reviews, but for structured reflection after each of their match-funded campaigns. The problem? Their tooling wasn’t keeping up. As a charity, keeping costs low is a real constraint — but that couldn’t come at the expense of quality. Big Give needed a solution that was both affordable and genuinely fit for purpose. ## Why Big Give chose TeamRetro A straightforward Google search led Dominique to TeamRetro. After running a few trial retrospectives, the decision was clear. The combination of a clean user interface, strong functionality, and Jira integration made TeamRetro stand out from the alternatives. What clinched it was actually using it: the trial experience gave the team enough confidence to commit. ## How Big Give uses TeamRetro Big Give now runs two distinct retrospective rhythms with TeamRetro: every four weeks for the development team, and after each of their six annual campaigns for the whole organization. One of Dominique’s top tips for anyone learning how to run retrospectives remotely? Set up the board well in advance. > ***“The ability to set up a board and invite participants long in advance of a retro is great because it means we can capture reflections directly on the board while they are still fresh.”*** That head start transforms the quality of the conversation. Instead of asking people to recall how they felt three weeks ago, reflections are captured in the moment and ready to explore when the team gathers. *Image provided by Big Give – reproduced with permission* ## Benefits the team experienced ### A richer, more connected conversation Working mostly from home, Big Give relies on TeamRetro as their retrospective tool for remote team collaboration. The asynchronous features — commenting and emoji reactions — let team members engage with each other’s reflections before the live session even begins. > ***“This allows for a much richer conversation when we’re holding discussions about each reflection.”*** ### One central home for every retro One of the most tangible wins has been having all retrospectives in one place. No more lost data, no more hunting through old tools or documents. For a professional, fast-paced team running continuous improvement retrospectives across multiple campaigns and development cycles, that consistency is invaluable. > ***“Efficiency and central data storage have made our retros more productive and helpful.”*** ### A Jira integration that closes the loop The retrospective tool’s Jira integration was a key reason Big Give chose TeamRetro — and it continues to be one of its most valued features. Actions don’t get lost between tools. They flow straight into the team’s existing workflow, keeping accountability tight without adding friction. ### A format the team actually enjoys When it comes to the live discussion, the team appreciated TeamRetro’s presentation mode, which keeps the conversation focused and structured. Combined with the ability to comment on individual tickets, it makes the discussion feel purposeful rather than scattered. > ***“The team liked the interface, the fact that you can comment on tickets and the presentation mode for the discussion.”*** ## Outcomes for a team with an outsized impact For an organization of 12 people, continuous improvement isn’t a nice-to-have — it’s how Big Give punches above its weight. > ***“TeamRetro is helping us become more efficient while maintaining high quality and a good work-life balance for everyone — not only in the fact that we now have all of our retros in one place but also in the ease of use and integration with other platforms.”*** ## Dominique’s tip for running remote retrospectives Dominique’s advice is simple, practical, and easy to implement: > ***“Set up the boards in advance so people can add things as they come up.”*** It’s one of the most underrated techniques for anyone figuring out how to run retrospectives remotely. Reflections captured in the moment are more honest, more specific, and more useful than memories reconstructed days later. If you’re not already opening your boards early, start there. Want more than what a free agile retrospective tool can offer? Try [TeamRetro](https://secure.teamretro.com/login/new) and see what a difference the right choice makes. --- # How an agile coach saves time and effort with a better health check and retrospective tool URL: https://www.teamretro.com/case-studies/blablacar/ What would you do if you started a role as ScrumMaster, Agile Coach or Program leader with 40 teams to lead? How would you manage their happiness, get a sense of what is motivating the team, while keeping admin low? We’re pleased to share Marion’s story here about how she did just that. [BlaBlaCar](https://blablacar.com/) is a marketplace and carpooling platform that connects drivers and travelers from one city to another around the world. They allow users to share rides, split travel costs and reduce the environmental impact of long distance ride shares. — Hey there Agile enthusiasts! Marion here, Senior Agile Coach leading the charge at [BlaBlaCar](https://blablacar.com/). I’m passionate about exploring the world, meeting diverse people, and adding a sprinkle of animal love to my travels. If you’re curious about my journey, feel free to check out my LinkedIn profile: [www.linkedin.com/in/marionbenard](https://www.linkedin.com/in/marionbenard/). Now, let’s dive into the thrilling world of Agile coaching and how I, along with my fantastic team, navigated the challenges of Health check processes at BlaBlaCar. ## The challenge: tackling tedious health checks In 2021, I joined the BlaBlaCar family, and one of my initial tasks was to support 30 software engineer teams through their Health check process. Picture this – a jungle of documents and spreadsheets, loads of manual tasks, and a high risk of errors. The pain point? The crucial part of analyzing results and defining actions was getting buried in the chaos. The most important work was being rushed. ## Seeking solutions: embracing tools for efficiency We chose to continue with a health check model we had been using in spreadsheets before we started using TeamRetro. Our health check model was a version of the Spotify health model that we adapted to our very own culture. Eager to bring order to this chaos, I reached out to peers and scoured the internet for solutions. Several tools were tested to find the perfect match that would save time and allow us to focus on what truly mattered. Enter TeamRetro – a game-changer that streamlined our health check processes. With the ability to create and duplicate templates effortlessly, sending links for participant answers, and managing discussions about improvements, we could now breathe easy. Action follow-ups became a breeze, even if we weren’t entirely efficient with email reminders (not really our internal culture). ## Benefits unveiled: time savings and global insights Managing health checks for 40 teams in the same timeframe became a reality. The tool’s user-friendly interface allowed us to appreciate a global view of results and trends for all our teams. A single page showcased our strengths and highlighted areas needing our focus. An interesting discovery during my occasional dives into the activity overview was a strong correlation between the frequency of retrospectives and team health. This revelation led us to provide more support to teams lacking regular retrospectives. We didn’t actually force people to use TeamRetro for tools, but we now have over 90% of our retrospectives used by teams, so it was adopted very quickly! ## Efficiency in action: agile coaches and catalysts in sync As Agile coaches, we saved precious time, enabling our Agile Catalysts within teams to have a centralized hub for improvement action items. The tool’s simplicity and quick usage, as well as the ‘auto-grouping’ feature was a wow factor for us. ## Format freedom: fun retrospectives for your terms While some comments surfaced about missing more fun retrospective formats, TeamRetro’s flexibility allowed teams to choose their preferred formats. This avoided the dreaded boring effect while still centralizing actions seamlessly. ## The stats speak: TeamRetro in action Approximately 90% of our retrospectives now happen within TeamRetro, and a whopping 100% of our health checks are efficiently managed through this tool. It translates to centralized data, easy analysis, and a simplified user experience. (Provided by BlaBla Car for illustrative purposes only) ## Pro tip: enable participation for dynamic events Don’t forget to unleash the mode where every participant can create groups or add comments and actions. It injects dynamism into the event and keeps things lively! In a nutshell, TeamRetro saves us time, provides insights, and ensures our health checks and retrospectives are a breeze. Happy retrospecting! Marion 🚀🔍 ## What is a team health check? An Agile [Team Health Check](/health-check-templates/team-health-check/) is like a checkup for a team to see how well they’re working together. It looks at things such as how they talk to each other, collaborate, and follow their Agile practices. The main goal is to help the team get better over time and make sure they’re on the same page with Agile values. This checkup helps find and solve problems early, improves how the team communicates, and supports the growth of team members. Overall, it boosts team morale, engagement, and ability to adapt. It creates a culture of openness and flexibility, so the team can handle changes in the project and keep a positive and effective work environment. --- # How Culture Amp uses TeamRetro to unify agile feedback and boost visibility URL: https://www.teamretro.com/case-studies/culture-amp/ At Culture Amp, building a better world of work starts from within. [Culture Amp](https://www.cultureamp.com/) is a leading employee experience platform that helps companies take action to improve employee engagement, performance, and development. With a strong focus on creating a culture-first company, their mission centers on helping organizations use data to drive performance while fostering care and connection. With teams building products to support employees and managers alike, agile feedback is at the heart of how they work. This case study was contributed by [Ibrahim Abram](https://www.linkedin.com/in/abrahimabram), Procurement Specialist at Culture Amp. He shared how TeamRetro has helped him as a Team Lead to ensure that teams are “high performing, but happy at the same time.”, by giving him insights as to where to focus as a team improves and stays happy and productive. ## The challenge: disparate retrospectives, limited visibility With many teams running retrospectives using different tools, there was no unified way to gain insight across departments. Culture Amp needed a solution that could offer a centralized, consistent view of retrospective outcomes and team health. > “There was no way of going into one place to see how things are going in different teams across specific areas of the company. TeamRetro made this possible for us.” Using built-in features like [team tagging within TeamRetro](https://help.teamretro.com/article/309-team-tagging), Culture Amp unlocked high-level visibility. > “We started using tags (for departments, teams etc) which could give us an overarching view of retros and health checks. This is a very helpful tool for directors as they can view their team’s health and actions”. ## Choosing TeamRetro to simplify and scale agile feedback Drawn to TeamRetro’s intuitive design and insightful features, the team began by running Spotify-style squad health checks. The positive response led to wider adoption by teams, which then expanded into running team retrospectives as well. > “I love the simplicity of the interface to run retrospectives and health checks. Particularly for health checks, I love the graph that shows the trends.” says Ibrahim. *Image provided by Culture Amp* ## Supporting agile feedback through health checks, values, and Jira Culture Amp runs fortnightly retrospectives and health checks that vary from fortnightly to quarterly depending on team needs. With TeamRetro, they can conduct these sessions seamlessly while tracking follow-up actions over time. A core Culture Amp value is to “Learn faster through feedback”. As Ibrahim shares, “TeamRetro is one of the key tools that enables us to live this value within our engineering organization. It provides us a way to run these effectively and track actions that come out of these sessions.” *Image provided by Culture Amp* One of the standout features for the Culture Amp team is TeamRetro’s integration with Jira, helping to make sure actions from retrospectives are captured and remain accountable. > “TeamRetro’s integration with Jira for action items has been invaluable for driving follow-through. By tracking retro actions in the same place as our project work, they stay visible and prioritized.” Another aspect that has created more engagement, novelty, and incited new ideas is the range of retrospective templates and health check styles. As Ibrahim explains, “Out of the box templates to run retros and health checks allowed teams to use different formats that helped them think about their teams from different perspectives.” ## Benefits for teams and leaders: visibility, voice, and well-being TeamRetro has helped foster a stronger sense of engagement and ownership among Culture Amp’s teams. Regular retrospectives ensure that everyone’s voice is heard, and the visible follow-through on feedback has reinforced a culture of responsiveness and trust. “The most significant impact is a clear sense of being heard, with visible follow-through on feedback. TeamRetro provides me and the team insights that help us understand where we should focus as a team to improve and be more happy.” ## Advice for Scrum Masters using TeamRetro Culture Amp’s tip for turning retrospectives into results? > “Make sure your teams focus on actions explicitly and hold each other accountable if they are not taken in time. Running these sessions is just the first step. But the real improvement is achieved from taking the actions that come out of these sessions.” Ready to reflect and improve? Run your own [TeamRetro](/) session with this tip in mind now. --- # Tips on running effective retrospectives for team feedback URL: https://www.teamretro.com/case-studies/dedalus/ Managing an agile team is much like conducting a symphony – it requires harmony, rhythm, and listening to each other in the group. Effective management of agile teams requires more than just meetings – it’s about fostering an environment where candid feedback thrives. Damian Obalka, a Software Developer and Scrum Master at Dedalus HealthCare, knows this all too well. Since 2019, he’s been steering his team through the choppy waters of software development, seeking ways to keep everyone engaged and the feedback flowing. Cue TeamRetro! With this tool in hand, they’ve turned retrospectives into a playground for ideas, criticisms, and everything in between. Damian highlights some of his tips that he uses in running successful retrospective meetings with TeamRetro. ## Introduction Hi, I’m Damian Obalka from Dedalus HealthCare and I have been working as a Software Developer and Scrum Master for the company since 2019. We first started to use TeamRetro early in 2020, so that we could continue our retrospectives even in a remote setup. Quickly, we started to enjoy the tool and the benefits it brought and still brings to us. Overall, it has been a terrific addition to our meetings! ## Getting honest feedback from your team To solve issues that prevent your team from performing at its best, you will need an environment in which your colleagues feel safe to share their honest thoughts, feelings and worries about their daily working experience. Consequently, a tool for retrospectives and health checks that is both fun to use and adds features where you can write down your ideas, observations and criticism anonymously is a perfect match to establish such an environment. You can decide for every new retrospective and health check that you will start in TeamRetro, whether you want it to be anonymous or not. Doing this occasionally has proven to be very insightful for us. Sometimes your team members might not feel confident enough to voice all their concerns for several reasons. However, this feedback often proves to be the most vital one to improve your workflows and team happiness. *An example of creating an anonymous agile retrospective meeting* ## Create the ideal retrospective format for your team Another feature of TeamRetro that we have been enjoying is the customizability of its templates. While you do have a large library of standard and community templates to choose from, you can also decide to create a new custom template for your specific needs in your next meeting. This flexibility is greatly appreciated by us. Since you probably don’t want your retrospectives to become predictable and stale, you might want to try something new. If you are looking for more inspiration to achieve that, then the community (and AI) templates can be a great source to start your search. If you already have a highly specific topic in mind for your team/participants, TeamRetro will have you covered so that you can create a matching template. ## Add an icebreaker to your meeting It is also worth mentioning that your options for customization and planning do not stop with your templates. In fact, you can additionally include several options such as a dedicated “welcome” or “icebreaker-slide” to start your health check/retrospective. On top of that, you can assign a duration for most sections during your meeting if you want the tool to assist you in keeping track of the elapsed time. This can be adjusted for each new meeting that you start even if you use the same template! As you can see, there is an abundance of customization choices for you to choose from depending on your needs. So, there you have it! Managing an agile team is no walk in the park, but with tools like TeamRetro, the journey becomes a bit smoother. Damian’s story shows us the importance of creating a space where everyone feels heard and valued. TeamRetro’s customizable templates and planning features make it a breeze to tailor each retro to fit your team’s vibe. ## Who is Dedalus Health? Dedalus is a leader in healthcare software, offering ways for seamless care and value across the healthcare ecosystem with innovative solutions. They are one of the largest Global Health Software Companies globally. In 2016, Dedalus decided to accelerate its expansion strategy by focusing on the growing demand for innovative and comprehensive solutions to support the digital transformation of the healthcare ecosystem. Working across the whole continuum of care and offering Open Standards-based solutions, Dedalus helps healthcare organizations to deliver new models of care. They have over 40 years' experience of delivering healthcare software and services to over 6,700 healthcare organizations. Their software is used widely across the world, managing each year more than 3 billion diagnostic results, serving 540 million people, 28 million inpatient and 35 million emergency admissions, and in primary care, serving more than 120 million citizens. --- # Helping nonprofits thrive through agile grant writing URL: https://www.teamretro.com/case-studies/dh-leonard-consulting/ [Beth Archer](https://www.linkedin.com/in/elizabeth-archer-b5368791) wears two hats at [DH Leonard Consulting & Grant Writing Services, LLC](https://www.linkedin.com/company/dh-leonard-consulting-&-grant-writing-services-llc/) – as both a Registered Scrum Master (RSM) and a Grant Professional Certified (GPC) strategist. DH Leonard Consulting helps nonprofit organizations competitively apply for, receive, and manage grant funding so they can better serve their communities and drive meaningful impact. Using an Agile approach, the firm breaks down the grant writing process into iterative steps that promote faster delivery, open communication, and continuous improvement. Beth’s passion lies in helping her remote team leverage the Scrum framework to streamline internal workflows and enhance outcomes for their clients. > *“**I love how using the Scrum framework has made it possible for us to serve our clients more efficiently and effectively,**”* she says. ## The challenge: managing retrospectives in a fully remote team As a fully remote organization, DH Leonard Consulting needed tools that supported distributed collaboration without adding friction. Their previous method relied on a virtual whiteboard for retrospectives, but setting it up required outside help. > ***“A challenge for our team is that we are all remote, so we need tools that help, not hinder, our virtual work environment. Additionally, as someone who wears both the Scrum Master hat and the team member hat, it is challenging to balance my time and ensure that I’m managing each of my roles effectively. We had a system that was working well for our team’s Retrospectives using a virtual whiteboard tool, but due to capacity constraints, we were actually utilizing a colleague outside of our team to set them up for us each week.”*** ## Choosing TeamRetro to support agile ceremonies When the team discovered TeamRetro, it quickly became the perfect solution. > ***“It is the exact kind of tool we need as a remote team. It allows us to do some of the work asynchronously, while also supporting live discussions. Because it is so easy to set up and run each Sprint, we have also been able to keep the work within our team and not have to rely on our other colleagues.”*** With its ease of use and autonomy, TeamRetro allowed the team to fully own their agile ceremonies—no more relying on outside support. ## Weekly retrospectives with structure, flexibility, and fun DH Leonard Consulting runs weekly retrospectives at the end of each sprint. Using TeamRetro templates as a base, the team customizes them with questions tailored to their process, including metrics on team happiness and stress. > ***“We do weekly Retrospectives at the end of each Sprint. I love the templates, we use them each week; however, we are also able to edit them and add our own questions (e.g., we measure team happiness and team stress each Sprint). We also use the icebreakers, which have helped to get people warmed up and engaged.”*** ## More engagement, less setup Beth notes that retrospectives now run more smoothly, with less time spent on logistics and more time focused on meaningful reflection and outcomes. > ***“We have spent less time setting up our virtual Retrospectives and have been able to keep the work within our team, instead of asking a colleague outside of our team for support. We have regularly started Retrospectives with an icebreaker (something we previously did intermittently), which has improved the tone of and engagement during Retrospectives.”*** This structured approach has enabled better follow-through and greater accountability on team actions. ## Easy transition and positive feedback > ***“The Retrospectives, and particularly the templates. This has made our Retro setup so easy!”*** The feedback from the team has been overwhelmingly positive. They appreciate the streamlined setup, consistent format, and the ability to centralize everything in one platform. Icebreakers and customizable templates have added an extra layer of engagement. > ***“It is easy to use and was straightforward to transition from our previous system to TeamRetro. The team also appreciates the templates and icebreakers, as well as the fact that everything is in one place.”*** ## A tool that empowers remote teams For Beth and her team, TeamRetro has done more than just simplify retrospectives — it’s made their agile process more impactful. > ***“TeamRetro has been a great addition to our team. It has made things easier and faster!”*** ## Advice for Scrum Masters and agile teams Beth’s top tip for teams starting out with TeamRetro? > ***“Know that there is so much room for customization! You can truly make it into exactly what you need/want.”*** TeamRetro continues to support agile practices at DH Leonard Consulting, helping them deliver value to clients while building a stronger, more engaged remote team. [Try TeamRetro today](https://secure.teamretro.com/login/new) and bring structure, flexibility, and energy to your retrospectives—no matter where your team is. --- # Eurowings Digital empowers teams with remote retrospectives URL: https://www.teamretro.com/case-studies/eurowings-digital/ ## Eurowings turn digital [Eurowings](https://www.eurowings.com/en.html) is part of the [Lufthansa Group](https://www.lufthansa.com/), one of the leading airlines in the European market. In 2018, the airline established a subsidiary called [Eurowings Digital](https://eurowings-digital.de/) to support the transformation of the Eurowings brand from an airline to a holistic digital travel companion for the entire travel chain. Since its inception, Eurowings Digital has been tackling some crucial challenges within the travel industry, including: - Customer needs are continuously changing and becoming more and more digital. Eurowings Digital has a strong focus on customer experience to enable the group to offer quick solutions for any change in this area. - The airline and travel market are complex and changing significantly. By having a focus on new trends through Eurowings Digital, Eurowings wants to take advantage of its leading position in the European airline market to become a strong player in this new market. - To create the best digital services, Eurowings needs the best tech talents. Eurowings Digital wants to offer an environment that attracts these talents. Rebecca Graf is the Scrum Master at Eurowings Digital and her work focuses on being a key driver and problem solver in Eurowings agile environment, working within a team and supporting the entire organization. ***”In my role I help our Squad teams to live the agile values and also support them to remove blockers or to solve other dependencies, allowing the Squad teams to work at 100% capacity without issues.”*** Image credit: Rebecca Graf ## Remote retrospective challenge for the scrum team Image credit: Eurowings Digital Eurowings Digital follows a scrum methodology for its team’s sprints. While the team has worked in a partially remote environment before, they have always conducted their sprint change face to face, when every team member is in the office. When COVID-19 hit, the Eurowings team moved to complete remote work and were not able to continue the normal face to face component of their scrum methodology. ***“Suddenly I could not create flipcharts for retrospectives, distribute Post-It and have dots voting on them anymore,”** commented Rebecca.* ***“I had no previous experience in remote retrospective work and needed to find a way to handle the retrospectives in a structured and efficient way, particularly at this difficult time.”*** ***“The important criteria for me was for the remote retrospectives to remain diverse and the team should have fun still with it.”*** ## An online solution to run remote retrospectives Remote retros with TeamRetro To support her team and the Eurowings Digital organization to continue their retrospectives, Rebecca went in search of a remote retrospective solution. ***“I asked around, researched and tried out different options for remote retrospectives. These ranged from simple* [*Google Doc*](https://www.google.com.au/docs/about/) *to* [*Confluence Templates*](https://www.atlassian.com/software/confluence) *and various tools, some explicitly made for this purpose like* [*TeamRetro*](/)*****, others a bit more universally applicable,”** explained Rebecca.* Rebecca signed up for the [30 days free trials of TeamRetro](https://secure.teamretro.com/login/new/) to gauge its suitability for her team and organization. The trial helped Rebecca decide to use TeamRetro for Eurowings Digital. ***“In this trial phase, TeamRetro convinced me because it is easy and intuitive to use, offers a* [*HealthCheck*](/health-checks/) *in addition to the functionality for the* [*retrospective*](/retrospectives/) *itself and also offers other pleasant features like tool integrations for* [*Slack*](https://slack.com/intl/en-au/) *as well as a nice documentation.”*** ## Benefits of going remote with your retrospectives Rebecca explains that with TeamRetro, her team and organization are now supported to conduct their remote retrospectives effectively. Every remote retrospective now starts with a follow up on the action items which can be done really easy within the team dashboard in TeamRetro. This allows for the team to quickly discuss each action item and check it off if it’s done. Then the team would move on to the [HealthCheck](/health-checks/) and they use the Custom Health Check here. The set of questions and the choices are the same for all teams, to allow a comparison of the results. ***“As the HealthCheck is meant to get a quick overview it really suits our need as it can be filled out in just seconds.”*** Team health check with TeamRetro Rebecca also explains that the various templates in TeamRetro help to create a good structure to the remote retrospectives, keeping teams focused and the retros highly productive. TeamRetro ready to use templates ***“We use Retrospectives in various versions. Depending on what is required, we use the ready-made templates or create our own retrospective. We like the given process of Brainstorm > Group > Vote > Discuss > Review > Share very much. It’s easy to follow and gives the whole meeting a good structure.”*** ***“The collection of topics can be done really easily, the grouping works quite well, the voting helps to focus on the most important topics and the timer ensures that you don’t lose track of time.”*** ## Remote retrospective gets the tick of approval! By using TeamRetro, Rebecca was able to support her squad team to continue to run one of the most important parts of the scrum methodology – retrospectives – remotely. Through the experience, Rebecca and her team have also provided many valuable pieces of feedback to enhance the TeamRetro experience so the platform continues to help teams around the world to run remote retrospectives and deliver every sprint effectively and productively, in the face of a global pandemic. ***“Teamretro helped us massively to run efficient and well-structured remote retrospectives. Furthermore, I can save myself the trouble of documenting the results afterwards, as everything is automatically available in TeamRetro.”*** TeamRetro Health Check ## Try TeamRetro Are you and your team or organization looking to conduct remote retrospectives and team health checks? Whether you have a partially remote, fully remote or hybrid work environment, TeamRetro can help to make sure that your important retros run efficiently and in an engaging manner. [Try it FREE today for 30 days!](https://secure.teamretro.com/login/new?cc=TeamRetroBlog) --- # Go.Compare builds a culture of continuous improvement with TeamRetro URL: https://www.teamretro.com/case-studies/go-compare/ [Go.Compare](https://www.gocompare.com/) is one of the UK’s most recognizable and trusted comparison websites, helping millions of consumers find better deals on insurance, utilities, broadband, and financial services. Known for its iconic TV adverts and focus on simplifying complex decisions, Go.Compare is part of Future PLC, a global multi-platform media company. We are honored to introduce [Dan Evans](https://www.linkedin.com/in/danevans/), VP of Technology who leads the PCW-Tech organization, overseeing critical technology functions that include customer journeys, partner integration, renewals, and strategic initiatives. Passionate about building high-performing teams and delivering resilient, scalable technology, Dan focuses on aligning engineering outcomes with business value while fostering a culture of continuous improvement. ## The challenge: aligning retrospectives across growing teams As Go.Compare’s engineering teams scaled, so did the complexity of managing agile ceremonies across squads. In a growing, innovative organization it was still important to provide direction and leadership when leading agile processes around continuous improvement. Dan shares, **“*Our teams were growing in size and complexity, with multiple squads working across interconnected journeys. Retrospectives were inconsistent across teams, with variable depth of insight and a lack of standardization. We needed a structured, engaging way to capture feedback, drive actionable improvements, and ensure alignment across squads.*”** ## Choosing TeamRetro to support scalable agile practices Faced with the need for a more unified and effective approach, Dan and his team evaluated several tools before selecting TeamRetro. **“*We evaluated a range of tools, but TeamRetro stood out for its balance of structure, flexibility, and ease of use. It enabled distributed teams to collaborate effectively, supported multiple templates and health checks, and gave us a single consistent platform to embed a culture of continuous improvement.*”** ## The process: regular retros and monthly health checks Go.Compare uses TeamRetro to run agile ceremonies that are both scalable and actionable. Empowering teams to be disciplined in their practices while making it straightforward, easy and interactive meant that everyone could participate in the meetings. ***“We run regular retrospectives and monthly health checks at both the squad and organizational level”***, Dan says. > *“TeamRetro provides templates we can adapt, anonymous input to encourage candour, and reporting to track themes over time. It supports a cycle of reflection, prioritization, and follow-up, helping us close the loop on improvements.”* ## The outcomes: consistency, visibility, and psychological safety By adopting TeamRetro across squads, Go.Compare achieved several measurable improvements. Dan shares some of the key benefits he has seen with his team as well as individual people in the organization. - *Improved consistency and quality of retrospectives across squads.* - *Clearer visibility of recurring themes (e.g., tooling, deployment, cross-squad alignment).* - *Increased psychological safety, with more honest feedback from team members.* - *Actionable insights that feed into our engineering OKRs and performance measures.* The transition to TeamRetro didn’t just benefit leadership—it positively impacted the entire team experience. This can only lend itself to boosted productivity and improved return on time invested in meetings. > *“Easier participation, especially for quieter voices in the team. A more engaging format compared to traditional retrospective boards. Confidence that feedback would be seen, tracked, and acted upon.”* ## Team feedback and broader organizational impact The reception from both teams and stakeholders has been overwhelmingly positive. “*Teams have highlighted that retrospectives feel more valuable, structured, and productive. I appreciate the ability to surface organizational themes and to see how actions are being followed through.*” And what does TeamRetro mean to Go.Compare as a whole? – Dan summarizes *“For me, it has been a key enabler in building a culture of continuous improvement. For teams, it means their voices are heard and acted upon. It provides assurance that teams are reflecting, adapting, and continuously improving against delivery and quality goals.”* ## Advice to agile leaders and Scrum Masters Dan shares three hot tips to help transform culture and build team spirit. 1. Make retrospectives part of your cultural rhythm, not just a process. 2. Use health checks to get ahead of issues. 3. Most importantly, ensure that insights lead to visible action. Teams need to see that their feedback creates change. We integrated Retro actions into ADO so they become items on the backlog that the team can address. We’d like to thank Dan for his contributions here and for sharing his experiences from his team and leadership. ## Empower your teams with TeamRetro Go.Compare’s experience shows how TeamRetro can create consistency, elevate team engagement, and ensure agile ceremonies lead to real outcomes. Whether you’re scaling squads or strengthening feedback loops, TeamRetro helps turn reflection into results. [Try TeamRetro today](https://secure.teamretro.com/login/new/?cc=TeamRetroBlog) and bring continuous improvement to life across your organization. --- # Herman Miller's remote agile team achieves new goals with TeamRetro URL: https://www.teamretro.com/case-studies/herman-miller/ ### Herman Miller adopts agile practices [Herman Miller](https://www.hermanmiller.com/en_au/) is a well-known producer of high-quality office furniture and equipment and home furnishings. They are a global organization, with a head office in Zeeland, Michigan, USA and resources across the world – including a technology center based in Bangalore, India and regional offices in Europe, Asia and South America. Herman Miller has been slowly adopting Agile practices for developing software and technical teams in general for several years, to support the design, creation and production of their award-winning products. Tim Stayman is the Java Services Manager and Agile Coach for Herman Miller. > ***“I am a Work Team Leader for 6 Java developers who all work on Agile Product Teams. I am a SCRUM Master for two Product Teams. I am also one of 4 agile coaches at Herman Miller.”*** ### Remote retrospective for an agile team Herman Miller Innovation Lab Tim explained that Herman Miller’s agile adoption was “grassroots” in nature, which resulted in a less-than-coordinated approach for conducting effective retrospectives. > ***“Teams were going about it in different ways and using different tools, including various retrospective tools.”*** > ***“We tried several ‘free’ tools but they all fell short in terms of supporting remote teams and delivering features and functions required to run a valuable retrospective.”*** > ***“As a result, some teams were either conducting poor retrospectives or not having retrospectives at all.”*** In addition, the COVID19 global pandemic resulted in all of Herman Miller’s teams working remotely. This added to the issue of conducting poor or no retrospectives that already existed. ### A solution to run remote retrospectives Remote retros with TeamRetro Tim and his team were using a free version of an Agile Retrospective tool before requesting Herman Miller’s Agile Guild – the group that provides guidance on the recommended use of tools – to create a team to evaluate available, best option retrospective tools. > [***“TeamRetro***](/) ***was a highly recommended tool that a colleague has used at a different job. The features and capabilities of TeamRetro seemed to also meet our set goals to choose a tool.”*** Tim explained that his team’s guiding goals for choosing the right Agile Retrospective tool included: 1. Simple to use; 2. Reasonably priced or free; 3. Supports remote workers; 4. Deliver results to drive improvement. ### Effective retrospectives with TeamRetro Tim indicated that TeamRetro is primarily used to [run retrospectives](/retrospectives/) across Herman Miller’s 12 or so product teams. Having an easy-to-use tool that is especially designed for Agile Retrospectives has provided many positive results that Tim and the product teams noticed. The [ready-to-use and customizable templates](/retrospectives/) also contribute greatly to making sure Agile Retrospectives can happen quickly and in a focused manner. > ***“The most noticeable effect is that all of our product teams are conducting effective retrospectives and sticking with it.”*** > ***“In fact, most teams look forward to attending the retrospective.”*** > ***“Our Product Teams particularly enjoy the use of Agile Retrospectives templates and custom templates for problem solving and ideas generation.”*** > ***“We also rate highly the ability to record feedback in real time, have actions in one spot that can be tracked on week to week and downloaded at a click of a button.”*** TeamRetro Agile Retrospectives Templates TeamRetro’s continued integration with popular task management and communications tools has also been a favorite among all users. > ***“Continued integration into Teams is important as we are a Teams environment.”*** ### Higher engagement and increase in velocity with TeamRetro Tim indicated that by using TeamRetro there have been noticeable improvements in engagement and productivity. > ***“Having TeamRetro manage our retrospectives has been vital in keeping our Product Teams focused and engaged.”*** > ***“On one product team that I am the SCRUM Master for, we have implemented over 100 improvements in the past year, resulting in higher engagement and a 10% increase in velocity.”*** Herman Miller teams have now used TeamRetro for over a year and Tim indicated that it has really helped support the Agile way of working at the organization. ### Try TeamRetro for remote retrospective with your agile team! Are you and your team or organization looking to conduct effective remote Agile retrospectives and team health checks? Whether you have a partially remote, fully remote or hybrid work environment, TeamRetro can help to make sure that your important retros run efficiently and in an engaging manner. [Try it FREE today for 30 days!](https://secure.teamretro.com/login/new/) --- # Hogar Sí — ending homelessness with agile methodologies URL: https://www.teamretro.com/case-studies/hogar-si/ As part of their agile adoption and software development process, Hogar SI needed to run effective retrospectives across all of their teams. To do this, they looked to TeamRetro. Scrum Master Fernando Baghe shares how they used TeamRetro to create actions that lead towards positive change and continuous improvement. ## Who we are [Hogar SI](https://hogarsi.org/) is a non-profit organization with a mission to end homelessness by providing affordable housing for those in need. Our team has been working tirelessly to make this goal a reality. However, coordinating and executing effective retrospective meetings has been a challenge for our decentralized team. That’s why we decided to implement TeamRetro as part of our agile adoption process. > ***With TeamRetro, our team has been able to improve communication and collaboration, leading to more effective adoption of agile methodologies and a greater impact on our mission to end homelessness.*** ## Our TeamRetro experience Before TeamRetro, each team member was using different tools and methods to conduct retrospectives. This resulted in inconsistent and less effective reviews. With TeamRetro, we now have a consistent and easy-to-use platform for conducting retrospectives. The ready-to-use and customizable templates have also made it easier for our team to focus on the most important issues and come up with actionable solutions. > ***One of the most significant benefits of using TeamRetro is the ability to record feedback in real-time and track progress on a week-to-week basis.*** This has allowed our team leads to closely monitor the team’s progress and satisfaction levels, making it easier to identify and address any issues that may arise. TeamRetro’s integration with popular task management and communication tools has also been a hit with our team. This has allowed us to seamlessly integrate retrospectives into our daily workflow, saving us time and increasing productivity. ## Why we recommend TeamRetro In summary, TeamRetro has been instrumental in our agile adoption process and has helped us achieve our mission of ending homelessness. > ***Our team is more engaged and productive, and we look forward to conducting retrospectives each week.*** We highly recommend TeamRetro for any organization looking to improve their agile adoption process. Thanks to our writer – [Fernando Baghe](https://es.linkedin.com/in/fernandobaghe/en) – Agile coach and certified scrum trainer. --- # Agile retrospectives and team health: expert insights URL: https://www.teamretro.com/case-studies/industrial-logic/ Conversations around agile can often be centered on the Scrum framework, with its scheduled meetings and defined roles. However, as agile philosophy continues to mature, is this spotlight shifting? In this interview, Full-Stack Agile Coach [Jon Fazzaro](https://www.industriallogic.com/people/fazzaro/) addresses that question and more. Things kick off with a bang as Jon challenges relying solely on Scrum as a launchpad for agility. Instead, he advocates for a more organically agile approach. As the discussion unfolds, the retrospective takes center stage, and the role of the coach is examined. Last of all, insights into agile team health are shared along with invaluable advice when it comes to supporting your team. Let’s dive in! ## An evolving perspective on scrum *I’ve read your piece on Medium* [*The Retrospective is the Heartbeat of the Project*](https://medium.com/yesterdays-weather/the-retrospective-is-the-heartbeat-of-the-project-45a8aa2027bd)*. Do you still think that’s the case or would you say that there’s something that’s more important that should be considered now?* Since writing that piece, I’ve definitely moved past thinking Scrum is the best way to start being agile if you’re not already. I’m going to steal a metaphor that the head of our company, [Joshua Kerievsky,](https://www.industriallogic.com/people/joshua/) shared a while ago in a talk that he did. When you’re learning to ride a bike, you have training wheels. At least, that’s the way most kids do it; they have little training wheels bolted onto the side of their bike. What they learn to do first is to pedal. So, when you take the training wheels off, the first thing they do is fall down. They don’t realize that they have to pedal forward. They haven’t learned to balance. There’s an alternative way of teaching kids to ride a bike. It’s called a balance bike. It’s very simple. It doesn’t even have pedals. It’s bike-shaped, with two wheels and a seat. And you just tell them to walk; walk their way along and see if they can scoot and maintain their balance. That’s the better way to teach a kid to ride a bike. Balancing is the thing that’s hard, not pedaling. In the same way, Scrum is the most common way for teams to say ‘OK, we need to get agile, let’s go ahead and adopt Scrum’. Then they go ahead and bolt their Scrum training wheels on. They say ‘these are the meetings, these are the roles, and this is what we do’. Unfortunately, in practice, Scrum doesn’t do enough. Don’t get me wrong. On paper the guide is very good. It’s got a lot of very good ideas. But Scrum doesn’t tend to do enough to teach a team what it really needs to be agile. ## The role of retrospectives in agile teams *With your position on Scrum and its relationship to agile having evolved, what about the retrospective?* I still believe it’s important to stop working and talk about how you’re doing the work. I think that’s the most important thing. I like the idea of having more frequent retrospectives. To turn the heartbeat up. The team doesn’t have to do an intense, two-hour retrospective every day. Instead, maybe if you took a half an hour each day at a certain point that remains, a heartbeat. You might discover things sooner that are important. Rather than waiting two weeks to fix ‘the thing’ and amassing a backlog of ‘other things’ to cover, the team can address it almost immediately. Frankly, that’s more agile. Rather than batching it up and waiting. *What could that regular, possibly faster heartbeat mean to the management team of an organization?* Ostensibly that they care about the fact that the team is healthy, and performs at a predictable rate. As the people minding the business that teams serves, they want to be able to rely on that team to produce what they need in order to meet their business goals. If a team is not regularly meeting and tuning itself in, that team might become unpredictable. They might have had a stellar week because everybody put in extra hours, but they are burned out. Then they just create bugs and nonsense for the three weeks following. So that’s what I would care about in a management position. I think that there is a really great deal of value in knowing that. ## The agile coach and effective retrospectives *What indicators, not necessarily data, could a Scrum Master be looking for given not all of them have a development background?* Well, in the retrospective, a Scrum Master is fundamentally their coach. If we apply a sports metaphor, usually a coach is somebody who is an expert in the game. Maybe a former player. To be useful, they have to take the stance that they can’t help the players by playing themselves. The person running the retrospective has to step outside the content of the conversation. They have to look more at the contour of the conversation. So, it could actually be of benefit if they don’t understand certain things being discussed because those things could be a distraction. It could take their focus away from watching how the team is interacting. Let’s say somebody keeps getting talked over. That’s where the coach could step in. They can help to try and adjust the conversation. While the content of the conversation belongs to the people having it, sometimes the mechanics of it go wrong. You need somebody there who’s only watching how it’s happening. They can be nudged into ‘playing’ better with each other. *They are helping to make sure that ‘play’ is optimized?* Yes. *If they want to take things up a notch, what could the coach be doing?* Well, the phrase that comes to mind is ‘holding space’ from Open Space Technology. Holding Space is its own job. That’s what a facilitator of retrospective would be doing whether they are a coach or a Scrum Master, whatever their title. That role of facilitating the conversation. You’re not in the content, but you’re creating the container, and watching the contour of the conversation. That entails communicating how you’re going to have the conversation. You’ve arranged for the prompts for that conversation. You’ve set the boundaries. It takes a lot of design work. In my experience, when a retrospective doesn’t go well, usually the thing that’s lacking is that the person facilitating it hasn’t taken the time to design it. They are just kind of winging it. That’s not useful. What’s useful is for them to establish a time box, say 10 minutes. When that time box is up, they’re not fluffy about it, they’re firm. ‘OK, we’re done talking about that, it’s time to make a decision and move on’. *So those parameters are really quite important to make it an effective space. What have you observed go wrong that a simple fix could have addressed?* In terms of retrospectives, the common mistake is to say, ‘let’s have a wide-open conversation’. Then the group goes on to talk about whatever is on their mind. While that’s an important thing to do in some spaces, you really want to get punctuated value out of the time that’s put aside for a retrospective. Remember, we’re not working on the work. We’re working on the team. We’re working on how we work. The thing that often gets skipped, on the way to discussing how we felt about what happened, is establishing *what actually happened*. Making sure that everybody in the room has a similar mental model of what we’re talking about. So, an alignment. A calibration of ‘do we agree on the facts?’ Often, for me, a handy device to help do this is to take a few minutes and have the team establish a timeline of what happened. Draw a horizontal line on a board and start putting down notes on it. ‘Early in the sprint this happened, then there was this’. This works against any recency bias. They’re not just going to think about the things that have happened in the last day or two, or hour or two. This is important especially if it’s a two-week iteration, or one month or longer. There are a lot of things you won’t remember. Giving them time to actively remember is really helpful. There might be parts of the team that didn’t feel the same or didn’t remember things as strongly. They might have heard about something, but they weren’t involved. So it paints a picture for them that’s a little more holistic and shared. From that point, once the team agrees on what happened, then they can talk about what that means and how they feel about it and what could be better. *Amnesia can be addressed first.* Or just completely different points of view. Completely different mental models of what happened can be addressed before the retrospective starts. So, imagine the alternative. Going right into talking about, ‘was that good or was that bad?’ You have people with their own versions of what happened in their head. Those stories are all completely different. It means the words that they use to describe things are going to be completely inappropriate from the other person’s point of view. There’s going to be no connection. No insight can come from that. ## Agile teams as living systems: exploring the metaphor *Now to tap even further into your mastery of the metaphor. If the retrospective is the heartbeat, what’s the team?* It’s a system. A body of organs working together. Doing different jobs. It’s trying to keep going, to grow, to learn. It’s trying to be healthy. *That does segue, really nicely, into the topic of team health. Have you ever encountered a team that is dysfunctional but effective? There are high functioning people who have real issues.* Sure, they are getting through their day. That’s the phrase though, ‘getting through it’. If you get through something, you know there’s probably something that’s difficult that healthier people don’t find difficult. There are missed opportunities. This takes us back to predictability. I would think that one of the most devastating things about having a serious health condition is how unpredictable that would make my life. I couldn’t, really reliably, make any plans because I don’t know if I’m going to suddenly fall over. I might need an ambulance and go to the hospital. There goes my week. I think that’s the thing about health and the health metaphor. You are putting in this extra effort to improve things so that the world becomes easier. In my own, personal experience, I’m kind of terrible when it comes to exercising and maintaining a routine. But there have been periods in my life where I’ve been good at it for a few months. I would do something kind of minimal. Say, 10 push ups every day. And I’ve been good at that for a long stretch. When I’ve been good at that, my keenest observation about how I feel is that not that I feel bigger or stronger. But I feel like the world got easier. Difficulty is turned down. That smoothness. That ease of movement when you’re healthy. That’s why I think that’s what you’re going for with a team when you tune it up properly. The effect that has on the people that the team is doing work for is that team is predictable, like a clock, it’s reliable, you know? There’s an idea from Tim Ferriss’ The 4-Hour Body of minimum effective dose. You don’t have to be in Olympic shape, it’s the minimum to have a positive effect. What’s the minimum that we can do to have an effect, a positive effect on the team. Which is enough in many cases. ## Symptoms of a healthy agile team *What could someone facilitating a retrospective look for to gauge the health of their team?* Well, they should definitely see decisions being made. The scenery changes on the healthy team. They are tweaking. They are adjusting. They are experimenting freely. Responsibility doesn’t lie at an individual level. It lies with everybody. There’s sort of this blameless atmosphere of, ‘hey, that didn’t go so well’. They might identify that somebody did something and it caused a problem, but you wouldn’t say ‘when you did that, that really screwed everything up, and what are you going to do to fix that? It’s more, ‘what can we do better to react to that?’ You know the responsibility belongs to the whole team, even when it’s one person’s actions that might have caused something to go wrong. In general, there’s a notion of blamelessness. They handle conflict well. A go-to symptom of a good team is that they are not quiet — they complain. Because they have a bedrock-safe atmosphere in which they feel able to bring up the things that bother them. ## A final pearl of agile wisdom *With 30 seconds to go and no forewarning, what’s your ultimate pearl of wisdom for any person embarking on an agile endeavor?* Stop to retrospect before you need to. A lot of teams will only meet about the thing once it becomes a problem, and well, it’s easy to skip the retrospective when it feels like everything is fine. If you have done that, you haven’t inspected closely and discovered the thing that might cause us a problem. Weeks from now or days from now. ## Thank you! A huge thank you is extended to [Jon Fazzaro](https://www.industriallogic.com/people/fazzaro/) for participating in this interview. Jon is a Full-Stack Agile Coach, and has been in software development for over twenty years. He is a hands-on advocate for modern agile practices like ensemble programming, test-driven development, and daily collaboration with stakeholders. He is also a strong proponent of Lean Product Management and Systems Thinking. Jon has been a regular speaker at software conferences since 2015. You can head to [“Oh! The Humanity.”](https://youtu.be/qYV_eWNl8vQ?feature=shared) a close-up of his current professional thinking. --- # Making team health visible to create transparency in agile teams URL: https://www.teamretro.com/case-studies/infi/ A happy and healthy agile team can impact their ability to deliver high-quality software and meet customer needs. The question of course is how do you know if your team is happy? How do you keep on top of this and how can you track team happiness over time? An agile team health check can be a simple tool that lets you pick the key dimensions (or criteria) of health that matters most to the organization. Spotify, Atlassian, Google are just some of the companies that share their health check models and help to popularize this concept. [Infi](https://infi.nl/), a Dutch software company, used TeamRetro to shape their own health check model that used a range of dimensions specific to their values, culture, team goals and organizational requirements. Based on this set of criteria, this crew of developers initially ran verbal meetings in which each person responded to their model each week. However, this can be hard to track efficiently so they went to the next level. Capturing this information with an agile team health check tool meant that they could capture that data quickly. They then used TeamRetro’s API to build their own API that displayed their health check data on their office TV screens. This meant that the data was always visible and highlighted the organization’s commitment to supporting happy, productive teams. Here, Software Developer Martijn Groeneveldt, shares their story… and their link to Github so you can try out the dashboard for yourself. ## Why does your software development team use health checks? Our team runs health checks because we are a company that truly believes in caring for our employees. We believe that in the software development and consultancy business, human factors can make the difference between ‘okay’ and ‘awesome’. That’s why we run weekly check-ins. They are a good way to check whether there are things we can do, or do differently, so individuals are able to do their jobs to the best of their ability. ## What health check dimensions did you use to measure team happiness? We chose to continue with a model we were using for verbal check-ins before we started using TeamRetro. Our health check model consists of the following six factors – (translated from Dutch) ### Stress Do you experience stress or busyness in your life? ### Fun Do you have fun in what you do? ### Impact Do you have the feeling that you’re making an impact for the client or Infi? ### Colleagues How does the collaboration with colleagues and clients go? ### Technology Is the technology you are working with (still) fun and interesting? ### Process Are the processes that should make everything run smooth working as intended, or do they get in your way? ## How does TeamRetro support your health checks? By using the TeamRetro health checks to have weekly team meetings, team members consistently respond to the same prompts. This way they don’t accidentally forget or leave things out. Using TeamRetro also means team members can write down their thoughts ahead of the weekly team meeting. We also can produce a nice statistics graph of all health checks done the previous periods. We then display this on our screens so that our team can see it as needed. *(Example as shown – data is for illustrative purposes only and is not reflective of Infi)* -  -  ## What are the benefits of making your agile metrics visible? Having the data visible means you also have the ability to make better decisions, reduce decision latency and ensure that any issues are addressed as soon as possible. This suggests that transparency is [crucial to agile](https://www.linkedin.com/pulse/what-transparency-why-crucial-agile-khojiforagile/). While most teams can focus on the quantitative aspect of burn down charts, velocity points and error rates, having your team’s health check clear and upfront is a great way to put people in the picture too. With special thanks to [Martijn Groeneveldt](https://github.com/dutchmartin), software developer at Infi, you can access their code for the dashboard here: [TeamRetro Health Dashboard](https://github.com/dutchmartin/TeamRetroHealthDashboard). Want to run your own health check? Here are a [few models ready to go](/health-check-templates/), or you can create your own. --- # Mitrais Software Development — supporting sprint retrospectives with TeamRetro URL: https://www.teamretro.com/case-studies/mitrais/ Having everyone in a team be able to think about ways to improve and contribute is essential for any successful agile project. This is just as true of the humble retrospective. It’s at this point in time that having a team being able to reflect on the last sprint, feel like they are being heard, and contribute to delivering value to the next sprint can help deliver value to the project. We share the experience of software development services company Mitrais and how they provide both value to clients and to their team when they tried out TeamRetro. Rommy Rempas, the Competency Development Manager at Mitrais, emphasizes the importance of open collaboration in his team’s sprint retrospectives. He notes that “it is the time for their voice to be heard,” and that using a tool like TeamRetro has helped his team feel more comfortable sharing their thoughts and ideas. By fostering an environment of open collaboration, Rommy’s team has been able to identify issues and improve their processes more effectively. The Competency Development Group have been implementing Scrum at Mitrais since 2014 and took about a year before teams were familiar enough with the transition in order to implement projects without waiting for requirements to be baselined. With this in mind, Rommy shared that success meant that ”the team is able to improve their skills while delivering the product and meeting the expectations of the stakeholder”. He went on to say that the teams have found more success through Scrum. The short iteration to release gives the team more opportunity to grow and learn based on periodic feedback, improving productivity and the team being able to better adapt to dynamic requirements. ## Adding value with sprint retrospectives The role of the sprint retrospective is important to Rommy’s team. The event gives his team the chance to reflect, learn from both their failures and successes, and then shape improvements. Rommy has found the action items generated through the meeting particularly useful. Rommy’s tip when encountering a team who are not engaging with the retrospective is to focus on the benefits it offers. “I would coach the team. After all, without the retro, the benefit of having an incremental release could be lost. With each release, the team usually improves its capability and performance. The retro gives them this opportunity to reflect and improve.” In addition to open collaboration, it is important to use tools that support a safe and engaging meeting. This can help ensure that all team members are able to participate fully in the retro and contribute to its success. Tools like TeamRetro provide a predefined workflow that helps guide the team through the retro process and ensure that everyone is on the same page. ### “My team members enjoy doing the retro. It is the time for their voice to be heard. Using a product like TeamRetro helps a lot, especially since it has a predefined workflow that helps the team with their retro process.” ## Engagement leads to buy-in and overall team happiness When team members are engaged and feel like their opinions and ideas are being heard, they are more likely to be invested in the success of the project and their work. Rommy notes that his team members enjoy participating in retrospectives because it gives them the opportunity to be heard. By creating an environment of open collaboration and using tools that support engagement, Rommy’s team has been able to improve their experience of a team running a retrospective. This increased engagement has also led to improved team happiness, which has had a positive impact on the overall success of the project. ## Tips for better retrospectives If a team is struggling to follow through on their actions, Rommy’s advice is that support is the key. “Proper management support could be necessary to help the team to improve”. While ideally each team should feel empowered to get things done, sometimes there is still a need for management to provide the tools, or the nudge to get things done. Having a clear outcome and a shared definition of done is also important. A team needs to understand that work in progress does not bring value and that the goal is to deliver value in a timely manner at the right quality. “We may also coach the team. It is important, for example, for everyone to commit to a Definition of Done (DoD) that is shared by the team. A DoD that is outside of team capability will become an issue.” In terms of inviting people outside the team to sprint retrospective, Rommy has an inclusive approach. “If it’s relevant, why not?”. Having people outside the team from time to time provide useful insight, feedback and perspectives that can add to the team’s energy and bring new ideas to the retrospective. His final piece of advice when it comes to sprint retrospectives? ### “Just enjoy the process, retrospectives are fun.” ## Who is Mitrais? Mitrais has two lines of business – software development and software product services. Based in Indonesia, they offer a full range of software development capabilities including Microsoft, mobile, web, Java and more. Their product services cover the deployment and support of leading software products targeting the mining sector. These activities are backed by best-in-class human capital management systems and an integrated engagement model. --- # How Moneybox boosts squad health, performance and happiness URL: https://www.teamretro.com/case-studies/moneybox/ A squad health check is a regular survey of critical areas that make a team efficient, proficient, and happy. By creating an opportunity for members of the squad to safely reflect on those critical areas and provide their feedback, the health checks support their continuous improvement. They identify areas in need of development, and track the success of the treatments that are applied. [Moneybox](https://www.moneyboxapp.com/) is a UK-based fintech company offering an award-winning app designed to help people achieve their financial goals. To date, their app has over a million users who have the option to invest, save or plan for their retirement. When Moneybox implemented a system of squads to optimize their value delivery to users, they also introduced a way to optimize their health and performance. They did this with squad health checks. Moneybox needed a way to deliver their customized squad health checks simply, efficiently and effectively; they chose TeamRetro. Head of iOS, Valerio Bettini, shares their TeamRetro story. ## Who we are At Moneybox, we value our company culture. We strive to ensure that our team members enjoy their work and that they have the necessary tools and processes to deliver the best features. We recently reorganized our cross-functional teams into Squads. These are dedicated delivery teams focused on specific feature areas. It became apparent that we needed a tool to monitor and assess the health of each Squad. One that would evaluate the different aspects that make the team happy, efficient, and proficient. ## Our TeamRetro experience To address this need, we developed customized templates that cover a range of areas critical to Squad health. We quickly realized that using TeamRetro would provide the ideal platform to conduct health checks and assess the success of each squad. ### “We found that organizing health checks was easy.” TeamRetro allowed us to customize the assessment to monitor the aspects that were most important to our company. These areas include: - Mission - Ownership - Velocity - Delivering value - Suitable processes - Communication - Team roles - Support and resources - Work in harmony - Technology ***Team health radar using random data created for illustration purposes only*** After just one iteration of the squad health checks, we began to see positive results. We recognized the need to revisit some of the processes in use and better define the roles within the Squads. Specifically, we noticed a lower score on two particular dimensions identified by using TeamRetro. This allowed us to take proactive action and support the team. We now hold a health check every two months. We organize an interactive session to discuss the anonymous feedback received. This provides an opportunity to create action points that can be assigned to people directly using the interface provided by TeamRetro. Overall, using TeamRetro to conduct Squad health checks has been a game-changer for us at Moneybox. ## Using health checks to support our squads The history of health checks is also valuable. We can make comparisons with past assessments and understand if our actions and changes brought an improvement in scores. The reports allow us to compare the different squads with one another, identifying similarities and differences. ### “By using this platform, we have been able to identify areas where improvements are needed and take the necessary steps to ensure that each Squad is performing at its best.” We now have a system in place that allows us to regularly assess the health of each Squad and take action to improve any areas that need attention. By doing so, we are creating a culture of continuous improvement that ensures that our team members enjoy their work and that our customers receive the best features and products possible. Thanks to our writer – [Valerio Bettini](https://www.linkedin.com/in/vbettini/?originalSubdomain=uk), an iOS developer since 2009. Valerio is a product-minded, user-focused, accomplished team leader with a vast portfolio of published iOS apps. He is currently the Head of iOS at Moneybox, the company that has delivered a multi-award-winning app of the same name. --- # Inside Planted: how retros power purpose-driven teams URL: https://www.teamretro.com/case-studies/planted/ [Planted](https://www.planted.green/) is the Sustainability Transformation Platform for mid-sized companies. Founded in 2021 in Germany, the fast-growing team of 50+ employees across Cologne, Berlin, and remote locations helps organizations make ESG transformation simple, measurable, and impactful. At its core, Planted believes sustainability doesn’t begin with CO₂ reports or ESG strategies—it starts with people. When teams collaborate effectively, share feedback openly, and reflect together, they can accelerate the change our planet urgently needs. Co-founder and COO [Heinrich Rauh](https://www.heinrichrauh.de/), who brings years of experience leading cross-functional teams across Europe, helps guide Planted’s mission to connect collaboration with sustainability. ## The challenge: growing teams, growing complexity As Planted scaled, so did the complexity of its work. With employees spread across multiple cities and working remotely, the company faced three big questions: 1. How to create a clear feedback loop between Product, Sales, and Sustainability teams? 2. How to make sure remote employees feel included and heard? 3. How to ensure retrospectives don’t turn into routine checkboxes, but drive real change? ## The solution: retrospectives with TeamRetro Since 2024, Planted has been using TeamRetro to structure retrospectives in a way that is efficient, inclusive, and motivating. The platform has helped the company professionalize its feedback culture and strengthen collaboration across borders. What Planted values most about TeamRetro: - Structured workshops: Every retrospective follows a clear flow – saving time and creating focus. - Inclusive feedback: Remote and introverted team members contribute equally. - Actionable outcomes: Insights are turned into concrete tasks immediately – no more “lost notes.” > ***“TeamRetro has been a real game-changer for us. Our retros are not only more productive but also enjoyable. Most importantly, we can see how feedback translates directly into product improvements and better processes.”*** > ***– Heinrich Rauh, COO & Co-Founder of Planted*** ## Measurable results Using TeamRetro, [Planted](https://www.planted.green/) has already seen tangible improvements: - Faster product development: Feedback from retros feeds directly into the backlog – reducing time from idea to implementation. - Higher team satisfaction: Anonymous surveys show a consistent team happiness score above 8/10. - Greater transparency: Challenges are surfaced early, long before they become blockers. ## Sustainability meets new work For [Planted](https://www.planted.green/), retrospectives aren’t just a team ritual—they are the foundation of its sustainability mission. By ensuring collaboration, inclusion, and accountability, TeamRetro helps Planted align people with purpose and make ESG transformation scalable. Both Planted and TeamRetro share a common belief: that lasting transformation starts with effective collaboration—whether in tackling climate change or improving daily teamwork. ## Building sustainable growth through collaboration With TeamRetro, Planted found not just a tool but a trusted partner that strengthens feedback culture, builds alignment, and lays the foundation for sustainable growth. Because only when teams stay aligned can a mission like *“securing the future of all life on Earth”* truly succeed. Just as sustainability isn’t a one-time project but a continuous journey, effective retrospectives build habits that sustain teams through growth and change. Join teams like Planted who are building a better future. [Run your next retrospective with TeamRetro](/) and see how better retrospectives drive sustainable growth. --- # How Reward Insight uses TeamRetro to measurably increase their agile maturity URL: https://www.teamretro.com/case-studies/reward-insight/ [Reward Insight](https://rewardinsight.com/) is a London-based company specializing in loyalty technology and marketing solutions, helping businesses enhance customer engagement and drive growth. Founded in 2001, the company uses advanced analytics to deliver personalized offers and loyalty programs for leading retailers and financial institutions across 20 countries. With a strong focus on innovation and customer connection, Reward Insight continues to shape the future of loyalty programs globally. [Rick Collins](https://uk.linkedin.com/in/rick-collins-a435141b3) is a seasoned Scrum Master and Agile Coach with over 15 years of experience in team facilitation, release coordination, and agile transformation. Currently serving at Reward, he supports global expansion initiatives and system modernization. Previously, Rick spent over a decade at Allstate Northern Ireland, honing his expertise in release management and technical leadership. With a background in architectural technology, Rick combines a unique blend of technical and collaborative skills to drive team success and deliver impactful results. As a Scrum Master at Reward, Rick’s focus is on fostering an environment that maximizes productivity and team well-being. Reward specializes in delivering innovative loyalty solutions for sports and retail industries, underpinned by Agile methodologies that promote adaptability and continuous improvement. TeamRetro has become an invaluable tool in their journey to optimize teamwork processes. As Rick shares “*As a Scrum Master at Reward, I’m deeply committed to optimizing teamwork processes. My focus is on fostering an environment that maximizes both productivity and team well-being. To continuously improve is paramount, and TeamRetro has been an invaluable tool in this journey.*” Here’s their story… ## Challenges faced before TeamRetro Prior to adopting TeamRetro, Reward faced several challenges. Rick explains, “*Company-wide, our Continuous Improvement initiatives faced challenges due to a lack of consistency in how we gathered and implemented improvements. Each team adopted its own unique process, resulting in a fragmented approach and inconsistent outcomes.* *At the team level, driving engagement and ensuring all team members’ feedback was considered proved challenging. The use of anonymous whiteboards in remote meetings often led to passive participation, as some individuals felt less inclined to actively contribute*.” > *Driving engagement and ensuring that all feedback is received has proved challenging across teams.* ## Discovering TeamRetro The recommendation to trial TeamRetro came from a Development Manager with prior experience using the platform. Not relying on hearsay alone, Reward wanted to conduct their own due diligence. “*The Agile Delivery Group conducted thorough research and were highly encouraged by many aspects of TeamRetro, as it demonstrated strong potential to complement and enhance our existing Agile practices*.” Rick explains. ## How TeamRetro supports Reward’s agile framework Reward’s Agile framework incorporates elements of Scrum, Kanban, and Scaled Agile, all rooted in the principle of continuous improvement. Rick describes how TeamRetro supports this, “*The platform’s ability to facilitate the rapid creation of retrospectives and health checks enables us to establish baselines and drive incremental improvements with greater efficiency.*” ## Outcomes achieved with TeamRetro Using TeamRetro, Reward has achieved several significant outcomes. By establishing a baseline at the start of the year and re-evaluating using the same health checks, Reward gained a clear understanding of its progress, demonstrating an increase in Agile maturity. Scheduled generation of boards ensures retrospectives are aligned with team cadence, enabling live feedback without delays. Real-time board updates remove the need for screen-sharing in meetings, promoting openness and anonymity. AI-driven grouping of feedback saves time and adds efficiency, while themed retro boards add an element of fun and engagement. “*With the assistance of TeamRetro, we have achieved a measurable increase in our Agile maturity. By establishing a baseline at the beginning of the year and then re-evaluating using the same Health Check at the end, we gained a clear and quantified understanding of our progress.” Rick says.* Reward’s team members appreciated the simplicity of the platform and its engaging features, such as emojis and GIFs, which made retrospectives enjoyable and interactive. Real-time updates encouraged honest and anonymous feedback, fostering an open and collaborative environment. *“We have found the recent enhancements to the embedded AI to be highly beneficial. Being able to quickly and intuitively group feedback live in a retrospective saves a lot of time. Team Members also appreciate the fun brought via the themed retro boards”, Rick elaborates.* ## Advice for running effective retrospectives Rick emphasizes the importance of consistency by using recurring templates to keep retrospectives a regular part of the workflow. Having retro boards always available encourages teams to reflect and contribute continuously. Customization of settings ensures sessions remain engaging and prevents them from becoming stale. Reviewing action items at the start of each session helps close feedback loops and ensures accountability. Rick’s Retro Tip – “*Create a recurring template from your favorite Retro Board and use this to generate a new board at the end of every retrospective period. This means a retro board is always available for thoughts and feedback. Having continual access to a retro board, then encourages the team to give feedback and reflect continuously.* *With a plethora of customizable settings, you can tweak each board to stop your retrospectives from becoming stale and uninteresting.”* ## Transform your retrospectives today with TeamRetro Reward’s experience highlights how TeamRetro can empower teams to enhance Agile practices, boost engagement, and achieve measurable improvements. Make your team’s retrospective meetings become even more effective and insightful. **[Join TeamRetro today and discover the difference!](https://secure.teamretro.com/login/new?redirectUrl=https%3A%2F%2Fsecure.teamretro.com%2F)** --- # Introduction to RoleModel Software: pioneers in custom software solutions URL: https://www.teamretro.com/case-studies/rolemodel-software/ [RoleModel Software](https://rolemodelsoftware.com/), with over 25 years in custom software development, serves industries like healthcare and manufacturing. Known for their dedication to quality and craftsmanship, their team includes skilled developers and designers at all experience levels. Guided by values of character, collaboration, and craftsmanship, [RoleModel Software](https://www.linkedin.com/company/rolemodel-software) is committed to excellence as it builds solutions that enhance client operations and stand the test of time. Their commitment to continuous improvement drove them to seek tools that enhance their processes and empower their teams to deliver high-quality software. Mitch Fernandez is an executive leader with over 25 years of experience in strategic planning, technology management, and innovation across diverse sectors, including technology, government, and biotechnology. Known for driving operational excellence and strategic growth, Mitch excels at leading large, complex organizations and fostering a culture of continuous improvement. With a forward-thinking approach and a talent for bridging technical and non-technical communication, he is recognized for his integrity, vision, and collaborative leadership. Here is their story… ## The challenges of a growing, innovative agile team Before adopting TeamRetro, we faced several challenges that prompted us to seek out a better solution for our retrospectives and team health tracking. First, we wanted to ensure consistency across all our projects by conducting regular retrospectives, ideally one every two weeks. Retrospectives are critical to our process, as they allow us to reflect, learn, and improve, but ensuring this cadence across all teams was a challenge. In addition, we were looking for a way to gather meaningful metrics about project health. Collecting team feedback through a structured, reliable, and insightful process was key for us, and we needed something that could handle this systematically. > ***TeamRetro’s Team Health Check feature allowed us to run quick surveys, providing a pulse on how our teams felt about aspects like communication and workload.*** Another significant factor was cost. We wanted a solution that provided all the features we needed but at a more competitive price compared to other tools we had evaluated. Finding a tool that was cost-effective without sacrificing functionality was important for us as a company with multiple projects and team members. **Moreover, we wanted a tool that was engaging and enjoyable to use, not just another checkbox in the process.** Retrospectives should allow teams to express their thoughts openly; a dull or cumbersome tool could inhibit participation. > ***TeamRetro’s interactive and intuitive design made the retrospective process both fun and insightful, enhancing team engagement.*** Finally, **ease of use—both internally and with our customers—was a top priority**. We needed a tool that was simple enough for our internal teams to adopt without extensive training, but also easy for our clients to interact with during joint retrospectives. TeamRetro struck that balance by offering an interface that was accessible to all, from project managers to external stakeholders. This user-friendly experience encouraged full participation and made our retrospectives more effective overall. In summary, our primary challenges were maintaining consistent retrospectives, collecting valuable team metrics, finding a cost-effective and user-friendly solution, and ensuring the tool was fun and easy to use for both internal teams and customers. TeamRetro addressed all of these challenges seamlessly. ## Discovering TeamRetro: a feature-rich, cost-effective solution We discovered TeamRetro through a simple Google search. At the time, we were using another tool for our retrospectives, but we found that it didn’t align with our budget over the long term. We needed a solution that offered similar functionality but at a more affordable price, especially as our team scaled. This led us to TeamRetro, which immediately stood out due to its more cost-effective pricing plans. Cost wasn’t the only factor, though. One of the things that really impressed us was how TeamRetro matched—and in some cases exceeded—the features we were accustomed to. We were pleased to find that TeamRetro offered the same key capabilities for running retrospectives, including structured templates, anonymity options, and easy-to-use interfaces. It gave us everything we needed without having to sacrifice any of the functionality we had come to rely on. Beyond the tool itself, *TeamRetro’s customer support played a big role in our decision*. From the very beginning, their team was responsive, attentive, and willing to listen to our specific needs. In fact, after we started using the tool, we made a feature request, and not only did TeamRetro take it seriously—they actually implemented it. This level of customer care and responsiveness is rare and was a significant factor in solidifying our decision to not only stick with the tool but also to upgrade our plan to take advantage of even more features. > ***We chose TeamRetro because it was cost-effective, packed with all the features we were used to (and more), and backed by excellent customer support.*** The responsiveness of their team, especially in implementing customer feedback, made us feel like we were more than just users—we were partners in the development of a tool that continues to help us improve our retrospectives. ## Tailoring TeamRetro to the RoleModel way of working Our process for retrospectives is structured, methodical, and designed to ensure that we get the most out of every session. While we already had a process in place before adopting TeamRetro, the tool has not only supported this process but has also enhanced it in meaningful ways. We begin each retrospective with a custom 10-question health check. This has become a crucial part of our process because it allows us to take a snapshot of team morale, project challenges, and general well-being at the start of each session. The health check results are seamlessly transformed into project metrics that align with the historical data we’ve collected, giving us a way to track progress over time and identify areas that may need attention. TeamRetro’s built-in health check feature has been an invaluable tool for collecting this information efficiently. While we initially enjoyed using the icebreaker feature to help team members feel comfortable and ease into the retrospective, we’ve recently opted to streamline our meetings and have paused using this feature. That said, we found the icebreakers to be excellent, and we may consider reintroducing them in the future as time permits. The core of our retrospective is where TeamRetro really shines. We like to mix things up, so we regularly switch between different retrospective templates to keep things fresh and engaging for the team. > ***The flexibility of rotating through different templates keeps retrospectives fresh and engaging, tailored to our team’s evolving needs.*** TeamRetro offers a wide variety of retrospective templates, so it’s easy to find something that fits the specific needs of each session. Whether we want to focus on what went well, opportunities for improvement, or even more creative approaches, the tool provides plenty of flexibility. Once we’ve selected a template, we begin by spending 5 minutes allowing each team member to write down their comments, with anonymity maintained to ensure everyone feels comfortable sharing openly. TeamRetro’s anonymity feature is crucial for fostering honest feedback and participation. Afterward, we move into a comment-grouping phase. While the team is free to group comments manually, ***we often take advantage of the AI-driven feature that helps organize related comments quickly and accurately*** This has been a huge time-saver for us. Next, we spend a few minutes voting on which topics to prioritize for discussion. The voting feature in TeamRetro allows us to quickly identify the most pressing issues. Once the voting is complete, we focus on the top three topics, discussing each for around five minutes. The built-in timer helps us stay on track, but we allow flexibility if the team agrees that a particular topic requires more time. While some team members find the timer a bit loud and obnoxious, we’ve taken a lighthearted approach to this. We’ve turned it off for the most part but occasionally use it when we want to gently nudge people into finishing quickly. It’s become more of a running joke within the team, and we’ve adapted our use of it to suit our style. During these discussions, we use reactions and comments to engage further and add action items in real-time. This way, we can immediately begin to address the issues raised during the retro. At the end of the retrospective, we review the action items we’ve created and then rate the retrospective itself using TeamRetro’s built-in rating feature. We conclude by downloading the session summary as a PDF and sharing it directly to the project’s Slack channel, ensuring that everyone stays informed and accountable. Something we’ve recently identified as an area for improvement is reviewing open action items at the start of each retro. While we haven’t been consistent in doing this, we plan to experiment with it to close the feedback loop more effectively. > ***TeamRetro provides a structured yet flexible framework that aligns perfectly with our process, making our retrospectives smoother and more productive.*** The tool’s customizable templates, AI-driven features, and integration with our communication channels have made our retrospectives smoother, more productive, and more engaging for everyone involved. ## Results: improved team dynamics, cost savings, and client transparency Our team has experienced several key benefits from using TeamRetro that have improved both the retrospective process and our overall workflow. One of the most important benefits we’ve seen is the consistency in how we collect project health metrics. By using the health check feature at the start of each retrospective, we now have a clear and regular way to track key indicators across all of our projects. This has made it easier to spot trends, identify potential issues early, and ensure that we stay on top of the overall health of our teams and projects. > ***Rather than just identifying problems, we’re now consistently coming up with ways to address them, which has increased the effectiveness of our retrospectives.*** Next is the ease of use. This means that no time is wasted figuring out the tool, and everyone can focus on sharing valuable insights and feedback. The fact that TeamRetro serves as a shared platform has also been a significant advantage. It creates a central hub for our retrospectives, where all team members can contribute, see each other’s feedback, and stay aligned on action items. This shared space ensures consistency and keeps everyone on the same page, both during the retrospectives and afterward, as we review progress. Retrospectives have also become a powerful platform for problem-solving. We frequently use these sessions to identify challenges, brainstorm potential solutions, and then put those solutions into action. This proactive approach has led to measurable improvements in our projects and processes. Rather than just identifying problems, we’re now consistently coming up with ways to address them, which has increased the effectiveness of our retrospectives. Additionally, TeamRetro has had a positive impact on team dynamics. Although our team doesn’t typically have a lot of grievances or complaints, the retrospectives have created a safe and open environment where everyone feels comfortable sharing their thoughts and challenges. Team members know their voices will be heard and that their concerns will be taken seriously. This has fostered a culture of trust and transparency, which is vital to maintaining a healthy and productive work environment consistent with our core values. > ***The ability to identify and address problems in real-time has been a standout benefit with TeamRetro, making our retrospectives proactive and action-focused.*** Having a dedicated space for tracking and referencing action items means that nothing is forgotten or overlooked. Team members can easily revisit these items in subsequent retrospectives, ensuring accountability and follow-through. > ***The feedback from both team and leadership on TeamRetro has been overwhelmingly positive, especially for its cost-effectiveness and user-friendly experience.*** We have encountered a few minor technical issues, such as when two people try to update the title for a group of topics simultaneously, this creates a conflict. That said, these issues are rare and haven’t significantly disrupted our workflow. TeamRetro’s robust features have allowed us to navigate these minor hiccups with ease, and we’re confident that future updates will only improve the experience. The platform has also helped to enhance team camaraderie. We use retrospectives not just to tackle problems but also to celebrate our successes. TeamRetro gives us the opportunity to congratulate ourselves when things go well, and we even engage in some friendly teasing, which lightens the mood and makes the retrospectives something the team looks forward to. This balance between addressing serious topics and having fun has made the retros more engaging and has brought our team closer together. On the more positive side, one feature that everyone loves is the ability to use reactions. It’s a simple but effective way for the team to engage during discussions, adding a layer of fun and interactivity to the retros. It’s these small touches that make the retrospectives more engaging and dynamic, helping to break up the more serious discussions with moments of levity. Leadership, in particular, has been pleased with the results. They are glad to see that we’re conducting retrospectives on a regular basis and that we’ve been able to do so in a cost-effective manner. The consistency of the retros, enabled by TeamRetro, has provided valuable insights into our projects and teams that leadership appreciates. From a customer perspective, TeamRetro has given them insight into how we work and has provided a valuable opportunity to address any problems they’ve encountered. > ***Including customers in our retrospectives through TeamRetro has strengthened our client relationships by fostering a collaborative and transparent atmosphere.*** This level of transparency has strengthened our relationships with clients and has fostered a collaborative atmosphere where both parties work together to continuously improve the project. Looking ahead, we aim to build on these successes by continuing to refine our process and deepen our engagement with both our teams and our customers. We’re excited about the possibilities that TeamRetro offers and are confident that it will continue to play a crucial role in helping us achieve our goals of consistent improvement, stronger collaboration, and a more engaged team. Overall, TeamRetro has helped us streamline our retrospectives, promote transparency, and ensure that problems are addressed promptly, all while keeping the process simple and efficient for everyone involved. ## Advice for teams When it comes to running retrospectives and health checks, my top piece of advice is to establish consistency. Teams may initially resist frequent retros, but once it becomes a habit and part of the standard approach to project management, people not only get used to them, they sometimes even start looking forward to them. Retros become an opportunity for team members to share their thoughts openly and get things off their chest, knowing they’ll be heard. One area of mixed feedback has been the frequency of the retrospectives. Some team members question whether having retros every two weeks is necessary, especially when there isn’t much to discuss. However, leadership and I agree that the regular cadence is valuable. Even on quieter weeks, having the retrospective on the calendar ensures that we’re ready to address issues when they do arise, and it creates a sense of preparedness across the team. The key is to make retrospectives a regular occurrence, not something you run only when issues arise. If you’re always waiting for a reason to hold a retro, you’ll end up reacting to problems rather than proactively managing your projects. Having a consistent cadence helps you stay ahead of potential issues and fosters continuous improvement. To keep things fresh, take advantage of the features that TeamRetro offers. Using Icebreakers and reactions adds an element of fun, which helps teams engage more fully. Respect team members’ privacy by keeping comments anonymous; this encourages more open and honest feedback. At the same time, make sure to guide the team on the purpose of the retrospective—it’s not just for addressing problems but also for celebrating wins and accomplishments. Don’t be afraid to mix things up by rotating through different retrospective templates. If you have a specific reason to use a particular template, go for it—but also familiarize yourself with the options so you can keep the retros interesting and aligned with your team’s needs. Creating custom templates and health checks tailored to your organization is another way to ensure the retros are meaningful. By asking the right questions, you can generate insights that matter and help your teams grow. It’s also essential to stay consistent with health checks. By using the same set of questions across projects, you’ll be able to compare results over time, identify trends, and truly gauge how your teams and projects are evolving. And don’t forget about the importance of internal and customer-facing retrospectives—both play a valuable role. For internal retros, consider setting up a separate team to keep sensitive discussions private. We use one team for all of our internal retros to save on costs, but this setup works well for us, as we can still maintain confidentiality. Lastly, take full advantage of TeamRetro’s integrations, like Slack, to share results efficiently. Always share the findings from each retro and health check with the team—it keeps everyone informed and accountable. If you ever need to close a team, be sure to export and download your results for historical reference, so you don’t lose valuable insights. > ***Consistency, engagement, and variety are the keys to running successful retrospectives with TeamRetro, leading to meaningful improvements in our projects.*** ## Make the switch to TeamRetro today RoleModel Software’s experience demonstrates how TeamRetro can help teams enhance their retrospective process, engage participants, and streamline project health tracking—all while staying budget-friendly. If you’re ready to see how TeamRetro can make a difference for your team, start your journey with TeamRetro today. **[Try TeamRetro today to transform your retrospectives!](https://secure.teamretro.com/login/new)** --- # How Sympower charged ahead with TeamRetro as their preferred retrospective tool URL: https://www.teamretro.com/case-studies/sympower/ [Sympower](https://sympower.net/ "Sympower website") is a transformative company that empowers commercial and industrial energy users to build sustainable energy systems. As a B-certified company, its goal is to increase sustainability, cost reduction, and grid stability around the world. Sympower is a company defined by its people and culture, with a shared vision of a truly sustainable world. Specializing in demand response and energy flexibility solutions, Sympower helps balance the grid and integrates renewable energy sources. As part of its commitment to continuous improvement, Sympower has adopted TeamRetro to streamline processes and foster a culture of collaboration and growth. Fred Puistaja is an accomplished Engineering Manager at Sympower where he has demonstrated his expertise and leadership for over 6 years, moving up through pivotal roles. His previous manager and teammate described him as having a keen eye for data quality, with continuous improvement embedded in his heart and brain, and as a cool life hacker! Fred shares why TeamRetro is the preferred retrospective tool. “We are a software team and company. We were looking for tools to help us better run our retrospectives and needed features that would help improve the way our meetings were run.” For us, this meant things like: - You didn’t need to mess with stickies - You could write down action items and track them - You could hide all ideas before discussing - You could color ideas by the author - You could generate a summary of the retro We found that TeamRetro had these features and also a well-structured way of doing retros. The other tools didn’t have all of these features in one. We run our bi-weekly retrospectives in our Scrum teams, so having the right agile retrospective meeting tool is important. Some of our non-engineering teams also use TeamRetro on occasion. Having good retrospectives means we can get fast feedback from our sprints. Small improvements each time help us fine-tune our processes. One of the aspects that we really enjoy is that it also allows us to have retrospectives with minimal effort from the facilitator. It allows the team to focus on the task at hand because it is just easier. It’s great that it also allows us to share the summary easily with other teams and team members. It reduces the facilitator’s workload, which means they can be more effective and helpful for the team. Team members could also fill in their ideas beforehand, and privately – without showing them to everyone else already. This means the input is unbiased and can be in their own time. You can also schedule recurring retros. One of the benefits of using TeamRetro is that it allows you to create and track actions right next to the retro (and idea) itself, so you can see where the reason for the action came from. One of the cons or areas for improvement would be that during the presentation stage, when we are going through ideas, those ideas can be sorted by topic, and by person. This would allow us to go through topic areas first, rather than by most voted which is the default. **TeamRetro Feature Update:** Great feedback Fred. And good news! This feature is now live so you can sort by topic and person in the presentation phase! Overall, our team says our retros are now more organized, which allows us to have fast feedback cycles on how we are working. As a piece of advice for teams, it’s important to always aim to create a safe environment to share feedback in order to get the most out of your retrospectives. — Thanks for your feedback Fred. We hope to help you and your teams continue to run amazing and worthwhile retrospectives! --- # Scrum Master creates happy, empowered agile teams through health checks and AI-powered retrospectives URL: https://www.teamretro.com/case-studies/trendminer/ It’s always appreciated when we get feedback from our clients; it’s their input that helps guide us as we learn, grow and evolve TeamRetro. Their stories are why we do what we do. We are delighted to share with you this piece written by Caitlin Whittaker, Scrum Master who shares her experience of supporting and empowering happy, productive and engaged agile teams. Overcoming the challenges of a global team, building consistency and cadence and having happy team members which boosts productivity are all part of the success points of this Scrum Master (and new mum!). Whether it’s using AI features to create engagement, having a consistent tool to run health checks to get a sense of how the team is tracking, through to goal setting and running futurespectives, Caitlin helps her teams continuously engage, improve and feel good about the work that they do. ## Choosing an online retrospective tool for global teams The path leading to TeamRetro started when I needed a way to consolidate retros when my teams started expanding globally. I was also looking for a way to easily implement a team Health Check on a regular basis so that we could monitor how the teams were feeling as we evolved as a company and product. *“Developers are some of the most highly intelligent problem solvers you will ever be fortunate enough to work alongside, and my one goal for all my teams is their contentment.”* As I was also about to take leave to deliver a mini human being, I wanted a solution that would allow my teams to maintain consistency and continuity. I am not a fan of disruptions so having a solution where the teams could continue with all the prior history and action points already available and accessible was invaluable. ## Creating happy, healthy and productive teams Developers are some of the most highly intelligent problem solvers you will ever be fortunate enough to work alongside, and my one goal for all my teams is their contentment. This may sound cheesy but it is the key to unlocking the greatest productivity in teams. Happy, motivated teams are productive teams and also as a result long-term employees. Individuals and teams are most productive when they feel heard, understood and motivated which is why we hold retrospectives on a regular basis at the end of each sprint cycle. Essentially the impact of retros in an Agile framework should lead to continuous improvement but this is hard to measure on a broader scale. This is where I have found TeamRetro invaluable both as a tool to consolidate the retros from my teams and monitoring sentiment and the feelings of the team. ## Using team feedback to improve team health With TeamRetro, pain points can easily be identified. We can also see if this is a common theme across the teams and consequently a deeper underlying issue which needs resolving or specific to a certain team. Improvements can then be monitored in the future to make sure that we’ve really made a change that is valuable or if we are not quite there yet. As companies and processes evolve, there will always be areas which require attention and with TeamRetro we can consolidate all feedback and allow the teams to also be involved in constructive action points to move forward on. ## Adaptable, fun, and open retrospectives and futurespectives Because TeamRetro is so adaptable, I have also used it for goal-setting and ‘futurespectives’ for the teams. Setting goals for what teams want to achieve in a certain time frame and keeping the action points visible so that we can focus on achieving, looking forward and committing to making it happen. ## Using AI to generate retrospective themes The new AI feature has also been fantastic in keeping retrospectives fun and open. Teams really enjoy coming into a retro where it is based on current affairs. I have used themes such as Wimbledon, NFL and Barbie. Using this to create a more relaxed atmosphere has led to some very insightful retros and consequently positive change and improvements for the teams. — Thanks Caitlin. We wish you and your teams, and the new bub all the best. Thanks for sharing your story. --- # Making retrospective meetings productive: Trigama's success story URL: https://www.teamretro.com/case-studies/trigama/ ## Introduction to Trigama: a leader in custom IT solutions Trigama International s.r.o. is a dynamic IT company specializing in developing custom-made applications for its diverse clientele. With a commitment to creativity and technological excellence, Trigama leverages advanced methodologies to deliver innovative solutions that meet specific client needs. Václav Nidrle serves as the Managing Director and CTO of Trigama. With a keen eye for innovation and a strategic approach to leadership, Václav has been instrumental in steering the company toward growth and adapting to new challenges, particularly in the realm of remote work. ## Challenges of remote scrum retrospectives at Trigama Trigama’s development teams operate using the Scrum methodology, necessitating regular retrospective meetings. Initially, these meetings were conducted on-site, but the onset of COVID-19 and the company’s growth led to an increase in remote work. This transition posed challenges, including lack of preparation for retrospectives and inefficiencies during meetings. “Our development teams are working using Scrum methodology. We used to do retrospective meetings on-site in our office, but the growth of Trigama and the onset of COVID-19 caused much more remote workers in our team,” says Václav. ## Finding the perfect tool: why Trigama chose TeamRetro In search of a user-friendly tool to streamline their retrospectives, Trigama found TeamRetro. “We were looking for an easy-to-use tool that will help us with organizing retrospectives,” explains Václav. The platform’s intuitive interface, pre-meeting preparation features, and capability to drive actionable steps made it an ideal choice for the company. “We liked TeamRetro being intuitive, its help with preparation of points to discuss in advance, and also that it pushes the team to make action steps about each problem being discussed.” TeamRetro became integral to Trigama’s retrospective meetings, allowing the teams to prepare discussion points in advance and manage the meeting agendas effectively. This tool supported the teams in maintaining structured and productive retrospectives, crucial for continuous improvement. “As said before, the retrospective meeting is the crucial process. We have used TeamRetro to prepare and manage retrospective meetings for our development teams,” Václav adds. ## Key benefits of using TeamRetro for Scrum Masters and teams The implementation of TeamRetro led to significant improvements in meeting efficiency and team confidence. The ability to prepare points beforehand and the tool’s ease of use meant that even without a Scrum Master, the teams could conduct retrospectives smoothly. “It helps the team to go through the retrospective process even without Scrum Master presence, it gives confidence to the team and even new team members in going through the process,” Václav highlights. This resulted in more focused discussions on team and project issues, rather than on meeting logistics. - Enhanced meeting efficiency and time management. - Increased team confidence, even among new members. - Structured and standardized outcomes from each retrospective. - Reduction in the dependency on the Scrum Master for facilitating meetings. The team at Trigama found TeamRetro to be an intuitive tool that significantly improved their retrospective meetings. “Intuitive tool,” Václav says simply but effectively. > By leveraging TeamRetro, Trigama successfully navigated the challenges of remote work, enhancing their retrospective meetings and overall team productivity. Explore TeamRetro to see how it can benefit your organization. ## Advice for Scrum Masters “Try TeamRetro to see the benefits it can bring to your teams,” recommends Václav Nidrle. Ready to transform your retrospective meetings? Discover how TeamRetro can help your team work more efficiently and effectively.**[ Get Started with TeamRetro Today!](https://secure.teamretro.com/login/new?cc=TeamRetroBlog)** --- # Supporting Typewise's distributed team with online retrospectives URL: https://www.teamretro.com/case-studies/typewise/ ## Introducing Typewise’s smartphone keyboard app Typewise logo [Typewise](https://typewise.app/) is a Switzerland based tech startup company focused on a vision of enabling a digital world that respects user privacy. The company has developed a next generation AI-powered smartphone keyboard app for [iOS](https://apps.apple.com/us/app/typewise-keyboard/id1470215025) and [Android.](https://play.google.com/store/apps/details?id=ch.icoaching.wrio&hl=en) Janis Berneker is the CTO and Co-Founder of Typewise. He leads the product development with three distributed team sections – design, app development and AI development. ***“The smartphone keyboard is today’s most important human-machine interface, used 76x per day on average across all kinds of apps. However, 70% of users are dissatisfied with many typos on their smartphones.”*** ***“Over 1 billion people have installed third-party keyboard apps that promise to make typing easier. The caveat: these apps require the permission to transmit everything the user types on their phones. Consequently, 77% of users are concerned that their keyboard records everything they type.”*** ***“Typewise solves this problem through its revolutionary, patented hexagon layout, making the keys wider and easier to hit. Typewise also learns where the user exactly hits the keys and adapts itself automatically thanks to AI.”*** ## The challenge of a distributed team Typewise smartphone keyboard app Typewise began full-time work on their app in October 2019. The startup recently completed a successful fundraising campaign which allowed them to build their team. Typewise’s team of ten people – including its CEO, CTO, UX designer, marketers, app developers and AI engineers – are located in Zurich but many of them work partially or remotely on this project. ***“Since we’re a start-up I have several roles with the most important being product manager but also many other roles like scrum master and part-time developer.”*** ***“In my previous job I learned how powerful Scrum and Retros in particular can be. There the whole team worked on-site though.”*** ***“However, at Typewise part of our team works completely remotely. So communication and regular feedback loops are even more important.”*** To ensure that regular, engaging and effective retrospectives happen, Janis started looking for an online retrospective tool that would complement the distributed team working environment at Typewise. ## Online retrospectives for Typewise’s distributed team In trying to find an online retrospective solution for his distributed team, Janis tried many different solutions available. However, he found that most of them lacked a good user experience (UX). ***“Since online retros are already less convenient than offline ones, UX was a crucial factor for us.”*** ***“When we tried*** [***TeamRetro***](/)***, it worked much more smoothly than other online retrospective solutions we tried.”*** ***“That is why we decided to go for TeamRetro.”*** ## TeamRetro’s Health Check and agile retro tools Typewise started using the [Team Radars and Health Check](/health-checks/) feature of TeamRetro to track the satisfaction of its whole team. Team health check results, courtesy of Typewise. The team would then conduct a [full online retrospective](/retrospectives/) with one of the available templates. TeamRetro templates range from [Agile Retrospectives,](/retrospective-templates/agile-retrospective/) [Anchors and Engine](/retrospective-templates/anchors-engines-retrospective/), [Four Ls](/retrospective-templates/4ls-retrospective/), [Start, Stop, Continue](/retrospective-templates/start-stop-continue-retrospective/) or create your own custom online retrospective. FLAP retrospective activity template format example ***“My experience is that it’s good to change between the templates because they often provide different perspectives, which can be very helpful.”*** ***“Online retrospective with TeamRetro helps people to communicate issues early and also to learn to think about how to improve the product or processes proactively.”*** ## Positive work and culture outcomes for a distributed team By using TeamRetro for their online retrospectives, Janis has indicated that it has helped develop a positive team and work culture at Typewise. The Team Radars and Health Check has also empowered Janis and his management team to assess the level of happiness within the startup. ***“TeamRetro has helped us establish an open feedback culture where everyone is at eye level, and increased happiness.”*** Being able to run online retrospectives has also meant that Typewise’s distributed team members don’t feel like they are missing out on one of the important team activities of providing feedback, assessing performance and creating actions for improvements. ***“TeamRetro has also helped to encourage exchange between the different teams, as all team members participate in the same Retro.”*** ## Try TeamRetro Are you and your team or organization looking to conduct remote retrospectives and team health checks? Whether you have a partially remote, fully remote or hybrid work environment, TeamRetro can help to make sure that your important retros run efficiently and in an engaging manner. [Try it FREE today for 30 days](https://secure.teamretro.com/login/new/) --- # University of Wollongong used TeamRetro as an agile training tool URL: https://www.teamretro.com/case-studies/university-of-wollongong/ [The University of Wollongong](https://www.uow.edu.au/) (UOW) is known for its commitment to excellence in education, research, and innovation. With a focus on equipping students with practical skills and real-world experience, UOW integrates innovative technologies and evidence-based practices to elevate student learning and foster real-world problem-solving skills. One such initiative involved integrating TeamRetro, an agile retrospective tool, to help students improve collaboration and address group challenges early in their projects. [Dr. Sie](https://scholars.uow.edu.au/rory-sie), a senior lecturer at UOW, shared how TeamRetro has supported his teaching practices. His work focuses on the practical application of Generative AI and large language models (LLMs), with a particular interest in tackling challenges like scalability, reliability, cost-efficiency, and security in AI deployment. He also supervises capstone group projects, guiding students as they collaborate on real-world solutions and gain hands-on experience. Here’s his story… ## The challenge: addressing group dynamics in student projects Before using TeamRetro, Dr. Sie observed a recurring issue in group projects: students were unfamiliar with reflecting on their group process. This lack of structured reflection meant group challenges only became apparent at critical moments—usually when assignment deadlines loomed or after submission reviews. By the time these challenges surfaced, resolving them became difficult, often affecting group performance and outcomes. Dr. Sie realized the need for a tool to help students reflect and address issues earlier in their group work. ## Discovering TeamRetro: bridging education and industry practices Dr. Sie was already familiar with TeamRetro from his previous role, where it had proven highly effective for the teams he supervised. Confident in its value, he decided to introduce the tool to his students at UOW. “I thought it could work for students as well, and it gave them an opportunity to utilize a tool that is widely used in the industry,” Dr. Sie explained. By incorporating TeamRetro, he provided students with a practical learning experience while helping them adopt a reflective mindset essential for collaboration and problem-solving. *”We used TeamRetro on a large scale at my previous employer and it worked great for the teams that I supervised. I thought it could work for students as well, and it gave them an opportunity to utilize a tool that was being used in industry.”* ## Implementing agile practices with TeamRetro Dr. Sie adopted an agile approach in supervising group projects, incorporating TeamRetro’s group retrospectives to help students reflect on their progress and processes. The retrospectives encouraged open discussions and action-oriented thinking, allowing students to identify challenges and solutions early in the session. > *“By using TeamRetro, students were able to reflect on group processes and identify actions early, helping them solve group challenges quickly.”* Starting early allows teams to uncover insights and set a strong foundation for collaboration and continuous improvement. Dr. Sie shared a practical tip for those facilitating retrospectives: *“Run retrospectives as quickly as possible after you form a new team or group, so you can quickly identify opportunities to improve the team process.”* ## Key outcomes and benefits of using TeamRetro as a training tool By using TeamRetro, students at UOW achieved several significant outcomes: **Early Problem Identification**: TeamRetro helped students reflect on their group dynamics and identify potential challenges early. **Collaborative Problem-Solving**: Students worked together to define clear actions for improvement, fostering teamwork and accountability. **Self-directing groups**: Dr. Sie found that students became more self-sufficient in resolving group challenges, reducing the need for his direct intervention. **Real-World Experience**: Students gained exposure to industry tools and practices, preparing them for future careers. The feedback from students was positive, with many noting how helpful the tool was in improving their group process and collaboration. ## The impact of TeamRetro The University of Wollongong’s experience with TeamRetro demonstrates how agile retrospectives can transform group collaboration in an educational setting. By introducing TeamRetro, Dr. Sie provided students with a structured approach to reflection, enabling them to solve challenges early and improve their overall experience in group projects. For educators and team leaders looking to enhance group dynamics and promote continuous improvement, TeamRetro offers a practical, user-friendly solution that delivers meaningful results. [Try TeamRetro today](https://secure.teamretro.com/login/new) and see how it can empower your team to reflect, adapt, and grow. --- # WWE Smackdown Showdown Retrospective URL: https://www.teamretro.com/retrospective-templates/wwe-smackdown-showdown-retrospective/ Step into the ring and turn your team reflection into a main-event spectacle with the WWE Smackdown Showdown Retrospective. Inspired by the high-energy world of professional wrestling, this playful format reframes your sprint review as a championship bout — celebrating signature moves, calling out the heavy hitters that pinned your progress, tagging in fresh ideas, and crowning the champions who carried the team. It's a fun, gamified twist that re-energizes teams who may be feeling retro fatigue. This retrospective works by guiding your team through four wrestling-inspired prompts, each capturing a different angle of the sprint. Participants share what went well (Signature Moves), what knocked them down (Body Slams), what new tactics to try (Tag-Team Plays), and who deserves recognition (Championship Belt). The familiar theatrics of the squared circle lower the barrier to honest conversation, making it easier for quieter members to step up and for everyone to engage with both wins and setbacks. Beyond the laughs, the goal is genuine continuous improvement. The format keeps psychological safety high while surfacing real blockers, actionable experiments, and meaningful kudos. Run it in TeamRetro to keep the momentum going with anonymous contributions, grouping, voting, and clear action items — so your team leaves the arena ready to defend its title next sprint. ## Topics - **Signature Moves**: What went well and what should we keep doing? - **Body Slams**: What knocked us down or slowed us this sprint? - **Tag-Team Plays**: What new ideas or experiments should we try next? - **Championship Belt**: Who deserves recognition and a shoutout this sprint? ## When to use - When your team has retro fatigue and needs a fun, themed format to re-energize reflection. - After an intense or high-pressure sprint where celebrating wins and recognizing effort will boost morale. - For team-building sessions where you want to lower barriers and encourage everyone to speak up. - When you want a lighthearted way to surface blockers without anyone feeling blamed. ## Tips and tricks - Lean into the theme — use wrestling sound effects, entrance music or fun visuals to set the energy, but don't let the gimmick overshadow real takeaways. - Keep the 'Body Slams' section blameless. Focus on situations and systems, not individual wrestlers, to protect psychological safety. - Time-box each round so the session stays punchy and doesn't go into overtime. - Make sure quieter team members get a turn in the spotlight — use anonymous entries in TeamRetro to level the playing field. - Always convert 'Tag-Team Plays' into clear, owned action items so good ideas don't get left on the mat. - Don't skip the Championship Belt — recognition is often the most memorable and motivating part of the session. ## Icebreaker questions - If you had a wrestling entrance, what song would play and what would your finishing move be called? - Which fictional or real character would you tag in to help with your hardest task this sprint? --- # Working, Not Working Retrospective URL: https://www.teamretro.com/retrospective-templates/working-not-working-retrospective/ The Working Not Working retrospective is a straightforward yet powerful approach to team reflection that focuses on identifying what's effective and what needs improvement in your processes, projects, or team dynamics. This binary format helps teams quickly distinguish between successful practices and areas requiring attention. Originally popularized in agile environments, this retrospective format stands out for its simplicity and clarity. By creating a clear distinction between working and non-working elements, teams can easily prioritize their improvement efforts and maintain what's already successful. This format is particularly effective for teams who want to cut through complexity and focus on practical outcomes. It encourages honest feedback while maintaining a solution-oriented mindset, helping teams identify both positive patterns to replicate and challenges to address. ## Topics - **What is working?**: What is going to plan? - **What is not working?**: What is not going to plan? ## When to use - When you need a quick, clear assessment of team processes and practices - During periods of change to identify which new approaches are effective - When the team feels overwhelmed and needs to simplify their reflection process - To gather straightforward feedback about recent changes or implementations ## Tips and tricks - Keep the focus on actionable items rather than vague complaints or praise - Encourage balanced participation by asking quieter team members to share their perspectives - Use dot voting to prioritize which non-working items to address first - Create specific action items for addressing 'not working' items before concluding - Document working practices so they can be replicated and standardized - Schedule follow-ups to review progress on addressing non-working items ## Icebreaker questions - What's one thing that made your work easier this week? - If you could instantly fix one thing about our current process, what would it be? --- # Quarterly Retrospective URL: https://www.teamretro.com/retrospective-templates/quarterly-retrospective/ The Quarterly Retrospective is a structured, Agile-aligned team reflection designed for the rhythm of a three-month cycle. While sprint retrospectives zoom in on short iterations, the quarterly format gives teams the breathing room to step back and assess broader patterns — what's been working across multiple sprints, where systemic blockers have emerged, and how the team's goals align with the bigger organisational picture. It's the ideal cadence for teams who want to honour Agile principles without the noise of reviewing every two-week sprint in depth. Rooted in the core values of the [Agile Manifesto](https://agilemanifesto.org/), this retrospective encourages continuous improvement at a strategic level. Teams examine their wins, challenges, and evolving processes over a longer horizon, making it easier to spot trends that shorter retrospectives might miss. By reflecting quarterly, teams can make more meaningful, lasting changes rather than reactive micro-adjustments — fostering a culture of genuine learning and sustainable improvement. Whether you're a cross-functional product team, an engineering squad, or a leadership group, the Quarterly Retrospective helps you celebrate progress, address recurring pain points, set intentions for the next quarter, and strengthen team cohesion. Running this in TeamRetro ensures every voice is heard, ideas are captured in real time, and action items are tracked through to completion — making your quarterly review both efficient and impactful. ## Topics - **What went well?**: What achievements or practices made this quarter a success? - **What didn't go well?**: What obstacles, frustrations, or failures held the team back this quarter? - **What did we learn?**: What key insights or lessons has the team gained this quarter? - **What will we do differently next quarter?**: What concrete changes or experiments will the team commit to next quarter? ## When to use - Use a Quarterly Retrospective at the end of each three-month cycle to reflect on broader trends and patterns that shorter sprint retrospectives might miss. - It's ideal when your team wants to align their continuous improvement efforts with quarterly planning or OKR review cycles. - Run a quarterly retro when recurring issues keep surfacing in sprint retros but never seem to get fully resolved — the longer lens helps identify root causes. - Use it to re-energise and realign a team after a particularly intense or challenging quarter, giving space to acknowledge effort and reset intentions. - It's especially valuable for distributed or remote teams who benefit from a dedicated, structured moment to connect and reflect at a strategic level. ## Tips and tricks - **Review your sprint retros before the session.** Spend a few minutes before the quarterly retro scanning themes from the past sprints. This helps you spot recurring patterns and come prepared with data-backed observations rather than relying purely on memory. - **Timebox each topic.** With a broader scope than a sprint retro, conversations can easily run long. Allocate time per topic (e.g. 10–15 minutes each) and use TeamRetro's facilitation tools to keep the session on track. - **Prioritise ruthlessly.** A quarter generates a lot of material. Encourage the team to vote on the most impactful items rather than trying to discuss everything. Focus on the top 3–5 themes for deeper conversation. - **Ensure psychological safety.** Quarterly retros can surface bigger, more sensitive issues. Set clear ground rules at the start — this is a blame-free, solutions-focused space. Consider using anonymous idea submission to encourage candour. - **Assign clear owners to action items.** The longer time horizon of a quarterly retro means action items can easily get forgotten. Make sure every commitment has a named owner and a target date, and review them at the start of the next quarter. - **Don't skip the celebration.** It's easy to jump straight to problems, but acknowledging what went well over a full quarter is powerful for team morale and motivation. Start with wins before diving into challenges. ## Icebreaker questions - If you had to describe this past quarter as a weather forecast, what would it be and why? - What's one word that sums up how you're feeling heading into next quarter? --- # Baby Steps Retrospective URL: https://www.teamretro.com/retrospective-templates/baby-steps-retrospective/ Big transformations rarely happen overnight. The Baby Steps Retrospective embraces the philosophy that lasting improvement comes from small, manageable, and achievable changes rather than sweeping overhauls. By focusing on incremental progress, your team can build momentum, reduce overwhelm, and create habits that actually stick. This format is perfect for teams who feel stuck after committing to ambitious action items that never quite get done, helping them break improvement into bite-sized pieces that move them steadily forward. The retrospective works by guiding teams to reflect on where they are now, identify the smallest meaningful step they can take next, and rally support to make it happen. Instead of debating large structural changes, participants concentrate on practical, low-effort actions that deliver visible value quickly. This reduces friction, builds confidence, and reinforces a culture of continuous improvement where every small win counts. Over successive sprints, these baby steps compound into significant progress. The beauty of the Baby Steps approach lies in its accessibility and inclusivity — anyone can contribute, because no idea is too small. It pairs naturally with agile and Kanban ways of working, and is especially effective for newly formed teams, teams experiencing change fatigue, or those looking to make their retrospectives more actionable. By celebrating progress and keeping commitments realistic, teams stay motivated and focused on continuous, sustainable growth. ## Topics - **Where are we now?**: What is our current situation or starting point? - **What's the smallest step?**: What is one tiny change we could realistically make? - **What support do we need?**: What or who will help us take this step? - **How do we measure growth?**: What signal will tell us this step made a difference? ## When to use - Your team has struggled to follow through on large, ambitious action items and needs a more achievable approach. - A newly formed team wants to establish a habit of continuous improvement without feeling overwhelmed. - The team is experiencing change fatigue and needs to rebuild momentum with small, confidence-building wins. - You want to make retrospectives more actionable by focusing on concrete, low-effort next steps. - The team is adopting agile or Kanban practices and wants to embed incremental improvement into their routine. ## Tips and tricks - Keep the focus genuinely small — if a proposed step feels big, challenge the team to break it down until it's truly achievable in one sprint. - Limit the team to one or two baby steps per retrospective so commitments stay realistic and don't dilute focus. - Assign a clear owner to each step so accountability is shared and the action doesn't slip through the cracks. - Revisit previous baby steps at the start of each session to celebrate wins and reinforce the value of incremental progress. - Use dot voting in TeamRetro to democratically choose which small step the team tackles first, avoiding dominance by louder voices. - Frame the conversation positively — no step is too small, and every contribution counts toward building momentum. ## Icebreaker questions - What's the smallest habit change you've made that ended up having a surprisingly big impact on your life? - If you could take one tiny step toward a personal goal this week, what would it be? --- # SCOR Futurespective URL: https://www.teamretro.com/retrospective-templates/scor/ The SCOR Futurespective is a forward-looking strategic planning framework that helps teams analyze potential future scenarios by examining Strengths, Challenges, Opportunities, and Risks. Unlike traditional retrospectives that focus on past events, this technique encourages teams to anticipate and prepare for future situations. Developed as an adaptation of the classic SWOT analysis, SCOR specifically focuses on future-oriented thinking and scenario planning. Teams use this framework to identify their current strengths, acknowledge potential challenges, recognize upcoming opportunities, and prepare for possible risks. This approach is particularly valuable for teams entering new projects, planning strategic initiatives, or preparing for organizational changes. By systematically examining these four dimensions, teams can develop more robust action plans and better position themselves for future success. ## Topics - **Strengths**: What major strengths do we have? - **Challenges**: What difficulties or threats could we face? - **Opportunities**: What can we capitalize on based on our strengths? - **Risks**: What risks lie ahead and how can we reduce them? ## When to use - Before starting a new project or initiative to assess readiness and identify potential challenges - During strategic planning sessions to align team vision and prepare for future scenarios - When facing significant organizational changes to evaluate impact and preparation needs - Quarterly planning sessions to adjust strategy based on emerging trends and challenges ## Tips and tricks - Start with strengths to build confidence and create a positive atmosphere before addressing challenges - Use dot voting to prioritize the most important items in each category for focused action planning - Encourage participants to think beyond immediate timeframes and consider long-term implications - Create specific action items for each identified risk and opportunity - Document and review previous SCOR analyses to track how predictions and preparations played out - Keep the focus on actionable items rather than vague or unchangeable circumstances ## Icebreaker questions - If you could time travel five years into the future, what's one thing you'd want to know about our team/project? - What's one skill or capability you think will be crucial for our success in the coming year? --- # Marketing Team Retrospective URL: https://www.teamretro.com/retrospective-templates/marketing-team-retrospective/ Marketing moves fast — campaigns launch, content ships, metrics roll in, and before you know it the next quarter is already underway. The Marketing Team Retrospective gives your team the space to pause and make sense of it all. It's a structured session designed to help marketers reflect on what resonated with audiences, which channels delivered results, and where energy and budget could be better spent. By looking back with intention, your team can turn campaign data and lived experience into sharper, more confident decisions. This retrospective works by guiding the team through a focused conversation about campaign performance, collaboration, and creative output. Participants surface the wins worth repeating, the bottlenecks slowing delivery, the experiments worth scaling, and the lessons that should shape future planning. Because marketing spans many disciplines — content, brand, demand generation, social, design, and analytics — the format encourages cross-functional perspectives so everyone's view of the customer journey is heard. The result is a shared understanding of what's driving growth and what's getting in the way. Run in TeamRetro, this marketing retrospective keeps discussion organised, inclusive, and action-oriented. Ideas are grouped, prioritised, and converted into clear next steps, so insights don't evaporate the moment the meeting ends. Whether you're closing out a major product launch, wrapping a quarterly campaign cycle, or simply building a habit of continuous improvement, this template helps your marketing team learn faster and perform better together. ## Topics - **Campaigns that delivered**: Which campaigns or content performed best, and why? - **What slowed us down**: What blockers, bottlenecks, or friction held the team back? - **Experiments and learnings**: What did we test, and what did the results teach us? - **Ideas for next cycle**: What should we start, prioritise, or improve going forward? ## When to use - At the end of a major campaign or product launch to review what worked and capture learnings while they're fresh. - As a recurring quarterly or monthly check-in to keep the marketing team continuously improving. - When cross-functional collaboration between content, design, demand generation, and analytics needs to be reviewed and strengthened. - After a period of missed targets or process friction, to diagnose bottlenecks and agree on fixes. - When onboarding a new marketing initiative or rhythm and you want a shared baseline of priorities. ## Tips and tricks - Share key campaign metrics and dashboards before the session so the conversation is grounded in data, not just opinions. - Invite voices from across the marketing function — content, brand, design, demand gen, and analytics — to capture the full customer journey. - Keep feedback focused on campaigns, processes, and channels rather than individuals to maintain psychological safety. - Timebox each topic so you leave enough room to prioritise actions, not just gather observations. - Use anonymous brainstorming in TeamRetro to encourage honest input, especially about what slowed the team down. - Assign a clear owner and due date to every action so insights translate into measurable improvements next cycle. ## Icebreaker questions - What's the best piece of marketing — an ad, campaign, or post — you've seen from another brand this month? - If our team had a tagline that summed up this quarter, what would it be? --- # State of Nirvana Futurespective URL: https://www.teamretro.com/retrospective-templates/state-of-nirvana-futurespective/ The State of Nirvana Futurespective is a forward-looking retrospective format that helps teams envision their ideal future state and create a practical roadmap to achieve it. By working backward from a perfect end state, teams can identify concrete steps and milestones needed to realize their vision. This technique combines elements of backcasting and progressive goal-setting, allowing teams to break down their aspirational goals into manageable time-boxed achievements. Starting with the ultimate vision of success, participants collaboratively define what 'nirvana' means for their team and then plot the necessary changes and improvements across different time horizons. Originally inspired by solution-focused coaching techniques, this retrospective format helps teams maintain motivation by connecting daily work to longer-term objectives. It's particularly effective for teams feeling stuck in current patterns or those needing to align around a compelling shared vision. ## Topics - **Our definition of Nirvana**: The ultimate state we want to be in. - **1 month**: Things to do by month 1 - **3 months**: Things to do by month 3 - **6 months**: Things to do by month 6 - **10 months**: Things to do by month 10 ## When to use - When the team needs to align on long-term goals and create a shared vision for the future - During strategic planning sessions or when starting new major initiatives - When the team feels stuck and needs inspiration to break out of current patterns - Before undertaking large-scale transformation efforts ## Tips and tricks - Start by creating psychological safety - there are no 'impossible' ideas during the vision phase - Use timeboxing for each topic to maintain momentum and ensure all periods get adequate attention - Document concrete, measurable actions rather than vague aspirations - Review and adjust the timeline regularly as circumstances change - Keep the nirvana state visible and reference it in daily work to maintain focus - Consider external factors and dependencies that might impact the timeline ## Icebreaker questions - If you could instantly master one skill or technology, what would it be and why? - What's one thing you wish you could automate away in your daily work? --- # Easter Retrospective URL: https://www.teamretro.com/retrospective-templates/easter-retrospective/ The Easter Retrospective provides a meaningful framework for teams to reflect on themes of renewal, transformation, and hope. Drawing inspiration from the Easter story, this retrospective encourages participants to examine their journey of growth, celebrate victories, acknowledge challenges, and envision new beginnings. This reflective format helps teams identify areas where they've experienced renewal and transformation, while also highlighting opportunities for growth and positive change. The structure encourages honest dialogue about obstacles overcome, lessons learned, and aspirations for the future. Through this process, teams can develop actionable insights that lead to meaningful improvements and renewed commitment to their shared goals. ## Topics - **New Life**: What signs of renewal and transformation have you observed? - **Victory**: What obstacles or challenges have we overcome? - **Hope**: What opportunities for growth and improvement do you see ahead? - **Easter Eggs**: What unexpected discoveries or pleasant surprises have we encountered? ## When to use - During the Easter season when teams want to reflect on themes of renewal and transformation - When the team needs to focus on hope and new beginnings after challenging periods - To celebrate victories and growth while planning for future improvements ## Tips and tricks - Create a welcoming atmosphere that encourages open sharing about personal and professional growth - Use Easter-themed metaphors to help frame discussions about transformation and renewal - Balance reflection on past challenges with forward-looking hope and optimism - Ensure all team members feel comfortable participating regardless of their religious beliefs - Focus on practical actions that can emerge from the themes of renewal and transformation ## Icebreaker questions - What's something in your work or life that has recently been renewed or transformed? - Share a moment when you overcame a significant challenge and emerged stronger --- # Fostering an Inclusive Workplace Retrospective URL: https://www.teamretro.com/retrospective-templates/fostering-an-inclusive-workplace/ The Fostering an Inclusive Workplace retrospective is a structured activity that encourages teams to reflect on their diversity, equity, and inclusion (DEI) practices. It provides a safe space to share perspectives, identify areas for improvement, and develop actionable steps to cultivate a more inclusive and equitable work environment. This retrospective draws inspiration from the principles of psychological safety, empathy, and allyship. By openly discussing DEI topics, teams can deepen their understanding, challenge biases, and co-create strategies to foster a culture of belonging and respect for all. Ultimately, this activity aims to empower teams to embrace diversity as a strength, promote equitable opportunities, and ensure every voice is heard and valued, leading to enhanced collaboration, innovation, and overall team effectiveness. ## Topics - **Diversity Perspectives**: How well does our team embrace and leverage diversity? - **Equitable Opportunities**: How can we ensure fair and equitable opportunities for all? - **Inclusive Practices**: What inclusive practices can we adopt or improve? - **Psychological Safety**: How can we foster a psychologically safe environment? - **Allyship and Advocacy**: How can we become better allies and advocates? ## When to use - When you want to assess and improve your team's diversity, equity, and inclusion practices. - After noticing potential biases, microaggressions, or lack of representation within the team. - As part of regular team-building or culture-shaping activities to reinforce inclusive values. - When introducing new team members from diverse backgrounds to foster understanding and create a welcoming environment. - After organizational changes or initiatives related to DEI to align the team and gather feedback. ## Tips and tricks - Create a safe and judgment-free environment where everyone feels comfortable sharing their perspectives and experiences. - Encourage active listening and avoid interrupting or dismissing others' viewpoints, even if they differ from your own. - Be mindful of potential biases or assumptions, and approach discussions with an open and curious mindset. - Respect confidentiality and anonymity if requested, as some individuals may feel more comfortable sharing sensitive experiences privately. - Focus on actionable steps and solutions rather than dwelling on problems or assigning blame. - Follow up on the action items and commitments made during the retrospective to drive meaningful change. ## Icebreaker questions - If you could invite any historical figure to dinner, who would it be and why? - What's a skill or talent you possess that might surprise others on the team? --- # Weather Report Retrospective URL: https://www.teamretro.com/retrospective-templates/weather-report-retrospective/ The Weather Report retrospective uses weather as a powerful metaphor to help teams express their feelings and experiences about the work period. By associating different weather conditions with various aspects of their work environment, team members can communicate complex emotions and situations in an accessible, non-confrontational way. This technique encourages participants to think metaphorically about their experiences, making it easier to discuss challenging topics through the lens of familiar weather patterns. Team members can describe their experiences as 'stormy' for turbulent periods, 'sunny' for positive achievements, 'cloudy' for uncertain situations, or 'rainy' for challenging but necessary developments. Originally adapted from various agile practices, this retrospective format has become popular due to its intuitive nature and ability to facilitate open dialogue. It's particularly effective in multicultural teams where weather serves as a universal language for expressing emotions and experiences. ## Topics - **Stormy**: Turbulent - **Rainy**: Interruptive - **Cloudy**: Promising - **Sunny**: Cheerful ## When to use - When you want to encourage more emotional intelligence and awareness in team discussions - During periods of significant change or uncertainty to gauge team sentiment - To help teams who struggle with direct communication express themselves through metaphors - When you need a fresh approach to understanding team morale and satisfaction ## Tips and tricks - Encourage participants to explain why they chose particular weather conditions to represent their experiences - Use follow-up questions to explore how the team might 'improve the weather' in challenging areas - Consider tracking weather patterns over multiple retrospectives to identify trends - Allow team members to use multiple weather conditions if needed to express complex situations - Create a safe space where all weather reports are valid and accepted without judgment - Use the weather metaphor to discuss both team and organizational climate ## Icebreaker questions - If your perfect workday was a type of weather, what would it be and why? - What's your favorite kind of weather for being productive? --- # Project Kickoff Planning URL: https://www.teamretro.com/retrospective-templates/project-kickoff-planning/ A Project Kickoff Planning meeting is a collaborative meeting to align the team on the goals, scope, processes, and potential risks for an upcoming project. It provides a structured way to gather insights, identify challenges, and develop a shared understanding before execution begins. It starts by defining the project's objectives and success criteria. Then, the team brainstorms ideas across key areas like approach, timeline, resources, and risks. This fosters open discussion, surfaces diverse perspectives, and allows the team to create a comprehensive project plan. By conducting this exercise upfront, teams can proactively address potential roadblocks, leverage team members' expertise, and build a robust strategy to increase the likelihood of project success. ## Topics - **Project Goals**: What are the key objectives and success criteria for this project? - **Approach & Timeline**: What strategies, processes, and milestones should we follow? - **Team & Resources**: What skills, roles, and resources are needed for success? - **Risks & Constraints**: What potential risks or constraints should we plan for? - **Stakeholder Engagement**: How will we collaborate with stakeholders and get their buy-in? - **Success Measures**: How will we track progress and measure the project's impact? ## When to use - When kicking off a new project to align the team on goals, approach, and potential challenges. - After a project has been approved but before execution begins, to develop a comprehensive plan. - When there are significant changes to an ongoing project's scope, timeline, or resources. ## Tips and tricks - Encourage open and honest discussion by creating a safe space for all perspectives. - Assign a dedicated facilitator to keep the discussion focused and on track. - Use techniques like silent brainstorming to allow introverts to contribute ideas. - Prioritize and timebox discussions to ensure adequate coverage of all topics. - Capture action items and next steps, assigning clear owners and due dates. - Follow up the session with a documented project plan for team alignment. ## Icebreaker questions - If this project was a movie, what would be its title and tagline? - Share a past project experience, good or bad, that provided valuable lessons. --- # Air Travel Journey Retrospective URL: https://www.teamretro.com/retrospective-templates/air-travel-journey-retrospective/ Picture your last sprint or project as a flight. Every journey has its preparation on the ground, a thrilling takeoff, the occasional turbulence at cruising altitude, and (hopefully) a smooth landing at the destination. The Air Travel Journey retrospective borrows this familiar metaphor to help your team reflect on the full arc of a project, making it easy to surface what propelled you forward and what shook things up along the way. By mapping experiences onto distinct phases of flight, this retrospective encourages teams to think holistically rather than focusing only on the most recent events. The takeoff stage prompts reflection on momentum and starting strong, turbulence captures the obstacles and unexpected disruptions, cruising altitude highlights what kept things running smoothly, and the landing focuses on outcomes and how the team finished. This structure keeps conversations engaging and inclusive, giving quieter team members a clear, low-pressure framework to contribute. Ideal for agile teams, project groups, and anyone who enjoys a creative spin on the classic retrospective, the Air Travel Journey format turns reflection into a shared story. It builds psychological safety, sparks honest discussion, and helps teams agree on concrete actions to make their next journey even smoother — all within TeamRetro's collaborative environment. ## Topics - **Takeoff**: What gave us a strong start and momentum? - **Turbulence**: What disruptions or obstacles shook us up? - **Cruising Altitude**: What kept things running smoothly along the way? - **Landing**: How did we finish and what did we deliver? ## When to use - At the end of a sprint or project to reflect on the full journey from start to finish. - When you want a fun, metaphor-based alternative to a standard went-well/needs-improvement retrospective. - After a particularly bumpy or eventful delivery, to unpack what caused turbulence and how to avoid it. - When onboarding a team to retrospectives and you need an approachable, engaging framework. - To celebrate a successful launch while still capturing honest lessons learned. ## Tips and tricks - Set the scene by inviting the team to imagine the project as a flight — a strong metaphor makes contributions flow more freely. - Timebox each phase so the conversation moves steadily from takeoff to landing without getting stuck on turbulence. - Encourage specifics in the Turbulence section so blockers become clear, actionable improvements rather than vague complaints. - Keep the tone blameless — focus on the journey and the system, not on individuals. - Use grouping and voting in TeamRetro to surface the most impactful themes before agreeing on actions. - Capture concrete action items for the next 'flight' so the retrospective leads to real change. ## Icebreaker questions - What's the most memorable flight you've ever taken, and why? - If your last sprint were a flight, would it have been smooth, bumpy, or a white-knuckle ride? --- # Four Ls Retrospective URL: https://www.teamretro.com/retrospective-templates/4ls-retrospective/ The 4Ls stands for Liked, Learned, Lacked and Longed For and was initially developed by Mary Gorman and Ellen Gottesdiener. It is a simple and popular technique for scrum masters and their team to highlight the positives (liked and learned), as well as the negative (lacked and longed for) from both a factual and emotional perspective. This approach provides a balanced view of both positive experiences and areas for improvement. By exploring what team members liked and learned, the exercise celebrates successes and captures valuable insights. The 'lacked' and 'longed for' categories help identify gaps and opportunities for enhancement, creating a comprehensive picture of the team's experience. ## Topics - **Liked**: What did we like about the last sprint? - **Learned**: What did we learn from the last sprint? - **Lacked**: What do we think was missing from the last sprint? - **Longed for**: What could we have done better in the last sprint? ## When to use - When you want to maintain a balanced perspective between positive aspects and areas for improvement - During regular sprint retrospectives to gather comprehensive feedback about team performance and processes - When introducing new team members to retrospectives, as the format is intuitive and easy to follow - When the team needs structure to organize their thoughts and feedback effectively ## Tips and tricks - Start with the 'Liked' category to create a positive atmosphere before diving into improvement areas - Use timeboxing for each L to ensure balanced discussion across all categories - Encourage specific examples rather than general statements to make feedback more actionable - Look for patterns across categories to identify systemic issues or opportunities - Create action items that address the 'Lacked' and 'Longed for' feedback while maintaining what people 'Liked' - Consider using dot voting to prioritize which items to address first ## Icebreaker questions - If you could instantly master one new skill that would help the team, what would it be and why? - What's one thing you learned recently that surprised you? --- # Mission: Agile Possible Retrospective URL: https://www.teamretro.com/retrospective-templates/mission-agile-possible-retrospective/ Step into the world of secret agents with Mission: Agile Possible, a playful, espionage-themed retrospective that turns your team's reflection into a high-stakes mission briefing. Inspired by classic spy thrillers, this format invites team members to debrief their latest sprint as if they were field operatives reporting back to headquarters—identifying mission accomplishments, uncovering hidden threats, decoding obstacles, and planning their next covert operation. The themed framing adds energy and fun to the agile ceremony while keeping the focus firmly on continuous improvement. This retrospective works by guiding your squad through four mission-style topics that map neatly onto the proven structure of a sprint retrospective. Agents share what went according to plan, where the mission hit unexpected resistance, what intelligence they gathered, and what their next moves should be. By reframing familiar agile questions through a spy lens, teams often feel more comfortable surfacing candid feedback, celebrating successes, and naming risks that might otherwise go unspoken. Whether you're running a regular sprint review or simply want to inject some creativity into your team retrospectives, Mission: Agile Possible delivers an engaging, structured way to reflect and act. It's ideal for agile teams, Scrum Masters, and facilitators looking to keep retrospectives fresh, inclusive, and outcome-focused—turning each meeting into an actionable mission debrief. ## Topics - **Mission Accomplished**: What objectives did we successfully complete this sprint? - **Enemy Encounters**: What threats, blockers or obstacles did we run into? - **Classified Intel**: What did we learn or discover during this mission? - **Next Mission Briefing**: What actions and improvements should we plan for next time? ## When to use - When your regular sprint retrospectives have become routine and the team needs a fresh, energising format to re-engage. - At the end of a sprint or project milestone where you want a structured way to celebrate wins and surface blockers. - When you want to lower the tension around discussing obstacles by framing them in a playful, blame-free way. - For teams that enjoy themed ceremonies and respond well to gamified, narrative-driven facilitation. - When onboarding a new agile team and you want an approachable retrospective that still covers all the essentials. ## Tips and tricks - Lean into the theme—open the session with a 'mission briefing' framing to set the tone and get agents into character. - Keep the playful theme from overshadowing the substance; make sure every fun item still links back to a real, actionable insight. - Timebox each topic so the squad moves through the mission at a steady pace and leaves enough time for action planning. - Encourage quieter team members to contribute by reminding everyone that every agent's intel matters to the mission. - Group similar ideas together before voting so the team focuses discussion on the highest-impact threats and learnings. - Always close with clear, owned action items from the Next Mission Briefing so the retrospective drives real change. ## Icebreaker questions - If you were a secret agent, what would your codename and signature gadget be? - What's the most 'mission impossible' task you've ever managed to pull off at work? --- # Code Review Retrospective URL: https://www.teamretro.com/retrospective-templates/code-review-retrospective/ A Code Review Retrospective is a structured meeting where development teams reflect on their code review practices, identify areas for improvement, and implement actionable steps to enhance code quality and collaboration. During this retrospective, team members discuss their experiences with code reviews, sharing what went well, what could be improved, and any challenges or blockers they faced. The goal is to foster an open and constructive dialogue that leads to better code review processes, improved knowledge sharing, and higher-quality codebase. This retrospective activity is particularly valuable for teams practicing agile methodologies, as it aligns with the principles of continuous improvement and adaptation. By regularly examining their code review practices, teams can identify and address inefficiencies, strengthen collaboration, and ultimately deliver better software. ## Topics - **Effective Practices**: What aspects of our code review process worked effectively? - **Areas for Improvement**: What aspects of our code review process need improvement? - **Action Items**: What specific actions can we take to improve our code review process? - **Continuous Improvement**: How can we foster a culture of continuous improvement in our code review practices? ## When to use - When you want to improve the effectiveness and efficiency of your team's code review process. - After implementing a new code review tool or process and want to gather feedback and refine it. - When you notice recurring issues or bottlenecks in your code review workflow. - As part of a regular cadence (e.g., quarterly) to continuously improve your development practices. - When onboarding new team members to align on code review expectations and best practices. ## Tips and tricks - Encourage open and honest feedback, but maintain a constructive and respectful tone. - Involve team members from different roles (developers, QA, product owners) to get diverse perspectives. - Consider using anonymous feedback mechanisms to encourage candid responses. - Prioritize action items and assign owners to ensure follow-through. - Celebrate successes and improvements, no matter how small, to reinforce positive change. - Be prepared to adapt and iterate based on the feedback and insights gathered. ## Icebreaker questions - If you could add one feature to our code review tool, what would it be and why? - Share a memorable or humorous experience you've had during a code review (without naming names). --- # Budget Planning Futurespective URL: https://www.teamretro.com/retrospective-templates/budget-planning-futurespective/ The Budget Planning Futurespective is a forward-looking exercise that helps teams align on strategic priorities and allocate resources accordingly. By envisioning desired future outcomes and initiatives, teams can make informed budgeting decisions that support their long-term goals. This collaborative activity encourages open discussion and creative thinking around potential opportunities, challenges, and investments needed to drive the organization forward. It combines elements of strategic planning, budgeting, and futurespective techniques to foster alignment and ensure resources are allocated effectively. The Budget Planning Futurespective was developed by financial planning experts to bridge the gap between high-level strategy and practical resource allocation. It has been widely adopted by organizations seeking to make data-driven budgeting decisions that align with their vision and priorities. ## Topics - **Strategic Initiatives**: What new initiatives or projects should we prioritize in the upcoming budget cycle? - **Revenue Streams**: What existing or new revenue streams should we focus on to drive growth? - **Cost Optimization**: Where can we optimize costs or streamline operations to improve profitability? - **Growth Investments**: What investments should we make to fuel long-term growth and competitiveness? ## When to use - When preparing for an upcoming budget cycle and aligning on strategic priorities. - During long-term planning sessions to envision future opportunities and challenges. - As part of a periodic review process to evaluate resource allocation and make necessary adjustments. - When considering major investments, expansions, or strategic shifts that require significant financial resources. - To foster cross-functional collaboration and alignment on budgeting decisions that impact multiple departments or teams. ## Tips and tricks - Encourage participants to think beyond the current fiscal year and envision long-term strategic initiatives. - Provide relevant data and market insights to inform discussions and support proposed ideas. - Ensure a diverse range of perspectives and roles are represented to capture a comprehensive view of the organization's needs. - Prioritize ideas based on their potential impact, feasibility, and alignment with the organization's overall strategy. - Establish clear decision-making criteria and processes to facilitate effective budgeting decisions. - Document the rationale behind budgeting decisions for future reference and accountability. ## Icebreaker questions - If you had an unlimited budget for one year, what would be your top priority for investment? - Share a time when a strategic investment paid off significantly for your organization or team. --- # 4th of July Celebration Retrospective URL: https://www.teamretro.com/retrospective-templates/4th-of-july-celebration-retrospective/ Light up your team's reflection with a festive 4th of July Celebration retrospective that blends patriotic fun with meaningful conversation. Inspired by the spirit of Independence Day, this format invites teams to honor their achievements, declare freedom from outdated processes, and set off sparks of new ideas for the road ahead. It's a seasonal twist on the classic team retrospective, perfect for keeping engagement high during the summer months. The session works by guiding participants through themed prompts that mirror the holiday — celebrating the "fireworks" of recent wins, declaring "independence" from the habits and blockers holding the team back, and igniting "sparklers" of innovation worth exploring. Each topic encourages open, honest dialogue while keeping the mood light and inclusive, helping teams reconnect after the busy first half of the year. By framing reflection around a shared celebration, this retrospective boosts morale, strengthens team bonds, and turns continuous improvement into something to look forward to. Run it in TeamRetro to capture every idea, vote on priorities, and convert insights into clear action items — all while enjoying a bit of holiday spirit. ## Topics - **Fireworks**: What wins are worth celebrating with a bang? - **Declaration of Independence**: What should we free ourselves from going forward? - **Sparklers**: What new ideas could light up our future? - **Picnic Plans**: What actions will we commit to next? ## When to use - Around Independence Day or the early summer when you want a festive, themed retrospective to keep engagement high. - After a major release or milestone that's worth celebrating with the team. - When team morale needs a lift and a lighter, more playful reflection format would help. - As a mid-year checkpoint to celebrate progress and reset priorities for the second half of the year. ## Tips and tricks - Lean into the festive theme with patriotic colors or holiday emojis to set a celebratory mood, but keep the focus on real, actionable reflection. - Start with the 'Fireworks' topic to build positive energy before moving into areas the team wants to improve. - Make sure quieter voices get heard — use TeamRetro's anonymous brainstorming so everyone can contribute freely. - Timebox each topic to keep the energy high and avoid the session dragging during the busy holiday period. - Vote on the most important ideas before discussion so the team focuses on what matters most. - End with clear, owned action items so the celebration translates into real momentum. ## Icebreaker questions - What's your favorite way to celebrate the 4th of July? - If your last sprint were a firework, what would it look like and why? --- # Big & Small Perspectives Retrospective URL: https://www.teamretro.com/retrospective-templates/big-and-small-perspectives-retrospective/ Some of the most valuable team insights live at opposite ends of the scale. The Big & Small Perspectives retrospective invites your team to deliberately shift between the wide-angle view and the close-up detail, ensuring that strategic themes and everyday frictions both get the attention they deserve. By moving between these two lenses, teams uncover patterns they might otherwise miss when they stay fixed at a single altitude. The format works by guiding participants through four complementary perspectives: the big things that went well, the big things that need attention, the small things that went well, and the small wins or annoyances that often go unspoken. This balance prevents the common trap where teams either get lost in minor grievances or talk only in lofty abstractions that never translate into action. In TeamRetro, everyone can contribute ideas in parallel, group similar themes, vote on what matters most, and turn discussion into clear, trackable action items. The result is a richer, more honest conversation that respects both the forest and the trees. Whether you are reflecting on a sprint, a project milestone, or a quarter of work, this retrospective helps your team celebrate meaningful achievements, surface nagging issues early, and decide where to focus next — all while keeping every voice heard. ## Topics - **Big Wins**: What major successes or achievements stood out? - **Big Challenges**: What major obstacles or risks need our attention? - **Small Wins**: What little victories or improvements made a difference? - **Small Annoyances**: What minor frustrations or niggles slowed us down? ## When to use - When your team tends to focus only on big-picture themes and overlooks the small frictions that affect daily work. - At the end of a sprint, project, or quarter when you want a balanced view of both strategic outcomes and everyday details. - When morale needs a boost and you want to celebrate small wins alongside major achievements. - When recurring minor annoyances are quietly building up and you want a structured way to surface and resolve them. ## Tips and tricks - Set the scale clearly at the start — explain the difference between 'big' (strategic, systemic) and 'small' (everyday, tactical) so contributions land in the right category. - Timebox each perspective so the team doesn't spend the whole session in one quadrant; the value comes from moving between scales. - Use anonymous contributions in TeamRetro to encourage honest naming of small annoyances people might otherwise stay quiet about. - Group similar ideas before voting so the team can spot patterns that span both big and small perspectives. - Convert the top-voted items into clear action items with owners — small annoyances are often quick wins worth tackling immediately. - Rotate who facilitates to keep the format fresh and to give everyone experience balancing different perspectives. ## Icebreaker questions - If you could zoom out to see your whole year so far, what's the one big highlight that stands out? - What's a tiny thing — like a coffee or a shortcut — that made your day better recently? --- # Studio Ghibli Journey Retrospective URL: https://www.teamretro.com/retrospective-templates/studio-ghibli-journey-retrospective/ Inspired by the enchanting worlds of Hayao Miyazaki and Studio Ghibli, the Studio Ghibli Journey retrospective invites your team to look back on their sprint or project as if it were an epic, heartfelt adventure. Just like the heroes of films such as Spirited Away, My Neighbor Totoro, and Princess Mononoke, every team embarks on a journey filled with wonder, obstacles, unexpected helpers, and personal growth. This themed format transforms a routine review into an imaginative storytelling session that helps people open up, connect emotionally, and reflect more honestly about their shared experience. The retrospective works by mapping the team's recent journey onto familiar Ghibli storytelling beats. Participants explore the magical moments that brought joy, the spirits and forests that challenged them, the friendly companions who offered help along the way, and the lessons they carry forward into the next adventure. By stepping into a narrative frame, teams often surface insights they might otherwise overlook, and they do so in a relaxed, creative atmosphere that lowers defensiveness and encourages participation from quieter voices. Ideal for teams that enjoy a playful change of pace, this format is a wonderful way to celebrate wins, name struggles with kindness, and set intentions for what comes next. It blends fun with genuine reflection, making it especially effective for keeping engagement high while still capturing meaningful, actionable takeaways. Whether you are wrapping up a tough sprint or simply want to inject some imagination into your regular cadence, the Studio Ghibli Journey helps your team see their work as the remarkable adventure it truly is. ## Topics - **Magical Moments**: What brought joy and wonder this journey? - **Spirits & Obstacles**: What challenges or blockers did we face? - **Friendly Companions**: Who or what helped us along the way? - **The Road Ahead**: What lessons will we carry into the next adventure? ## When to use - When your team needs a refreshing, creative break from the standard retrospective format while still capturing meaningful insights. - At the end of a long or challenging sprint or project, to reflect on the journey with a sense of perspective and kindness. - When you want to boost engagement and encourage quieter team members to open up through a relaxed, storytelling approach. - To celebrate milestones and reinforce team morale alongside honest reflection. ## Tips and tricks - Set the mood at the start — share a Ghibli image or play soft soundtrack music to ease people into the imaginative theme. - Keep the storytelling light and inclusive; the metaphor should invite participation, not become a barrier for those unfamiliar with the films. - Timebox each topic so the discussion stays balanced and you leave room for capturing action items in The Road Ahead. - Use anonymous brainstorming for the Spirits & Obstacles section so people feel safe naming difficult challenges. - Make sure every action item from The Road Ahead has a clear owner so reflections turn into real change. - Celebrate the Magical Moments genuinely — taking time to acknowledge wins keeps morale and motivation high. ## Icebreaker questions - If you could live in any Studio Ghibli world for a day, which one would you choose and why? - Which Ghibli character best represents how you felt during this sprint? --- # Captain America's Agile Mission Retrospective URL: https://www.teamretro.com/retrospective-templates/captain-america-agile-mission-retrospective/ Rally your squad like a true super-soldier and lead your team through a mission-themed retrospective that turns reflection into action. Inspired by Captain America's unwavering leadership, teamwork, and sense of duty, this format invites your team to reflect on the battles won, the shields that held strong, the threats that slowed your advance, and the strategy needed for the next mission. It's a fun, narrative-driven way to bring energy and purpose to your team's continuous improvement. The mission metaphor helps teams frame their work as a shared objective where everyone has a role to play. By thinking in terms of victories, defenses, obstacles, and next moves, participants can celebrate their wins, recognise the practices that protected them, surface the enemies of progress, and align on a clear plan of attack. This approach is especially effective for boosting morale, reinforcing camaraderie, and keeping discussions focused on outcomes that matter. Whether you're closing out a sprint, wrapping up a project, or simply taking stock of how the team is operating, Captain America's Agile Mission gives your retrospective a heroic spin. It encourages honest, courageous conversation while keeping things light and engaging — because every great team needs a clear mission and the resolve to see it through. ## Topics - **Mission Victories**: What battles did we win this mission? - **The Shield (What Protected Us)**: What strengths and practices kept us safe? - **Enemy Forces (Obstacles)**: What threats slowed our advance? - **Next Mission (Plan of Attack)**: What's our strategy for the next mission? ## When to use - When team morale needs a lift and you want a fun, themed way to celebrate wins and build camaraderie. - At the end of a sprint or project to review victories, defences and obstacles in an engaging narrative format. - When the team has faced significant blockers and you want to frame them as shared enemies to tackle together. - For newly formed or cross-functional teams that benefit from a sense of shared mission and collective purpose. ## Tips and tricks - Lean into the mission theme to keep energy high, but make sure the conversation always ties back to real, actionable insights. - Frame obstacles as 'enemy forces' fought together to keep feedback blameless and avoid finger-pointing. - Use dot voting to prioritise the most important victories, threats and next actions so discussion stays focused. - Assign clear owners and due dates to each Next Mission action so commitments don't get lost after the session. - Give quieter team members space to contribute their wins and concerns so no perspective is left behind. - Timebox each topic to keep the mission moving and ensure you leave enough time to agree your plan of attack. ## Icebreaker questions - If you could have one of Captain America's qualities — strength, leadership, or that unbreakable shield — which would help your team most right now? - What's a superhero team-up (real or fictional) that reminds you of how this squad works together? --- # Idea Storm URL: https://www.teamretro.com/retrospective-templates/idea-storm-retrospective/ Idea Storm is a high-energy brainstorming session designed to generate a wide range of fresh ideas in a short space of time. Whether you're tackling a tricky problem, exploring new product features, or simply looking to inject creative momentum into your team, this format encourages everyone to contribute freely without judgement. By focusing on quantity first and quality later, teams unlock unexpected solutions and build on each other's thinking in a collaborative, inclusive way. The session works by guiding participants through structured prompts — capturing every idea, grouping related themes, and then voting on the most promising directions. This separation of divergent thinking (generating ideas) from convergent thinking (refining and selecting) helps teams avoid premature criticism that can shut down creativity. It's a flexible technique rooted in classic brainstorming principles popularised by advertising executive Alex Osborn, who championed the idea that deferring judgement leads to more original thinking. The real value of an Idea Storm lies in its ability to surface diverse perspectives and give quieter team members an equal voice. Running it in TeamRetro means everyone can add ideas simultaneously and anonymously, reducing groupthink and ensuring the loudest voice doesn't dominate. The result is a richer pool of possibilities, clearer next steps, and a team that feels genuinely heard and energised about what comes next. ## Topics - **Wild Ideas**: What bold, no-limits ideas could we imagine if anything were possible? - **Tiny Tweaks**: What small improvements could we try quickly and easily right now? - **Opposite Thinking**: What if we reversed our usual approach — what would we do instead? - **Borrowed Brilliance**: What great ideas could we borrow from other teams, industries, or products? - **One-Sprint Experiments**: What safe experiments could we test within a single sprint? - **Future Us**: Looking back from future success, what ideas got us there? ## When to use - When your team faces a problem with no obvious solution and needs a fresh wave of ideas to explore. - At the start of a new project or feature when you want to gather diverse possibilities before narrowing down. - When creativity feels stale or the same few voices dominate and you want broader, more inclusive participation. - Ahead of planning sessions to build a rich backlog of options to prioritise. - Whenever you need to break out of conventional thinking and encourage bold, innovative contributions. ## Tips and tricks - Defer judgement during the idea-generation phase — no idea should be criticised or dismissed until you reach the grouping and voting stages. - Use a clear, focused prompt or challenge statement so participants know what problem they're solving for. - Encourage quantity over quality early on; more ideas mean more raw material to build on later. - Leverage anonymous contributions so quieter team members and junior staff feel equally safe to share bold thoughts. - Timebox each phase to keep energy high and prevent the session from dragging or losing focus. - Always close with concrete next steps and owners so good ideas don't evaporate after the meeting. ## Icebreaker questions - If you could instantly master any skill to solve a problem at work, what would it be? - What's the most creative solution you've ever come up with for an everyday annoyance? --- # Soccer Retrospective URL: https://www.teamretro.com/retrospective-templates/soccer-retrospective/ The Soccer Retrospective is an engaging team reflection format that uses football/soccer metaphors to evaluate team performance and collaboration. Drawing inspiration from the beautiful game, this retrospective framework helps teams analyze their successes, challenges, and defensive strategies through familiar sporting concepts. Teams use football-themed categories like Goals (achievements), Penalties (setbacks), Saves (risk prevention), and Walls (obstacles) to structure their discussion. This sports-oriented approach makes the retrospective more engaging and relatable, especially for teams that might find traditional formats too formal. This retrospective style is particularly effective in fostering open dialogue about team dynamics, celebrating victories, and addressing challenges in a way that feels natural and fun. The soccer metaphor helps create a playful atmosphere while maintaining focus on serious improvement opportunities. ## Topics - **Goals**: What achievements are we proud of? - **Penalties**: What did not go to plan? - **Saves**: What issues did we prevent? - **Walls**: What things got in our way? ## When to use - When you want to make retrospectives more engaging for sports-enthusiastic teams - After completing a major project milestone or release to evaluate team performance - When team morale needs a boost through a more playful retrospective format - To break away from traditional retrospective formats and inject some energy into the meeting ## Tips and tricks - Keep the soccer metaphor fun but don't let it overshadow the serious reflection needed for improvement - Encourage everyone to participate by using 'passing the ball' as a way to take turns sharing thoughts - Use a timer for each section to maintain good 'match pace' and keep the retrospective on schedule - Consider using actual soccer/football terms to make the experience more authentic and engaging - Balance between celebration (Goals) and constructive criticism (Penalties) to maintain team morale - Create action items that are as clear as game strategies - specific, actionable, and measurable ## Icebreaker questions - If our team were a soccer/football team, what would be our team name and why? - What's your most memorable moment as part of a team (sports or otherwise)? --- # What? So What? Now What? Retrospective URL: https://www.teamretro.com/retrospective-templates/what-so-what-now-what-retrospective/ The What? So What? Now What? framework, developed by Rolfe et al. (2001), is a structured reflection method that helps teams process experiences and plan future actions. This powerful approach breaks down reflection into three clear stages, making it easier for teams to analyze situations thoroughly. In the 'What?' stage, teams focus on objectively describing events and observations without judgment. The 'So What?' phase encourages deeper analysis of these observations, exploring their significance and impact. Finally, the 'Now What?' stage channels these insights into concrete action plans for improvement. This retrospective format is particularly effective for teams dealing with complex situations or when a systematic approach to problem-solving is needed. It helps prevent teams from jumping to solutions before fully understanding the context and implications of their experiences. ## Topics - **What?**: How would you describe the situation? - **So What?**: How does this affect us? - **Now What?**: What do we need to do to move forward? ## When to use - After completing a significant project milestone or release to systematically analyze outcomes - When facing complex challenges that require structured analysis and problem-solving - During organizational changes to help teams process and adapt to new situations - When teams need to move from surface-level observations to deeper insights and concrete actions ## Tips and tricks - Keep the 'What?' phase focused on facts and observations, avoiding interpretation or judgment - Use timeboxing for each phase to ensure balanced discussion across all three stages - Encourage quieter team members to contribute by using round-robin or written submissions - Create clear connections between observations in 'What?' and actions in 'Now What?' - Document actions with specific owners and deadlines to ensure follow-through - Consider using dot voting to prioritize which insights to focus on in the 'Now What?' phase ## Icebreaker questions - What's the most surprising thing you learned last week? - If you could instantly master one new skill, what would it be and why? --- # Dog Day Demo Retrospective URL: https://www.teamretro.com/retrospective-templates/dog-day-demo-retrospective/ Bring a little tail-wagging joy to your team reflection with the Dog Day Demo Retrospective, a lighthearted format that uses our four-legged friends as a friendly metaphor for how the team is feeling and functioning. Whether your sprint felt like a relaxing walk in the park or a chaotic chase after a squirrel, this themed retrospective creates a relaxed, inclusive space where everyone feels comfortable sharing the good, the bad, and the slobbery. The format works by inviting participants to reflect through canine-inspired lenses: the moments worth celebrating ("Good Boy!"), the frustrations that need attention ("Bad Habits"), the things you want more of ("Fetch More"), and the new tricks worth trying next time. By wrapping serious continuous improvement conversations in a fun, approachable theme, teams lower their guard, build psychological safety, and surface honest insights they might otherwise hold back. Themed retrospectives like this one are a proven way to break the monotony of routine sprint reviews and re-energize teams who have grown tired of the same old format. The Dog Day Demo Retrospective is ideal for agile teams looking to combine genuine reflection with a morale boost, helping you turn observations into actionable improvements while keeping spirits high. ## Topics - **Good Boy!**: What did the team do brilliantly this time? - **Bad Habits**: What behaviours or issues kept tripping us up? - **Fetch More**: What should we go get more of next time? - **New Tricks**: What new approaches should we try next sprint? ## When to use - When team morale needs a lift and the usual retrospective format feels stale or repetitive. - After an intense or stressful sprint, when a lighter, playful theme can help people open up honestly. - For teams who love a bit of fun and want to combine genuine reflection with a morale boost. - As a seasonal or special-occasion retrospective, such as around a company dog day or team celebration. - When onboarding new team members who may feel more comfortable sharing in a relaxed, themed setting. ## Tips and tricks - Lean into the theme to keep things light, but make sure each topic still drives toward real, actionable improvements. - Timebox each section so the fun does not crowd out the substance, aim for a balanced, focused session. - Encourage everyone to contribute before discussing, so quieter voices are not drowned out by the loudest in the room. - Group similar ideas and dot-vote on the most important items so the team focuses on what matters most. - Always close by converting 'New Tricks' into clear action items with owners, otherwise the experiments never happen. - Invite people to share a photo of their pet at the start to break the ice and build connection across remote teams. ## Icebreaker questions - If your last sprint were a dog, what breed would it be and why? - What's the best trick you've ever taught yourself (or your pet)? --- # Agile Retrospective URL: https://www.teamretro.com/retrospective-templates/agile-retrospective/ The agile retrospective technique asks 4 basic questions that gets the team thinking about the outcomes of the last sprint, and what actions they should focus on next. While it is straightforward, it sends the basic message that you are listening and geared for improvement. Based on the book by Esther Derby, Diana Larsen and Ken Schwaber, this tried and true method acts as an engine tune-up that keeps your team working at peak performance. Held regularly, it uncovers issues with the software development life cycle and gives your team a way to solve it together. Rather than running a post mortem, regular agile retrospectives that are short, sharp and documented means that you can quickly make changes before it’s too late. Much like steering a big ship, it’s a lot easier to make small changes en route to the destination, than finding out at the end you have docked in the wrong port. Unlike debriefs or post mortems is it is intended to have a more positive and proactive focus. ## Topics - **What went well?**: Things we are happy about. - **What went less well?**: Things we should improve. - **What do we want to try next?**: Things we should do differently. - **What puzzles us?**: Unanswered questions we have. ## When to use - At the end of each sprint or iteration to reflect on the past cycle. - When a team wants to identify specific areas for improvement. - After a major project milestone or release to discuss lessons learned. - Whenever a team feels stuck and needs to get back on track. - As part of an organization's agile transformation to foster a culture of continuous improvement. ## Tips and tricks - Set a positive tone and create a blame-free environment for open discussion. - Timebox each section to keep the retrospective focused and productive. - Encourage participation from all team members, not just the vocal few. - Capture action items and make someone accountable for following up. - Don't try to solve every issue - prioritize and experiment incrementally. - Consider having a rotating facilitator role to get fresh perspectives. ## Icebreaker questions - If you could add one tool or process to help our team, what would it be? - What's one small thing that could have a big positive impact on our team? --- # Lost in the Matrix Retrospective URL: https://www.teamretro.com/retrospective-templates/lost-in-the-matrix-retrospective/ Inspired by the iconic sci-fi world where reality and illusion blur, the Lost in the Matrix retrospective invites your team to question what's real, what's simulated, and what's quietly holding you back. It's a creative, theme-driven format that uses the metaphor of the Matrix to surface hidden assumptions, escape unhelpful patterns, and reconnect with the truth of how your team actually works. By framing reflection through red pills, blue pills, glitches, and exits, teams feel safe to speak openly about the gap between perception and reality. This retrospective works by guiding participants through a series of evocative prompts that map to familiar agile reflection themes while keeping engagement high. Teams identify comforting illusions they've been living with (the blue pill), uncomfortable truths worth confronting (the red pill), recurring glitches and disruptions, and the agents or obstacles blocking progress — before charting their path toward the exit. The playful framing lowers defensiveness and encourages honest, lateral thinking that a standard start-stop-continue format might miss. Ideal for teams who enjoy themed sessions or feel stuck in repetitive retrospectives, this format reenergizes reflection and uncovers systemic issues that often go unspoken. Whether you're mid-project or wrapping a sprint, Lost in the Matrix helps your team unplug from autopilot, embrace reality, and decide which patterns to keep and which to leave behind. ## Topics - **The Blue Pill**: What comfortable illusions are we choosing to believe? - **The Red Pill**: What uncomfortable truths do we need to face? - **Glitches in the System**: What recurring disruptions keep pulling us off course? - **The Agents**: What obstacles or forces are blocking our progress? - **The Exit**: How do we escape and move toward a better reality? ## When to use - When your team feels stuck in repetitive retrospectives and needs a fresh, engaging format to reenergize reflection. - When you suspect hidden assumptions or unspoken truths are quietly affecting team performance. - After a challenging sprint or project phase where perception and reality seem out of sync. - When you want to surface systemic blockers and recurring issues that standard formats tend to miss. - For teams who enjoy themed, creative sessions and respond well to playful metaphors. ## Tips and tricks - Set the scene with a short Matrix-themed intro so everyone understands the red pill / blue pill metaphor before diving in. - Emphasise psychological safety — confronting 'red pill' truths only works if no one feels blamed for naming them. - Encourage people to focus on systems and patterns rather than individuals, especially in the Agents topic. - Timebox each section so the team doesn't get stuck debating illusions and runs out of time for The Exit actions. - Group similar glitches and agents together to spot recurring themes before voting on what matters most. - Always close with specific, owned action items so insight translates into real change after the session. ## Icebreaker questions - If you could download one new skill instantly like Neo learning kung fu, what would it be? - Red pill or blue pill — do you prefer the comfortable illusion or the uncomfortable truth, and why? --- # Minecraft Quest Retrospective URL: https://www.teamretro.com/retrospective-templates/minecraft-quest-retrospective/ Embark on a block-building adventure that turns your team's reflection into an epic quest. Inspired by the world of Minecraft, this themed retrospective invites your crew to mine for valuable insights, craft new improvements, and band together to survive the creepers and challenges of the last sprint. The familiar gaming metaphors create a relaxed, inclusive atmosphere where everyone feels comfortable sharing — whether they're seasoned crafters or brand new to the realm. The Minecraft Quest retrospective works by organising the conversation into themed building blocks. Your team explores what resources they gathered (wins and achievements), what they crafted (things to build on and improve), the creepers and mobs that threatened progress (blockers and risks), and the treasure they want to dig for next (goals and aspirations). This gamified structure keeps energy high while still surfacing the honest, actionable feedback a great retrospective depends on. It's especially powerful for teams who love a bit of playful storytelling or who need a creative break from standard agile formats. By the end of the session, your team will have collaboratively built a shared map of where they've been and where they're headed — complete with prioritised action items to carry into the next sprint. Use it to boost engagement, strengthen psychological safety, and remind everyone that building great software, like building in Minecraft, is always better with a team by your side. ## Topics - **Resources Mined**: What wins and resources did we gather this sprint? - **Crafted & Built**: What did we build on or improve to level up? - **Creepers & Mobs**: What blockers or risks threatened our progress? - **Treasure to Seek**: What goals and treasure do we want to dig for next? ## When to use - When your team enjoys gamified or themed retrospectives and needs a fresh, engaging format to break the routine. - After an intense or challenging sprint, when a playful approach can lighten the mood while still surfacing honest feedback. - For teams that include gamers or anyone who responds well to storytelling and creative metaphors. - When onboarding new team members who may feel more comfortable sharing within a fun, low-pressure framework. ## Tips and tricks - Set the scene early — frame the session as a shared quest so the metaphors land and everyone gets into the spirit. - Don't let the theme overshadow the substance; gently steer playful comments back toward concrete, actionable insights. - Use the Creepers & Mobs block to model blameless discussion, focusing on situations rather than pointing fingers. - Give quieter team members space to contribute by using anonymous brainstorming before discussion. - Time-box each block so you reach the Treasure to Seek section with enough energy to define real action items. - Vote on the most impactful items so the team leaves with a prioritised map for the next sprint. ## Icebreaker questions - If you could craft any one item from Minecraft to use in real life, what would it be and why? - Are you more of a careful builder, a fearless explorer, or the one who always falls in the lava? --- # Olympics Retrospective URL: https://www.teamretro.com/retrospective-templates/olympics-retrospective/ The Olympics Retrospective transforms team reflection into an engaging experience inspired by the world's greatest sporting event. Drawing parallels between athletic excellence and team performance, this format encourages teams to celebrate their achievements, acknowledge collaborative efforts, and identify areas for improvement. Just as Olympic athletes strive for excellence through continuous improvement and teamwork, this retrospective format helps teams recognize their 'medal-worthy' moments while maintaining a growth mindset. Teams reflect on their victories (Medals), demonstrate sportsmanship (Olympic Spirit), acknowledge setbacks (Stumbles), and capture key learnings (Olympic Torch). This format is particularly effective for fostering a positive team culture while maintaining honest dialogue about challenges and opportunities for improvement. It helps teams build resilience, celebrate success, and maintain momentum in their continuous improvement journey. ## Topics - **Medals**: Our achievements - **Olympic Spirit**: Shout out to team players - **Stumbles**: Things that did not go to plan - **Olympic Torch**: Learnings to take forward ## When to use - After completing a major project milestone or release to celebrate achievements and identify improvement areas - When the team needs a morale boost and wants to focus on both achievements and growth opportunities - During team building exercises to strengthen collaboration and mutual appreciation - When you want to energize your regular retrospective with a fresh and engaging format ## Tips and tricks - Start by sharing an inspiring Olympic moment or story to set the tone and context for the session - Encourage balanced participation by ensuring everyone gets a chance to share their 'medal-worthy' moments - Use the Olympic spirit theme to maintain a positive atmosphere even when discussing challenges - Keep a timer for each section to maintain momentum, just like Olympic events have specific timeframes - Consider using virtual medals or certificates to recognize particularly valuable contributions - End the session by creating a 'training plan' of specific actions for improvement ## Icebreaker questions - If you could compete in any Olympic sport, what would it be and why? - What's your most memorable Olympic moment or inspiration? --- # Vital Signs: Team Health Check URL: https://www.teamretro.com/retrospective-templates/vital-signs-team-health-check-retrospective/ Just like a doctor checks your pulse, temperature, and breathing to gauge your overall wellbeing, the Vital Signs team health check gives you a fast, holistic read on how your team is really doing. Instead of waiting for problems to surface in delivery metrics or burnout, this format invites everyone to rate and reflect on the core "vital signs" of a healthy team — energy, collaboration, clarity, and morale. It turns the abstract idea of "team health" into something tangible you can measure, discuss, and improve over time. The session works by guiding participants through a handful of diagnostic dimensions, each acting as a different vital sign. Team members share where they feel strong and where things feel strained, then explore the underlying causes together. Because the framing is medical and metaphorical, it lowers defensiveness and makes it easier to surface sensitive topics like stress, trust, or unclear direction. Running it regularly creates a baseline so you can spot trends, celebrate recovery, and catch warning signs early. The real value of the Vital Signs health check is in the conversation and the action it triggers. Patterns that emerge across the team highlight shared concerns worth addressing, while individual perspectives add nuance to the diagnosis. By the end of the session your team has a clear picture of its current condition and a prioritized set of treatments to keep it thriving sprint after sprint. ## Topics - **Pulse (Energy & Morale)**: How energized and motivated does the team feel right now? - **Breathing (Collaboration & Communication)**: How smoothly are we communicating and working together? - **Temperature (Trust & Safety)**: How safe do we feel to speak up and take risks? - **Reflexes (Clarity & Direction)**: How clear are our goals, priorities and roles? ## When to use - At regular intervals (monthly or quarterly) to track team health trends over time and catch warning signs early. - When you sense morale, energy, or collaboration dipping but can't quite pinpoint the cause. - After a period of intense delivery, organizational change, or team restructuring to assess how people are coping. - As a complement to delivery-focused sprint retrospectives, giving space to the human side of the team. ## Tips and tricks - Run the health check on a consistent cadence so you can compare results over time and spot trends rather than reacting to one-off readings. - Keep ratings anonymous where possible so people feel safe being honest, especially on sensitive dimensions like trust and morale. - Don't just collect scores — always set aside time to discuss the 'why' behind them and agree on concrete actions. - Watch for outliers and divergent views; a wide spread in responses often reveals more than a uniform average. - Avoid turning the results into a performance scorecard, which discourages honesty and breeds defensiveness. - Close the loop by reviewing previous actions at the start of each check so the team sees the diagnosis leads to real treatment. ## Icebreaker questions - If your current energy level was a weather forecast, what would today's report say? - On a scale from 'hospital gown' to 'marathon-ready', how is the team feeling this week? --- # New Year Retrospective URL: https://www.teamretro.com/retrospective-templates/new-year-retrospective/ The New Year Retrospective provides teams with a structured opportunity to reflect on their collective journey over the past year while setting intentional goals for the future. This retrospective format combines celebration of achievements with strategic planning, creating a balanced approach to year-end reflection. By examining both accomplishments and challenges from the previous year, teams gain valuable insights that inform their path forward. The process encourages honest dialogue about what worked well, what could be improved, and what aspirations team members hold for the coming year. This retrospective is particularly powerful in fostering team unity and shared purpose. It helps teams acknowledge their growth, learn from experiences, and align their goals for the upcoming year. The format creates space for both individual reflection and collective planning, ensuring everyone's voice contributes to shaping the team's future direction. ## Topics - **Proudest Achievements**: What accomplishments from the past year make you most proud? - **Valuable Lessons**: What important lessons did we learn this year? - **Future Aspirations**: What do we want to achieve in the coming year? - **Action Steps**: What concrete steps will help us achieve our goals? ## When to use - At the end of the calendar year to reflect on team progress and plan for the upcoming year - During annual planning sessions to align team goals with organizational objectives - When teams need to celebrate achievements and set new directions for growth ## Tips and tricks - Encourage participants to prepare by reflecting on their year before the session - Use data and metrics to support discussions about achievements and lessons learned - Ensure goals set for the new year are SMART (Specific, Measurable, Achievable, Relevant, Time-bound) - Create a positive atmosphere that celebrates successes while honestly addressing challenges - Document key decisions and action items for regular review throughout the coming year ## Icebreaker questions - What was your most unexpected positive surprise from the past year? - If you could choose one word to describe your hopes for the coming year, what would it be? --- # Lead Generation Strategy Planning URL: https://www.teamretro.com/retrospective-templates/lead-generation-strategy-planning-retrospective/ The Lead Generation Strategy Planning activity is a focused meeting for evaluating the effectiveness of your current lead generation tactics and planning improvements for future campaigns. This collaborative exercise encourages open discussion and analysis of what worked well, what didn't, and how to optimize your lead gen strategies moving forward. By reflecting on recent performance data, market trends, and team experiences, you'll gain valuable insights to refine your approach. This futurespective drives continuous improvement by turning lessons learned into actionable next steps for more successful lead acquisition. ## Topics - **What went well?**: Which lead generation tactics were most successful? - **What didn't go well?**: Which lead gen initiatives underperformed or had challenges? - **What did we learn?**: What key insights did we gain from this period? - **What should we do next?**: What are our priorities for optimizing lead gen efforts? ## When to use - At the end of each quarter or campaign period to review performance and recalibrate strategies. - When launching new lead generation initiatives to set a benchmark and identify opportunities. - After major changes in your market, product, or business that impact lead acquisition tactics. - Anytime you need to get stakeholder alignment on adjusting your lead management processes. ## Tips and tricks - Come prepared with lead generation metrics and performance data to facilitate an objective discussion. - Encourage participation from cross-functional team members involved in lead gen efforts. - Use virtual whiteboarding or sticky notes to capture ideas during the session. - Assign owners to each action item with clear due dates and success metrics. - Schedule a follow-up session to review progress on your updated lead gen game plan. ## Icebreaker questions - If you could generate leads from any celebrity endorsement, who would you choose? - What's the craziest lead generation idea you've ever heard of or tried? --- # Quarterly Retrospective URL: https://www.teamretro.com/retrospective-templates/quarterly-retrospective/ Stepping back to look at the bigger picture is essential for any team that wants to grow with intention. A Quarterly Retrospective gives your team the dedicated space to zoom out from sprint-level details and reflect on the past three months as a whole — celebrating major wins, learning from challenges, and recalibrating priorities for the quarter ahead. Unlike a sprint retro, this longer-horizon review focuses on trends, themes, and strategic alignment rather than day-to-day fixes. The format works by guiding teams through a structured reflection on accomplishments, obstacles, lessons learned, and forward-looking goals. Participants share their perspectives, group common themes, and vote on the most important areas to focus on next. Running it in TeamRetro keeps everyone engaged with collaborative brainstorming, dot voting, and action item tracking — so insights translate into measurable improvements rather than fading away after the meeting ends. Quarterly retrospectives are particularly valuable for distributed and cross-functional teams who need a regular cadence to stay aligned on the bigger mission. By creating a consistent rhythm of reflection, teams build psychological safety, surface recurring patterns, and make smarter decisions about where to invest their energy. The result is a culture of continuous improvement that compounds quarter after quarter. ## Topics - **Wins & Achievements**: What were our biggest accomplishments this quarter? - **Challenges & Obstacles**: What slowed us down or held us back this quarter? - **Lessons Learned**: What insights will we carry into next quarter? - **Goals & Focus**: What should we prioritise for the next quarter? ## When to use - At the end of each business or fiscal quarter to review progress and reset priorities for the next three months. - When your team needs to step back from sprint-level details and reflect on broader trends and themes. - Ahead of quarterly planning sessions to ground goal-setting in honest reflection and lessons learned. - When onboarding a new cadence of strategic alignment for distributed or cross-functional teams. ## Tips and tricks - Send out a pre-read or prompt a few days early so participants can reflect on the full quarter rather than just the most recent weeks. - Keep the focus on themes and trends, not minor day-to-day issues — those belong in your sprint retros. - Use dot voting to prioritise the most important challenges and goals so the discussion stays focused and time-boxed. - Always end with clear, owned action items and revisit them at the start of your next quarterly retro to ensure accountability. - Invite a diverse mix of voices and encourage quieter team members to contribute to avoid recency or dominance bias. - Celebrate wins genuinely before diving into challenges — it sets a positive, psychologically safe tone for the session. ## Icebreaker questions - If you could sum up the past quarter in one emoji, which would you pick and why? - What's one thing — work or personal — that you're most proud of from the last three months? --- # Product Development Process URL: https://www.teamretro.com/retrospective-templates/product-development-process/ The Product Development Process retrospective is a comprehensive review of an organization's end-to-end product development lifecycle. It provides a structured approach to analyze the current processes, identify areas for improvement, and implement changes to enhance efficiency and product quality. This retrospective goes beyond the typical sprint or iteration review, focusing on the overarching product development methodology. It examines key aspects such as requirements gathering, design, development, testing, deployment, and post-release activities. By conducting this retrospective, teams can uncover bottlenecks, streamline workflows, and foster a culture of continuous improvement. It promotes cross-functional collaboration, aligns stakeholders, and ensures that the product development process remains agile and adaptable to changing market demands. ## Topics - **Process Alignment**: How well does our current process align with our product vision and goals? - **Process Efficiency**: What bottlenecks or inefficiencies exist in our current process? - **Cross-Functional Collaboration**: How effectively do teams collaborate across functions and disciplines? - **Data-Driven Decisions**: How effectively do we leverage data and metrics to inform our process? - **Innovation and Growth**: How well does our process foster innovation and continuous improvement? ## When to use - When you want to assess the overall effectiveness of your product development lifecycle and identify areas for improvement. - When you're experiencing recurring issues or bottlenecks in your development process that need to be addressed. - When you're planning to introduce a new development methodology or make significant changes to your existing process. - As part of a regular process review and continuous improvement initiative. - When you want to align cross-functional teams and stakeholders around a common understanding of the development process. ## Tips and tricks - Encourage open and honest feedback from all participants, regardless of their role or seniority. - Ensure representation from all teams and functions involved in the product development process. - Set the tone by helping the team examine the forest from the trees. That is, consider things at a high level, rather than just the last sprint. - Foster a blame-free environment where participants can openly discuss challenges and failures. - Prioritize actionable insights and create a clear plan for implementing process improvements. - Use the propose ideas features for team members to suggest changes, and get buy-in from the team before committing an action. ## Icebreaker questions - If our product development process were an animal, what animal would it be and why? - Share a funny or memorable experience from your time working on product development. --- # Support Tools and Resources Retrospective URL: https://www.teamretro.com/retrospective-templates/support-tools-and-resources-retrospective/ The Support Tools and Resources Retrospective is a focused meeting for teams to reflect on the tools, resources, and processes used to provide customer or internal support. It aims to identify areas for improvement, share best practices, and ensure the team has the necessary resources to deliver efficient and effective support. This retrospective encourages open discussion about the challenges faced, successes achieved, and opportunities for optimization. By evaluating the current state, teams can make informed decisions to streamline workflows, enhance collaboration, and ultimately improve the support experience. Originally developed by experienced support professionals, this retrospective format has been widely adopted across various industries to foster continuous improvement in support operations. ## Topics - **Support Tools Evaluation**: How effective were the tools used for support? - **Resource Availability**: Did we have access to the necessary resources? - **Process Efficiency**: How well did our processes support effective operations? - **Collaboration and Communication**: How well did we collaborate and communicate as a team? ## When to use - When evaluating the effectiveness of your support tools and identifying areas for improvement. - After implementing new support tools or processes to assess their impact and gather feedback. - Periodically, to ensure your support operations remain efficient and aligned with best practices. - When onboarding new team members, to familiarize them with the tools, resources, and processes used. - When planning for upcoming changes or initiatives that may impact support operations. ## Tips and tricks - Encourage open and honest feedback from all team members, regardless of their role or experience level. - Involve stakeholders from other teams, such as product, engineering, and customer success, to gain diverse perspectives. - Use data and metrics to support observations and identify areas for improvement. - Prioritize action items and assign owners to ensure follow-through on identified improvements. - Foster a culture of continuous improvement by regularly revisiting and refining your support tools and processes. - Celebrate successes and share best practices to reinforce positive behaviors and encourage knowledge sharing. ## Icebreaker questions - If you could invent a new support tool, what would it do? - Share a memorable customer interaction that highlights the importance of effective support. --- # Agile Games Retrospective URL: https://www.teamretro.com/retrospective-templates/agile-games-retrospective/ An Agile Games Retrospective is a structured way to review and discuss the team's experience after participating in an agile game or simulation. These interactive activities are designed to illustrate agile principles and practices in an engaging, hands-on manner. The retrospective provides a forum to share insights, lessons learned, and areas for improvement. By reflecting on the game experience, teams can reinforce their understanding of agile concepts like collaboration, iterative development, and customer focus. The retrospective also encourages open communication, continuous improvement, and team building. This template offers thought-provoking topics to guide the discussion, allowing participants to explore the game's dynamics, challenges faced, and potential applications to real-world projects. The goal is to foster a safe environment for honest feedback and to identify actionable steps to enhance the team's agile mindset and capabilities. ## Topics - **Key Takeaways**: What were the main lessons or insights you gained from the game? - **Challenges Faced**: What were the most significant challenges you encountered during the game? - **Collaboration Insights**: What did you learn about effective collaboration and teamwork? - **Real-World Applications**: How can you apply the lessons from the game to your actual projects? ## When to use - After participating in an agile game or simulation as a team-building exercise. - When you want to reinforce agile principles and practices through an interactive and engaging experience. - To foster open communication, continuous improvement, and team building within your agile team. - As a retrospective activity to reflect on the lessons learned and identify areas for growth. - To bridge the gap between theoretical agile concepts and practical applications in real-world projects. ## Tips and tricks - Encourage active participation and create a safe environment for open and honest feedback. - Relate the game experience to real-world scenarios and challenges the team faces to make the lessons more relatable. - Capture key insights and action items during the retrospective for future reference and follow-up. - Consider inviting stakeholders or external observers to provide additional perspectives on the team's performance. - Use visual aids, such as whiteboards or digital collaboration tools, to facilitate the discussion and capture ideas. - Celebrate successes and acknowledge areas for improvement in a constructive manner. ## Icebreaker questions - If the agile game you played was a movie, what would its title be and why? - Share a funny or memorable moment from the game that exemplified the agile principles in action. --- # Snakes and Ladders Retrospective URL: https://www.teamretro.com/retrospective-templates/snakes-and-ladders-retrospective/ The Snakes and Ladders retrospective transforms the classic board game concept into a powerful project reflection tool. Drawing inspiration from the traditional game of advancement and setbacks, this format helps teams visualize their journey toward their goals. Participants identify potential shortcuts (ladders) that can accelerate progress and pitfalls (snakes) that might slow them down. This creates a strategic map of opportunities and risks, allowing teams to plan their path forward more effectively. This retrospective format is particularly effective for project planning and risk assessment, as it encourages teams to think both optimistically and critically about their journey. It helps create a balanced view of challenges and opportunities while maintaining an engaging, game-like atmosphere. ## Topics - **Start**: What things should we start? - **Snakes**: What pitfalls should we be aware of? - **Ladders**: What will help take us to the next level? - **Finish**: What do we expect at the end? ## When to use - When planning a new project or initiative to identify potential risks and opportunities early - During project milestones to assess progress and adjust strategy - When the team needs to break out of a rut and think creatively about solutions - For teams that respond well to gamified approaches to problem-solving ## Tips and tricks - Keep the game metaphor light and fun, but ensure discussions remain focused on actionable insights - Encourage participants to think about both short-term and long-term implications of each snake and ladder - Use voting or prioritization to identify the most critical snakes to address and the most valuable ladders to pursue - Consider creating a visual board to track progress on addressing identified snakes and leveraging ladders - Balance the discussion between risks and opportunities to maintain a positive outlook - Follow up on previous retrospective items to ensure continuity and progress ## Icebreaker questions - What was your favorite board game as a child and why? - If you could instantly master one skill that would help our team, what would it be? --- # Process Improvement Retrospective URL: https://www.teamretro.com/retrospective-templates/process-improvement-retrospective/ A Process Improvement Retrospective is a structured meeting where teams review an existing process to identify areas for enhancement. By examining the purpose, challenges, and effectiveness of the current approach, teams can pinpoint what's working well and what needs improvement. This collaborative analysis enables teams to develop actionable strategies for streamlining and optimizing processes, ultimately boosting efficiency and productivity. The retrospective follows a proven format that encourages open discussion and constructive feedback. Participants share insights from their unique perspectives, fostering a comprehensive understanding of the process. Through this systematic review, teams can uncover root causes of inefficiencies, explore innovative solutions, and develop a roadmap for implementing positive changes. By regularly conducting Process Improvement Retrospectives, organizations can cultivate a culture of continuous improvement, ensuring their processes remain aligned with evolving business needs and industry best practices. ## Topics - **Process Overview**: What is the current process we're reviewing? - **Process Purpose**: Why does this process exist? What is its intended goal? - **Pain Points**: What challenges or issues are you currently facing with this process? - **What's Working Well**: What aspects of the process are effective and should be retained? - **Improvement Ideas**: What changes or enhancements could be made to optimize the process? ## When to use - When you identify recurring issues or inefficiencies within an existing process. - After implementing a new process and want to assess its effectiveness and identify areas for refinement. - As part of a continuous improvement initiative to regularly review and optimize critical processes. ## Tips and tricks - Encourage open and honest feedback by creating a safe, judgment-free environment. - Involve stakeholders from different roles and perspectives to gain a comprehensive understanding of the process. - Use visual aids, such as process maps or flowcharts, to facilitate discussion and identify bottlenecks. - Prioritize improvement ideas based on their potential impact and feasibility. - Assign clear ownership and timelines for implementing agreed-upon actions. - Schedule follow-up sessions to review progress and make necessary adjustments. ## Icebreaker questions - If you could redesign the process from scratch, what would be your first step? - Share a humorous or frustrating experience you've had with the current process. --- # An Unexpected Journey Retrospective URL: https://www.teamretro.com/retrospective-templates/an-unexpected-journey-retrospective/ Every project is an adventure, and rarely does it follow the map exactly as planned. An Unexpected Journey Retrospective borrows the spirit of a heroic quest to help your team look back on where you set out to go, the surprises you encountered along the way, and the treasures and lessons you gathered. By framing reflection as a story, this retrospective makes it easier for teams to talk openly about the twists, turns, and dragons they faced without assigning blame. This narrative-driven format works by guiding your team through the key chapters of any journey: the starting point and goals, the unexpected challenges, the moments of discovery, and the wisdom to carry into the next quest. It encourages everyone to share their own perspective on how the path unfolded, turning ordinary status reflections into a shared tale of resilience and growth. The storytelling lens lowers defensiveness and sparks creativity, helping quieter team members contribute and surfacing insights that a standard checklist might miss. Ideal for end-of-project reviews, milestone celebrations, or any team that wants a refreshing change from the usual retrospective routine, An Unexpected Journey helps you celebrate how far you've come and chart a wiser course forward. The result is a more engaged conversation, clearer action items, and a team that feels united by the story they've created together. ## Topics - **Where We Set Out**: What were our original goals and expectations? - **Unexpected Detours**: What surprises or obstacles knocked us off course? - **Treasures Discovered**: What good things or wins did we find along the way? - **Wisdom for the Next Quest**: What lessons will we carry into our next adventure? ## When to use - At the end of a long or complex project to reflect on how the journey actually unfolded versus the plan. - After reaching a major milestone, when the team wants to celebrate wins and capture lessons learned. - When a standard retrospective feels stale and you want a fresh, story-driven format to re-engage the team. - Following a turbulent period full of surprises or scope changes, to process events in a safe, blame-free way. ## Tips and tricks - Set the scene with a short story framing at the start so everyone embraces the adventure metaphor and feels comfortable sharing. - Encourage every voice by giving quieter members dedicated time to contribute their part of the journey. - Treat detours as part of the story rather than failures, keeping the conversation blame-free and curious. - Group similar reflections to spot recurring patterns in challenges and wins before prioritising. - Timebox each chapter of the journey so you leave enough room for the 'Wisdom for the Next Quest' actions. - Convert the lessons into specific, owned action items so insights translate into real change. ## Icebreaker questions - If this project were a movie adventure, what genre would it be and why? - What's the most unexpected detour you've ever taken on a real-life trip? --- # Rugby Retrospective URL: https://www.teamretro.com/retrospective-templates/rugby-retrospective/ The Rugby Retrospective transforms the familiar rugby field into a powerful framework for team reflection and improvement. Drawing inspiration from the strategic zones of a rugby pitch, this retrospective helps teams analyze their performance, identify obstacles, and plan their path to success. Each section of the field represents a different aspect of team performance, from immediate challenges at the 10M line to ultimate goals at the try line. Teams move through these positions systematically, building a comprehensive understanding of their current state and future aspirations. This unique approach resonates particularly well with sports-minded teams and those who appreciate visual metaphors. The rugby field layout provides a natural progression through the retrospective, making it easy for teams to organize their thoughts and develop actionable insights. ## Topics - **Halfway Line**: What will help us start moving forward? - **10M line**: What are the immediate challenges? - **22M line**: What will help us accelerate? - **Try Line**: What will get help us reach our goal? - **Deadball line**: What should we take out of play? ## When to use - When you want to energize a team that enjoys sports metaphors and competitive analogies - For teams that need to balance immediate challenges with long-term strategic goals - During quarterly planning sessions to map out progressive improvement steps ## Tips and tricks - Use the rugby field visualization to help team members understand how each area contributes to overall success - Encourage participants to think about both tactical (short-term) and strategic (long-term) improvements - Keep the sports metaphor alive by using rugby terminology to make the session more engaging - Consider using a timer for each 'position' to maintain momentum, just like in a real rugby match - End the session by creating a 'game plan' that outlines specific actions and owners ## Icebreaker questions - If your team were a rugby team, what position would you play and why? - What's your most memorable sporting moment that taught you about teamwork? --- # Sitcom Sprint Retrospective URL: https://www.teamretro.com/retrospective-templates/sitcom-sprint-retrospective/ Every sprint has its plot twists, comedic mishaps, breakout stars, and cliffhangers that set up the next episode. The Sitcom Sprint retrospective invites your team to look back on the sprint as if it were an episode of their favourite TV comedy. By reframing work events as scenes, characters, and storylines, teams lower their guard, laugh together, and uncover honest insights they might not surface in a traditional retrospective format. This playful agile retrospective works because humour creates psychological safety. When people describe a tricky bug as a "running gag" or a great collaboration as a "feel-good moment," they engage more openly and remember the takeaways longer. The Sitcom Sprint structure walks teams through what made them laugh, what the recurring jokes (and recurring problems) were, who the episode's stars were, and what the cliffhanger is for the next sprint. Ideal for teams that want to inject energy into their regular cadence, the Sitcom Sprint balances fun with genuine reflection. Facilitators can use it to break retrospective fatigue, celebrate wins, and still capture meaningful action items. It keeps the conversation light while making sure the lessons of the episode carry over into the next season. ## Topics - **The Laugh Track**: What moments made the team smile or laugh this sprint? - **The Running Gag**: What problems or annoyances kept popping up again and again? - **Breakout Star**: Who or what stood out and deserves recognition this sprint? - **The Cliffhanger**: What's unresolved and carrying over into next sprint? ## When to use - When your team is experiencing retrospective fatigue and needs a fresh, energising format to re-engage. - When you want to celebrate wins and build morale while still capturing meaningful improvement actions. - After a particularly intense or eventful sprint that would benefit from a lighter, more reflective tone. - When onboarding new team members and you want an approachable, low-pressure way to spark open conversation. ## Tips and tricks - Set the tone early by leaning into the sitcom theme — invite people to name the episode or pick a genre to get everyone in a playful mindset. - Keep humour inclusive; make sure jokes are about situations and not aimed at individuals, so the session stays psychologically safe. - Timebox each topic so the fun doesn't crowd out the actionable insights — aim to convert recurring gags and cliffhangers into clear next steps. - Encourage quieter members by starting with the lighter 'Laugh Track' topic before moving into challenges. - Group similar ideas together during voting so the team can prioritise the running gags and cliffhangers that matter most. - Close by assigning owners and due dates to action items so the next 'episode' starts with momentum. ## Icebreaker questions - If this sprint were a sitcom, what would the episode title be? - Which TV character best represents how you felt during this sprint, and why? --- # Ancient Greek Odyssey Retrospective URL: https://www.teamretro.com/retrospective-templates/ancient-greek-odyssey-retrospective/ Set sail with your team on an epic voyage inspired by Homer's legendary tales. The Ancient Greek Odyssey retrospective reframes your sprint or project as a heroic journey across uncharted waters, where every storm weathered, monster slain, and siren resisted becomes a lesson for the next adventure. By stepping into the world of myth and legend, teams unlock fresh perspectives on the obstacles they faced and the wins they earned, making reflection both memorable and meaningful. This themed retrospective works by mapping familiar Odyssey motifs onto your team's real experiences. The Departure captures your goals and intentions as you left the harbour, Storms & Sirens surface the challenges and distractions that knocked you off course, Heroic Feats celebrate the moments of brilliance and resilience, and the Course Home turns insight into action for the journey ahead. The narrative structure keeps energy high, encourages storytelling, and helps quieter voices contribute through a shared metaphor everyone can rally around. Perfect for teams who enjoy a creative twist on the classic agile retrospective, the Ancient Greek Odyssey format injects fun without sacrificing substance. Inspired by the timeless storytelling of Homer's Odyssey, it transforms routine reflection into a collaborative myth-making exercise. Run it in TeamRetro to break monotony, build psychological safety, and ensure your crew arrives at clear, actionable next steps for the voyage to come. ## Topics - **The Departure**: What goals did we set as we left the harbour? - **Storms & Sirens**: What challenges and distractions knocked us off course? - **Heroic Feats**: What moments of brilliance and resilience should we celebrate? - **Course Home**: What will we do differently to navigate the next voyage? ## When to use - When your team needs a refreshing, creative alternative to the standard sprint retrospective to re-energise reflection. - After a particularly long or challenging project where a storytelling lens can help process highs and lows. - When you want to build psychological safety and encourage quieter team members to contribute through a shared metaphor. - For team-building sessions where engagement and fun are as important as actionable outcomes. ## Tips and tricks - Set the scene briefly at the start so everyone understands the metaphor before diving into reflections. - Encourage storytelling but keep an eye on the clock so the narrative doesn't crowd out actionable outcomes. - Use grouping and voting to surface the storms and feats that matter most to the whole crew. - Make sure Course Home actions have clear owners and timelines so insight turns into change. - Lean on the theme to depersonalise difficult feedback, framing setbacks as storms rather than individual failings. - Rotate the role of 'captain' or facilitator across voyages to keep perspectives fresh and shared. ## Icebreaker questions - If your team were a crew on Odysseus's ship, which mythical role would you play and why? - Which Greek monster best represents the biggest obstacle you faced this sprint? --- # Team Mood and Health Retrospective URL: https://www.teamretro.com/retrospective-templates/mood-and-health-retrospective/ Healthy teams do their best work, yet the signals of burnout, stress, and disengagement often go unnoticed until they become problems. The Mood & Health Checkup gives your team a structured, judgment-free space to reflect on how they're really feeling — emotionally, physically, and professionally — so you can spot early warning signs and celebrate what's keeping people energized. This check-in works by inviting everyone to share their current mood, energy levels, sources of stress, and what's helping them stay well. By making wellbeing a regular and visible part of your team rhythm, you create psychological safety, build trust, and show that people matter as much as deliverables. Facilitators can use the results to guide supportive conversations, adjust workloads, and reinforce healthy habits across the team. Whether you run it weekly, at the end of a sprint, or during particularly demanding periods, the Mood & Health Checkup helps teams stay connected and resilient. It pairs perfectly with traditional sprint retrospectives by adding a human-centered lens, ensuring that performance and people-care go hand in hand. ## Topics - **Feels Good**: What made you feel positive or proud this sprint? - **Felt Heavy**: What left you feeling flat or deflated? - **Felt Frustrating**: What stressed or irritated you? - **Feels Hopeful**: What are you genuinely looking forward to? ## When to use - When you want to proactively monitor team wellbeing and prevent burnout before it escalates. - During intense delivery periods or after a challenging sprint to check on how people are coping. - As a regular weekly or fortnightly ritual to build trust and psychological safety. - When you sense disengagement or low morale and need a structured way to open the conversation. - Alongside a sprint retrospective to balance performance reviews with a human-centered focus. ## Tips and tricks - Set the tone early by sharing your own honest check-in first — vulnerability from the facilitator gives others permission to open up. - Make participation safe by allowing anonymous responses so people feel comfortable being truthful about stress and mood. - Look for patterns across the whole team rather than focusing on individuals, and follow up privately if someone signals they're struggling. - Always close with concrete actions or commitments so the team sees their input leads to real support, not just venting. - Keep it short and regular — a quick recurring checkup builds more trust than an occasional deep-dive. - Avoid turning wellbeing into a performance metric; the goal is care and connection, not scoring. ## Icebreaker questions - If your current mood was a weather forecast, what would today's report say? - What's one small thing that made you smile this week? --- # World of Warcraft Raid Review URL: https://www.teamretro.com/retrospective-templates/world-of-warcraft-raid-review-retrospective/ Whether your guild just downed a Mythic boss or spent the night wiping on the same mechanic, every raid night is a chance to learn and grow as a team. The World of Warcraft Raid Review brings the spirit of the after-action report to your raid group, helping officers and members reflect on encounters, coordination, and morale in a structured, friendly way. It borrows the proven format of an agile retrospective and reskins it for the world of Azeroth, making continuous improvement feel as natural as repairing your gear between pulls. This format works by guiding your raid team through what went well, where the wipes happened, and what to change before the next lockout resets. By focusing the conversation on encounters, mechanics, communication, and group cohesion rather than individual blame, you create a safe space for honest feedback and shared accountability. Topics prompt members to surface insights about boss strategies, raid assignments, voice comms, and consumable readiness so the whole roster can show up sharper next time. The real value is in turning raid frustration into actionable progress. Guilds that review their raids consistently clear content faster, retain members longer, and keep raid nights fun. Use this template after a progression night, a fresh tier launch, or a tough wipefest to keep your team aligned, motivated, and ready for the next big pull. ## Topics - **Epic Loot**: What went well in our raid this week? - **Wipes & Mechanics**: Where did we wipe or struggle with mechanics? - **Strats & Assignments**: What should we change in our strategy or roles? - **Guild Morale**: How is the team feeling and how can we keep it fun? ## When to use - After a progression night where your guild was working on a new boss and want to refine the strategy before the next attempt. - Following the launch of a new raid tier to align the roster on assignments, consumables, and expectations. - When a string of wipes is causing frustration and you want to turn the night into constructive, actionable feedback. - At the end of a raid lockout to reflect on overall performance, morale, and what to improve next reset. ## Tips and tricks - Keep feedback about mechanics and encounters, not individual players, to avoid blame and keep the guild together. - Run the review shortly after raid night while the pulls are still fresh in everyone's memory. - Give quieter members a chance to contribute by collecting ideas anonymously before discussing them. - End on the strategy and assignment changes so everyone leaves with a clear plan for next pull. - Celebrate at least one win every session, even on a rough wipefest, to keep morale high. - Timebox the review so it stays snappy and doesn't eat into rest time before the next night. ## Icebreaker questions - If your raid team were a boss encounter, what would our signature mechanic be? - What is the most memorable wipe you have ever been part of and what did you learn from it? --- # Remote Team Retrospective URL: https://www.teamretro.com/retrospective-templates/remote-team-retrospective/ Working across time zones, home offices, and digital channels brings unique challenges that traditional retrospectives don't always address. The Remote Team Retrospective is designed specifically for distributed and hybrid teams who want to reflect on how they collaborate, communicate, and stay connected when they're not in the same room. It creates a structured space to celebrate what's working, surface hidden friction, and find practical ways to make remote work feel more human and effective. The format guides your team through four focused areas: how well you're communicating, how connected you feel as a team, what's helping you stay productive, and what's getting in the way. Because it runs entirely online in TeamRetro, every team member—whether they're at a kitchen table or a co-working space, can contribute equally and anonymously, levelling the playing field for quieter voices and different time zones. Grouping, voting, and action tracking happen in real time or asynchronously, so the conversation stays inclusive and outcomes are easy to follow up on. The goal is simple but powerful: build a remote working culture that's intentional rather than accidental. By regularly checking in on the things that matter most to distributed teams—trust, clarity, tools, and wellbeing, you create momentum for continuous improvement and prevent the slow drift toward burnout and disconnection that remote teams can experience. Use it after a sprint, a project milestone, or simply on a recurring cadence to keep your virtual team thriving. ## Topics - **How well are we communicating?**: Is information flowing clearly across channels and time zones? - **How connected do we feel?**: Are we building trust and rapport despite the distance? - **What's helping us thrive?**: Which tools, habits, or rituals are boosting our remote work? - **What's getting in our way?**: What friction or blockers are making remote work harder? ## When to use - After transitioning to a fully remote or hybrid working model and you want to assess how the team is adapting. - On a recurring cadence to maintain connection, trust, and communication across distributed team members. - Following a project or sprint where collaboration across time zones felt strained or particularly successful. - When onboarding new remote team members and you want to surface gaps in process, tools, or culture. - If you sense rising disconnection, burnout, or communication breakdowns within a distributed team. ## Tips and tricks - Use anonymous brainstorming so quieter team members and those in different time zones feel equally safe to contribute honestly. - Consider running the retro asynchronously over a day or two to include everyone across time zones, then meet briefly to discuss and vote. - Keep video on where possible during discussion to read body language and build connection, but be mindful of video fatigue. - Focus on a small number of high-impact actions rather than trying to fix everything at once—remote change takes intentional effort. - Rotate the facilitator role so different perspectives shape the conversation and no single voice dominates. - Always assign owners and due dates to actions in TeamRetro so improvements don't get lost between sessions. ## Icebreaker questions - What's the best thing about working from your current setup—and the one thing you'd change? - If your team could meet in person anywhere in the world for a day, where would you go? --- # Start Stop Retrospective URL: https://www.teamretro.com/retrospective-templates/start-stop-retrospective/ The Start Stop Retrospective is a streamlined approach to team reflection that focuses on two fundamental questions: what new practices should be adopted and what current practices should be discontinued. This straightforward format helps teams identify both opportunities for positive change and areas where current activities may be hindering progress. Originally developed as a simplified variation of the traditional retrospective format, this technique is particularly effective for teams who want to make clear, actionable decisions without getting overwhelmed by complexity. By limiting the discussion to just two categories, teams can quickly reach consensus and create focused improvement plans. The power of this retrospective lies in its simplicity and clarity. Teams can easily distinguish between introducing new beneficial practices (Start) and eliminating ineffective ones (Stop), leading to concrete action items that can be implemented immediately. ## Topics - **Start**: What should we start doing? - **Stop**: What should we stop doing? ## When to use - When teams need to make quick, decisive changes to their processes or practices - After completing a project phase where clear adjustments are needed - When team efficiency needs improvement and you want to focus on concrete actions - During periods of change when you need to evaluate current practices ## Tips and tricks - Keep the focus on actionable items that can be implemented within a reasonable timeframe - Encourage all team members to contribute by using round-robin participation - Maintain a balanced discussion between both categories to ensure comprehensive improvement - Document decisions and create specific action items with owners and deadlines - Follow up on previous retrospective actions before starting new ones ## Icebreaker questions - What's one positive change you've seen in our team recently? - If you could instantly implement one improvement to our process, what would it be? --- # Ramadan Reflection Retrospective URL: https://www.teamretro.com/retrospective-templates/ramadan-retrospective/ The Ramadan Reflection Retrospective draws inspiration from the core principles of Ramadan: self-reflection, community support, and continuous improvement. This thoughtful framework encourages team members to examine their work with the same intentionality and mindfulness that characterizes the holy month. Just as Ramadan invites practitioners to reflect on their actions and seek personal growth, this retrospective creates space for teams to honestly assess their processes, celebrate achievements, identify areas for improvement, and strengthen their bonds. The structure promotes both individual accountability and collective responsibility. By incorporating themes of patience, gratitude, and purposeful action, teams can gain deeper insights into their dynamics and develop more meaningful improvement strategies. The format encourages participants to approach challenges with compassion while maintaining focus on tangible progress—creating a balanced retrospective experience that honors both personal growth and team advancement. ## Topics - **Mindful Reflection**: What have we learned about ourselves? - **Community Support**: How have we supported each other's growth? - **Purposeful Improvement**: What specific changes would create the most value? - **Gratitude & Celebration**: What accomplishments should we acknowledge and celebrate? ## When to use - When your team needs to refocus on their core purpose and values after a period of intense delivery pressure. - When team members would benefit from deeper reflection on their interactions and collaborative processes. - When you want to strengthen team bonds and foster a more supportive community environment. - When the team needs to practice patience and perseverance through challenging project phases. - When you want to encourage both personal growth and collective improvement simultaneously. ## Tips and tricks - Begin by explaining the connection between Ramadan principles and effective retrospectives - both emphasize reflection, community, and improvement. - Create a calm, thoughtful atmosphere for the session by minimizing distractions and encouraging participants to approach the discussion with mindfulness. - Encourage team members to listen deeply to each other without immediately jumping to solutions or judgments. - Balance reflection on past events with forward-looking improvement plans to ensure the retrospective leads to meaningful change. - Consider ending the retrospective with each team member sharing one thing they're grateful for about the team, reinforcing positive connections. - If team members come from diverse backgrounds, take time to briefly explain the principles of Ramadan that inspired this format to ensure everyone understands the context. ## Icebreaker questions - If you could develop one new habit that would improve our team's effectiveness, what would it be and why? - What's one small act of kindness from a team member that made a significant difference to you recently? --- # Pokémon Trainer's Journey Retrospective URL: https://www.teamretro.com/retrospective-templates/pokemon-trainers-journey-retrospective/ Gotta retro 'em all! The Pokémon Trainer's Journey retrospective transforms your team reflection into an adventure inspired by the world of Pokémon. Just as a trainer sets out from their hometown with big dreams, your team embarks on each sprint or project ready to catch wins, battle tough challenges, and level up along the way. This playful, themed format keeps energy high while still surfacing the honest insights every team needs to grow. Structured around four memorable stages of a trainer's journey, this retrospective invites participants to celebrate the Pokémon they caught (their achievements), reflect on the gym battles they fought (the challenges they faced), identify the badges they earned (skills and learnings gained), and chart the next route on their map (actions and goals for the future). The familiar gaming metaphors lower the barrier for sharing, encourage creative thinking, and make even difficult conversations feel approachable and fun. Ideal for agile teams, gaming communities, and anyone who loves a bit of nostalgia, this retrospective is a great way to break routine and keep your retros fresh. By framing progress as a continuous journey, teams build a growth mindset, recognise each other's contributions, and stay motivated to become the very best — like no team ever was. Whether you're wrapping up a sprint or a major release, this engaging format helps everyone reflect, connect, and plan their next adventure. ## Topics - **Pokémon We Caught**: What wins and achievements did we capture this time? - **Gym Battles We Fought**: What challenges or obstacles did we battle along the way? - **Badges We Earned**: What new skills, lessons or insights did we gain? - **The Next Route**: Where do we go next and what actions will get us there? ## When to use - When your team needs a fun, themed break from standard retrospective formats to re-energise reflection. - At the end of a sprint, project milestone, or major release to celebrate progress and plan ahead. - For gaming communities, hackathon teams, or playful cultures that enjoy gamified facilitation. - When you want to encourage a growth mindset by framing learning and challenges as part of an ongoing journey. - To make difficult conversations feel safer and more approachable through familiar, lighthearted metaphors. ## Tips and tricks - Set the scene at the start by reminding everyone they are trainers on a shared adventure — it primes creative, playful contributions. - Timebox each stage so the celebration of wins doesn't crowd out time for actions and goals. - Make sure the 'Gym Battles' stage stays constructive and blame-free; focus on the obstacle, not the person. - Encourage shout-outs in the 'Pokémon We Caught' stage so quieter team members get recognised. - Limit the number of actions in 'The Next Route' to a few achievable commitments with clear owners. - Don't worry if not everyone knows Pokémon — keep the metaphors light and explain the meaning of each stage clearly. ## Icebreaker questions - If you could have one Pokémon on your team this sprint, which would it be and why? - What's your team 'starter Pokémon' — the strength you always rely on to get going? --- # Taskmaster Trials Retrospective URL: https://www.teamretro.com/retrospective-templates/taskmaster-trials-retrospective/ Inspired by the beloved comedy game show, the Taskmaster Trials retrospective brings competitive fun and creative reflection to your team's review. Instead of the usual columns, your team works through a series of playful "tasks" or trials that prompt members to reflect on their challenges, clever solutions, points of frustration, and standout wins from the taks, last sprint or project. It's a fresh, energizing format that lowers the stakes and encourages even the quietest team members to share openly. The format works by framing reflection prompts as light-hearted challenges that mirror the unpredictable, lateral-thinking spirit of the show. Each trial uncovers a different dimension of the team's experience — the impossible tasks they faced, the ingenious workarounds they devised, the small wins worth celebrating, and the prizes (improvements) they want to claim next time. By gamifying the conversation, teams build psychological safety, spark laughter, and still surface the genuine insights and action items that drive continuous improvement. This approach is perfect for teams who feel fatigued by standard retrospective formats or who want to inject creativity and connection into their meetings. It celebrates effort and ingenuity while still holding space for honest discussion about obstacles, making it a great choice for building morale alongside meaningful change. ## Topics - **The Impossible Task**: What challenges felt impossible or unfair this sprint? - **Best Use of Initiative**: What clever solutions or creative workarounds did we pull off? - **Points on the Board**: What wins, big or small, deserve to be celebrated? - **Claim Your Prize**: What improvements do we want to win for next time? ## When to use - When you have completed a specific experiment, trial run or spike and want the team to reflect on the experience. - When you want to build morale and psychological safety by adding fun and laughter to the reflection process. - When quieter team members need a lower-stakes, playful framing to feel comfortable sharing openly. - When celebrating creativity and effort is just as important as identifying improvements, such as after a tough or intense sprint or spike. ## Tips and tricks - Lean into the playful framing — set the tone by introducing each trial with a bit of game-show flair to get the team relaxed and engaged. - Balance the fun with focus; make sure the 'Claim Your Prize' trial converts laughs into concrete, owned action items. - Time-box each trial to keep energy high and prevent any single challenge from dominating the conversation. - Encourage everyone to contribute to every trial so quieter voices are heard, not just the most vocal contestants. - Avoid turning 'The Impossible Task' into a blame game — keep the focus on the obstacle, not the person. - Rotate who 'awards points' or facilitates each round to share ownership and keep the format feeling collaborative. ## Icebreaker questions - If you were given a bizarre Taskmaster challenge right now, what hidden talent would help you win? - What's the most creative workaround you've ever used to solve an everyday problem? --- # Energy Levels Retrospective URL: https://www.teamretro.com/retrospective-templates/energy-levels/ The Energy Levels retrospective helps teams understand and optimize their collective energy and motivation. By visualizing energy as battery levels, teams can easily identify activities and practices that energize or drain them during sprints. This format encourages honest discussions about sustainable pace, work-life balance, and team motivation. It helps surface both energizing elements that should be amplified and draining factors that need to be addressed. Teams using this retrospective often discover practical ways to maintain high energy levels, reduce burnout, and create more engaging work environments. It's particularly effective for addressing team morale and well-being while identifying concrete actions to improve team dynamics. ## Topics - **Full Battery**: What energized you in the last sprint? - **Medium Battery**: What took up the right amount of energy in the last sprint? - **Low Battery**: What drained you in the last sprint? - **Re-charge**: What will re-energize you for the next sprint? ## When to use - When team morale seems low or inconsistent across sprints - After particularly challenging or intense work periods to assess team burnout - During times of organizational change to monitor team well-being - When trying to establish more sustainable work practices - To proactively address potential burnout before it becomes a problem ## Tips and tricks - Encourage honest feedback by sharing your own energy levels first - Look for patterns in what consistently energizes or drains the team - Focus on actionable solutions rather than just identifying problems - Consider both individual and team-wide energy factors - Use the insights to adjust sprint planning and work allocation - Follow up on implemented changes in subsequent retrospectives ## Icebreaker questions - What's one thing that always gives you an energy boost at work? - If you could eliminate one energy-draining task from your day, what would it be? --- # Wu Kong Retrospective URL: https://www.teamretro.com/retrospective-templates/wu-kong-retrospective/ The Wu Kong Retrospective is inspired by the classic Chinese novel 'Journey to the West' and the mischievous Monkey King. This playful template encourages teams to explore their recent challenges and successes through the metaphor of an epic adventure. Just as the Monkey King encountered obstacles and learned valuable lessons on his pilgrimage, teams can gain insights from reviewing their own 'journey' and the trials they overcame. This template fosters a spirit of curiosity, resilience, and continuous improvement. ## Topics - **Mischievous Moments**: Like the Monkey King's playful antics, what unexpected events or 'mischief' did you encounter? - **Formidable Foes**: What daunting challenges or 'demons' did you face on your journey? - **Enlightening Experiences**: What profound insights or 'wisdom' did you gain along the way? - **Sacred Sanctuaries**: What practices, processes or 'havens' provided strength and refuge? ## When to use - When your team could benefit from a fun, metaphorical approach to exploring challenges and growth. - After a particularly demanding project or 'epic journey' that had its share of ups and downs. - If you want to foster a spirit of curiosity, resilience, and continuous learning within your team. - When introducing or reinforcing agile values like adaptability, self-improvement, and embracing change. ## Tips and tricks - Encourage participants to embrace the metaphor and share stories in an engaging, narrative style. - Use imagery or props related to the Monkey King story to set the tone and spark creativity. - Celebrate both the team's mischievous moments and profound insights - growth often comes from unexpected places. - Look for opportunities to reframe challenges as learning experiences and sources of wisdom. - Remind the team that every journey has obstacles, but facing them with courage and an open mind leads to personal and professional growth. ## Icebreaker questions - If you could have a magical cloud like the Monkey King to travel anywhere, where would you go? - What supernatural power or ability would you want to have on an epic adventure? --- # Shout Out Spectacle URL: https://www.teamretro.com/retrospective-templates/shout-out-spectacle-retrospective/ Recognition is one of the most powerful drivers of team morale, yet it often gets lost in the rush of day-to-day delivery. The Shout Out Spectacle turns appreciation into a celebration, giving everyone a dedicated space to acknowledge the people, moments, and milestones that made a difference. It's a positive, energizing format that shines a spotlight on the contributions that too often go unnoticed. The format works by guiding your team through layers of recognition — from individual shout outs and team wins to lessons learned through generosity and the goals that deserve a public commitment. By making gratitude visible, you reinforce the behaviors you want to see more of, strengthen relationships, and build a culture where people feel genuinely valued. In TeamRetro, participants can quickly add and group their appreciation, vote on standout moments, and turn the warm feelings into shared action. Whether you're closing out a sprint, wrapping up a major project, or simply want to inject some positivity into your team rhythm, the Shout Out Spectacle helps you finish on a high note. It's especially useful for boosting engagement, recognizing remote and hybrid contributors equally, and reminding everyone why the work — and the people doing it — matter. ## Topics - **Indivvidual Shout Outs**: Who deserves a public thank you this time? - **Team Wins**: What did we achieve together worth celebrating? - **Lessons in Generosity**: Where did support, sharing, or kindness make a difference? - **Future celebrations**: What should we commit to and celebrate next? ## When to use - At the end of a sprint or project when you want to finish on a high and reinforce positive momentum. - When team morale needs a lift or recognition has been lacking in recent weeks. - For distributed or hybrid teams where contributions can easily go unseen and deserve a spotlight. - After a particularly challenging period, to acknowledge the effort and support that pulled the team through. - As a regular cadence to build a sustainable culture of appreciation and gratitude. ## Tips and tricks - Encourage specificity — naming the exact action behind a shout out makes recognition far more meaningful than generic praise. - Make sure recognition is distributed fairly; gently prompt the group to acknowledge quieter or behind-the-scenes contributors. - Keep the energy high by reading shout outs aloud and letting people add reactions or votes to amplify standout moments. - Avoid letting it become a popularity contest — frame the session around behaviors and impact, not personalities. - Time-box each section so the celebration stays lively and doesn't drift into a generic catch-up. - Close by converting the goodwill into commitments with clear owners so appreciation leads to lasting change. ## Icebreaker questions - If you could give yourself a fun award for this sprint, what would it be called? - Who is someone outside this team who deserves a shout out, and why? --- # Halloween Retrospective URL: https://www.teamretro.com/retrospective-templates/halloween-retrospective/ Transform your team retrospective into a spooktacular event with the Halloween Retrospective format. This engaging approach uses the familiar trick-or-treat concept to explore team experiences, where 'treats' represent positive outcomes and successes, while 'tricks' highlight challenges and areas for improvement. Drawing inspiration from Halloween traditions, this format creates a playful atmosphere that encourages open dialogue and creative problem-solving. Team members can share their 'treats' - celebrating wins and positive practices, while also addressing the 'tricks' - identifying obstacles and opportunities for growth. The Halloween theme helps reduce tension around difficult conversations by framing feedback in a lighthearted context. This makes it easier for team members to discuss challenges while maintaining a constructive and enjoyable atmosphere. The format is particularly effective for teams who appreciate themed activities or need to inject some fun into their retrospective routine. ## Topics - **Sweet Treats**: What successes or positive moments should we celebrate? - **Tricky Situations**: What challenges or obstacles did we encounter? - **Magic Spells**: What solutions or improvements could we implement? - **Costume Party**: What new roles or perspectives should we try? ## When to use - When you want to make retrospectives more engaging and fun, especially around the Halloween season - When the team needs a creative way to discuss challenges and improvements in a less formal setting - When you want to encourage more open and honest feedback through a playful theme ## Tips and tricks - Encourage participants to use Halloween-themed metaphors when sharing their feedback - Keep the atmosphere light and playful while still addressing serious improvement opportunities - Consider using Halloween-themed rewards or recognition for particularly valuable insights - Set a time limit for each 'trick or treat' discussion to maintain momentum - Follow up on action items from previous retrospectives before introducing new ones ## Icebreaker questions - What's the scariest bug or technical challenge you've encountered in your career? - If you could dress up as any famous tech personality for Halloween, who would it be and why? --- # Monthly Milestone Map Retrospective URL: https://www.teamretro.com/retrospective-templates/monthly-milestone-map-retrospective/ Stepping back at the end of each month gives teams a powerful vantage point to see how far they've come and where they're headed next. The Monthly Milestone Map turns a month's worth of work into a visual journey, helping your team celebrate progress, surface lessons, and align on the road ahead. Rather than getting lost in the day-to-day, this retrospective zooms out to capture the bigger picture across a longer cadence than a typical sprint review. The format works by guiding your team through four reflective stations: the milestones you reached, the obstacles you navigated, the insights you gathered, and the goals you're setting for the month to come. As everyone contributes, patterns emerge that single-sprint retrospectives often miss, making it ideal for teams that operate on monthly rhythms or want a regular checkpoint to recalibrate. The collaborative mapping approach keeps the conversation grounded in real outcomes while staying forward-looking. By running a Monthly Milestone Map in TeamRetro, you create a shared record of achievements and learnings that builds momentum month over month. It strengthens team alignment, reinforces a culture of continuous improvement, and ensures hard-won lessons translate into concrete actions. Whether you're a community group, a product team, or a cross-functional squad, this retrospective helps you honour progress and plan with purpose. ## Topics - **Milestones Reached**: What key achievements and milestones did we hit this month? - **Obstacles Navigated**: What challenges did we face and how did we work through them? - **Lessons Learned**: What insights or learnings can we carry forward? - **Goals Ahead**: What do we want to achieve in the month ahead? ## When to use - Your team works on a monthly cadence and wants a regular checkpoint to review progress and plan ahead. - You want to zoom out beyond individual sprints to see broader patterns, achievements, and recurring challenges. - You're leading a community group, volunteer team, or cross-functional squad that benefits from celebrating milestones together. - You want to turn a month's lessons into concrete goals and maintain momentum over time. ## Tips and tricks - Gather a few key metrics or milestones before the session so the team has a shared reference point to anchor the discussion. - Keep the tone celebratory when reviewing milestones — recognising wins builds morale and motivation for the month ahead. - Frame obstacles as learning opportunities rather than failures to encourage open, blame-free conversation. - Limit the number of goals you set so the team stays focused and the commitments remain achievable. - Use anonymous brainstorming first to ensure quieter voices and dissenting views are captured before group discussion. - Revisit last month's goals at the start of the session to keep accountability and continuity front of mind. ## Icebreaker questions - If this past month were a movie title, what would it be called? - What's one thing you're personally proud of from the last month, work or otherwise? --- # Among Us (Agile Edition) Retrospective URL: https://www.teamretro.com/retrospective-templates/among-us-agile-edition-retrospective/ Inspired by the wildly popular social-deduction game, the Among Us (Agile Edition) retrospective turns the hunt for "impostors" into a playful framework for spotting what's secretly sabotaging your team's flow. Instead of accusing crewmates, your team identifies the hidden blockers, sneaky inefficiencies, and unspoken tensions that quietly undermine progress — then celebrates the "crewmates" and behaviours keeping everyone on course. It's a fun, gamified spin on the classic sprint retrospective that lowers the stakes and gets even quiet team members talking. The format works by framing reflection around game roles: completing tasks (what's done well), reporting suspicious activity (blockers and friction), identifying impostors (root causes of problems), and voting on next actions (improvements to commit to). This metaphor makes it psychologically safe to surface uncomfortable truths because the "blame" lands on the impostor concept rather than individuals. Teams find it especially useful for breaking up retro fatigue and re-energising recurring sprint reviews with a theme everyone instantly recognises. Run it in TeamRetro to keep the energy high while still capturing structured, actionable outcomes. Whether you're a Scrum team, a DevOps squad, or a remote group looking for a lighthearted yet meaningful check-in, this themed retrospective helps you uncover the real problems, recognise good work, and emerge with a clear plan — all while having a bit of fun along the way. ## Topics - **Tasks Completed**: What did we accomplish and do well this sprint? - **Suspicious Activity**: What felt off, slowed us down or raised red flags? - **Spot the Impostor**: What is the real root cause secretly sabotaging us? - **Vote to Eject**: What actions will we commit to next sprint? ## When to use - When recurring sprint retrospectives have grown stale and the team needs a fun, gamified format to re-engage. - When you want to surface hidden blockers and root causes in a psychologically safe, low-blame way. - When the team enjoys playful themes and you want quieter members to open up more easily. - When onboarding a new team and you want a lighthearted icebreaker that still produces real action items. ## Tips and tricks - Keep the 'impostor' framing aimed at processes and root causes, never at individuals, to maintain psychological safety. - Time-box each column so the playful theme doesn't eat into reaching real, actionable outcomes. - Use dot voting to decide which impostor is causing the most damage before agreeing on actions. - Lean into the theme with a fun icebreaker but bring everyone back to focus when it's time to commit to actions. - Limit the number of actions you 'eject' so the team can realistically deliver them next sprint. - Revisit last retro's actions at the start to check whether previous impostors were truly ejected. ## Icebreaker questions - If you were the impostor on our team this sprint, what task would you have faked doing? - Which fictional crewmate (cautious, chaotic, or always-doing-tasks) best matches your work style this sprint? --- # Buddy Boost Retrospective URL: https://www.teamretro.com/retrospective-templates/buddy-boost-retro-retrospective/ Recognition is the fuel that keeps great teams moving, and the Buddy Boost Retrospective puts peer appreciation front and centre. Instead of focusing purely on processes and problems, this format invites teammates to shout out the people who made a difference, the support they received, and the small wins that often go unnoticed. It's a warm, energising way to close out a sprint, project, or milestone while reinforcing the connections that make collaboration thrive. Here's how it works: participants reflect on the people around them and share the moments where a colleague boosted their day, helped them over a hurdle, or simply made work more enjoyable. As ideas surface in TeamRetro, the team groups related shout-outs, votes on the standout themes, and turns gratitude into actionable commitments, such as continuing helpful behaviours or spreading good practices across the wider group. The result is a positive, psychologically safe space where appreciation is visible and intentional. The benefits go well beyond a feel-good moment. Regular peer recognition is linked to higher engagement, stronger trust, and better retention, and the Buddy Boost Retrospective makes that recognition a repeatable team habit. Use it to balance more critical retrospectives, to lift morale during demanding periods, or to onboard new members by helping the team appreciate each other's strengths and contributions. ## Topics - **Shout Outs**: Who made a positive difference for you recently? - **Helping Hands**: Where did support or collaboration help us succeed? - **Feel-Good Moments**: What moments lifted your spirits or energy? - **Boost Forward**: How can we keep the appreciation and support going? ## When to use - After an intense sprint or project crunch when the team needs a morale lift and a chance to recognise each other's effort. - As a regular ritual to balance more problem-focused retrospectives and keep peer appreciation a consistent habit. - When onboarding new members, to help the team learn each other's strengths and build trust quickly. - Following a major milestone or launch, to celebrate contributions and reinforce the behaviours that led to success. ## Tips and tricks - Encourage specific shout-outs that name a person and the exact action, since vague praise feels less genuine and memorable. - Keep an eye on inclusivity, ensure quieter or behind-the-scenes contributors are recognised, not just the loudest voices. - Set a positive tone up front and reassure everyone that no contribution is too small to celebrate. - Timebox the session so it stays energising, around 30-45 minutes is usually plenty for a focused boost. - Capture commitments under Boost Forward so appreciation translates into ongoing team habits rather than a one-off. - Mix up who facilitates so recognition feels owned by the whole team, not just the manager or scrum master. ## Icebreaker questions - If you could give your teammate a fun award title for this sprint, what would it be? - Who in the team would you want on your side in a zombie apocalypse, and why? --- # Sales Team Retrospective URL: https://www.teamretro.com/retrospective-templates/sales-team-retrospective/ Sales teams thrive on momentum, but rarely pause to ask what's actually driving—or stalling—their results. The Sales Team Retrospective gives your reps, SDRs, and managers a dedicated space to step back from the daily grind of calls, demos, and quotas to reflect on what worked, what didn't, and what to do differently next cycle. It turns scattered anecdotes about lost deals and big wins into shared, actionable insights the whole team can rally behind. Running this retrospective is simple: the team reflects on the past sales period across structured topics like wins, lost opportunities, process bottlenecks, and ideas to test. Everyone contributes ideas in TeamRetro, groups related themes, votes on what matters most, and turns the top discussion points into clear action items with owners. Because sales performance is so measurable, this format pairs especially well with reviewing pipeline data, conversion rates, and quota attainment alongside the qualitative feedback from the team. The benefit is a faster, more collaborative feedback loop that helps you refine your sales playbook, improve win rates, and keep your team motivated and aligned. Whether you run it after a monthly close, the end of a quarter, or a major campaign, a regular sales retrospective builds a culture of continuous improvement where reps learn from each other instead of repeating the same mistakes deal after deal. ## Topics - **Wins to Celebrate**: Which deals, milestones, or moments went really well? - **Lost Deals & Roadblocks**: What deals slipped away or what got in our way? - **Process & Tools**: How well are our workflows, CRM, and tools supporting us? - **Ideas to Test**: What should we try or improve next cycle? ## When to use - At the end of a monthly or quarterly sales close to review performance and reset goals. - After a major product launch, campaign, or pricing change to assess its impact on selling. - When win rates or pipeline velocity are declining and the team needs to diagnose why. - Following the onboarding of new reps to refine the sales playbook and share knowledge. - Whenever the team wants to celebrate wins and maintain momentum through a tough quarter. ## Tips and tricks - Pair qualitative reflections with hard data—pull up win rates, quota attainment, and pipeline metrics so the conversation stays grounded in reality. - Keep the tone blame-free when discussing lost deals; frame losses as shared learning opportunities rather than individual failures. - Give quieter reps space to contribute by using TeamRetro's independent idea entry before group discussion, so louder voices don't dominate. - Limit action items to two or three high-impact experiments per retrospective so the team can actually follow through before the next cycle. - Rotate the facilitator role between reps and managers to keep perspectives fresh and ownership shared. - Always review last cycle's action items at the start so the retrospective drives real, accountable change over time. ## Icebreaker questions - If your sales month were a weather forecast, what would it be and why? - What's the best 'no' you received this cycle—and what did it teach you? --- # Company Culture Retrospective URL: https://www.teamretro.com/retrospective-templates/company-culture-retrospective/ A company culture retrospective is a structured activity that allows teams to reflect on the current state of their organizational culture, identify strengths and areas for improvement, and develop actionable steps to foster a more positive and productive work environment. This retrospective encourages open dialogue and honest feedback from stakeholders across the company. By examining various aspects of the culture, such as values, communication, leadership, and employee engagement, teams can gain valuable insights and develop strategies to align the culture with the company's mission and goals. The retrospective format promotes active participation, facilitates constructive discussions, and empowers teams to take ownership of shaping the desired culture. It is a powerful tool for continuous improvement and can lead to increased employee satisfaction, better collaboration, and a more cohesive and high-performing organization. ## Topics - **Our Core Values**: How well do our actions align with the company's stated values? - **Communication and Collaboration**: How effective is our communication and collaboration across teams and departments? - **Leadership and Management**: How effective is our leadership in setting the right tone and direction? - **Innovation and Growth**: How well does our culture support innovation, creativity, and professional growth? - **Employee Engagement**: How engaged and motivated are employees in their work? - **Diversity and Inclusion**: How inclusive and welcoming is our culture for diverse perspectives and backgrounds? ## When to use - When conducting a periodic review of the company's culture to identify strengths, weaknesses, and areas for improvement. - During times of organizational change or transformation, to ensure alignment and buy-in from stakeholders. - As part of a strategic planning process, to ensure the culture supports the company's vision and goals. - When onboarding new employees, to introduce them to the company's culture and values. - After a significant event or milestone, to assess the impact on the culture and make necessary adjustments. ## Tips and tricks - Encourage open and honest feedback by creating a safe and judgment-free environment. - Involve stakeholders from various levels and departments to gain diverse perspectives. - Use anonymous feedback mechanisms to allow for candid responses without fear of repercussions. - Prioritize actionable insights and develop a clear plan for addressing identified areas of improvement. - Celebrate and reinforce positive aspects of the culture that align with the company's values and goals. - Regularly revisit and reassess the culture to ensure continuous improvement and alignment with the evolving needs of the organization. ## Icebreaker questions - If our company culture were an animal, what animal would it be and why? - Share a personal experience or story that exemplifies our company's culture at its best. --- # 4-Week Sprint Retrospective URL: https://www.teamretro.com/retrospective-templates/4-week-sprint-sprint-retrospective/ Stretching a sprint to four weeks gives teams more room to deliver complex work, but it also means a lot can happen between retrospectives. The 4-Week Sprint Retrospective is designed to help teams pause at the end of a longer cycle, look back across the entire month, and surface the patterns, milestones, and learnings that shorter retros can miss. It encourages everyone to zoom out, connect the dots across multiple weeks, and capture what truly mattered. The format works by guiding your team through four reflective lenses: what went well, what slowed you down, what you learned, and what to commit to next. Because a four-week sprint covers more ground, this structure helps you separate the signal from the noise and prioritise the changes that will have the biggest impact. In TeamRetro, participants add their thoughts anonymously, group similar ideas, vote on priorities, and turn insights into clear, trackable action items. This longer-cadence retrospective is ideal for teams running monthly sprints or those whose work doesn't fit neatly into one- or two-week cycles. By regularly reflecting at the end of each four-week period, your team builds a habit of continuous improvement, keeps morale high by celebrating progress, and ensures that recurring blockers get addressed before they become entrenched. The result is a more aligned, resilient, and forward-looking team. ## Topics - **What went well?**: Which wins and successes stood out this month? - **What slowed us down?**: What blockers or friction held the team back? - **What did we learn?**: What new insights or knowledge did we gain this month? - **What will we commit to?**: What actions will we take into the next sprint? ## When to use - Your team runs monthly or four-week sprints and needs a retrospective cadence that matches that rhythm. - Work is complex or spans multiple weeks, making shorter retrospectives feel too granular. - You want to step back and identify longer-term patterns, recurring blockers, and accumulated learnings. - You're closing out a major milestone or release at the end of a longer delivery cycle. ## Tips and tricks - Because a four-week sprint covers a lot of ground, share a quick timeline or summary of key events beforehand so the team can recall early-month moments as well as recent ones. - Timebox each topic to keep the session moving — longer sprints generate more ideas, so grouping similar items helps prevent overwhelm. - Use anonymous input to encourage honest feedback about blockers, especially around sensitive process or cross-team issues. - Limit your action items to two or three high-impact commitments so the team can realistically deliver on them within the next cycle. - Revisit the previous sprint's commitments at the start of the retro to build accountability and track progress over time. - Rotate the facilitator role each month to keep the format fresh and give everyone a sense of ownership. ## Icebreaker questions - If you had to sum up the past four weeks in a single emoji, what would it be and why? - What's one thing from this month — work or personal — that made you smile? --- # Ticket Resolution Retrospective URL: https://www.teamretro.com/retrospective-templates/ticket-resolution-retrospective/ A Ticket Resolution Retrospective is a focused meeting for teams to analyze their ticket management processes and identify areas for improvement. By reflecting on recent tickets, teams can pinpoint bottlenecks, inefficiencies, and opportunities to streamline workflows. This retrospective encourages open discussion about challenges faced during ticket resolution, successful strategies employed, and lessons learned. The goal is to continuously enhance ticket handling procedures, leading to faster response times, better communication, and increased customer satisfaction. This retrospective format has proven valuable for any team dealing with a high volume of support tickets or project requests. It fosters a culture of continuous improvement and empowers teams to take ownership of their processes. ## Topics - **Ticket Highlights**: What tickets stood out, and why? - **Process Challenges**: What process issues impacted ticket resolution? - **Communication Gaps**: Where did communication break down? - **Improvement Ideas**: How can we enhance our ticket processes? ## When to use - After a major incident or service outage to analyze the ticket response process. - When customer satisfaction scores related to ticket handling are declining. - After onboarding a new ticketing system or making significant process changes. - On a recurring basis (e.g., monthly or quarterly) to continuously improve. - When there are persistent bottlenecks or inefficiencies in ticket resolution workflows. ## Tips and tricks - Encourage participation from all team members involved in the ticket lifecycle, including support agents, developers, and managers. - Review a diverse range of tickets, including both successes and challenges, to gain a well-rounded perspective. - Avoid blame or finger-pointing; focus on constructive feedback and process improvements. - Prioritize action items and assign owners to ensure follow-through on proposed changes. - Consider inviting customers or stakeholders to share their experiences and perspectives. - Celebrate wins and positive outcomes to maintain team morale and motivation. ## Icebreaker questions - If you could instantly resolve any one type of ticket, which would it be and why? - Share a humorous or memorable experience from a recent ticket interaction. --- # Drop Add Keep Improve Retrospective URL: https://www.teamretro.com/retrospective-templates/daki-retrospective/ The Drop Add Keep Improve (DAKI) retrospective is a simple yet powerful way to review processes, projects, or team dynamics. It prompts participants to reflect on what should be dropped (stopped), added (started), kept (continued), and improved (enhanced). This format provides a structured approach to gather feedback and drive positive change. By focusing on these four key areas, teams can quickly identify strengths, weaknesses, and opportunities for growth. The DAKI retrospective originated in the Lean manufacturing principles but has been widely adopted in various industries, including software development, due to its effectiveness in continuous improvement. ## Topics - **Drop**: What practices should we stop or discontinue? - **Add**: What new practices should we adopt? - **Keep**: What's working well that we should continue? - **Improve**: What could we do better? ## When to use - At the end of a project, sprint, or major milestone to review what went well and what could be improved. - When a team is struggling with specific processes, tools, or dynamics and needs to identify areas for change. - As a regular check-in (e.g., monthly or quarterly) to continuously improve and adapt team practices. ## Tips and tricks - Encourage open and honest feedback by creating a safe, blame-free environment. - Use anonymous or private voting techniques if the team is hesitant to voice concerns openly. - Prioritize the most impactful items in each category and create actionable next steps. - Follow up on agreed improvements in subsequent retrospectives to ensure continuous progress. - Consider rotating the facilitator role to get fresh perspectives and ensure shared responsibility. - Set a positive tone by starting and ending with items in the 'Keep' category to reinforce what's going well. ## Icebreaker questions - If our team was a vehicle, what kind would it be and why? - What's one thing you've learned or improved on since our last retrospective? --- # Fishbone (Ishikawa) Retrospective URL: https://www.teamretro.com/retrospective-templates/fishbone-ishikawa-retrospective/ The Fishbone (Ishikawa) Retrospective is a structured problem-solving approach that helps teams identify and understand the root causes of challenges or issues. Developed by Kaoru Ishikawa in the 1960s, this technique visualizes cause-and-effect relationships in a format resembling a fish skeleton. During the retrospective, teams explore six key dimensions that might contribute to their challenges: Systems, Processes, Forms, People, Policies, and Place. This comprehensive analysis ensures no potential factor is overlooked, leading to more effective solutions. This method is particularly valuable for teams dealing with complex problems where multiple factors may be at play. By organizing potential causes into distinct categories, teams can better understand the relationships between different issues and develop targeted improvements. A fishbone diagram (also called an Ishikawa diagram or a cause-and-effect diagram — the three names refer to the same tool) works by writing the problem at the "head" of the fish and drawing the major cause categories as bones branching off the spine. In its original manufacturing and quality-management form, those categories are the classic "6 Ms": Manpower (people), Method (process), Machine (equipment), Material (inputs), Measurement (data and metrics), and Mother Nature (the surrounding environment). Teams brainstorm possible causes under each bone, then keep asking "why?" to trace each branch down to its root cause rather than stopping at the visible symptom. The categories in this TeamRetro template — System, Process, Forms, People, Policies, and Place — are a team-process adaptation of the same 6 Ms method, retuned for software and knowledge-work teams rather than a factory floor. The technique is identical; only the category labels change to fit the kind of work you do. For example, if the problem at the head of the fish is "releases keep slipping," a People cause might be "key reviewer is a bottleneck," a Process cause might be "no definition of done," and a System cause might be "flaky CI pipeline." Mapping causes this way stops a team fixing symptoms and missing the underlying driver. ## Topics - **System**: What technology, software, or tools might be affecting our team's performance or outcomes? - **Process**: What workflows or sequences of activities are causing delays or inefficiencies in our work? - **Forms**: What issues with our templates or documentation could be impacting clarity or accuracy? - **People**: What factors related to individual or team skills, communication, or roles are affecting our success? - **Policies**: What guidelines or rules might be misaligned with our actual practices or creating challenges? - **Place**: What aspects of our physical or virtual workspace might be impacting our collaboration or productivity? ## When to use - When facing complex problems that may have multiple root causes or contributing factors - After identifying a significant issue or challenge that requires systematic analysis - When the team needs to move beyond symptoms to understand underlying causes - During project post-mortems or incident reviews to prevent future problems ## Tips and tricks - Start with the effect or problem statement clearly defined at the 'head' of the fish - Encourage equal participation from all team members across all categories - Focus on identifying causes rather than jumping to solutions too quickly - Use the 'Five Whys' technique within each category to dig deeper into root causes - Document all insights, even if they don't initially seem significant - Schedule enough time (90-120 minutes) to explore all categories thoroughly ## Icebreaker questions - If our team were a machine, what part would need the most maintenance right now? - What's the most surprising solution you've discovered to a recurring problem? --- # Cross-Team Collaboration Retrospective URL: https://www.teamretro.com/retrospective-templates/cross-team-collaboration-retrospective/ The Cross-Team Collaboration and Synergy Retrospective is a powerful team activity designed to foster open communication, build trust, and enhance collaboration across teams. By analyzing cross-team interactions, communication channels, and enablement factors, teams can identify areas for improvement and develop strategies to strengthen synergy and teamwork. This retrospective encourages teams to reflect on their experiences, share insights, and collectively brainstorm solutions to overcome silos, break down barriers, and cultivate a culture of collaboration. Through facilitated discussions and interactive exercises, participants gain a deeper understanding of each other's roles, challenges, and perspectives, paving the way for more effective cross-functional collaboration. By embracing this retrospective, teams can unlock their full potential, leverage diverse strengths, and achieve greater success through seamless cooperation and shared goals. ## Topics - **Collaboration Enablers**: What factors or practices have enabled effective collaboration across teams? - **Communication Challenges**: What communication barriers or breakdowns have hindered cross-team collaboration? - **Synergy Opportunities**: Where do you see opportunities for teams to collaborate more effectively and create synergies? - **Trust and Psychological Safety**: How can we build trust and create a psychologically safe environment for cross-team collaboration? - **Ideal Outcomes**: What are the potential benefits and ideal outcomes of effective cross-team collaboration? ## When to use - When teams are working on cross-functional projects or initiatives that require collaboration across multiple teams. - When there are communication breakdowns, siloed mindsets, or a lack of trust hindering effective collaboration. - When teams want to identify opportunities for synergy and leverage each other's strengths and expertise. - When teams are undergoing organizational changes or restructuring that impact cross-team dynamics. - As a regular check-in to assess the state of cross-team collaboration and identify areas for improvement. ## Tips and tricks - Encourage open and honest communication by creating a safe space for participants to share their perspectives without fear of judgment or repercussions. - Ensure that all teams and roles are represented in the retrospective to capture diverse viewpoints and experiences. - Use visual aids, such as diagrams or process maps, to help participants better understand cross-team interactions and dependencies. - Assign a dedicated facilitator to guide the discussions, manage time effectively, and ensure that all participants have an opportunity to contribute. - Follow up on action items and commitments made during the retrospective to ensure that improvements are implemented and progress is tracked. - Consider involving stakeholders or leadership representatives to provide context, support, and buy-in for any proposed changes or initiatives. ## Icebreaker questions - If you could collaborate with any team or department in the organization, which one would it be and why? - Share a memorable experience where cross-team collaboration led to a significant achievement or breakthrough. --- # Silicon Valley Startup Sprint Retrospective URL: https://www.teamretro.com/retrospective-templates/silicon-valley-startup-sprint-retrospective/ Channel the fast-paced, high-energy spirit of a Silicon Valley startup into your team's reflection. The Silicon Valley Startup Sprint Retrospective is built for teams who live by the mantra of building, measuring, and learning — and who want a retrospective format that mirrors the lean, iterative culture of the world's most innovative companies. Instead of dwelling only on what broke, this format pushes teams to think like founders: validating assumptions, doubling down on what creates value, and ruthlessly cutting what doesn't. The format guides your team through four startup-inspired lenses: what shipped and won, what slowed us down, what we learned, and where we should pivot or persevere. Borrowing from lean startup thinking popularized by Eric Ries in The Lean Startup, each topic encourages a hypothesis-driven mindset where every sprint is an experiment and every result is data. This keeps conversations forward-looking and action-oriented rather than getting stuck in blame. By framing your sprint review through a startup lens, teams build a culture of rapid learning, customer obsession, and bold decision-making. It's especially powerful for product squads, founders, and innovation teams who want to maintain velocity without losing sight of direction. Run it regularly in TeamRetro to keep your team agile, ambitious, and always shipping value. ## Topics - **Shipped & Won**: What did we ship that created value this sprint? - **What Slowed Us Down**: What blockers or friction killed our velocity? - **What We Learned**: What new insight or validated learning did we gain? - **Pivot or Persevere**: What should we double down on, change, or cut? ## When to use - At the end of a product sprint when you want a fast, forward-looking review that mirrors lean startup thinking. - For startup teams, founders, and innovation squads who want to keep velocity high while staying focused on customer value. - When the team is wrestling with a key decision and needs a structured way to decide whether to pivot, persevere, or cut. - To inject fresh energy into retrospectives that have become routine, using a build-measure-learn framing. ## Tips and tricks - Set the tone up front: this is about learning fast, not assigning blame. Psychological safety drives honest input. - Encourage hypothesis-driven language — what did we assume, and what did the results actually show? - Timebox each topic to keep the startup pace; momentum matters more than exhaustive lists. - In the Pivot or Persevere stage, push for clear decisions with owners rather than vague intentions. - Watch for the loudest voice dominating — use anonymous input in TeamRetro so quieter members shape the wins and decisions too. - Track recurring blockers across sprints to spot the systemic issues worth a bigger investment to fix. ## Icebreaker questions - If your team were a startup pitching at a demo day, what would your one-line elevator pitch be? - Which famous tech founder's mindset would you want to channel for this sprint, and why? --- # Meme Madness Retrospective URL: https://www.teamretro.com/retrospective-templates/meme-madness-retrospective/ Who says retrospectives have to be serious? The Meme Retrospective brings the internet's favorite form of communication into your team's feedback loop, using the classic Stop, Start, Continue format to surface insights with a healthy dose of humor. By framing team reflections through the lens of memes, you create a psychologically safe space where even the toughest feedback lands with a smile — because nothing softens a hard truth like a perfectly placed meme reference. This format works brilliantly for teams that thrive on visual culture and shared humor. Whether you're referencing "This is fine 🔥" for things you need to stop doing, "Distracted Boyfriend" for shiny new ideas to start, or "One Does Not Simply" for the habits worth continuing, memes act as a universal shorthand that gets everyone on the same page fast. The result? A retrospective that's not only fun but surprisingly candid — people open up more when they're laughing together. The Meme Retrospective is ideal after sprints packed with collaboration, creative problem-solving, or even a few chaotic moments worth immortalizing. It's a community favorite for remote and hybrid teams looking to inject energy into their regular cadence. Inspired by the agile retrospective tradition of continuous improvement, this format keeps the spirit of reflection alive while making sure your team actually looks forward to the meeting. ## Topics - **Stop (The "This is Fine" Meme)**: What should we stop doing that's quietly burning us down? - **Start (The "Distracted Boyfriend" Meme)**: What shiny new ideas or practices should we finally commit to? - **Continue (The "One Does Not Simply" Meme)**: What's working so well it would be chaos to stop? ## When to use - Best used after a sprint or project phase that had a mix of highs and lows — the humor helps the team process both without defensiveness. - Great for remote or hybrid teams who rely on digital communication and already share memes in team channels, making the format feel natural and familiar. - Use this template when team morale needs a boost and you want to make the retrospective something people actually look forward to attending. - Ideal for teams that have been running the same retrospective format for a while and need a fresh, engaging way to surface the same important feedback. - Perfect for onboarding new team members into the retro culture — the lighthearted format lowers the barrier to participation and encourages everyone to contribute. ## Tips and tricks - Set the tone early by sharing a relevant meme in the meeting intro — it signals that humor is welcome and gets people in the right headspace. - Encourage participants to reference actual meme formats in their responses (e.g., 'Drake pointing,' 'Expanding Brain') to keep the energy light and creative, but remind the team that the underlying feedback should still be genuine and actionable. - Watch out for the retro becoming all laughs and no action items — make sure to close each topic by identifying at least one concrete next step the team will commit to. - If some team members are less familiar with meme culture, do a quick 2-minute 'meme primer' at the start or share a few examples in the meeting notes beforehand so no one feels left out. - Use dot voting to prioritize the most important items in each category — even in a fun retro, focus is key to driving real improvement. - Keep the session timeboxed to 60 minutes or less. The meme format naturally keeps energy high, but fatigue can set in quickly if the meeting drags on. ## Icebreaker questions - If your last sprint were a meme, which one would it be and why? - What's a meme that perfectly describes your current relationship with your to-do list? --- # Team Work Makes the Dream Work Retrospective URL: https://www.teamretro.com/retrospective-templates/team-work-makes-the-dream-work-retrospective/ Great results rarely come from individuals working in isolation — they come from teams that trust each other, communicate openly, and pull in the same direction. The Team Work Makes the Dream Work retrospective puts collaboration front and center, giving your team a structured space to reflect on how well they're working together and where they can grow stronger as a unit. This retrospective works by guiding your team through reflections on shared goals, communication, support, and the dynamics that either help or hinder collaboration. Rather than focusing purely on tasks and deliverables, it shines a light on the human side of teamwork — the trust, the handoffs, the moments of support, and the friction points that quietly slow everyone down. By naming what's working and what isn't, teams build the self-awareness needed to operate as a cohesive, high-performing group. The real value lies in turning insights into action. Use this team building retrospective to reinforce the behaviours that make collaboration feel effortless, address the obstacles that get in the way, and commit to small changes that make a big difference. Whether you're a newly-formed group finding your rhythm or an established team looking to level up, this format helps you make the dream work, together. ## Topics - **Dream Goals**: What shared goals are we chasing together? - **Working Together**: What helped us collaborate effectively as a team? - **Out of Sync**: Where did teamwork break down or cause friction? - **Make the Dream Work**: What will we do to strengthen teamwork going forward? ## When to use - When a newly-formed team is finding its rhythm and wants to establish strong collaboration habits early. - When an established team senses friction, silos or communication breakdowns slowing them down. - After completing a major project or milestone to reflect on how well the team worked together. - As a periodic team building check-in to reinforce trust, alignment and shared purpose. - When onboarding new members and you want to align everyone around how the team collaborates. ## Tips and tricks - Set a positive, blame-free tone from the start so people feel safe sharing honest reflections about teamwork. - Encourage quieter team members to contribute by using anonymous brainstorming before grouping and voting on ideas. - Focus on behaviours and situations rather than individuals to keep friction points constructive and safe. - Limit your action items to two or three meaningful commitments so the team can actually follow through. - Revisit the actions from your previous retrospective at the start to build accountability and show progress. - Celebrate the wins and the moments of great collaboration — recognition reinforces the behaviours you want more of. ## Icebreaker questions - If our team were a sports team, what position would you play and why? - What's the best team you've ever been part of, and what made it work? --- # Cowboy Roundup Retrospective URL: https://www.teamretro.com/retrospective-templates/cowboy-roundup-retrospective/ Saddle up, partner! The Cowboy Roundup retrospective brings a playful Wild West spirit to your team reflection, turning the usual review into a memorable trail ride. Inspired by the imagery of cowboys herding cattle across open plains, this themed format invites the team to celebrate their best rides, wrangle the stray issues that wandered off, dodge the obstacles on the path, and chart the trail ahead. The lighthearted framing lowers the stakes of giving feedback and makes it easier for everyone to speak up honestly. Each topic maps a classic retrospective question onto a frontier metaphor, so the team reflects on what went well, what caused trouble, what got in the way, and where they're heading next. The narrative theme keeps energy high and engagement strong, which is especially valuable for teams that have grown tired of standard retrospective formats. By framing problems as "strays" to be rounded up rather than failures to be blamed, the format encourages a constructive, blame-free conversation. Best run at the end of a sprint, project milestone, or quarter, the Cowboy Roundup works just as well for distributed teams in TeamRetro as it does for co-located ones. The familiar structure of celebrate, identify, remove, and plan ensures you still produce concrete, actionable outcomes while having a bit of fun along the way. It's a great pick when you want to re-energize tired retros without sacrificing the value of genuine team improvement. ## Topics - **Best Rides**: What went well and made you proud on the trail? - **Stray Cattle**: What wandered off course or caused trouble? - **Rough Terrain**: What obstacles slowed the team down? - **Next Trail**: Where should we head and what should we try next? ## When to use - At the end of a sprint when the team wants a fresh, energising twist on the standard retrospective format. - After a major project or release milestone to celebrate wins and round up lingering issues. - When standard retrospectives feel stale and you want to re-engage a tired or disengaged team. - For quarterly reviews where you want both reflection on the past and a clear plan for the trail ahead. - With distributed or hybrid teams who benefit from a playful theme to break the ice and boost participation. ## Tips and tricks - Lean into the theme - use Wild West language and maybe a fun background or avatar to set the mood and boost engagement. - Keep the Stray Cattle topic blame-free by focusing on issues and systems rather than individuals. - Timebox each topic so the celebration of Best Rides doesn't crowd out the planning in Next Trail. - Use voting to prioritise the most important strays and obstacles before the group discusses them in depth. - Convert the top ideas from Next Trail into clear action items with owners and due dates so improvements actually happen. - Encourage quieter team members to contribute by giving everyone silent time to add their thoughts before discussion begins. ## Icebreaker questions - If you were a cowboy or cowgirl, what would your trusty sidekick animal be and why? - What's one 'wild frontier' challenge you tackled this sprint that you're proud of? --- # Skeleton Crew Retrospective URL: https://www.teamretro.com/retrospective-templates/skeleton-crew-retrospective/ Running with a skeleton crew means doing more with less — covering critical work while half the team is on leave, between hires, or pulled onto other priorities. The Skeleton Crew Retrospective gives your team a structured, slightly playful way to reflect on those periods when capacity was tight, energy was running low, and only the essentials kept the lights on. It helps surface what truly mattered, what got dropped without consequence, and how the team coped under pressure. Built around a Halloween-inspired theme, this format keeps things light while tackling a serious topic: sustainable workload and prioritisation. By exploring which "bones" of your process held the structure together, what felt like dead weight, and where the team was haunted by stress or single points of failure, you uncover practical insights about resilience, delegation, and focus. It's a great way to learn from a stretched period rather than simply surviving it. Whether you're emerging from a holiday season, a hiring gap, or an unexpectedly busy sprint, this retrospective turns a draining experience into actionable lessons. Run it in TeamRetro to capture ideas, group recurring themes, vote on what to fix, and walk away with clear actions that make the next lean stretch far less scary for everyone involved. ## Topics - **The Bones**: What essentials held everything together while we were stretched? - **The Hauntings**: What stressed us out or kept coming back to spook us? - **Dead Weight**: What could we drop without anyone noticing or missing it? - **Raising the Dead**: What should we revive or change before the next lean stretch? ## When to use - After a holiday season or period when a large portion of the team was on leave and you ran on minimal staffing. - During a hiring gap or after departures when the remaining team had to cover critical work. - Following an unexpectedly busy sprint where the team had to ruthlessly prioritise essentials. - When you want to identify single points of failure and build resilience before the next lean period. - As a themed seasonal retrospective around Halloween to keep engagement high while tackling workload. ## Tips and tricks - Set a psychologically safe tone — running lean is stressful, so make it clear the goal is to learn, not to assign blame for what slipped. - Lean into the Halloween theme to keep things light, but make sure the actions that come out are concrete and owned. - Give quieter or part-time members space to contribute, since they may have covered unusual tasks and hold valuable perspective. - Watch for survivorship bias — celebrate what worked, but dig hard into the hauntings and single points of failure that could bite next time. - Timebox each topic so the conversation doesn't dwell only on negatives; aim to spend real time on the 'Raising the Dead' actions. - Prioritise and vote on improvements so the team commits to a small number of high-impact changes rather than an overwhelming list. ## Icebreaker questions - If you were a Halloween character during our busiest week, which one would you have been and why? - What's the one task you'd happily bury six feet under and never deal with again? --- # Appreciation Round Retrospective URL: https://www.teamretro.com/retrospective-templates/appreciation-round-retrospective/ Recognition is one of the most powerful drivers of team motivation, yet it's often the first thing we forget when deadlines loom and work gets busy. The Appreciation Round retrospective creates dedicated space for team members to express gratitude, celebrate one another's contributions, and acknowledge the small (and big) moments that made a difference. By making appreciation a deliberate ritual rather than an afterthought, teams build stronger relationships, deeper trust, and a culture where people feel genuinely valued. This format works by guiding participants through structured prompts that surface gratitude in different forms — from thanking individuals for specific help, to celebrating shared wins, to recognising the behaviours and qualities that strengthen the team. Each person contributes their appreciations, which are then shared and discussed, allowing recognition to flow openly across the group. The simplicity of the structure means it can be run as a standalone session or woven into the close of a regular sprint retrospective. The benefits go well beyond a feel-good moment. Regular appreciation rounds have been shown to improve psychological safety, reduce burnout, and increase engagement and retention. When people know their efforts are seen and valued, they're more likely to keep showing up with energy and commitment. Use this retrospective to end a project on a high note, reconnect a team after a tough stretch, or simply make gratitude a recurring part of how your team works together. ## Topics - **Thank You**: Who helped you and what did they do? - **Wins to Celebrate**: What shared achievements should we recognise together? - **Qualities I Value**: What behaviours or strengths make this team great? - **Pay It Forward**: How can we keep appreciation going beyond today? ## When to use - At the end of a major project or release to celebrate everyone's contributions and finish on a positive note. - When team morale is low or after a particularly stressful period, to reconnect people and rebuild energy. - As a recurring ritual to embed recognition and gratitude into your team's regular cadence. - When a team member is leaving or a milestone is reached, to acknowledge what they've brought to the group. - To strengthen psychological safety and trust in newly formed or recently merged teams. ## Tips and tricks - Encourage specificity — 'thank you for staying late to fix the build' lands far more than a generic 'thanks for everything'. - Make sure everyone gives and receives appreciation; gently steer recognition toward quieter team members who may be overlooked. - Set a positive tone from the start and keep the session free of criticism — this is a space purely for gratitude. - Allow a moment of silence for reflection before sharing, so people can think of meaningful appreciations rather than reaching for easy ones. - Keep it time-boxed and light; even 15 minutes of genuine recognition can have a big impact on team morale. - Lead by example as the facilitator by sharing a heartfelt appreciation first to model the depth and tone you're hoping for. ## Icebreaker questions - Who is someone outside of work you're grateful for right now, and why? - What's a small thing that made you smile this week? --- # Lead Generation and Quality Retrospective URL: https://www.teamretro.com/retrospective-templates/lead-generation-and-quality/ The Lead Generation and Quality Retrospective is a structured meeting for sales and marketing teams to reflect on their lead generation strategies, lead quality, and conversion rates. By analyzing what worked well, areas for improvement, and potential roadblocks, teams can identify actionable steps to optimize their lead acquisition and nurturing processes. This retrospective encourages open discussion and data-driven insights, fostering a culture of continuous learning and adaptation. It helps teams stay agile and responsive to market changes, ultimately driving better lead quality and higher conversion rates. Originally developed by sales experts at HubSpot, this retrospective format has been widely adopted by B2B companies seeking to improve their lead generation and sales pipeline effectiveness. ## Topics - **Lead Sources**: Which lead sources performed well this period? - **Lead Quality**: How well did the leads align with our ideal customer profile? - **Conversion Rates**: How effectively did we convert leads into opportunities and closed business? - **Areas for Improvement**: What challenges or roadblocks impacted our lead generation and conversion efforts? ## When to use - At the end of a sales quarter or marketing campaign to review performance and identify areas for optimization. - When launching a new product, service, or go-to-market strategy to ensure effective lead generation and nurturing. - After making significant changes to your marketing or sales processes to assess the impact and course-correct as needed. - Periodically (e.g., quarterly or bi-annually) as part of a continuous improvement cycle for your revenue operations. - When onboarding new marketing or sales team members to align on lead management best practices. ## Tips and tricks - Encourage data-driven discussions by having teams come prepared with relevant metrics and reports. - Invite cross-functional participation from marketing, sales, and customer success to gain diverse perspectives. - Use a parking lot or follow-up tracker to capture action items and ownership for addressing identified issues. - Consider breaking into smaller groups for more focused discussions on specific topics or lead sources. - Celebrate wins and successes in addition to identifying areas for improvement to maintain a positive, growth-oriented mindset. - Rotate the facilitator role to encourage shared ownership and different facilitation styles. ## Icebreaker questions - If you could generate leads from any fictional universe, which one would you choose and why? - Share a funny or embarrassing story from a past lead generation or sales experience. --- # Dream Within a Dream Retrospective (Inception Edition) URL: https://www.teamretro.com/retrospective-templates/dream-within-a-dream-inception-edition-retrospective/ Inspired by the mind-bending world of Christopher Nolan's Inception, the Dream Within a Dream Retrospective invites your team to journey through layered levels of reflection. Just as the film descends from reality into deeper dream states, this format encourages teams to peel back the surface and explore what's happening beneath the obvious. Each layer represents a deeper level of honesty and insight — from the things you noticed on the surface to the root truths buried in your subconscious. The retrospective works by guiding participants through four progressively deeper "dream levels." Teams start with surface observations, then descend into recurring patterns, hidden tensions, and finally the core ideas they want to take back to "reality." This structure helps surface insights that often get missed in standard retrospectives, while keeping the session playful and memorable. By framing reflection as a shared dream, teams feel safer to voice deeper concerns and aspirations. Ideal for teams looking to break out of retrospective fatigue, the Inception Edition combines creative storytelling with genuine continuous improvement. It's a fun, themed way to spark fresh conversations, encourage psychological safety, and ensure your team leaves with a clear "kick" — the actionable takeaways that bring everyone back to reality, ready to act. ## Topics - **Level 1: Reality**: What did you notice on the surface this sprint? - **Level 2: The Dream**: What recurring patterns or habits are shaping our work? - **Level 3: The Subconscious**: What hidden tensions or unspoken truths are below the surface? - **The Kick (Back to Reality)**: What actions will bring us back, stronger than before? ## When to use - When your team is experiencing retrospective fatigue and needs a fresh, creative format to re-energise reflection. - When you want to dig beneath surface-level observations to uncover root causes and unspoken tensions. - When building psychological safety so team members feel comfortable sharing deeper concerns. - When you want a memorable, themed session that still produces concrete, actionable takeaways. ## Tips and tricks - Set the scene early — a short reference to the Inception theme helps participants embrace the layered journey and have fun with it. - Resist the urge to rush the deeper layers. The subconscious level holds the richest insights, so give people quiet thinking time before sharing. - Watch for one or two voices dominating; invite quieter members in directly to keep reflection inclusive. - Keep Level 1 light and quick so you preserve energy and time for the deeper, more valuable layers. - Limit the number of actions in 'The Kick' to two or three so commitments are realistic and owned. - Remind the team that the subconscious layer is a judgement-free zone to encourage genuine honesty. ## Icebreaker questions - If you could design your own dream world, what's the first thing you'd add to it? - What's a recurring dream you've had, and what do you think it was trying to tell you? --- # New Year Kickoff Retrospective URL: https://www.teamretro.com/retrospective-templates/new-year-kickoff-retrospective/ The New Year Kickoff Retrospective is a team activity to reflect on the previous year's achievements, challenges, and lessons learned, especially around the busy holiday season. It provides an opportunity to celebrate successes, identify areas for improvement, and set goals for the upcoming year. This retrospective encourages open discussion and sharing of perspectives in a supportive environment. By reviewing the past year, teams can gain valuable insights to inform their strategies and priorities for the new year, fostering continuous improvement and growth. The activity is designed to be engaging and thought-provoking, with a focus on constructive feedback and actionable takeaways. It can be customized to suit the specific needs and culture of the team, making it a versatile tool for fostering team alignment, collaboration, and personal development. ## Topics - **Highlights and Achievements**: What were your biggest accomplishments or successes last year? - **Challenges and Lessons Learned**: What were the biggest challenges you faced, and what did you learn? - **Goals and Priorities**: What are your goals and priorities for the upcoming year? - **Continuous Improvement**: How can we continue to improve and grow as a team? ## When to use - At the start of a new year or quarter to reflect on the previous period and set goals for the upcoming one. - After a major project, initiative, or busy season to review successes, challenges, and lessons learned. - As part of regular team-building and continuous improvement efforts to foster open communication and growth. - When onboarding new team members to share the team's history, culture, and values, and to align on goals and priorities. - During times of change or transition to help the team process and adapt to new circumstances or directions. ## Tips and tricks - Encourage open and honest feedback by creating a safe and supportive environment where all perspectives are valued. - Use visual aids, such as a whiteboard or digital collaboration tools, to capture and organize ideas and insights. - Assign a dedicated facilitator to guide the discussion, keep the conversation on track, and ensure everyone has a chance to contribute. - Consider breaking into smaller groups for certain topics to encourage more in-depth discussions and diverse perspectives. - Follow up on action items and ensure clear ownership and accountability for implementing agreed-upon improvements or initiatives. - Celebrate successes and achievements, but also embrace failures as learning opportunities for growth and improvement. ## Icebreaker questions - What was the most memorable or impactful moment for you during the past year, either professionally or personally? - If you could sum up the past year in one word or phrase, what would it be and why? --- # Three Little Pigs Retrospective URL: https://www.teamretro.com/retrospective-templates/three-little-pigs-retrospective/ The Three Little Pigs retrospective is a creative and engaging format that uses the classic children's story as a metaphor for evaluating team practices and processes. By categorizing feedback into houses of straw, sticks, and bricks, teams can identify weak points, areas needing reinforcement, and strong foundations in their work. This retrospective framework encourages teams to think critically about the durability and sustainability of their practices. The house of straw represents fragile or temporary solutions, the house of sticks indicates partially robust processes that need strengthening, and the house of bricks highlights solid, reliable practices worth maintaining. Originally adapted from the beloved fairy tale, this retrospective format helps teams identify varying levels of stability in their work processes while maintaining a playful, accessible approach to serious improvement discussions. ## Topics - **House of Straw**: Things that could easily fall apart - **House of Sticks**: Things that are working but could be improved - **House of Bricks**: Things that are strong and stable - **The Big Bad Wolf**: What threats or challenges are we facing? ## When to use - When you want to evaluate the stability and sustainability of your team's practices and processes - After experiencing failures or setbacks that highlight weak points in your system - During periods of growth or change when you need to ensure your foundations are solid - When you want to make process improvement discussions more engaging and accessible ## Tips and tricks - Start by explaining the metaphor clearly and how it relates to team practices - Encourage participants to think about long-term sustainability rather than just immediate solutions - Use the wolf category to address external threats constructively rather than as a complaint session - Consider using visual aids or storytelling elements to maintain the theme and engagement - Balance the serious nature of process improvement with the playful theme of the retrospective - Set aside time to discuss how to transform 'straw' and 'stick' items into 'brick' solutions ## Icebreaker questions - If you could build a house from any material in the world, what would you choose and why? - What's your favorite childhood story and what lesson did it teach you? --- # Oh, Canada! Retro URL: https://www.teamretro.com/retrospective-templates/oh-canada-retrospective/ Eh, ready to look back on your sprint the Canadian way? The Oh, Canada! Retro brings a warm, friendly twist to your team reflection, using familiar Canadian icons to frame the conversation. From the things that were "True North" strong and reliable, to the moments that left you feeling a little "Eh?", this format gives teams a memorable and lighthearted structure to surface wins, frustrations and ideas for the next iteration. The retro works by guiding your team through four themed prompts inspired by Canadian culture and landmarks. Each prompt maps to a classic retrospective question — what's working well, what's holding us back, what fresh ideas we want to try, and what we want to thank each other for. The playful theme lowers barriers to honest sharing while keeping the underlying agile purpose intact, making it a great choice for distributed teams who want a bit of personality in their ceremonies. Beyond the fun factor, this themed retrospective drives the same outcomes as any effective sprint review: actionable insights, shared accountability and continuous improvement. It's especially handy when your team needs a change of pace from the usual Start, Stop, Continue, or when you want to celebrate national pride, mark Canada Day, or simply build a stronger sense of belonging across your group. ## Topics - **True North**: What went strong and reliable for us this sprint? - **Eh? What Slowed Us Down**: What left us puzzled, frustrated or stuck this sprint? - **New Frontiers**: What fresh ideas or experiments should we try next? - **Maple Syrup Moments**: Who or what do we want to give thanks for, eh? ## When to use - When you want to add a fun, culturally themed twist to your regular sprint retrospective to keep ceremonies fresh. - Around Canada Day or other moments where you'd like to celebrate national pride and build team belonging. - For distributed or Canadian teams that value a lighthearted, inclusive atmosphere during reflection. - When team energy is low and a playful theme can re-engage participation. - As a celebration-focused retro at the end of a big milestone or successful release. ## Tips and tricks - Set the tone early by leaning into the theme — a friendly 'eh?' or a maple emoji helps everyone relax and engage. - Timebox each topic so the playful theme doesn't lead to the discussion running long. - Use anonymous contributions for the 'Eh? What Slowed Us Down' column so people feel safe raising blockers. - Make sure the gratitude in 'Maple Syrup Moments' translates into ongoing recognition, not just a one-off. - Group similar ideas before voting so the most impactful actions rise to the top. - Close the loop by turning 'New Frontiers' ideas into concrete, owned action items with due dates. ## Icebreaker questions - If you could only eat one Canadian food for the rest of your life, would it be poutine, maple syrup, or a butter tart? - What's the most 'Canadian' thing you've done this week, eh? --- # No-Shave Movember Retrospective URL: https://www.teamretro.com/retrospective-templates/no-shave-movember-retrospective/ Movember has grown from a few mates growing moustaches into a global movement that funds men's health projects across prostate cancer, testicular cancer, mental health and suicide prevention. No-Shave November (or "No-Shave Movember") channels that same spirit by encouraging participants to embrace their natural hair growth for a month while donating what they'd normally spend on shaving and grooming to a good cause. Bringing this theme into a team retrospective is a fun, lighthearted way to combine reflection with a meaningful conversation about wellbeing, fundraising and team culture. This retrospective gives your team space to look back on the month's awareness campaign, celebrate the laughs and the dollars raised, and surface ideas for doing even better next year. Structured around a hairy growth metaphor, participants reflect on what flourished, what got a little patchy, what they want to keep growing, and the impact and conversations the campaign sparked. It works equally well as a standalone team-bonding session or as a wrap-up to a charity drive, giving everyone a voice and capturing momentum while the experience is still fresh. By running it in TeamRetro, you make it easy for distributed and in-office teams alike to contribute equally, group similar ideas, vote on what matters most, and turn good intentions into clear action items. The result is a more engaged team, a stronger sense of shared purpose around men's health, and a practical plan for keeping the cause front of mind well beyond November. Learn more about the movement at the official Movember Foundation site. ## Topics - **What grew well?**: What flourished during the Movember campaign? - **What got patchy?**: Where did things feel uneven or fall short? - **Impact & conversations**: What awareness or change did the campaign spark? ## When to use - At the end of November to wrap up your Movember or No-Shave campaign while experiences are still fresh. - As a fun, themed team-building session that blends reflection with a meaningful men's health conversation. - When closing out any charity drive or awareness initiative and you want to capture lessons learned. - To plan and improve next year's fundraising and awareness efforts based on real feedback. - When you want a lighthearted retrospective that still encourages openness around wellbeing topics. ## Tips and tricks - Keep the tone light and inclusive, the facial-hair theme is fun but not everyone can or wants to grow a moustache, so welcome other ways to participate. - Set the scene by sharing a few facts about Movember and men's health so the session stays connected to its purpose. - Use anonymous contributions in TeamRetro to make it safe for people to share personal reflections on wellbeing. - Balance celebration with honesty, capture both the wins and the patchy spots so next year's campaign improves. - Turn votes into clear, owned action items so good intentions don't fade once the moustaches come off. - Be sensitive to the topic, men's health includes serious subjects like mental health, so give people room and signpost support resources. ## Icebreaker questions - If you had to grow one ridiculous facial-hair style for a month, what would it be and why? - What's one small thing you do to look after your own health and wellbeing? --- # Hiring Process Retrospective URL: https://www.teamretro.com/retrospective-templates/hiring-process-retrospective/ The Hiring Process Retrospective is a structured meeting for reviewing your organization's approach to recruiting and onboarding new employees. It provides an opportunity to celebrate successes, identify areas for improvement, and develop actionable steps to enhance your hiring practices. This retrospective encourages open discussion among stakeholders involved in the hiring process, such as HR professionals, hiring managers, and interviewers. By examining the end-to-end experience from job posting to candidate onboarding, you can uncover insights to attract top talent, streamline processes, and create a positive impression for new hires. Whether you're looking to reduce time-to-hire, improve candidate experience, or better align hiring with organizational needs, the Hiring Process Retrospective offers a valuable framework for continuous improvement. ## Topics - **Successful Hiring Practices**: What aspects of our hiring process were effective and successful? - **Hiring Process Challenges**: What challenges or pain points did we encounter in our hiring efforts? - **Areas for Improvement**: What specific areas of our hiring process need improvement or change? - **Action Plan**: What specific actions can we take to implement the identified improvements? ## When to use - After completing a major hiring cycle or initiative, to evaluate the effectiveness of your processes. - On a regular basis (e.g., quarterly or annually) to continuously improve your hiring practices. - When facing challenges in attracting or retaining top talent, to identify areas for improvement. - After implementing new hiring tools, technologies, or processes, to assess their impact and make adjustments. ## Tips and tricks - Involve stakeholders from various roles and departments involved in the hiring process to gather diverse perspectives. - Encourage open and honest feedback by creating a safe, non-judgmental environment. - Use data and metrics, such as time-to-hire, cost-per-hire, and candidate feedback, to support observations and identify areas for improvement. - Prioritize action items based on their potential impact and feasibility of implementation. - Assign clear owners and timelines for action items to ensure accountability and follow-through. - Schedule regular follow-up sessions to review progress on action items and make adjustments as needed. ## Icebreaker questions - If you could hire anyone, living or historical, for a role in our organization, who would it be and why? - Share a memorable experience, positive or negative, from your own hiring or job search process. --- # October Harvest Retrospective URL: https://www.teamretro.com/retrospective-templates/october-harvest-retrospective/ October Harvest brings a warm, autumnal spirit to your team's reflection, inviting everyone to pause and gather the fruits of their recent labor. Just as farmers reap what they have sown, this seasonal retrospective encourages teams to celebrate what flourished, examine what withered, and decide which seeds to plant for the months ahead. It transforms a routine review into a meaningful, themed ritual that resonates with the rhythms of the season. The format works by guiding teams through four harvest-inspired themes: the bountiful crops worth celebrating, the rotten produce that caused problems, the seeds to sow for future growth, and the preserves worth carrying forward. Each prompt nudges participants to think reflectively about their work cycle while keeping the conversation engaging and lighthearted. In TeamRetro, contributions can be added, grouped, voted on, and turned into clear action items, making it easy to translate seasonal insights into concrete next steps. Beyond being a fun change of pace from standard sprint reviews, the October Harvest Retrospective fosters gratitude, honest reflection, and forward planning. It is ideal for end-of-quarter check-ins, autumn team-building, or any moment when you want a fresh, themed approach to continuous improvement. Teams come away feeling connected to one another and energized about cultivating better outcomes together. ## Topics - **Bountiful Crops**: What flourished and is worth celebrating this season? - **Rotten Produce**: What spoiled, caused problems, or held us back? - **Seeds to Sow**: What new ideas should we plant for future growth? - **Ready to Preserve**: What practices should we carry forward into next season? ## When to use - End-of-quarter or end-of-cycle reviews when you want to reflect on a longer stretch of work with a fresh, themed lens. - Autumn or seasonal team-building sessions that benefit from a lighthearted, engaging format. - When standard retrospectives feel stale and the team needs a change of pace to re-energize participation. - Whenever you want to balance celebrating wins with honest reflection and concrete forward planning. ## Tips and tricks - Set the scene with the harvest metaphor up front so everyone understands how the themes map to their work. - Timebox each section to keep momentum, and use TeamRetro's grouping to cluster similar ideas before discussion. - Encourage quieter members to contribute by adding ideas anonymously, ensuring all voices are gathered. - Keep the Rotten Produce section blameless by focusing on processes and situations rather than people. - Convert Seeds to Sow into clear, owned action items so insights don't wither after the meeting. - Revisit Preserves to Keep at the start of your next retro to confirm the good habits actually stuck. ## Icebreaker questions - What is your favorite thing about the autumn season? - If your last sprint were a fruit or vegetable, what would it be and why? --- # Mission Impossible: Agile Protocol Retrospective URL: https://www.teamretro.com/retrospective-templates/mission-impossible-agile-protocol-retrospective/ Cue the iconic theme music — your team has just completed another high-stakes mission, and it's time to debrief like the elite agents you are. The Mission Impossible: Agile Protocol retrospective reframes your sprint as a covert operation, inviting team members to review the intel they gathered, the gadgets that worked (and the ones that exploded), and the obstacles that nearly blew their cover. This playful spy theme injects energy into routine sprint reviews while still surfacing the practical insights that drive continuous improvement. By structuring the conversation around mission objectives, successful maneuvers, near-misses, and the next assignment, this format helps agile teams reflect on what went well, what threatened the mission, and how to adapt their tactics. The narrative framing lowers psychological barriers, encouraging quieter agents to speak up and making it safe to discuss failures as "intel" rather than blame. It's especially effective for teams that have grown weary of standard "Start, Stop, Continue" formats and want a fresh, gamified way to engage. Whether your squad is shipping features, defusing production incidents, or infiltrating a tricky backlog, this retrospective keeps morale high and feedback flowing. In TeamRetro, you can collaboratively brainstorm, group, vote, and assign action items so every mission ends with a clear plan for the next operation. Accept the mission — your team's improvement depends on it. ## Topics - **Mission Accomplished**: What objectives did we successfully complete? - **Gadgets That Worked**: Which tools, processes or tactics gave us an edge? - **Self-Destruct Sequences**: What nearly blew our cover or derailed the mission? - **Next Mission Briefing**: What actions will we take on the next operation? ## When to use - When your team needs a fun, themed change of pace from standard sprint retrospectives. - After completing a high-stakes sprint, launch, or major milestone that deserves a proper debrief. - When morale is low and you want to re-energise the team with a gamified format. - When you want to make discussing failures feel safe by reframing them as 'intel' rather than blame. - For distributed or remote agile teams looking to boost engagement during retrospectives. ## Tips and tricks - Lean into the theme — open with the iconic mission briefing tone to set a playful, energetic mood. - Keep psychological safety front of mind; frame failures as 'intel' so agents feel safe sharing setbacks. - Timebox each topic to keep the mission moving and prevent any single discussion from dominating. - Use dot voting to prioritise which threats and actions matter most for the next mission. - Always close with clear, owned action items so the retrospective leads to real improvement. - Rotate the facilitator role each sprint to keep the format fresh and share ownership of the mission. ## Icebreaker questions - If you were a secret agent, what would your spy gadget of choice be and why? - What's the most 'mission impossible' task you've ever pulled off at work? --- # Aussie Adventure Retrospective URL: https://www.teamretro.com/retrospective-templates/aussie-adventure-retrospective/ Take your team on a journey through the great Australian outback with this fun, themed retrospective that turns reflection into an adventure. Inspired by the rugged landscapes and good-natured spirit of Australia, the Aussie Adventure Retrospective uses iconic outback metaphors — sun-soaked highlights, treacherous billabongs, surprise critters and the road ahead — to help teams look back on their sprint or project in an engaging, lighthearted way. It's a refreshing alternative to standard formats that helps lower the stakes and spark honest, creative conversation. The retrospective works by guiding participants through a series of themed prompts, each representing a different aspect of the team's recent journey. Team members reflect on what went brilliantly, where they got bogged down, what unexpected challenges popped up, and where they're heading next. By framing familiar agile reflection through a playful adventure lens, the format keeps energy high and encourages quieter voices to contribute. Facilitators can group similar ideas, vote on priorities and turn insights into clear, actionable next steps. Themed retrospectives like this one are a great way to keep continuous improvement fresh and fun, especially for teams running frequent retros who want to avoid format fatigue. Whether you're an agile crew Down Under or simply embracing the adventurous spirit, this template builds team rapport while delivering the practical outcomes of a great retrospective. ## Topics - **Sunny Skies**: What went brilliantly and lifted the team? - **Bogged in the Billabong**: Where did we get stuck or slowed down? - **Critters & Surprises**: What unexpected things popped up along the way? - **The Road Ahead**: What should we do next to keep moving forward? ## When to use - When your team is suffering from retro fatigue and needs a fresh, fun format to re-energise reflection. - At the end of a sprint or project milestone to celebrate wins and surface blockers in an engaging way. - For newer or distributed teams looking to build rapport while still delivering practical improvement actions. - When you want a lighthearted theme to lower the stakes and encourage quieter team members to contribute. ## Tips and tricks - Lean into the theme — use the outback metaphors throughout to keep the energy playful and the conversation flowing. - Timebox each topic so you leave plenty of room for The Road Ahead, where the real action items emerge. - Group similar ideas together before voting to surface the themes that matter most to the team. - Make sure every voice is heard — invite quieter members to share a Sunny Skies moment first to build confidence. - Keep Bogged in the Billabong constructive and blame-free; focus on systems and process, not individuals. - Always close by assigning clear owners and due dates to your next steps so improvements actually happen. ## Icebreaker questions - If you could explore any Australian destination, would you pick the Outback, the Great Barrier Reef, or a city beach — and why? - What's your spirit Aussie animal this sprint: a busy bee, a chilled-out koala, or a hopping-everywhere kangaroo? --- # Mario Bros Level Up Retrospective URL: https://www.teamretro.com/retrospective-templates/mario-bros-level-up-retrospective/ Inspired by the iconic platforming adventures of Mario and Luigi, the Mario Bros Level Up Retrospective turns your team reflection into a playful journey through the Mushroom Kingdom. Just like guiding a hero from World 1-1 to the final castle, your team will celebrate the coins collected, dodge the Goombas that slowed you down, grab the power-ups that boosted your performance, and prepare for the next level ahead. This gamified format brings energy and nostalgia into your retrospective, making it easier for everyone to engage and share openly. The retrospective works by mapping familiar game mechanics onto real sprint or project experiences. Each topic invites participants to reflect through a different lens — wins, obstacles, accelerators, and goals — using imagery that lowers the barrier to honest conversation. Whether you're an agile coach looking to mix up a stale routine or a Scrum Master wanting to boost morale, the metaphor keeps the session lighthearted while still surfacing meaningful, actionable insights. By framing achievements as coins and blockers as Goombas, teams find it easier to depersonalize challenges and focus on continuous improvement. The format is great for building psychological safety, encouraging participation from quieter members, and ending each cycle on a motivating note as the team gears up for their next level. It's a fun, effective way to keep retrospectives fresh and your team leveling up sprint after sprint. ## Topics - **Coins Collected**: What wins and achievements did we collect this round? - **Goombas in the Way**: What blockers, obstacles or enemies slowed us down? - **Power-Ups**: What gave us a boost or helped us perform better? - **Next Level Goals**: What do we want to achieve in the level ahead? ## When to use - When a team's retrospectives feel repetitive and you want a fun, themed format to re-energize participation. - After completing a sprint or project milestone where there are clear wins to celebrate and obstacles to learn from. - When you want to build psychological safety and encourage quieter team members to share more openly. - For team-building sessions or end-of-quarter reviews where a lighthearted, gamified tone fits the mood. ## Tips and tricks - Set the scene with the theme up front — a quick reference to the Mario universe helps everyone get into the playful mindset and lowers the barrier to sharing. - Keep the metaphor consistent: coins are wins, Goombas are blockers, power-ups are boosts. This makes contributions easy to categorize and keeps the energy fun. - Timebox each topic so the game keeps moving and you don't get stuck on one 'level' — aim for a balanced session across all four areas. - Make sure Goombas (blockers) translate into concrete action items so the fun doesn't replace real follow-through. - Encourage every player to add at least one coin to celebrate wins — this builds inclusivity and ensures positive recognition isn't dominated by a few voices. - Watch for the loudest voices taking over; use grouping and anonymous adding in TeamRetro to balance participation and reduce bias. ## Icebreaker questions - If you could have one Mario power-up at work this week, would it be the super mushroom, fire flower, or invincibility star — and why? - Which video game character best represents how your sprint went, and what would they say about it? --- # Pirates on the High Seas Retrospective URL: https://www.teamretro.com/retrospective-templates/pirates-on-the-high-seas-retrospective/ Ahoy, crew! Set sail on a metaphor-rich retrospective that turns your sprint or project review into a high-seas adventure. The Pirates on the High Seas retrospective invites your team to imagine the journey so far through the lens of a pirate voyage — celebrating the treasure you've discovered, navigating the storms you've weathered, watching for the islands of opportunity ahead, and steering clear of the rocks that threaten to sink your ship. This playful framing lowers defenses, sparks creativity, and helps team members open up about wins and challenges in a way a standard agenda rarely achieves. This format works by guiding the crew through four nautical themes, each surfacing a different dimension of team performance. As participants share reflections about their treasure, storms, islands, and rocks, patterns emerge that reveal what's driving success and what's holding the ship back. In TeamRetro, ideas are grouped, voted on, and converted into clear action items so your crew leaves with a concrete heading rather than a vague feeling. The result is an engaging, inclusive session that keeps energy high while still delivering the honest insight a retrospective needs. The beauty of a themed retrospective like this is variety — running the same Start/Stop/Continue format every sprint leads to fatigue and shallow input. By reframing familiar reflection prompts as an imaginative pirate voyage, you re-engage seasoned teams, welcome newcomers with an approachable structure, and uncover insights that more clinical formats can miss. Hoist the sails and discover what your crew has really been navigating. ## Topics - **Treasure**: What valuable wins or discoveries did we find? - **Storms**: What rough weather or challenges did we battle? - **Islands of Opportunity**: What promising new lands or ideas should we explore? - **Rocks & Reefs**: What hidden dangers could sink us if ignored? ## When to use - Your team has been running the same Start/Stop/Continue format for a while and energy is flagging — a themed voyage re-engages the crew. - At the end of a sprint or project milestone when you want to balance celebrating wins with surfacing risks and opportunities. - With newer or distributed teams who benefit from a playful, approachable structure that lowers the barrier to honest sharing. - When you want to surface hidden risks and technical debt alongside the usual reflections in a non-threatening way. ## Tips and tricks - Lean into the theme — use nautical language in your facilitation to keep the energy playful, but don't let the metaphor obscure the real issues you need to discuss. - Timebox each section so the crew doesn't spend all their time on Treasure and skip the harder Rocks & Reefs conversation. - Use anonymous brainstorming in TeamRetro for the Storms and Rocks topics so quieter crew members feel safe naming sensitive risks. - Group and vote on ideas before discussing, so the team focuses its limited time on the items that matter most. - Always convert the top Islands of Opportunity and Rocks into concrete, owned action items — a voyage with no new heading was wasted. - Rotate the facilitator each session to keep the perspective fresh and share the helm across the crew. ## Icebreaker questions - If you were a pirate, what would your pirate name and signature catchphrase be? - What's the one item you'd absolutely want stashed in your treasure chest on a long voyage? --- # Daily Standup URL: https://www.teamretro.com/retrospective-templates/daily-standup/ The Daily Standup is a brief, focused meeting where team members share updates on their work progress, plans for the day, and any roadblocks they're facing. This agile practice promotes transparency, accountability, and collaboration within the team. During the standup, each person answers three key questions: What did you accomplish yesterday? What will you work on today? Are there any blockers or impediments? The standup should be timeboxed to 15 minutes or less, with participants standing to encourage brevity. By conducting these quick check-ins daily, teams can identify potential issues early, adapt their plans accordingly, and maintain a shared understanding of the project's status. The Daily Standup is a core agile ceremony that helps teams stay aligned, remove obstacles, and continuously improve their workflow. ## Topics - **Yesterday's Progress**: What did you accomplish yesterday? - **Today's Plan**: What will you work on today? - **Blockers or Impediments**: Are there any blockers or impediments? - **Open Discussion**: Any other updates, questions, or concerns? ## When to use - To ensure daily alignment and transparency within an agile team or project. - To identify and address any roadblocks or dependencies early on. - To promote accountability and a shared understanding of progress and priorities. - To foster collaboration and continuous improvement within the team's workflow. ## Tips and tricks - Keep the standup timeboxed to 15 minutes or less to maintain focus and brevity. - Encourage team members to be concise and avoid going into too much detail or getting sidetracked. - Rotate the order in which team members share their updates to ensure equal participation. - Address any blockers or impediments immediately after the standup, either by assigning action items or scheduling follow-up discussions. - Use a physical or virtual board to track progress, blockers, and any action items arising from the standup. - Consider having the standup at the same time and location each day to establish a consistent routine. ## Icebreaker questions - If you could have any superpower for a day, what would it be and why? - What's the most interesting or unusual fact you've learned recently? --- # Netball Retrospective URL: https://www.teamretro.com/retrospective-templates/netball-retrospective/ The Netball Retrospective uses familiar netball concepts to help teams reflect on their performance and identify areas for improvement. Drawing parallels between sports team dynamics and workplace collaboration, this template encourages participants to think about their achievements, obstacles, overreach moments, and opportunities for strategic position changes. Just as netball requires precise footwork, teamwork, and strategic positioning, this retrospective framework helps teams analyze their coordination, communication, and effectiveness. The format is particularly effective for sports-minded teams or organizations looking to build stronger connections between individual performance and team success. By structuring feedback around netball concepts like scoring points, managing obstructions, and position switching, teams can have focused discussions about their challenges and victories while maintaining an engaging, sports-themed perspective. ## Topics - **Point**: What did we achieve? - **Obstruction**: What got in our way? - **Stepping**: What made us over reach or lose balance? - **Switch positions**: What can we change to improve our performance? ## When to use - After completing a major project or milestone to evaluate team performance and dynamics - When team coordination or communication needs improvement - For teams that respond well to sports analogies and competitive motivation - During team restructuring or role reassignment periods ## Tips and tricks - Encourage participants to think about both individual and team performance aspects - Use netball terminology to keep the sports theme engaging but explain terms for those unfamiliar with the sport - Focus on constructive feedback rather than personal criticism - Keep the energy high and maintain a positive, game-like atmosphere - Set clear time boxes for each topic to maintain momentum - Document action items clearly and assign owners for follow-up ## Icebreaker questions - If our team was a sports team, what would be our signature winning move? - What position would you play in our team's game, and why? --- # Valentine's Day Retrospective URL: https://www.teamretro.com/retrospective-templates/valentines-day-retrospective/ The Valentine's Day Retrospective transforms the traditional retrospective format into a heartwarming celebration of team relationships and accomplishments. This engaging format encourages team members to express appreciation, acknowledge meaningful connections, and strengthen bonds within the group. Drawing inspiration from the spirit of Valentine's Day, this retrospective creates a safe space for team members to share what they value about working together. Teams explore areas of mutual appreciation, identify opportunities to support each other better, and celebrate the relationships that make their work meaningful. The format is particularly effective at fostering psychological safety and building stronger interpersonal connections. By focusing on positive relationships and mutual support, teams can improve collaboration, boost morale, and create a more inclusive work environment. ## Topics - **Love Letters**: What do you appreciate most about your teammates? - **Heartbreakers**: What challenges are affecting our team relationships? - **Cupid's Arrows**: What ideas could strengthen our team bonds? - **Sweet Commitments**: What actions will we take to nurture our team relationships? ## When to use - When you want to strengthen team relationships and build psychological safety - During periods of team growth or change to reinforce positive connections - To celebrate team achievements and express gratitude for team members ## Tips and tricks - Create a warm, welcoming atmosphere by using heart-themed imagery and positive language - Encourage specific, personal examples of appreciation rather than generic statements - Balance fun and professionalism to maintain focus while keeping the mood light - Use breakout rooms for larger teams to ensure everyone has a chance to share - Follow up on action items in subsequent meetings to show commitment to improvement ## Icebreaker questions - Share a moment when a teammate's support made a significant difference to you - What's your favorite way to show appreciation to others? --- # Sprint Retrospective URL: https://www.teamretro.com/retrospective-templates/sprint-retrospective/ The Sprint Retrospective is a key agile ceremony that allows teams to pause, reflect on their recent work, and identify opportunities for improvement. This template provides a structured format to discuss what went well, what could be improved, actionable steps to take, and any open questions or concerns. Regular retrospectives foster a culture of continuous learning, adaptation, and growth within agile teams. By openly examining successes, challenges, and puzzles, teams can adjust their processes, practices, and mindsets to enhance productivity, quality, and team dynamics. ## Topics - **What went well?**: Discuss the positive aspects and successes from the last sprint. - **What could be improved?**: Identify areas of improvement, challenges faced, and potential roadblocks. - **What actions can we take?**: Propose specific steps to address the areas for improvement. - **What still puzzles us?**: Surface any open questions, concerns or areas needing further discussion. ## When to use - At the end of each sprint or iteration to review the team's performance and identify areas for improvement. - When a team is facing recurring challenges or roadblocks and needs to adjust their approach. - After a major project milestone or release to reflect on lessons learned and plan for the next phase. - When a new team is formed or when there are significant changes in team composition or dynamics. ## Tips and tricks - Create a safe and judgment-free environment for open and honest discussion. - Encourage participation from all team members and value diverse perspectives. - Focus on identifying actionable steps rather than just listing problems. - Assign owners and target dates for key action items to ensure follow-through. - Celebrate successes and recognize team members' contributions. - Keep the retrospective time-boxed and focused to maintain engagement. ## Icebreaker questions - If our team was a vehicle, what kind would it be and why? - What's the most valuable lesson you've learned from a past project or experience? --- # Spartan Triumph Retrospective URL: https://www.teamretro.com/retrospective-templates/spartan-triumph-retrospective/ Channel the discipline, courage, and unity of the ancient Spartans into your team's reflection with the Spartan Triumph Retrospective. Inspired by the legendary warriors of Sparta who valued strength, strategy, and brotherhood, this themed retrospective encourages your team to look back on the campaign just completed — celebrating the battles won, learning from the wounds taken, and rallying for the conquests ahead. It transforms an ordinary sprint review into an epic narrative that energizes participants and frames everyday work as a shared, heroic endeavor. The Spartan Triumph format works by guiding your team through four themed phalanxes of discussion: the victories worth celebrating, the battle scars and setbacks to learn from, the weapons and allies that helped, and the strategy for the next campaign. By using vivid, motivational language, teams often open up more freely and engage with energy that traditional formats can struggle to spark. It's an especially powerful way to build morale, strengthen team cohesion, and reinforce a sense of collective achievement after intense periods of work. Whether you've just shipped a major release, survived a demanding quarter, or simply want a fresh and fun way to run your next retrospective, the Spartan Triumph helps you honour your wins, address your challenges head-on, and march into the future as a united front. Use it in TeamRetro to capture insights, vote on priorities, and turn reflection into decisive action. ## Topics - **Battles Won**: Which victories should we celebrate from this campaign? - **Battle Scars**: What wounds or setbacks did we take, and what can we learn? - **Weapons & Allies**: What tools, people or practices helped us prevail? - **Next Campaign**: What strategy and actions will guide our next conquest? ## When to use - After completing a major project, release, or demanding quarter when the team deserves to celebrate and reflect on its achievements. - When team morale needs a boost and you want a fun, motivational alternative to a standard sprint retrospective. - To strengthen team cohesion and reinforce a shared sense of collective achievement and identity. - When you want an engaging themed format that encourages quieter members to open up and contribute. ## Tips and tricks - Set the scene at the start by leaning into the Spartan theme — it primes the team for energy and storytelling, but keep it lighthearted and inclusive. - Make sure 'Battle Scars' stays focused on learning, not blame. Remind the team that scars are lessons, and protect psychological safety. - Use dot voting to prioritise which battle scars and next-campaign actions matter most so you don't try to fix everything at once. - Give every warrior a voice — use silent brainstorming time so quieter members contribute before discussion begins. - Always close by assigning clear owners and due dates to your Next Campaign actions so reflection turns into real progress. - Vary the theme over time to keep retrospectives fresh and avoid format fatigue across recurring sessions. ## Icebreaker questions - If you were a Spartan warrior, what would be your weapon of choice and why? - What's one personal victory — big or small — you achieved this sprint that deserves a battle cry? --- # Beethoven's Symphony of Agile Retrospective URL: https://www.teamretro.com/retrospective-templates/beethovens-symphony-of-agile-retrospective/ Just as Beethoven structured his symphonies into distinct movements that build toward a triumphant finale, your team can reflect on its work through a musical lens that brings rhythm and harmony to continuous improvement. The Beethoven's Symphony of Agile retrospective invites teams to examine their sprint or project as a four-movement composition — exploring the powerful opening notes, the discordant moments that need resolution, the recurring themes worth repeating, and the crescendo that propels them forward. This creative retrospective format works by mapping familiar agile reflection prompts onto the structure of a classical symphony. Each movement encourages participants to think about a different dimension of their teamwork: what set the tone, what felt out of tune, which motifs deserve an encore, and how to build toward a stronger finale. The metaphor adds a playful, memorable framing that helps teams break out of routine retrospective patterns and engage more deeply with both achievements and pain points. Inspired by the timeless work of Ludwig van Beethoven, this template is ideal for teams looking to refresh their retrospective ritual with something a little more imaginative. By the end of the session, your team will have a clear score of action items to perform — turning everyday agile practice into a symphony worth conducting. ## Topics - **Opening Movement**: What powerful notes set the tone this sprint? - **Discordant Notes**: Where did things feel out of tune or off-key? - **Recurring Themes**: Which motifs are worth playing again and again? - **The Crescendo**: How do we build toward a stronger finale next time? ## When to use - When your team's regular retrospective format feels stale and you want a creative, themed session to re-energise reflection. - At the end of a significant sprint, milestone, or project where the team has both wins and tensions worth exploring. - When you want a memorable metaphor that helps less vocal team members engage with the conversation. - For teams that enjoy playful framing and want to balance celebration with honest problem-solving. - As a quarterly or special-occasion retrospective to break the routine while still driving actionable outcomes. ## Tips and tricks - Set the mood by playing a Beethoven symphony quietly in the background as the team brainstorms — it reinforces the theme and lightens the atmosphere. - Lean into the musical metaphor when introducing each movement, but keep prompts concrete so people know exactly what to reflect on. - Time-box each movement so the session keeps a steady tempo and you reach the crescendo with energy to spare. - Use anonymous brainstorming for the Discordant Notes movement to encourage honest feedback without fear of blame. - Group and vote on ideas before the crescendo so action items focus on the highest-impact themes. - Always close by assigning owners and due dates to action items so the symphony turns into real performance. ## Icebreaker questions - If this sprint were a piece of music, what genre would it be and why? - What's a song that perfectly captures your mood right now? --- # Country Music Roundup Retrospective URL: https://www.teamretro.com/retrospective-templates/country-music-roundup-retrospective/ Saddle up and gather 'round the campfire — the Country Music Roundup brings a little twang to your team's reflection ritual. Inspired by the storytelling heart of country music, where every song tells a tale of triumph, heartbreak, and the long road home, this themed retrospective invites your team to look back on the sprint or project through a fresh, playful lens. By framing reflections as chart-topping hits, sorrowful ballads, and journeys down the open road, teams find it easier to open up and share honestly in a relaxed, low-pressure setting. The format works by guiding participants through four themed prompts that map directly onto familiar retrospective territory: celebrating wins, surfacing pain points, recognising the people who carried the load, and aligning on what comes next. Each "song" gives structure to the conversation while the country theme keeps the energy light and the discussion engaging. This is especially valuable for teams that have grown weary of the standard "what went well / what didn't" routine and want something that sparks creativity and camaraderie. Beyond the fun, the Country Music Roundup delivers the same outcomes you'd expect from any solid retrospective — clearer insight into team dynamics, actionable improvements, and a stronger sense of shared ownership. Themed retrospectives like this one are a proven way to boost participation, reduce meeting fatigue, and help quieter team members contribute. So tune your guitar, grab a hat, and let's see what stories your team has to tell. ## Topics - **Chart-Topping Hits**: What were our biggest wins this time around? - **Sad Country Ballads**: What caused us heartache or slowed us down? - **Unsung Heroes**: Who or what deserves a shout-out and thanks? - **The Open Road Ahead**: What should we change or try on the journey forward? ## When to use - Your team is tired of the standard retrospective format and needs a fresh, fun theme to re-energise participation. - You want to lighten the mood after a tough sprint while still surfacing honest feedback. - You're building team rapport and want a relaxed, creative space for reflection. - It's a milestone, end-of-quarter, or celebratory moment that calls for something a little more playful. ## Tips and tricks - Lean into the theme — consider playing some country music as people join to set the mood and break the ice. - Keep the 'Sad Country Ballads' section blame-free; focus on problems and processes, not pointing fingers at people. - Timebox each track so the discussion stays balanced and you reach the 'Open Road Ahead' action items. - Encourage quieter team members to contribute at least one unsung hero shout-out to build inclusivity. - Group similar ideas together before voting so the team can focus discussion on the biggest themes. - End every session with clear, owned action items so the retrospective drives real change. ## Icebreaker questions - If your week had a country song title, what would it be? - Cowboy boots, big hat, or pickup truck — which one best describes your work style and why? --- # Dungeons & Dragons Quest Retrospective URL: https://www.teamretro.com/retrospective-templates/dungeons-and-dragons-quest-retrospective/ Roll for initiative and gather your party! The Dungeons & Dragons Quest retrospective transforms your team's reflection into an epic adventure, framing the journey of your last sprint or project as a heroic quest filled with dragons to slay, treasure to claim, and lessons learned along the road. By casting your team as a fellow band of adventurers, this themed retrospective lowers the pressure of formal review meetings and invites creative, candid storytelling about what truly happened on the campaign trail. Inspired by the collaborative spirit of tabletop role-playing games, this format works because storytelling is a powerful way to surface insights. Team members reflect on the monsters they defeated (challenges overcome), the loot they gathered (wins and gains), the traps they triggered (mistakes and risks), and the quests still ahead (goals and next steps). The playful metaphor encourages even quieter party members to speak up, while the structure keeps the conversation grounded in real, actionable outcomes that your team can carry into the next adventure. Whether you're a seasoned guild of agile practitioners or a new party setting out on your first campaign, this retrospective builds camaraderie, sparks engagement, and produces meaningful improvement actions. Perfect for teams who love a little fantasy flavour with their continuous improvement, it turns the often-routine retrospective into a memorable shared story worth retelling. ## Topics - **Dragons We Slayed**: What big challenges or obstacles did we overcome? - **Treasure We Found**: What wins, gains or rewards did we collect along the way? - **Traps We Triggered**: What mistakes, risks or pitfalls tripped us up? - **Next Quest**: What adventures and goals should the party tackle next? ## When to use - When your team needs a fun, themed retrospective to re-energise reflection after a long or intense project. - When you want to lower the formality of a review and encourage quieter team members to share openly through storytelling. - When celebrating big wins and overcoming challenges, and you want a memorable way to capture lessons learned. - When building camaraderie in a new team and you want an engaging icebreaker-style retrospective. - When recurring sprint retrospectives have grown stale and you need a creative format to boost participation. ## Tips and tricks - Set the scene at the start by narrating the team's recent journey as a quest — a little dramatic flair helps everyone get into character. - Keep the metaphor light and inclusive; not everyone plays D&D, so briefly explain each topic so all party members feel welcome. - Timebox each phase so the storytelling stays energetic and you leave enough time to turn ideas into concrete actions. - Make sure every adventurer contributes — use anonymous brainstorming first so quieter voices aren't overshadowed by the loudest party member. - Always close by converting the best 'Next Quest' ideas into actions with clear owners so the adventure leads to real improvement. - Keep the tone blame-free when discussing 'Traps We Triggered' so people feel safe sharing mistakes as shared learning. ## Icebreaker questions - If you were a Dungeons & Dragons character class, which would you be and why? - What magical item would you want in your inventory to help with your work? --- # AI Evolution Retrospective URL: https://www.teamretro.com/retrospective-templates/ai-evolution-retrospective/ The AI Evolution Retrospective gives teams a dedicated space to step back and make sense of how artificial intelligence is changing the way they work. As AI tools become woven into daily workflows — from code assistants and content generators to automated analysis and decision support — teams rarely pause to ask what's actually working, what's risky, and where they should head next. This format turns those scattered observations into a shared, honest conversation. It works by guiding participants through four lenses: the AI wins worth celebrating, the friction and frustrations encountered, the risks and concerns that need attention, and the experiments or skills to pursue next. By structuring reflection this way, teams move beyond hype and fear to a balanced view of their AI maturity. The conversation surfaces practical lessons, aligns everyone on responsible use, and helps prioritise the investments — in tooling, training, or guardrails — that will have the biggest impact. The benefit is a team that adopts AI intentionally rather than reactively. Whether you're an engineering squad integrating coding copilots, a marketing team experimenting with generative content, or a leadership group setting AI policy, this retrospective builds the continuous-improvement habits that keep your AI journey safe, ethical, and genuinely valuable. Run it quarterly or at key milestones to track how your collective capability is evolving. ## Topics - **AI Wins**: Where has AI helped us work smarter or faster? - **Friction & Frustrations**: Where has AI slowed us down or let us down? - **Risks & Concerns**: What worries us about how we're using AI? - **Next Experiments**: What should we try, learn, or build next? ## When to use - After several weeks or months of adopting new AI tools, to assess what's working and what isn't. - When your team wants to align on responsible and ethical AI use before scaling it further. - At quarterly intervals to track how your team's AI maturity and capability are evolving. - When AI adoption feels chaotic and you need to consolidate tools, standards, and learnings. - Before setting AI strategy, policy, or training investments for the coming period. ## Tips and tricks - Set ground rules early that surfacing concerns about AI is welcomed, so people feel safe raising risks without seeming resistant to change. - Ask for concrete examples and specific tools rather than general opinions — this makes wins repeatable and frustrations actionable. - Balance the conversation so optimists and skeptics both contribute; AI discussions can easily tip into hype or fear. - Use anonymous brainstorming for the Risks & Concerns topic to encourage honesty about sensitive issues like data privacy or over-reliance. - Close by committing to only two or three experiments so the team doesn't overload itself between sessions. - Capture metrics where possible, such as time saved or error rates, to ground future retrospectives in evidence rather than impressions. ## Icebreaker questions - If you could hand off one part of your job to an AI today, what would it be and why? - What's the most surprising thing an AI tool has done for you — good or bad — recently? --- # Black Friday Frenzy Retrospective URL: https://www.teamretro.com/retrospective-templates/black-friday-frenzy-retrospective/ Black Friday is the high-pressure peak of the retail calendar — a frenzy of traffic spikes, flash deals, fulfillment crunches, and all-hands-on-deck energy. Once the dust settles, the Black Friday Frenzy Retrospective gives your team the structured space to unpack what actually happened during one of the most demanding periods of the year. It captures the wins worth repeating, the bottlenecks that nearly broke things, and the lessons that turn a chaotic scramble into a smoothly run operation next season. This retrospective works by guiding teams through reflection across the full lifecycle of a major sales event: the preparation that set you up, the moments that delivered under pressure, the pain points that caused stress, and the concrete improvements to lock in for next year. Whether you're an e-commerce, marketing, operations, customer support, or engineering team, it helps everyone share their perspective on a shared high-stakes experience while the details are still fresh. The real value comes from converting a once-a-year adrenaline rush into repeatable, documented knowledge. By celebrating effort, surfacing friction honestly, and agreeing on actionable next steps, your team builds resilience and confidence ahead of the next big retail moment — be it Cyber Monday, the holiday rush, or next year's Black Friday. ## Topics - **Deals That Delivered**: What worked well and is worth repeating next time? - **Bottlenecks & Breakdowns**: What caused stress, delays or frustration during the event? - **Prep & Planning**: How well were we set up before the big day? - **Lock It In For Next Time**: What improvements should we commit to for the next event? ## When to use - Immediately after a Black Friday, Cyber Monday or major sales event while details are fresh in everyone's mind. - When preparing for the next peak retail season and you want to carry forward lessons learned. - For e-commerce, retail, marketing, operations or support teams that experienced a high-volume, high-pressure period together. - To recognise and celebrate team effort after an intense all-hands sprint and rebuild momentum. - When you want to convert a once-a-year experience into a documented, repeatable playbook. ## Tips and tricks - Run the session within a week of the event so memories and emotions are still fresh and accurate. - Set a blameless tone upfront — the goal is to improve systems, not assign blame for breakdowns. - Invite voices from across teams (marketing, ops, support, engineering) for a complete picture of the event. - Balance the energy by spending real time celebrating wins, not just fixing problems — people are tired after the rush. - Prioritise improvements by impact and feasibility, then assign clear owners and deadlines so actions don't get lost. - Capture findings in a runbook or playbook you can reuse and refine before the next peak season. ## Icebreaker questions - What was your personal 'oh no' moment during the Black Friday weekend? - If you could give your past self one piece of advice before the event kicked off, what would it be? --- # Lost Deals Retrospective URL: https://www.teamretro.com/retrospective-templates/lost-deals-retrospective/ A Lost Deals Retrospective is a focused meeting to review recent lost sales opportunities and identify areas for improvement. By analyzing what went well, what didn't, and why deals were lost, teams can uncover valuable insights to refine their sales process, messaging, and strategies. This type of retrospective encourages open discussion in a blame-free environment. It helps teams learn from experiences, build on strengths, and address weaknesses. The goal is continuous improvement by turning losses into lessons. ## Topics - **What went wrong?**: What factors contributed to losing the deal? - **What went well?**: What did we do right during the sales process? - **What can we learn?**: What key lessons or insights did we gain? - **What should we do differently?**: How can we apply these lessons to improve? ## When to use - After losing a major sales opportunity to analyze what went wrong and identify areas for improvement. - On a recurring basis (e.g. quarterly) to review a group of lost deals and look for patterns or trends. - When struggling to meet sales targets or seeing a high percentage of deals falling through. - As part of continuous improvement efforts for your sales process and enablement. ## Tips and tricks - Create a blame-free environment focused on learning, not finger-pointing. - Involve all key stakeholders impacted by the lost deal for diverse perspectives. - Document key findings and commit to specific action items for improvement. - Follow up to ensure action items are implemented and having the desired impact. - Consider bringing in an outside facilitator for an objective point of view. - Build in time for open discussion beyond just the core topics. ## Icebreaker questions - If you could be a door-to-door salesperson, what would be the worst or weirdest product to sell? - What's the most memorable or cringeworthy sales call or pitch you've experienced? --- # End of Year Retrospective URL: https://www.teamretro.com/retrospective-templates/end-of-year-retrospective/ The end of year retrospective is an opportunity to look back on the past 12 months and celebrate successes, analyze setbacks, and identify areas for improvement. It allows teams to gain valuable insights and set the stage for an even more productive year ahead. This template encourages participants to share their perspectives on what went well, what didn't go as planned, and what they've learned. It fosters an open and constructive dialogue, helping teams build on their strengths and address any weaknesses or obstacles they encountered. By taking the time to reflect collectively, teams can develop a shared understanding of their journey and use those insights to inform their goals and strategies for the upcoming year. ## Topics - **Highlights and achievements**: What were the team's most significant accomplishments this year? - **Challenges and obstacles**: What were the most significant challenges or setbacks the team faced? - **Lessons learned**: What valuable lessons did the team learn from the challenges faced? - **Areas for improvement**: What aspects of our work or processes could be improved in the coming year? ## When to use - At the end of a calendar year or fiscal year, to review the past 12 months. - During annual planning or goal-setting sessions, to inform future strategies. - After completing a major project or initiative, to capture lessons learned. - When onboarding new team members, to provide context and insights from the previous year. - As part of a continuous improvement process, to identify areas for growth and development. ## Tips and tricks - Encourage open and honest feedback by creating a safe and judgment-free environment. - Use visual aids or prompts to stimulate discussion and capture key points. - Assign a dedicated note-taker to document the insights and action items. - Celebrate successes and achievements, but also embrace failures as learning opportunities. - Ensure that the retrospective remains constructive and focused on improvement, not blame. - Follow up on the identified areas for improvement by creating actionable plans. ## Icebreaker questions - What was the most memorable moment or highlight of the past year for you? - If you could describe the past year in three words, what would they be? --- # AI Agents Retrospective URL: https://www.teamretro.com/retrospective-templates/ai-agents-retrospective/ The AI Agents Assemble retrospective uses the metaphor of AI systems to help teams analyze successes, uncover glitches, and surface blockers for targeted improvement. By framing team dynamics through the lens of intelligent agents — each with inputs, outputs, and the occasional system error — this format makes it easier to talk honestly about what's working, what's breaking down, and what needs a reboot. It's a fresh, engaging way to run a retrospective that resonates especially well with tech-savvy teams. Inspired by the world of autonomous AI agents that collaborate, adapt, and self-correct, this retrospective invites your team to think of themselves as a high-performing system. Just like a well-designed AI pipeline, great teams depend on clean inputs, efficient processing, and reliable outputs. When something goes wrong, you don't blame the machine — you debug it. This format encourages a blameless, systems-thinking mindset that leads to more constructive conversations and actionable outcomes. Whether you're a software engineering team, a product squad, or any group that loves a good tech metaphor, the AI Agents Assemble retrospective brings energy and creativity to your regular cadence. Use it to celebrate your wins, identify the bugs slowing you down, and align on the upgrades your team needs to level up. It's the perfect retrospective for teams who want to reflect smarter, not harder. ## Topics - **Algorithms That Worked**: What processes or behaviours delivered great results? - **System Glitches**: What errors or failures slowed the team down? - **Missing Gaps **: What knowledge gaps or missing information held us back? - **Upgrade Requests**: What improvements or experiments should we run next? ## When to use - When your team wants a fresh, creative spin on the standard retrospective format that still drives meaningful outcomes. - Ideal for tech or engineering teams who will connect naturally with AI and systems-thinking metaphors. - Use it after a sprint or project phase where there were notable successes and failures worth unpacking in a structured but engaging way. - Great for teams experiencing recurring blockers or knowledge gaps that haven't been surfaced through traditional retrospective formats. - When you want to energise a team that has grown fatigued with the same retrospective structure and needs a new lens to spark honest conversation. ## Tips and tricks - Set a blameless tone early — remind the team that just like debugging software, the goal is to fix the system, not point fingers at individuals. - Timebox each topic to keep energy high. AI Agents Assemble works best as a fast-paced session; aim for 10–12 minutes per topic. - Encourage specificity in 'System Glitches' — vague complaints like 'communication was bad' are hard to act on. Push for concrete examples and root causes. - Don't let 'Upgrade Requests' become a wishlist. For each idea, ask the team to identify an owner and a first small step to make it actionable. - If the team is new to the AI metaphor, spend 2–3 minutes at the start framing the analogy — it helps people engage more creatively with the prompts. - Watch for patterns across topics. If the same theme appears in both 'System Glitches' and 'Missing Training Data,' it's likely a high-priority systemic issue worth addressing first. ## Icebreaker questions - If you were an AI agent, what would your core function be — and what's your most common error message? - If your team were an AI model, what dataset would you say you've been trained on, and what data are you still missing? --- # Pathfinder Retrospective URL: https://www.teamretro.com/retrospective-templates/pathfinder-retrospective/ The Pathfinder retrospective is a forward-thinking approach that helps teams chart their course toward improvement and innovation. By focusing on discussion, change, and experimentation, this format encourages teams to explore new possibilities and create actionable paths forward. This retrospective format is particularly effective for teams who want to break out of established patterns and discover fresh approaches to their work. It combines elements of strategic planning with practical experimentation, helping teams move from idea generation to concrete action. The three-phase structure guides teams through a natural progression: first exploring topics through open discussion, then identifying potential changes, and finally committing to specific experiments. This approach ensures that conversations lead to tangible outcomes and meaningful progress. ## Topics - **Let's discuss**: What should we talk about? - **Let's change**: What areas of change could we pursue? - **Let's try**: What should we try or experiment with? ## When to use - When the team feels stuck in current practices and needs fresh perspectives - During periods of organizational change when new approaches are needed - When you want to encourage innovation and experimental thinking - After identifying recurring issues that require new solutions ## Tips and tricks - Keep experiments small and timeboxed to reduce risk and increase learning opportunities - Ensure each experiment has clear success criteria and a defined evaluation period - Document both successful and unsuccessful experiments to build organizational knowledge - Encourage participation from all team members, as diverse perspectives lead to better experiments - Follow up on experiments in subsequent retrospectives to track progress and adjust as needed ## Icebreaker questions - What's the most interesting experiment or new approach you've tried recently, either at work or in your personal life? - If you could instantly change one thing about how we work together, what would it be? --- # Engineering Team Retrospective URL: https://www.teamretro.com/retrospective-templates/engineering-team-retrospective/ Engineering teams thrive when they take time to reflect on how they build, ship, and collaborate. The Engineering Team Retrospective gives developers, QA, DevOps, and engineering leads a structured space to examine the technical and human sides of their work — from code quality and deployment pipelines to communication and on-call health. By surfacing what's working and what's slowing the team down, you create a shared understanding that fuels continuous improvement sprint after sprint. This retrospective works by guiding the team through a series of focused topics covering technical practices, processes, collaboration, and wins. Participants reflect on questions like what engineering practices served them well, where technical debt or bottlenecks crept in, and how they can work smarter together. In TeamRetro, everyone can contribute ideas in parallel, group similar themes, vote on what matters most, and turn the conversation into clear, trackable action items. The result is an honest, blameless discussion that respects engineering culture and drives measurable change. Whether you run it at the end of every sprint, after a major release, or as a regular team health check, this format helps engineering teams build psychological safety, reduce recurring friction, and ship better software. It's a practical, developer-friendly way to keep your team learning and improving while celebrating the hard work that often goes unnoticed. ## Topics - **What worked well?**: Which engineering practices or wins should we keep? - **What slowed us down?**: What blockers, friction, or technical debt held us back? - **How did we collaborate?**: How well did we communicate and support each other? - **What should we try next?**: What experiments or improvements should we commit to? ## When to use - At the end of each sprint or iteration to reflect on engineering practices and continuously improve delivery. - After a major release, incident, or production issue to capture lessons learned in a blameless way. - As a regular team health check to surface technical debt, bottlenecks, and collaboration friction before they grow. - When onboarding new engineers or changing team structure to align on ways of working. ## Tips and tricks - Keep the discussion blameless — focus on systems, processes, and circumstances rather than pointing fingers at individuals. - Encourage every voice by collecting ideas anonymously and in parallel before discussion, so quieter engineers and seniors contribute equally. - Use dot voting to prioritize the most impactful topics rather than trying to solve everything in one session. - Turn insights into a small number of concrete, owned action items and review them at the start of the next retrospective. - Timebox each topic to keep energy high and avoid rabbit-holing on a single technical debate. - Rotate the facilitator role so the team shares ownership and the format stays fresh. ## Icebreaker questions - If your codebase were a city, what kind of place would it be right now? - What's one piece of tech or tooling you couldn't live without this sprint? --- # Seasons of the Year Retrospective URL: https://www.teamretro.com/retrospective-templates/seasons-of-the-year-retrospective/ The Seasons of the Year retrospective uses nature's cycles as a powerful metaphor for team development and organizational change. This innovative approach helps teams explore their experiences through the lens of seasonal transitions, making abstract concepts more tangible and relatable. By mapping team experiences to spring (growth), summer (peak performance), autumn (transformation), and winter (reflection), teams can identify patterns in their work cycles and understand how different phases affect their productivity and collaboration. This natural framework encourages honest dialogue about team dynamics while maintaining a positive, forward-looking perspective. Originally adapted from nature-based reflection techniques, this retrospective format helps teams acknowledge that change is natural and cyclical, leading to more constructive discussions about challenges and opportunities for growth. ## Topics - **Spring**: Growing or blossoming - **Summer**: Sizzling or shining - **Autumn**: Evolving or changing - **Winter**: Slowing or chilling ## When to use - When the team needs to reflect on different phases of their development or project lifecycle - During times of significant organizational change to help team members process and adapt - When you want to encourage metaphorical thinking to unlock new insights about team dynamics - To help teams understand that challenges and growth are natural, cyclical processes ## Tips and tricks - Encourage participants to think metaphorically about how their experiences align with seasonal characteristics - Remind the team that all seasons are necessary and valuable - winter isn't inherently negative - Use seasonal transitions to discuss how the team can prepare for and adapt to change - Consider running this retrospective quarterly to track how team dynamics evolve over time - Create a safe space for discussing 'winter' topics by emphasizing their role in renewal and growth ## Icebreaker questions - If your current work mood was a season, which would it be and why? - What's your favorite season at work, and what makes it special? --- # Project Kickoff Planning URL: https://www.teamretro.com/retrospective-templates/project-kickoff-planning/ A project kickoff planning session is a collaborative meeting where the team aligns on the project's objectives, scope, timeline, and potential risks. It allows everyone to voice their perspectives, identify challenges, and develop a shared understanding of the work ahead. This structured activity guides the team through brainstorming key aspects like goals, processes, risks, and dependencies. It promotes open discussion, captures diverse ideas, and ensures everyone is on the same page before execution begins. By investing time in thoughtful planning upfront, teams can anticipate roadblocks, establish clear responsibilities, and increase their chances of delivering a successful project. ## Topics - **Project Goals**: What are the key goals and objectives for this project? - **Key Processes**: What are the critical processes and workflows needed for success? - **Potential Risks**: What are the major risks or roadblocks we should plan for? - **Team & Dependencies**: Who are the key stakeholders, and what dependencies exist? - **Timeline & Milestones**: What are the key milestones and deadlines we need to hit? ## When to use - When kicking off a new project or major initiative to align the team on objectives, approach, and potential challenges. - After a project has been approved but before execution begins, to facilitate comprehensive planning and preparation. - Whenever a project experiences significant changes in scope, timeline, or resources, to re-evaluate and adjust the plan accordingly. - Periodically throughout a long-running project to review progress, identify risks, and course-correct as needed. ## Tips and tricks - Encourage open and honest discussion by creating a safe space for all perspectives to be shared. - Assign a dedicated note-taker to capture key points and action items for future reference. - Use visual aids like whiteboards or digital kanban boards to organize ideas and make connections more apparent. - Set a positive, solution-oriented tone, but don't shy away from addressing potential roadblocks head-on. - Leave ample time for Q&A and discussion to ensure everyone is aligned and bought into the plan. - Establish clear owners and next steps for any outstanding items or risks that require further investigation. ## Icebreaker questions - If this project was a movie, what would be the title and tagline? - Share one small win or accomplishment you're proud of from a past project. --- # All Aboard the Agile Express Retrospective URL: https://www.teamretro.com/retrospective-templates/all-aboard-the-agile-express-retrospective/ All Aboard the Agile Express turns your team reflection into a journey, using the metaphor of a train ride to explore where your sprint or project has been and where it's heading next. By framing the retrospective around a moving train — its engine, fuel, passengers, obstacles on the track, and final destination — teams gain a shared visual language that makes it easier to surface what's driving momentum and what's slowing the journey down. It's an engaging twist on the classic agile retrospective that keeps energy high while still uncovering meaningful, actionable insights. The format works by guiding participants through a series of train-inspired prompts. The team identifies the forces powering them forward, the friction holding them back, the cargo and people they're carrying, and the destination they're working toward. This narrative structure helps teams move beyond surface-level observations and connect their day-to-day work to a bigger picture, making it ideal for sprint reviews, project milestones, and quarterly check-ins alike. Themed retrospectives like this one are a great way to break monotony and re-engage teams who may have grown tired of standard "what went well / what didn't" formats. Whether you're a Scrum Master looking to inject some fun into a routine ceremony or an agile coach wanting to spark fresh conversation, the Agile Express keeps everyone on board and moving in the same direction toward continuous improvement. ## Topics - **The Engine**: What powered us forward this sprint? - **The Brakes**: What slowed us down or held us back? - **Obstacles on the Track**: What risks or obstacles lie ahead of us? - **Next Station**: Where do we want to be by our next stop? ## When to use - When your team has grown tired of the standard retrospective format and needs a fresh, engaging way to reflect. - At the end of a sprint or iteration to assess what's driving momentum and what's slowing progress. - During project milestones or quarterly check-ins to align the team on direction and upcoming risks. - When you want to balance celebrating wins with forward-looking risk planning in a single session. ## Tips and tricks - Set the scene by briefly explaining the train metaphor so everyone understands what each carriage represents before brainstorming. - Encourage equal participation by giving everyone quiet time to add ideas anonymously before discussion to reduce bias. - Frame The Brakes around systems and processes rather than individuals to keep the conversation blameless and safe. - Timebox each section to keep the train on schedule and ensure you reach the Next Station with concrete actions. - Group and vote on similar ideas to focus discussion on the themes that matter most to the team. - Always close by assigning owners and due dates to action items so insights translate into real change. ## Icebreaker questions - If our team were a train, would we be a high-speed bullet train, a scenic steam engine, or a stuck-at-the-station local? - What's the best or most memorable train (or travel) journey you've ever taken? --- # Agile Thanksgiving Retrospective URL: https://www.teamretro.com/retrospective-templates/agile-thanksgiving-retrospective/ Thanksgiving is the perfect moment to pause, reflect, and express appreciation for the people and progress that make your team great. The Agile Thanksgiving Retrospective blends the spirit of the holiday with proven agile reflection practices, giving your team a warm, festive space to look back on the work you've shared and the wins worth celebrating. It's a refreshing change of pace from the standard sprint review that keeps engagement high while still surfacing meaningful insights. This seasonal retrospective works by guiding your team through a series of gratitude-themed prompts — from giving thanks for teammates and accomplishments, to acknowledging the lessons learned and the "leftovers" worth carrying forward. As participants share what they're grateful for, what nourished the team, and what they'd like more of next time, you naturally uncover both strengths to reinforce and opportunities to improve. Recognition and appreciation are powerful drivers of morale and psychological safety, and structuring them into a retrospective builds a culture where people feel seen and valued. Whether you run it in the lead-up to Thanksgiving, at the end of a major sprint, or as a year-end wrap-up, the Agile Thanksgiving Retrospective helps teams reconnect, celebrate collective effort, and set a positive, intentional tone for what comes next. It's a simple, feel-good format that reminds everyone why the work — and the people doing it — matter. ## Topics - **Grateful For**: Who or what are you most thankful for this sprint? - **What Nourished Us**: What practices or wins fed the team and kept us strong? - **Leftovers to Reheat**: What unfinished items should we carry into next time? - **Room for Seconds**: What would you like more of going forward? ## When to use - During the Thanksgiving season or November sprints when you want to add a festive, appreciative tone to your reflection. - As a year-end or quarter-end retrospective to celebrate accomplishments and recognize teammates. - When team morale needs a boost and you want to reinforce a culture of gratitude and recognition. - Following an intense sprint or major release where the team deserves to pause and acknowledge their collective effort. ## Tips and tricks - Set a warm, inclusive tone at the start — remind everyone that no thanks is too small to share. - Make sure every voice is heard; go around the team so quieter members get a chance to express appreciation. - Balance gratitude with growth — don't let the festive theme stop you from capturing real improvement actions. - Avoid making recognition feel obligatory or generic; encourage specific, sincere callouts over blanket thank-yous. - Capture the 'Leftovers to Reheat' and 'Room for Seconds' items as concrete action items so they aren't forgotten. - Add a fun seasonal touch, like a virtual gratitude wall, but keep the session time-boxed to maintain focus. ## Icebreaker questions - If your sprint were a Thanksgiving dish, what would it be and why? - What's one thing — work or non-work — you're especially thankful for this year? --- # Escalation Process Retrospective URL: https://www.teamretro.com/retrospective-templates/escalation-process-retrospective/ The Escalation Process Retrospective is a focused review of how issues or incidents were escalated and handled within a team or organization. It provides a structured way to analyze the effectiveness of existing escalation processes, identify areas for improvement, and implement changes to streamline future escalations. This retrospective encourages teams to reflect on recent escalations, examining what went well, what didn't, and what could be done better next time. It fosters open communication, shared learning, and continuous process optimization. By regularly conducting Escalation Process Retrospectives, teams can refine their escalation procedures, enhance collaboration, and ensure a smoother flow of information and decision-making during critical situations. ## Topics - **Recent Escalations**: What recent escalations or incidents did we handle? - **Escalation Effectiveness**: How effective were our escalation processes? - **Process Improvements**: What improvements can we make to our escalation processes? - **Collaboration and Communication**: How can we improve collaboration and communication during escalations? ## When to use - After experiencing a significant incident or escalation to review the process and identify areas for improvement. - As part of a regular process review or continuous improvement initiative to optimize escalation procedures. - When introducing new systems, processes, or teams that may impact escalation procedures. - After organizational changes or restructuring to align escalation processes with new structures or roles. - When onboarding new team members or stakeholders to ensure a shared understanding of escalation processes. ## Tips and tricks - Encourage open and honest feedback by creating a safe environment for participants to share their perspectives without fear of blame or criticism. - Involve stakeholders from different teams and levels of the organization to gain diverse perspectives and ensure buy-in for any proposed changes. - Document the outcomes and action items from the retrospective, and assign clear ownership and timelines for implementing improvements. - Consider using anonymized examples or case studies to facilitate discussions without singling out individuals or teams. - Celebrate successes and positive outcomes from previous escalations to reinforce good practices and boost team morale. - Regularly review and update the escalation processes based on lessons learned and changing organizational needs. ## Icebreaker questions - If you could design a superhero to handle escalations, what powers would they have? - Share a funny or memorable experience from a past escalation (without naming names). --- # Christmas Carol Retrospective URL: https://www.teamretro.com/retrospective-templates/christmas-carol-retrospective/ The Christmas Carol Retrospective transforms Charles Dickens' classic tale into a powerful team reflection framework. By structuring discussions around the ghosts of Christmas Past, Present, and Future, teams gain a multi-dimensional perspective on their work and relationships. This retrospective creates a familiar narrative structure that encourages team members to honestly examine completed work, current challenges, and future aspirations. The storytelling approach makes reflection more engaging while the temporal framework ensures comprehensive coverage of team dynamics and project evolution. Beyond its festive theme, this retrospective delivers practical value by connecting historical patterns with current realities and potential outcomes. Teams emerge with clearer understanding of their journey, present circumstances, and actionable steps toward improvement. The format works particularly well during end-of-year reviews or when teams need perspective on their overall trajectory. ## Topics - **Ghost of Christmas Past**: What can we learn from our previous work and experiences? - **Ghost of Christmas Present**: What current challenges and successes are we experiencing? - **Ghost of Christmas Future**: What opportunities and risks do we see ahead? ## When to use - During end-of-year reviews when teams naturally reflect on their annual journey and set goals for the coming year. - When teams need to connect historical patterns with current challenges and future opportunities. - After significant organizational changes to help teams process what's been lost, what's currently changing, and what possibilities lie ahead. - When team morale needs a boost through a creative, story-based approach to reflection. - For distributed teams who can bond over the universally recognized Christmas Carol narrative. ## Tips and tricks - Encourage storytelling by asking team members to frame their reflections as mini-narratives rather than isolated points. - Balance the emotional aspects of reflection with practical action items, especially in the 'Ghost of Christmas Future' section. - Consider theming your retrospective visually with subtle holiday elements to enhance engagement without being distracting. - Allow adequate time for the 'Ghost of Christmas Present' section as current issues often generate the most discussion and immediate action items. - If team members struggle with the 'Ghost of Christmas Future' section, provide prompts about ideal scenarios or potential risks to stimulate thinking. - For multicultural teams, briefly explain the Christmas Carol story beforehand to ensure everyone understands the metaphor. ## Icebreaker questions - If you could time travel like Scrooge, which period in your team's history would you most want to revisit and why? - What's one 'gift' (skill, insight, or support) you've received from a team member this year that you're particularly grateful for? --- # KPop Demon Hunters Retrospective URL: https://www.teamretro.com/retrospective-templates/kpop-demon-hunters-retrospective/ Inspired by the high-energy world of KPop idols who moonlight as demon-slaying heroes, this playful retrospective turns your team reflection into a chart-topping performance. Just like a band that must rehearse, perform, and battle the demons threatening their next big show, your team gathers to celebrate the hits, confront the blockers, and plan the next encore. It's a creative way to break the routine of standard sprint reviews while still surfacing the insights that matter most. The format works by mapping familiar retrospective themes onto a fun, narrative-driven structure. Teams reflect on their recent "performances" (what went well), name the "demons" they faced (challenges and blockers), tune up their "harmony" (collaboration and process), and choose their "next hit" (action items and improvements). This storytelling lens lowers psychological barriers, encourages quieter members to contribute, and makes continuous improvement feel less like a chore and more like a shared mission. Ideal for agile teams looking to re-energize their retrospective cadence, this themed session blends entertainment with genuine reflection. By wrapping practical agile feedback in a memorable metaphor, you boost engagement, foster psychological safety, and walk away with concrete, prioritized actions — all while having a little fun together. ## Topics - **Chart-Topping Hits**: What performances and wins should we celebrate? - **Demons We Faced**: What blockers and challenges threatened our show? - **Finding Our Harmony**: How well did we collaborate and stay in sync? - **Our Next Hit**: What will we do to make the next sprint even better? ## When to use - When your team's retrospectives have gone stale and you want to re-energize the routine with a fun, themed session. - After an intense or challenging sprint where a lighter tone can help the team open up about blockers. - For teams that enjoy pop culture and respond well to creative, narrative-driven formats. - As a periodic change-of-pace retrospective to boost engagement and participation. ## Tips and tricks - Set the mood by introducing the theme up front — lean into the metaphor so everyone feels free to be playful. - Keep the 'Demons We Faced' discussion blameless; focus on the obstacle, not the individual, to protect psychological safety. - Timebox each topic so the fun doesn't crowd out the action planning at the end. - Make sure every voice is heard — invite quieter members to share their 'hit' or 'demon' directly. - Limit action items to one or two high-impact changes so they actually get done by the next sprint. - Revisit the previous session's action items at the start to close the loop and build accountability. ## Icebreaker questions - If your team were a KPop group, what would your band name be and who plays which role? - What's the one 'demon' (bad habit or blocker) you'd most love to slay this sprint? --- # Vendor Management Review URL: https://www.teamretro.com/retrospective-templates/vendor-management-review/ The Vendor Management Review is a structured retrospective that helps teams assess their relationships with external vendors, identify areas for improvement, and optimize processes. By examining what's working well, pain points, workflows, and other key factors, teams can strengthen vendor collaborations and drive better outcomes. This review encourages open discussions, fosters continuous improvement, and aligns teams and vendors towards shared goals. It's particularly valuable for teams that rely heavily on vendor services or have complex vendor management processes. ## Topics - **What's Working Well?**: Which vendor relationships are thriving, and what makes them successful? - **Pain Points & Challenges**: What vendor-related issues are causing frustration or delays? - **Process & Workflow**: How can we improve processes and workflows with our vendors? - **Strategic Alignment**: How can we better align vendor partnerships with our long-term goals? - **Cost Optimization**: How can we optimize costs and maximize value from our vendor relationships? ## When to use - When you have a significant number of vendor relationships that require regular review and optimization. - If you've experienced recurring issues or challenges with specific vendors that need to be addressed. - As part of a periodic vendor management process to ensure alignment, identify improvement areas, and foster continuous collaboration. - When considering strategic changes or initiatives that may impact your vendor partnerships or require new vendor relationships. ## Tips and tricks - Encourage open and honest feedback from all team members, but avoid personal attacks or blame games. - Invite representatives from key vendor partners to participate and provide their perspectives. - Use data and metrics to support observations and recommendations whenever possible. - Assign action items and owners for any identified improvement areas or follow-up tasks. - Consider involving stakeholders from other departments, such as procurement, legal, or finance, for a more comprehensive review. - Foster a collaborative and solution-oriented mindset, focusing on how to strengthen vendor partnerships for mutual benefit. ## Icebreaker questions - If you could outsource any aspect of your personal life to a vendor, what would it be and why? - Share a funny or memorable experience you've had while working with a vendor (without naming names). --- # Hawaiian Island Retreat Retrospective URL: https://www.teamretro.com/retrospective-templates/Island-retreat-retrospective/ Mahalo! Dive into our Hawaiian-inspired Island Retreat Retrospective — a refreshing and creative way to reflect on your sprint through the lens of island life. Surf the waves of progress, share the sunshine of successes, and navigate the tides of challenges to keep your team's momentum breezy and bright. Whether your team is riding high on a wave of wins or paddling through choppy waters, this retro brings a spirit of aloha to your continuous improvement journey. Inspired by the warmth, community, and natural rhythms of Hawaiian culture, this retrospective format encourages teams to reflect on what's propelling them forward like a perfect wave, what sunshine moments deserve celebration, what obstacles are creating rough tides, and what actions the team should paddle toward next. The tropical theme helps lower defenses, spark creativity, and foster open, honest conversations — even when discussing difficult topics. The Island Retreat Retrospective is perfect for teams looking to inject some fun and energy into their regular cadence of reflection. It's especially effective for remote or distributed teams who benefit from a shared imaginative space, or for any team that needs a morale boost. By framing retrospective topics in the language of the islands, teams can approach feedback with a spirit of gratitude and collaboration — the true meaning of aloha. ## Topics - **Catch the Wave **: What momentum carried us forward this sprint? - **Sunshine Moments **: What successes and bright spots deserve a Mahalo? - **Rough Tides **: What challenges or obstacles created rough waters? - **Set Sail **: What actions should we paddle toward next sprint? ## When to use - When your team needs a morale boost and a fresh, engaging format to re-energise their retrospective practice after a few repetitive sessions. - When onboarding new team members and wanting to create a welcoming, low-pressure environment for their first retrospective experience. - When running a retrospective for a remote or distributed team that benefits from a shared imaginative theme to build connection across locations. - When the team has just completed a particularly challenging sprint and needs a positive, gratitude-focused framework to balance reflection with celebration. - When you want to encourage quieter team members to contribute more freely — the playful Hawaiian theme can lower social barriers and make sharing feel safer. ## Tips and tricks - Set the aloha tone early — open the session by briefly explaining the Hawaiian theme and the spirit of Mahalo (gratitude). This helps participants engage with the theme authentically rather than feeling like it's just a gimmick. - Encourage equal participation across all four topics. It's common for teams to focus heavily on 'Rough Tides' — remind the group that celebrating sunshine moments and catching waves is just as important for team health. - Use the 'Set Sail' topic to drive accountability. Ensure every action item has a clear owner and a target date before the session ends. Vague actions rarely get completed. - Watch out for the 'island vibes' effect — while the fun theme is a strength, make sure the session doesn't become too light-hearted to address real issues. Create space for honest, constructive feedback on rough tides. - For remote teams, consider adding a short virtual icebreaker with a Hawaiian theme (e.g., sharing a favourite beach memory) to build connection before diving into the retro topics. - Timebox each topic to keep the session on track. A typical Island Retreat Retro works well in 60–90 minutes — allocate roughly 10–15 minutes per topic and save the last 15 minutes for prioritising actions in 'Set Sail'. ## Icebreaker questions - If you could work remotely from any Hawaiian island for a month, which would you choose and why? - If your current sprint were a Hawaiian dish, what would it be — a fresh poke bowl, a slow-cooked kalua pig, or something else entirely? --- # Spice Up Your Retro URL: https://www.teamretro.com/retrospective-templates/spice-up-your-retro-retrospective/ Bring some heat to your team reflections with a fun, food-inspired format that organizes feedback by intensity and flavor. Using a spice-themed metaphor, teams categorize their experiences from the mild observations worth noting to the fiery issues that need urgent attention. It's a refreshing change from the standard retrospective, designed to keep energy high while still surfacing the insights that matter most. The format works by mapping team feedback onto a spice scale: mild ingredients represent the small wins and steady progress, medium spices capture the things that added flavor and worked well, hot items highlight the challenges that created friction, and the secret sauce surfaces the bold ideas and experiments worth trying next. This playful structure lowers the barrier to honest conversation, encouraging quieter team members to contribute and helping the group balance positive recognition with constructive critique. Inspired by the agile retrospective tradition of using creative metaphors to reframe reflection, this themed approach is perfect for teams that want to break routine and inject some personality into their meetings. Whether you run it at the end of a sprint or as a quarterly check-in, the spicy theme keeps things engaging while still driving the continuous improvement that makes retrospectives valuable. ## Topics - **Mild**: What small wins and steady progress are worth noting? - **Medium**: What added flavor and genuinely worked well? - **Hot**: What are the burning issues or require urgent attention? - **Secret Sauce**: What bold ideas or experiments should we try next? ## When to use - When your team's retrospectives have become routine and need a fresh, energizing format to re-engage everyone. - At the end of a sprint or iteration when you want to balance celebrating wins with surfacing pain points. - For team-building sessions where you want a lighthearted theme that still drives meaningful reflection. - When quieter team members need a low-pressure, playful structure that makes it easier to contribute. ## Tips and tricks - Set the tone early — lean into the spicy theme with playful language to help the team relax and open up. - Encourage balance by reminding the team to add items across all flavors, not just the hot ones. - Group similar ideas together before voting so the team focuses discussion on the most impactful themes. - Timebox each section to keep energy high and avoid getting stuck dwelling on the 'hot' issues. - Always turn 'Hot' items and 'Secret Sauce' ideas into concrete, owned action items before closing. - Rotate the facilitator role to keep the format fresh and give everyone a chance to add their own flavor. ## Icebreaker questions - If your week at work was a dish, how spicy would it be and why? - What's your go-to comfort food after a tough day, and what made this week tough or easy? --- # Kanban Flow Retrospective URL: https://www.teamretro.com/retrospective-templates/kanban-flow-retrospective/ Keeping work flowing smoothly is at the heart of any successful Kanban practice, and the Kanban Flow Retrospective helps your team focus on exactly that. Instead of looking at a sprint as a fixed time-box, this format encourages teams to reflect on the continuous movement of work through the system — examining where items get stuck, where flow is fast, and what is causing delays or pile-ups. It's a practical, flow-focused way to surface the real friction points that affect delivery speed and predictability. The retrospective works by guiding the team through key dimensions of Kanban health: the work that flowed well, the bottlenecks that slowed things down, work-in-progress (WIP) limits, and concrete improvements to make. By visualizing and discussing these areas together in TeamRetro, your team builds a shared understanding of how value moves from "to do" to "done." This makes it ideal for teams practicing Lean and Kanban methodologies, as well as agile teams looking to improve cycle time, throughput, and overall flow efficiency. The benefits go beyond a single meeting. Running a Kanban Flow Retrospective regularly helps teams cultivate a culture of continuous improvement (kaizen), reduce context-switching, and deliver more consistently. By tying reflections directly to flow metrics and observable workflow behavior, teams move away from blame and toward systems thinking — identifying process changes that genuinely improve how work gets done. ## Topics - **What flowed well?**: Where did work move smoothly through the board? - **Where were the bottlenecks?**: Which stages caused work to pile up or stall? - **WIP limits and policies**: Are our work-in-progress limits and rules working? - **What will we improve?**: What concrete changes will improve our flow? ## When to use - When your team practices Kanban or Lean and wants to continuously improve flow rather than reflect on fixed sprints. - When cycle times are increasing or work feels stuck, and you need to pinpoint bottlenecks in the workflow. - When WIP limits and column policies feel unclear or aren't being followed and need review. - When you want to tie retrospective discussions directly to flow metrics like throughput and lead time. - On a regular cadence (e.g. fortnightly or monthly) to embed a habit of continuous improvement. ## Tips and tricks - Bring your board and flow metrics (cycle time, throughput, WIP) into the conversation so reflections are grounded in data rather than opinion. - Focus on the system, not individuals — bottlenecks are usually process problems, so keep the tone blame-free. - Limit the number of improvement actions to one or two so the team can actually deliver on them before the next retro. - Make sure every action has an owner and a way to measure success at the next session. - Encourage quieter team members to contribute by using anonymous idea entry before discussion. - Revisit actions from the previous retrospective at the start to build accountability and track progress. ## Icebreaker questions - If your workflow were a type of traffic, what would it be right now — open highway, rush hour, or total gridlock? - What's one thing in your daily routine that always flows smoothly, no bottlenecks attached? --- # Start Stop Continue Retrospective URL: https://www.teamretro.com/retrospective-templates/start-stop-continue-retrospective/ The Start Stop Continue retrospective is a straightforward yet powerful method for teams to reflect on their work practices and behaviors. This action-oriented format helps teams quickly identify specific changes they want to make and successful practices they want to maintain. Developed as a feedback tool in the 1970s, this retrospective format has become popular in agile environments due to its simplicity and effectiveness. Teams use three simple categories to organize their thoughts: activities to begin implementing (Start), practices to eliminate (Stop), and successful behaviors to maintain (Continue). The clear structure makes it easy for teams to generate specific, actionable feedback while maintaining a balanced view of both improvements and successes. This approach is particularly effective for teams who want to focus on concrete actions rather than abstract discussions. You will sometimes see this format written as "Stop Start Continue" rather than "Start Stop Continue." It is the same exercise — the three categories are identical and you can run them in whichever order your team prefers. Some facilitators like to lead with "Stop" to clear away what is not working before deciding what to begin, while others start with "Start" to keep the tone forward-looking. Either way, the goal is the same: turn reflection into a short, concrete list of behaviours to begin, end, and keep. Start Stop Continue is also useful well beyond the sprint retrospective. Because it produces specific, behaviour-level feedback, teams use the same Start Stop Continue template for peer feedback, manager one-on-ones, project post-mortems, and personal goal-setting. For example, in a one-on-one a report might suggest their manager "start sharing the weekly priorities earlier," "stop scheduling reviews on Friday afternoons," and "continue the open Q&A at standup." The free template above gives everyone a private space to contribute before the team groups, votes, and agrees on actions together. ## Topics - **Start**: What should we start doing? - **Stop**: What should we stop doing? - **Continue**: What should we continue doing? ## When to use - When you want to quickly identify specific actions for team improvement - During periods of change to determine which practices to keep or modify - With new teams who need a simple framework for giving feedback - When the team needs to focus on concrete actions rather than abstract discussion ## Tips and tricks - Start with the 'Continue' column to begin on a positive note and acknowledge what's working well - Encourage specific, actionable items rather than vague statements - Keep a balanced perspective by ensuring all three columns receive adequate attention - Focus on behaviors and practices rather than individuals - Limit the final number of action items to ensure they're achievable - Schedule follow-up discussions to track progress on implemented changes ## Icebreaker questions - What's one positive change you've noticed in our team over the last month? - If you could instantly implement one improvement to our team's way of working, what would it be? --- # American Football (NFL) Retrospective URL: https://www.teamretro.com/retrospective-templates/americal-football-nfl-retrospective/ The NFL Retrospective transforms traditional agile retrospectives into an engaging format inspired by American Football. Drawing parallels between team sports and project delivery, this template helps teams analyze their performance using familiar NFL concepts. Just as football teams review game footage and strategize for upcoming matches, this retrospective framework enables teams to examine their achievements (Touchdowns), constraints (Lines of Scrimmage), setbacks (Interceptions and Tackles), and future strategies (The Next Plays). This sports-themed approach makes retrospectives more engaging while maintaining their effectiveness in driving continuous improvement. This format is particularly effective for teams who appreciate sports metaphors or want to energize their retrospective routine. It helps transform potentially challenging conversations about team performance into more approachable discussions using familiar football terminology. ## Topics - **Touchdowns**: What key outputs did we deliver? - **Lines of Scrimmage**: What boundaries do we keep in mind - **Interceptions and Tackles**: What didn't go to plan? What slowed us down? - **The next plays**: What do we want to try next? ## When to use - When team morale needs a boost and you want to make retrospectives more engaging - After completing a major project milestone or release to review team performance comprehensively - When introducing new team members to the concept of retrospectives in a fun, approachable way - When the team needs a fresh perspective on analyzing their work and collaboration patterns ## Tips and tricks - Keep the sports metaphors consistent but don't let them overshadow the actual retrospective goals - Consider using NFL-style statistics or metrics to visualize team performance trends - Rotate the role of 'coach' (facilitator) to give different team members leadership experience - Use a timer to keep discussions focused, just like quarters in a football game - Create a 'playbook' of successful strategies identified during retrospectives - Ensure the sports theme doesn't exclude team members who aren't football fans by explaining concepts clearly ## Icebreaker questions - If our team were an NFL team, what would our team name and mascot be, and why? - What's your favorite comeback story (in sports or technology) and what made it successful? --- # All I Want for Christmas is Feedback Retrospective URL: https://www.teamretro.com/retrospective-templates/all-i-want-for-christmas-is-feedback-retrospective/ Wrap up the year with a little holiday cheer and a lot of honest reflection. "All I Want for Christmas is Feedback!" turns the familiar end-of-year retrospective into a festive celebration where teams gather around to share gifts of feedback, name the wins worth celebrating, and gently regift the habits they'd rather leave behind. It's a playful, themed format that lowers the barrier to candid conversation, making it easier for everyone to contribute during the busy and reflective holiday season. This Christmas-themed retrospective works by inviting each team member to think of their input as a series of presents under the tree — the gifts they want to give, the gifts they'd like to receive, and the lumps of coal worth acknowledging so the team can do better next time. By framing feedback as something joyful and shared rather than critical, you create a psychologically safe space that encourages openness, gratitude, and forward-looking planning. The holiday wrapping is fun, but the value underneath is real: clearer communication, stronger appreciation, and concrete actions for the year ahead. Run it as a year-end celebration, a final sprint retrospective before the holidays, or a team-bonding session that doubles as meaningful reflection. Whether your team has had a sleigh-ride of a year or weathered a few storms, this format helps surface the moments that mattered, recognise the people who made a difference, and set intentions for a fresh and productive new year. ## Topics - **Gifts to Give**: What appreciation or feedback would you like to give the team? - **Lumps of Coal**: What didn't go so well and should be left behind? - **Christmas Wishes**: What hopes or wishes do you have for the team in the year ahead? ## When to use - As a year-end or final-sprint-of-the-year retrospective to reflect on the past twelve months in a festive, lighthearted way. - When you want to boost morale and gratitude during the holiday season while still capturing meaningful improvement actions. - For distributed or hybrid teams who can't gather in person but still want a shared seasonal celebration and reflection. - When team feedback has been hard to surface and a playful theme could lower the barrier to candid conversation. - As a team-bonding session that pairs holiday spirit with concrete planning for the new year. ## Tips and tricks - Lean into the festive theme with seasonal music, a fun background or holiday emojis to set a relaxed, inclusive tone before diving in. - Set a clear expectation that 'Lumps of Coal' should target processes and situations, not people, to keep psychological safety intact. - Encourage specific feedback in the 'Gifts to Give' section so appreciation feels genuine rather than generic. - Timebox each section so the celebration stays energetic and you leave room to agree on New Year's Resolutions. - Be mindful that not everyone celebrates Christmas — keep the framing optional and welcoming so all team members feel comfortable joining in. - Group and vote on themes before discussion so the most impactful resolutions rise to the top and get clear owners. ## Icebreaker questions - What's the best gift you've ever given or received, and why did it mean so much? - If you could unwrap one new skill or superpower for the team next year, what would it be? --- # Must Should Could Won't Retrospective URL: https://www.teamretro.com/retrospective-templates/mscw-retrospective/ Our actions should express our priorities, and Must Should Could Won’t is a great sprint retrospective template to help teams identify those priorities to ensure they continue to deliver value where it is most needed. With that in mind, it’s an approach that aligns well with agile processes and frameworks given its focus on the delivery of valuable things first. It is also a great Scrum sprint retrospective idea as it offers the product owner a mechanism to step into the shoes of their customer and view the product from their perspective. Developed in the 1990s by Dai Clegg, the MSCW method gained prominence in agile project management and business analysis. It provides a structured way to organize tasks into four distinct categories: Must have (critical), Should have (important), Could have (desired), and Won't have (not priority). The strength of MSCW lies in its simplicity and effectiveness in facilitating group discussions about priorities. By categorizing items into these four buckets, teams can better align their efforts with strategic goals, manage resources efficiently, and maintain clear communication about what will and won't be delivered. ## Topics - **Must**: Things we must definitely do. - **Should**: Things we should do. - **Could**: Things we could do. - **Won't**: Things we won't do. ## When to use - When planning a new project or initiative and need to establish clear priorities - During backlog refinement sessions to organize and prioritize feature requests - When facing resource constraints and need to make tough decisions about scope - In stakeholder meetings to align expectations about deliverables and timelines ## Tips and tricks - Limit 'Must' items to no more than 60% of total requirements to maintain realistic scope - Review and revise categorizations periodically as business needs and constraints change - Use timeboxing during discussions to ensure efficient decision-making - Document the reasoning behind categorizations to maintain clarity and consistency - Involve all key stakeholders in the prioritization process to ensure buy-in - Consider dependencies between items when assigning categories ## Icebreaker questions - What's the most difficult priority decision you've had to make in a project? - If you could only deliver three features in your current project, what would they be and why? --- # Big Bang Blast Retrospective URL: https://www.teamretro.com/retrospective-templates/big-bang-blast-retrospective/ Big Bang Blast brings a cosmic, high-energy theme to your team's reflection, turning the usual retrospective into a celebration of explosive momentum and stellar discovery. Inspired by the origins of the universe, this format invites teams to explore the spark that ignited their work, the forces that propelled them forward, the debris that slowed them down, and the new galaxies they want to reach. It's a fun, metaphor-rich way to keep engagement high while still surfacing meaningful, actionable insights. The retrospective works by guiding participants through four themed topics that map to a natural narrative arc — from the initial energy and breakthroughs, through the obstacles and friction, to the bold ambitions ahead. By framing reflection around a memorable theme, teams overcome retrospective fatigue and feel more comfortable sharing candid feedback. The playful structure encourages creativity, helps quieter voices contribute, and makes patterns easier to spot when conversations get organized into clear cosmic categories. Ideal for agile teams, product squads, and project groups looking to break out of routine, the Big Bang Blast retrospective is especially effective after a major launch, milestone, or intense delivery period. It balances celebration with critical reflection, ensuring the team recognizes its achievements while still committing to concrete improvements. Run it in TeamRetro to capture ideas, vote on priorities, and turn insights into trackable action items. ## Topics - **The Spark**: What ignited momentum and got things moving? - **Expanding Forces**: What propelled us forward and helped us grow? - **Cosmic Debris**: What slowed us down or created friction? - **New Galaxies**: What bold ideas or improvements do we want to reach for? ## When to use - After a major product launch, milestone, or release when the team wants to celebrate momentum while reviewing what to improve. - When standard retrospective formats feel stale and you want a fun, themed approach to re-energize the team. - Following an intense or high-pressure delivery period that deserves both recognition and reflection. - At the start of a new quarter or initiative to capture lessons and set bold ambitions for what's ahead. ## Tips and tricks - Set the scene with the cosmic theme up front so everyone understands the metaphor and feels free to be playful. - Timebox each topic to keep energy high and prevent any single discussion from dominating the session. - Use anonymous idea entry to encourage candid feedback, especially around the 'Cosmic Debris' obstacles. - Vote on ideas in 'New Galaxies' to focus on the highest-impact improvements rather than trying to do everything. - Convert top-voted items into clear, owned action items with due dates so insights lead to real change. - Balance celebration and critique — make sure the team genuinely recognizes wins before diving into problems. ## Icebreaker questions - If your sprint were a celestial event, would it be a supernova, a meteor shower, or a quiet orbit — and why? - If you could name a star after one team achievement this cycle, what would the star be called? --- # SLA Compliance Retrospective URL: https://www.teamretro.com/retrospective-templates/sla-compliance-retrospective/ The SLA Compliance Retrospective is a focused meeting for teams to review their performance against agreed service level agreements (SLAs) and identify areas for improvement. It provides a structured format to analyze metrics, discuss challenges, and develop actionable steps to enhance service delivery and customer satisfaction. This retrospective is particularly valuable for teams in industries with strict SLA requirements, such as IT services, customer support, logistics, and healthcare. By regularly evaluating SLA compliance, teams can proactively address issues, streamline processes, and maintain high standards of service quality. The retrospective format encourages open dialogue, fosters a continuous improvement mindset, and aligns team efforts towards meeting or exceeding SLA targets. It can be customized to suit specific team needs and SLA parameters. ## Topics - **SLA Metrics Review**: How did we perform against our SLA targets? - **SLA Challenges**: What factors impacted our ability to meet SLAs? - **Improvement Opportunities**: How can we enhance our SLA performance? - **Cross-Team Collaboration**: How can we foster better collaboration for SLA success? ## When to use - When your team is responsible for delivering services with defined SLA targets. - To proactively identify and address factors impacting SLA compliance. - To foster a culture of continuous improvement and customer-centric service delivery. - To align cross-functional teams and enhance collaboration for meeting SLA commitments. - After a significant SLA breach or customer escalation to review root causes and preventive measures. ## Tips and tricks - Ensure you have access to accurate and up-to-date SLA performance data to facilitate an objective review. - Encourage open and blameless discussions, focusing on process improvements rather than individual accountability. - Involve stakeholders from different teams impacted by SLA delivery to gain diverse perspectives. - Prioritize actionable improvements that can be realistically implemented within the team's control. - Assign clear owners and timelines for agreed-upon action items to ensure follow-through. - Schedule regular SLA compliance retrospectives to maintain a continuous improvement cycle. ## Icebreaker questions - If you could create a new SLA for our team, what would it be and why? - Share a memorable experience (positive or negative) related to SLA compliance from your career. --- # Pipeline Management Retrospective URL: https://www.teamretro.com/retrospective-templates/pipeline-management-retrospective/ A Pipeline Management Retrospective is a structured meeting for teams to reflect on their pipeline processes, identify areas for improvement, and develop actionable strategies to streamline workflows and enhance overall productivity. By fostering open communication and collaboration, this retrospective empowers teams to optimize their pipeline management, leading to increased efficiency, better resource allocation, and ultimately, greater business impact. This retrospective draws inspiration from agile methodologies and lean principles, encouraging teams to continuously evaluate and refine their pipeline practices. Through facilitated discussions and interactive activities, participants gain valuable insights into bottlenecks, redundancies, and opportunities for automation or process simplification. By embracing a culture of continuous improvement, teams can proactively address pipeline challenges, foster cross-functional alignment, and cultivate a shared understanding of pipeline priorities and goals. The Pipeline Management Retrospective serves as a powerful tool for driving positive change, enabling teams to adapt swiftly to evolving market demands and stay ahead of the competition. ## Topics - **Pipeline Bottlenecks**: What pipeline stages or processes caused delays or created bottlenecks? - **Pipeline Streamlining**: How can we streamline our pipeline processes for better efficiency? - **Pipeline Roadblocks**: What external or internal factors hindered our pipeline progress? - **Pipeline Collaboration**: How can we foster better collaboration and alignment across pipeline stages? ## When to use - When your team is experiencing recurring pipeline bottlenecks or inefficiencies. - After a major pipeline process change or implementation of new tools or methodologies. - As part of a regular cadence (e.g., quarterly or bi-annually) to continuously improve pipeline management. - When onboarding new team members or restructuring teams involved in pipeline management. - When pipeline performance metrics or forecasting accuracy are not meeting expectations. ## Tips and tricks - Encourage open and honest feedback by creating a safe and judgment-free environment. - Involve cross-functional stakeholders from different pipeline stages to gain diverse perspectives. - Use data and metrics to support observations and identify areas for improvement objectively. - Prioritize actionable solutions and develop a clear implementation plan with assigned responsibilities. - Foster a culture of continuous improvement by scheduling regular pipeline retrospectives. - Celebrate small wins and successes along the way to maintain momentum and engagement. ## Icebreaker questions - If our pipeline was a famous movie, which one would it be and why? - If you could add one superpower to our pipeline management process, what would it be? --- # The Hero's Journey Retrospective URL: https://www.teamretro.com/retrospective-templates/the-heros-journey-retrospective/ The Hero's Journey retrospective transforms your team's experiences into an engaging narrative framework inspired by Joseph Campbell's monomyth structure. This innovative approach helps teams reflect on their work through the lens of an epic adventure, making the retrospective both fun and insightful. By casting team members as heroes on a quest, this format naturally surfaces challenges, support systems, and achievements in a way that resonates with human storytelling instincts. It encourages teams to think holistically about their journey, identifying not just what happened, but the resources, support, and opportunities that influenced their path. This template is particularly effective for long-term projects or significant organizational changes, as it helps teams recognize their growth, acknowledge their supporters, and prepare for future challenges. It creates a safe space for honest reflection while maintaining an optimistic, forward-looking perspective. ## Topics - **Hero**: The person or group going through the journey - **Quest**: The challenges ahead - **Guide**: The people supporting the hero - **Inventory**: The tools and resources available - **Treasure**: The rewards and achievements that await ## When to use - When starting a significant new project or initiative that will require sustained team effort - After completing a major milestone to reflect on the journey and prepare for the next challenge - When team morale needs a boost and you want to frame challenges as opportunities - During times of organizational change to help teams navigate uncertainty with a positive mindset ## Tips and tricks - Encourage storytelling and metaphors to help team members express challenges in a non-confrontational way - Use visual aids like journey maps or story boards to help teams visualize their progress and challenges - Ensure everyone contributes to each topic - heroes often emerge from unexpected places - Keep the tone positive and forward-looking, focusing on growth and opportunity rather than blame - Document the journey visually to create a compelling narrative that can inspire future efforts - Set aside adequate time for reflection and discussion - rushing through the story diminishes its impact ## Icebreaker questions - If you could choose any fictional character as a mentor for our team, who would it be and why? - What's the most epic 'quest' you've completed in your professional life so far? --- # Code Review Retrospective URL: https://www.teamretro.com/retrospective-templates/code-review-retrospective/ A code review retrospective is a structured meeting where development teams reflect on their code review practices. It helps identify areas for improvement, share best practices, and foster a culture of continuous learning. During the retrospective, team members discuss what went well, what didn't, and gather insights to streamline the code review process. This collaborative approach leads to higher code quality, knowledge sharing, and better team dynamics. The code review retrospective format originated from agile methodologies but can benefit any software team committed to delivering high-quality, maintainable code. ## Topics - **What is going well?**: What aspects of our code reviews are working effectively? - **What isn't going well?**: What challenges or pain points did we face during code reviews? - **What can we improve?**: How can we enhance our code review process and practices? - **What questions have surfaced?**: What new questions or areas for further exploration emerged? ## When to use - To identify areas for improvement in your team's code review process. - To share best practices and learn from each other's experiences. - To foster a culture of continuous learning and quality improvement. - After major releases or projects to reflect on the development process. - To align the team on review standards, expectations, and workflows. ## Tips and tricks - Encourage an open and blame-free environment for honest feedback. - Celebrate successes and recognize positive contributions. - Involve the entire team, including developers, testers, and reviewers. - Prioritize actionable improvements over lengthy discussions. - Follow up on action items and track progress in subsequent retrospectives. - Consider rotating the facilitator role to maintain fresh perspectives. ## Icebreaker questions - What's the most interesting or innovative code you've reviewed recently? - If you could add one feature to your code editor, what would it be? --- # Blogger Day Retrospective URL: https://www.teamretro.com/retrospective-templates/blogger-day-retrospective/ Blogger Day is a reflective session designed to bring writers, content creators and community members together to celebrate their craft and shape the road ahead. Whether you run a personal blog, contribute to a shared publication or manage a content team, this format gives everyone space to look back at what they've published, share lessons learned and reconnect with the purpose behind their words. Built around four guiding themes, the retrospective walks participants through what resonated with readers, where they hit creative or technical roadblocks, the ideas bubbling up for future posts, and how the community supported one another along the way. By gathering these perspectives in one place, contributors gain a clearer picture of their collective voice, can rally around shared goals, and leave with concrete next steps for the content calendar. The value of Blogger Day lies in turning scattered individual experiences into shared learning. It encourages honest reflection, sparks fresh ideas, and strengthens the bonds that keep a blogging community thriving. Use it at the end of a campaign, a publishing season, or simply as a regular check-in to keep momentum high and creativity flowing. ## Topics - **What resonated**: Which posts or moments connected best with readers? - **What got in the way**: What blocked you from writing or publishing well? - **Fresh ideas**: What new topics or formats should we try next? - **Community support**: How did we help and lift each other up? ## When to use - At the end of a publishing campaign or content season to review what worked and what didn't. - As a recurring check-in for a blogging community or content team to keep ideas and morale fresh. - After a collaborative project or guest series to capture lessons and celebrate contributors. - When planning a new content calendar and you want fresh, community-sourced ideas. ## Tips and tricks - Pull in actual metrics or reader comments beforehand so reflections are grounded in real signals, not just gut feel. - Keep the 'what got in the way' discussion focused on obstacles and processes rather than individual blame. - Time-box the fresh ideas brainstorm to keep energy high, then group and vote on the most promising ones. - Make sure quieter contributors get airtime — invite written input in TeamRetro before opening group discussion. - Close the session by turning the best ideas into concrete actions with owners and dates on the content calendar. - Celebrate wins out loud; recognition is one of the biggest drivers of long-term blogging motivation. ## Icebreaker questions - If your blog had a theme song, what would it be and why? - What's the one post you've written that you're secretly most proud of? --- # Lightning Retrospective URL: https://www.teamretro.com/retrospective-templates/lighting-quick-retrospective/ Charge up your sprint with the energy of a lightning storm! The Lightning Retrospective is a fast-paced, high-energy format designed to help agile teams quickly reflect on what sparked progress, what needs grounding, and how to channel their collective power for even brighter results. Inspired by the raw force of a thunderstorm, this retrospective uses vivid electrical metaphors to make reflection feel dynamic, memorable, and genuinely fun — perfect for teams who want to keep momentum without getting bogged down in lengthy meetings. The format guides teams through four energising topics: what sparked progress (the lightning bolts of success), what created friction or resistance (the thunder that slowed things down), what needs grounding (risks or issues that need to be safely managed), and how to amplify the team's energy going forward (the power surge of improvement actions). Each topic is designed to be quick and punchy, encouraging concise, honest contributions from every team member. The result is a focused, action-oriented session that leaves the team feeling energised and aligned. The Lightning Retrospective is ideal for teams running short sprints, those who feel their retrospectives have become stale, or any group looking to inject some creative energy into their continuous improvement practice. Whether you're a seasoned Scrum Master or a team lead exploring agile retrospective formats for the first time, this template delivers a structured yet exciting way to reflect, learn, and grow together — fast. ## Topics - **Lightning Bolts**: What sparked energy and drove progress this sprint? - **Thunder Clouds **: What created noise, friction, or slowed the team down? - **Power Surge**: How can we amplify our energy and supercharge the next sprint? ## When to use - When your team's retrospectives have started to feel repetitive or low-energy and you want to inject fresh momentum into the continuous improvement process. - When running a short sprint or a time-pressured iteration and you need a retrospective format that delivers real insights without taking up too much time. - When a team has recently faced a high-intensity period of work and you want a format that matches their energy and helps them process both the highs and the lows. - When onboarding a new team to agile retrospectives and you want a format that's engaging, easy to understand, and memorable thanks to its vivid metaphors. - When you want to balance celebrating wins, addressing friction, managing risks, and planning improvements all within a single focused session. ## Tips and tricks - Keep it fast and focused — the Lightning Retrospective is designed to be energetic and time-boxed. Aim for 45–60 minutes total and use a timer to keep each topic moving. Resist the urge to deep-dive on every point; save detailed discussions for dedicated problem-solving sessions. - Encourage everyone to contribute before the discussion begins. Having all team members add their ideas independently first helps surface diverse perspectives and prevents the loudest voices from dominating the conversation. - Don't let the Power Surge topic become a wishlist. Help the team narrow down to one or two concrete, actionable improvements with clear owners and a timeline. Unowned actions rarely get done. - Watch out for the Thunder Clouds topic becoming a venting session. Acknowledge frustrations, but gently redirect the conversation toward understanding root causes and identifying what the team can actually control or change. - Use the Ground Wires topic to surface issues that might otherwise stay hidden. Psychological safety is key here — remind the team that raising a risk early is a sign of strength, not weakness. - Revisit the actions from your last Lightning Retrospective at the start of the session. Celebrating completed actions and acknowledging incomplete ones builds accountability and shows the team that retrospectives lead to real change. ## Icebreaker questions - If your energy this sprint were a weather event, what would it be and why? - If you could harness the power of lightning for one superpower at work, what would it be? --- # The Telephone Game Retrospective URL: https://www.teamretro.com/retrospective-templates/the-telephone-game-retrospective/ Inspired by the classic children's game where a whispered phrase morphs into something unrecognizable by the time it reaches the last person, The Telephone Game Retrospective turns that playful idea into a powerful lens for examining how information travels through your team. Communication breakdowns are at the heart of many project hiccups, and this format helps surface where messages get distorted, lost, or reinterpreted between people, teams, and tools. During the session, your team explores the journey of information across a sprint or project. You'll trace how requirements, decisions, and updates were originally communicated, how they were received and understood, and where the gaps appeared along the way. By mapping these moments, you'll uncover the systemic causes of miscommunication rather than placing blame on individuals. The real value lies in turning fuzzy frustrations into concrete improvements. Teams walk away with a clearer picture of their communication channels, agreed-upon practices for sharing information more reliably, and a renewed appreciation for clarity. It's an engaging, lighthearted way to tackle a serious topic, making it ideal for distributed and cross-functional teams who depend on accurate handoffs every day. ## Topics - **The Original Message**: What was clearly and effectively communicated from the start? - **Lost in Translation**: Where did the message get distorted, lost, or misunderstood? - **The Source of the Static**: What caused the breakdowns in how information traveled? - **Clearing the Line**: How can we make our communication clearer and more reliable? ## When to use - When recurring misunderstandings or rework suggest communication is breaking down across the team. - After a project with multiple handoffs between people, teams, or tools, to trace where clarity was lost. - For distributed or cross-functional teams who rely heavily on async and written communication. - When onboarding new team members highlights gaps in how knowledge is shared and documented. - To lighten the mood while tackling a serious topic, using a playful format to spark honest reflection. ## Tips and tricks - Keep the conversation focused on systems and handoffs rather than individuals to avoid blame. - Trace a real example of a message that got distorted to ground the discussion in a concrete story. - Invite people from different roles and teams so you capture every point along the information chain. - Timebox each topic to keep momentum, especially when surfacing the source of breakdowns. - Prioritise just two or three high-impact improvements so commitments are realistic and trackable. - Revisit the agreed actions at the next retrospective to confirm communication has actually improved. ## Icebreaker questions - What's the funniest miscommunication you've ever been part of, at work or in life? - If your team's communication were a phone signal, how many bars would it have today? --- # Sailboat Retrospective URL: https://www.teamretro.com/retrospective-templates/sailboat-retrospective/ The Sailboat Retrospective uses a powerful maritime metaphor to help teams reflect on their progress and challenges. In this retrospective, the team's journey is represented by a sailboat navigating through waters. The wind represents helping forces, while anchors symbolize obstacles. Rocks represent risks ahead, and the sun represents positive elements keeping team morale high. The destination represents the team's goals. This visual approach makes it particularly effective for teams who prefer metaphorical thinking or want to break away from traditional retrospective formats. It helps teams identify both opportunities and challenges while maintaining a clear focus on their objectives. ## Topics - **Goal**: What are we working towards? - **Wind**: What is pushing us forward? - **Anchor**: What is holding us back? - **Rocks**: What risks do we face? - **Sun**: What is making us feel good? ## When to use - When you want to make retrospectives more engaging and visual for teams that might be experiencing retrospective fatigue - During project milestones or quarterly reviews to assess progress and plan ahead - When teams need to balance discussing both opportunities and challenges in a structured way - For teams that are new to retrospectives and need a clear, metaphorical framework to guide their discussions ## Tips and tricks - Start by explaining the metaphor clearly and ensure everyone understands what each element represents - Use the visual nature of the exercise to create a collaborative diagram during the session - Keep a balance between discussing problems (anchors/rocks) and opportunities (wind/sun) - Encourage quiet team members to contribute by going around the room for each element - End the session by prioritizing actions based on impact and feasibility - Consider using breakout rooms for larger teams to ensure everyone gets a chance to contribute ## Icebreaker questions - If your current project was a type of boat, what would it be and why? - What's your favorite memory of being near water (ocean, lake, river)? --- # Yellowstone Expedition Retrospective URL: https://www.teamretro.com/retrospective-templates/yellowstone-expedition-retrospective/ Embark on a guided journey through your team's recent work, framed as a wild expedition across the rugged landscapes of Yellowstone. Inspired by the spirit of exploration, this themed retrospective invites teams to reflect on the geysers of success, the bears they encountered along the trail, the breathtaking vistas worth celebrating, and the uncharted paths ahead. By mapping experiences to a memorable adventure, participants engage more deeply and recall insights more easily than in a traditional review. The Yellowstone Expedition works by guiding your team through four exploration-themed prompts that mirror the highs, hazards, and horizons of any sprint or project cycle. Each "landmark" on the map represents a different lens for reflection — from steady progress to unexpected dangers, from proud achievements to future goals. This narrative structure lowers defensiveness, encourages honest dialogue, and turns a routine meeting into a shared story that the whole team helps write. Themed retrospectives like this are an excellent way to break monotony, boost participation, and surface insights that more clinical formats might miss. Whether you run them quarterly to mix things up or as a special end-of-project celebration, the Yellowstone Expedition helps teams build trust, celebrate wins, and chart a clear course forward — all while having a little fun along the way. ## Topics - **Geysers (What erupted with success?)**: What went brilliantly and gushed with energy? - **Bears (What hazards did we face?)**: What dangers, blockers, or risks crossed our path? - **Vistas (What views are worth celebrating?)**: What achievements or moments deserve recognition? - **Horizons (Where do we head next?)**: What goals or actions should guide our next trek? ## When to use - When your team needs a refreshing change from standard sprint retrospectives and you want to re-energise participation. - At the end of a major project or milestone, where an expedition theme helps frame the whole journey and celebrate the summit. - When team morale could use a boost and you want a lighthearted yet meaningful way to surface both wins and challenges. - For teams that respond well to storytelling and metaphor, helping less vocal members open up through a playful frame. ## Tips and tricks - Set the scene at the start by briefly narrating the expedition theme — it primes the team to engage with the metaphor and have fun. - Encourage equal airtime across all four landmarks so the session doesn't dwell only on bears (problems) or only on geysers (wins). - Keep facilitation blame-free, especially around the Bears topic — focus on situations and systems rather than individuals. - Time-box each landmark to keep the expedition moving and ensure you reach the Horizons (actions) before time runs out. - Always convert Horizons discussions into clearly owned, specific action items so insights translate into real change. - Use anonymous contributions if trust is still building, so quieter explorers feel safe sharing hazards and honest feedback. ## Icebreaker questions - If you could explore any national park or wilderness in the world, where would you trek and why? - What's the one item you'd never leave behind on an expedition into the wild? --- # Agile Center of Excellence Retrospective URL: https://www.teamretro.com/retrospective-templates/agile-center-of-excellence-retrospective/ An Agile Center of Excellence (ACoE) brings together coaches, Scrum Masters, agile leaders, and practitioners to continuously improve how agility is practiced across an organization. This retrospective gives that community a structured space to reflect on the standards, coaching practices, and enablement efforts they champion — surfacing what is genuinely driving agile maturity and what is creating friction for the teams they support. Built for cross-team and program-level reflection, it moves the conversation beyond a single sprint. Participants examine the value the center is delivering, evaluate the consistency and adoption of agile practices, identify the organizational impediments that no individual team can solve alone, and align on the next set of improvement experiments. By focusing on systemic patterns rather than isolated events, the ACoE can prioritize the changes that ripple out to many teams at once. The result is a shared, prioritized improvement backlog and a renewed sense of purpose for the agile community. Whether you run it quarterly, after a major program increment, or as part of a community-of-practice cadence, this format helps an Agile Center of Excellence stay relevant, measure its impact, and keep championing meaningful change. Learn more about communities of practice and centers of excellence as part of scaling agile frameworks such as SAFe. ## Topics - **Value We're Delivering**: What impact is the center having on teams? - **Practices to Refine**: Which agile practices need more consistency or rethinking? - **Organizational Impediments**: What systemic blockers sit beyond any single team? - **Improvement Experiments**: What should we try next to grow agile maturity? ## When to use - Quarterly or after a major program increment, when your agile community wants to assess its collective impact and reset priorities. - When agile practices have started to drift or feel inconsistent across multiple teams and you need to realign on standards. - When recurring impediments span several teams and require systemic, organization-level solutions rather than local fixes. - As a regular cadence for a community of practice or center of excellence to stay relevant and demonstrate value to leadership. - During an agile transformation, to track maturity, capture lessons, and plan the next wave of enablement. ## Tips and tricks - Keep the focus on systemic, cross-team patterns rather than diving into the details of any single team's sprint — that's what makes this retrospective valuable at the center level. - Invite a mix of voices: coaches, Scrum Masters, agile leaders, and a few practitioners from the teams you support, so insights aren't filtered only through the community's own perspective. - Back impediments and value claims with evidence or examples where possible; data on adoption or maturity makes escalations far more persuasive to leadership. - Limit the number of improvement experiments you commit to so the center can actually deliver them and measure the outcomes next cycle. - Watch for the echo chamber effect — agile enthusiasts can over-celebrate practices that teams quietly find burdensome, so actively seek dissenting views. - Assign a clear owner and a success signal to every action so the next retrospective can review real progress rather than reopening the same discussions. ## Icebreaker questions - If our Agile Center of Excellence were a superhero, what would its superpower be? - What's one agile myth you wish you could permanently retire across the organization? --- # FIFA World Cup Retrospective URL: https://www.teamretro.com/retrospective-templates/fifa-world-cup-retrospective/ Kick off your next team reflection with the energy of the world's biggest sporting tournament. The FIFA World Cup Retrospective borrows the language of the beautiful game to help teams celebrate their goals, review near misses, and strategise for the next match. By framing your sprint or project as a football fixture, you create a playful yet purposeful space where everyone feels like part of the squad working toward a shared trophy. The format works by guiding the team through familiar football moments — the goals scored, the shots that went wide, the fouls and yellow cards that slowed momentum, and the game plan for the next match. Each topic invites participants to share what they are proud of, where opportunities were lost, what created friction, and how the team can level up. This metaphor lowers the barrier to honest conversation while keeping the mood upbeat and collaborative, making it ideal for teams who enjoy a themed twist on their regular cadence. Whether you run it during an actual World Cup season or simply want to inject some fresh energy into a recurring retrospective, this template helps surface actionable insights while building team spirit. In TeamRetro, you can collect ideas, group similar themes, vote on priorities, and turn the strongest plays into clear action items — ensuring your team walks off the pitch with a winning strategy for the next round. ## Topics - **Goals Scored**: What wins and achievements should we celebrate? - **Missed Shots**: What opportunities did we let slip away? - **Fouls & Yellow Cards**: What slowed us down or caused friction? - **Game Plan**: What's our strategy for the next match? ## When to use - During a World Cup or major football tournament season when you want a themed, energising twist on your usual retrospective. - When team morale needs a lift and you want to celebrate wins while still tackling real improvement areas. - At the end of a sprint, project, or quarter to review performance using an engaging, accessible metaphor. - For teams new to retrospectives who benefit from a playful framing that lowers the barrier to honest sharing. - When you want to balance celebration, reflection, and forward planning in a single fast-paced session. ## Tips and tricks - Set the tone early by leaning into the football theme — it keeps energy high and makes honest feedback feel safe and fun. - Time-box each topic so the conversation flows like a match with clear halves rather than dragging into extra time. - Encourage quieter team members to take their shot by inviting contributions directly and anonymously where helpful. - Keep the 'Fouls & Yellow Cards' topic focused on situations and processes, not individuals, to avoid blame. - Use dot voting to prioritise the most important plays before agreeing on your game plan, so action items stay focused. - Close by assigning clear owners to each game plan action so commitments don't get left on the bench. ## Icebreaker questions - If our team were a national football team, what would our team chant be? - Which World Cup moment best describes how our last sprint felt? --- # Fiscal Year-End Review URL: https://www.teamretro.com/retrospective-templates/fiscal-year-end-review/ The Fiscal Year-End Review is a structured meeting to reflect on the past year's financial performance, celebrate successes, identify areas for improvement, and align on strategies for the upcoming fiscal year. This retrospective allows teams to analyze revenue, expenses, budgets, and key initiatives through a financial lens. The primary goals are to assess progress against targets, uncover insights to inform future planning, and build consensus on priorities for the new fiscal year. Participants review metrics, discuss challenges and wins, and develop action plans to optimize spending, drive growth, and improve profitability. By taking a comprehensive look back, teams can make data-driven adjustments to their financial strategies. This collaborative process promotes accountability, cross-functional alignment, and a shared vision for strong fiscal health. ## Topics - **Revenue Analysis**: How did our revenue performance compare to targets? - **Expense Management**: How well did we control and optimize expenses? - **Strategic Initiatives**: What major initiatives drove (or hindered) our performance? - **Strategic Outlook**: How should we adjust our financial strategy for the upcoming year? ## When to use - At the end of each fiscal year to review performance and plan for the upcoming year. - When preparing annual budgets, financial projections, and strategic growth plans. - After major business events (e.g. acquisitions, funding rounds) to reassess financial strategy. - If financial performance deviates significantly from targets to identify course corrections. ## Tips and tricks - Encourage data-driven discussions by sharing relevant reports and metrics ahead of time. - Promote a blameless environment to have open and honest dialogues about misses. - Ensure all relevant stakeholders are present (finance, sales, marketing, product, etc.). - Build in time for strategic discussions beyond just reviewing the past year's results. - Assign owners and due dates for any major action items coming out of the retrospective. - Consider breaking into smaller groups for more in-depth analysis of specific areas. ## Icebreaker questions - If our company was a publicly traded stock, would you buy, sell or hold? Why? - What's one financial metric or KPI you wish we tracked more closely? --- # Speed Car Retrospective URL: https://www.teamretro.com/retrospective-templates/speed-car-retrospective/ The Speed Car retrospective uses racing metaphors to help teams evaluate their performance and identify areas for improvement. Drawing inspiration from Formula 1 racing teams, this format encourages participants to think about their work in terms of what propels them forward (Engines), what holds them back (Brakes), and who supports their success (Pit Crew). This engaging approach helps teams analyze their velocity and collaboration patterns while maintaining a fun, high-energy atmosphere. By focusing on these three key areas, teams can better understand their dynamics and make targeted improvements to enhance their performance. Particularly effective for fast-paced environments, this retrospective format helps teams identify both technical and interpersonal factors affecting their speed and efficiency. ## Topics - **Engines**: What is driving us forward? - **Brakes**: What is slowing us down? - **Pit Crew**: Who is supporting us? ## When to use - When you want to energize a team that feels stuck or moving slowly - After completing a fast-paced project to analyze what contributed to speed or caused delays - When the team needs to identify and optimize their support systems - When you want a fresh, engaging way to discuss team performance and velocity ## Tips and tricks - Use racing terminology throughout the session to maintain the theme and energy - Encourage participants to think about both technical and human factors in each category - Keep a balance between identifying problems and celebrating successes - Focus on actionable improvements that can be implemented in the next sprint - Consider using racing sound effects or visuals to make the session more engaging - Set a pace for discussions to ensure all three areas get adequate attention ## Icebreaker questions - If your team were a race car, what type would it be and why? - What's your favorite pit stop moment - a time when someone helped you overcome a challenge? --- # Captain Planet Team-Up Retrospective URL: https://www.teamretro.com/retrospective-templates/captain-planet-team-up-retrospective/ Inspired by the iconic 90s cartoon where five young heroes combine their elemental rings to summon Captain Planet, the Captain Planet Team-Up retrospective invites your team to reflect through the lens of Earth, Fire, Wind, Water, and Heart. Each element represents a different dimension of how your team works together, helping you uncover strengths, surface friction, and rally around a shared mission. It's a fun, themed format that brings energy and metaphor to your reflection while still driving meaningful, actionable outcomes. The format works by mapping each elemental power to a focus area: Earth grounds you in what's stable and working, Fire highlights the passion and energy (or burnout) in the team, Wind captures the ideas and changes blowing through, Water explores what's flowing smoothly or where things feel stuck, and Heart centers on team morale, connection, and collaboration. By moving through each element in TeamRetro, participants contribute reflections, group similar themes, vote on what matters most, and turn insights into concrete actions. This playful yet purposeful retrospective is ideal for teams that want to break out of the standard "what went well / what didn't" routine and inject some creativity into their reflection practice. It encourages holistic thinking, ensures emotional and relational health gets equal billing alongside delivery, and ends with the team "summoning" their collective power to commit to improvements. The power, after all, is yours. ## Topics - **Earth: What's Solid**: What stable foundations are supporting the team? - **Fire: Energy & Passion**: Where is energy high, and where is burnout creeping in? - **Wind: Ideas & Change**: What new ideas or changes are blowing through the team? - **Water: Flow & Blockers**: What's flowing smoothly and what's getting stuck? - **Heart: Team & Morale**: How connected, supported, and motivated does the team feel? ## When to use - When your team is in a routine rut and needs a fun, themed format to re-energize reflection. - When you want to balance delivery topics with team morale, energy, and emotional health. - After an intense or high-pressure sprint where burnout and motivation need a check-in. - When onboarding a creative or playful team culture that responds well to metaphor and storytelling. - As a quarterly or milestone retrospective where you want a holistic view across multiple dimensions. ## Tips and tricks - Set the scene by briefly introducing the five elements so everyone understands what each represents before contributing. - Encourage participants to add to every element, not just the ones that feel obvious, to get a balanced picture. - Give equal weight to the Heart topic, morale and connection often reveal the root causes behind delivery issues. - Use dot voting to prioritize themes across elements so the team focuses on the highest-impact actions. - Keep the tone light and lean into the theme, but make sure every insight converts into a clear, owned action item. - Timebox each element to keep momentum and avoid spending all your energy on the first one or two powers. ## Icebreaker questions - If you could have one of Captain Planet's elemental powers (Earth, Fire, Wind, Water, or Heart), which would you choose and why? - Which fictional team or duo do you think has the best 'combining powers' chemistry? --- # KALM Retrospective URL: https://www.teamretro.com/retrospective-templates/kalm-retrospective/ The KALM retrospective is a structured approach that helps teams reflect on their work practices through four key dimensions: Keep, Add, Less, and More. This format encourages teams to maintain effective practices while identifying areas for improvement and optimization. Unlike traditional start-stop-continue formats, KALM provides more nuanced options for change by separating increase and decrease decisions from binary choices. This allows teams to fine-tune their processes rather than making dramatic changes. This retrospective format is particularly effective for teams seeking gradual, sustainable improvements. By focusing on what to keep and adjust, rather than what to completely eliminate, KALM promotes a more positive and constructive dialogue about team practices. ## Topics - **Keep**: What should we keep doing? - **Add**: What should we start doing? - **Less**: What should we do less of? - **More**: What should we do more of? ## When to use - When you want to make incremental improvements rather than dramatic changes - During periods of stable team performance where fine-tuning is more appropriate than major overhauls - When the team needs a balanced approach to maintaining good practices while identifying areas for adjustment ## Tips and tricks - Start by reviewing the previous retrospective's action items to maintain continuity - Encourage participants to provide specific examples rather than general statements - Use dot voting to prioritize items if you receive many suggestions - Keep the focus on actionable improvements rather than complaints - Ensure each category gets equal attention during the discussion - End the session by creating concrete action items for the highest-priority items ## Icebreaker questions - What's one small change you made recently that had a positive impact? - If you could instantly master one new skill that would help the team, what would it be? --- # Dark Souls Bonfire Retrospective URL: https://www.teamretro.com/retrospective-templates/dark-souls-bonfire-retrospective/ Inspired by the iconic bonfires of FromSoftware's Dark Souls, the Bonfire Retrospective is a themed reflection where your team gathers around the warm glow of a checkpoint to recover, share hard-won lessons, and prepare for the challenges ahead. Just as players rest at a bonfire to restore their flask and plan their next attempt at a brutal boss, your team pauses to celebrate progress, name the tough encounters, and chart a smarter path forward. The format works by guiding your team through familiar Soulsborne moments: the relief of reaching a bonfire (wins), the bosses that tested you (challenges), the "you died" moments worth learning from (failures and lessons), and the upgrades and souls you'll carry into the next run (improvements and goals). It transforms the often dry retrospective into an engaging, narrative-driven session that lowers defensiveness and encourages honest reflection — because in Dark Souls, dying is simply part of getting better. Perfect for gaming-enthusiast teams or anyone looking for a fresh, memorable retrospective theme, this format helps build psychological safety, reinforce a growth mindset, and turn setbacks into actionable next steps. Run it in TeamRetro to capture every insight, vote on the toughest "bosses," and emerge from the fog wall ready to praise the sun. ## Topics - **Bonfires Lit**: What wins and milestones did we reach this sprint? - **Bosses We Fought**: What major challenges or obstacles tested the team? - **You Died — Lessons Learned**: Where did we fail, and what did those deaths teach us? - **Souls & Upgrades**: What improvements and actions will we carry into the next run? ## When to use - Your team enjoys gaming culture and you want a fun, themed retrospective that boosts engagement and attendance. - Morale has dipped after a tough sprint full of setbacks, and you want to reframe failures as lessons in a safe, lighthearted way. - You want to break the monotony of standard start-stop-continue retros with a fresh narrative format. - The team has faced one or more major obstacles ('bosses') and needs to debrief and build a strategy to overcome them. - You're fostering a growth mindset and want a format that normalises learning from failure. ## Tips and tricks - Set the mood early — share a bonfire image or play ambient Dark Souls music in the background to ease the team into the theme. - Keep the 'You Died' topic strictly blame-free; remind everyone the goal is shared learning, not pointing fingers. - Timebox each topic so the boss discussions don't consume the whole session — aim for 8-10 minutes per area. - Use grouping and voting in TeamRetro to identify the toughest 'boss' worth tackling first. - Always convert 'Souls & Upgrades' into assigned, trackable action items so improvements actually get equipped. - Invite quieter teammates explicitly — even a small bonfire counts, and every perspective makes the next run stronger. ## Icebreaker questions - If your past sprint were a Dark Souls boss, what would its name and signature attack be? - What's the one 'bonfire' moment recently that made you breathe a sigh of relief? --- # Road Trip Retrospective URL: https://www.teamretro.com/retrospective-templates/road-trip-retrospective/ Buckle up and reflect on your team's journey with the Road Trip Retrospective, a playful yet powerful way to review where you've been and chart where you're headed next. By framing your sprint or project as a road trip, this format turns abstract progress into a vivid, shared adventure—complete with smooth highways, unexpected potholes, scenic detours, and the fuel that keeps everyone moving forward. The Road Trip Retrospective works by guiding your team through four travel-inspired themes: the smooth roads you cruised along, the bumps and roadblocks that slowed you down, the fuel and resources that energized the team, and the destination you're aiming for next. This metaphor lowers the barrier to honest conversation, making it easier for everyone to surface wins, frustrations, and ideas in a relaxed, engaging way. The visual journey helps teams connect the dots between past experiences and future goals. Whether you're wrapping up an agile sprint, closing a major milestone, or simply taking stock as a team, this retrospective creates a memorable space for reflection and planning. It's especially effective for keeping energy high during routine retrospectives and for helping distributed teams build a shared sense of momentum and direction. ## Topics - **Smooth Roads**: What went well and kept us cruising forward? - **Potholes & Roadblocks**: What slowed us down or got in our way? - **Fuel in the Tank**: What energized and kept the team going? - **Next Destination**: Where do we want to head, and how do we get there? ## When to use - At the end of a sprint or iteration when you want a fresh, engaging alternative to a standard retrospective format. - After completing a major project or milestone to reflect on the full journey and plan the next leg. - When team energy feels low and you want a fun metaphor to re-engage people in honest reflection. - For distributed or remote teams who benefit from a shared visual journey to build momentum and alignment. ## Tips and tricks - Set the scene by introducing the road trip metaphor at the start so everyone understands how each lane maps to their experience. - Timebox each topic to keep the journey moving and prevent the conversation from stalling on any single issue. - Encourage quieter team members to share by reminding everyone that every passenger sees a different part of the road. - Group similar ideas together before voting to surface the biggest themes and avoid duplicate discussion. - Turn 'Next Destination' items into clear, owned action items so the retrospective leads to real change. - Rotate the facilitator each session to keep the format fresh and share ownership of the team's journey. ## Icebreaker questions - What's the best road trip snack of all time, and why is it non-negotiable? - If our team's journey this sprint were a type of road, what would it be—highway, dirt track, or scenic route? --- # Team Retreat Planning URL: https://www.teamretro.com/retrospective-templates/team-retreat-planning/ This template provides a framework for teams to collaboratively plan an upcoming retreat. It covers key aspects such as setting goals, designing activities, and fostering team bonding. The prompts encourage open discussion and ensure all voices are heard, leading to a well-rounded retreat that meets the team's needs. Whether you're planning a one-day offsite or a multi-day getaway, this template offers practical guidance to make the most of your team's time together. It's an invaluable tool for strengthening relationships, aligning on priorities, and reigniting passion for your shared mission. ## Topics - **Retreat Goals**: What are the key objectives you hope to achieve during the retreat? - **Agenda Planning**: What types of activities or sessions would help achieve the retreat goals? - **Team Bonding**: How can we create opportunities for genuine connection and relationship building? - **Venue and Logistics**: What factors should we consider when choosing a retreat location and accommodations? ## When to use - When your team is facing significant changes or challenges and needs to realign. - After a period of intense work or high stress, to recharge and reconnect. - When onboarding new team members, to foster integration and build relationships. - Annually or bi-annually, as a regular practice for team development and strategic planning. - When launching a new project or initiative, to ensure alignment and kick things off strong. ## Tips and tricks - Involve the entire team in the planning process to ensure buy-in and diverse perspectives. - Balance structured activities with ample free time for organic conversations and bonding. - Encourage a technology-free environment to promote focus and presence. - Assign roles and responsibilities to ensure smooth execution during the retreat. - Build in time for reflection and capturing key takeaways and action items. - Follow up after the retreat to reinforce learnings and maintain momentum. ## Icebreaker questions - If you could have any superpower, what would it be and why? - What's the most adventurous thing you've ever done? --- # New Team Member Onboarding Retrospective URL: https://www.teamretro.com/retrospective-templates/new-team-member-onboarding-retrospective/ The Team Member Onboarding retrospective is a collaborative exercise to identify and prioritize essential topics for effectively integrating new hires into your team. It covers crucial areas like understanding company culture, role responsibilities, team dynamics, growth opportunities, and more. The goal is to create a comprehensive onboarding plan that ensures a smooth transition, sets clear expectations, and empowers new team members to contribute and succeed from day one. This template encourages open discussion and knowledge sharing among current team members. By tapping into their collective experiences and insights, you can develop a well-rounded onboarding process that addresses both practical and cultural aspects of joining the team. It also allows you to continuously refine and improve the onboarding experience based on feedback and what the teams thinks is important, beyond your standard onboarding checklists and documents. ## Topics - **Company Culture**: What aspects of our company culture should new hires understand? - **Role Responsibilities**: What key duties and expectations should be covered for this role? - **Team Dynamics**: How can we help new hires integrate into the team smoothly? - **Growth and Development**: What opportunities exist for professional growth and skill development? - **Open Discussion**: What other areas should we cover during onboarding? ## When to use - When onboarding new hires to ensure a smooth transition and set them up for success. - As part of regular team-building activities to reinforce company culture and team norms. - After significant team changes or restructuring to realign on roles and responsibilities. - Annually or bi-annually to review and update onboarding processes as needed. ## Tips and tricks - Encourage open and honest feedback from both new and existing team members. - Have team members think back to their first day on the job. - Use the question, what's something you wish someone had told you about the organisation. - Where possible, involve cross-functional stakeholders to provide a wider perspective. - Share the results with the new team member/s and get their feedback or questions. - Consider running this activity as an icebreaker with the new team member, along with the current team. ## Icebreaker questions - If you could pick a new hobby or skill to learn, what would it be and why? - What's the best piece of advice you've ever received, and who gave it to you? --- # Volleyball Retrospective URL: https://www.teamretro.com/retrospective-templates/volleyball-retrospective/ The Volleyball Retrospective uses volleyball game mechanics as metaphors to analyze team performance and collaboration. Drawing parallels between volleyball plays and team dynamics, this engaging format helps teams reflect on their work through a sports lens. Just as volleyball requires coordinated effort, timing, and strategy, this retrospective framework encourages teams to examine their initiatives (serves), resilience (digs), enablers (sets), achievements (spikes), and risk management (blocks). The sports analogy creates an accessible and engaging way to discuss team dynamics and project outcomes. This format is particularly effective for teams who enjoy sports metaphors or need a fresh perspective on their retrospective discussions. It helps identify both tactical improvements and strategic opportunities while maintaining an energetic, game-like atmosphere. ## Topics - **Serves**: What did we start? - **Digs**: What challenges did we reframe? - **Sets**: What set us up for success? - **Spikes**: What winning moves did we make? - **Blocks**: What issues did we prevent? ## When to use - When teams need an energetic and fresh approach to their retrospective discussions - After completing a project phase where different team members played various crucial roles - When you want to emphasize the importance of teamwork and coordination - When the team would benefit from a sports analogy to discuss their work dynamics ## Tips and tricks - Encourage participants to think about both individual and team contributions, just like in volleyball where both personal skill and teamwork matter - Use the volleyball metaphor to maintain an energetic and positive atmosphere throughout the retrospective - Ensure everyone gets a chance to contribute by 'rotating positions' like in volleyball, giving each person time to speak - Keep the momentum going by timeboxing each topic discussion, similar to how volleyball games maintain their pace - Use the sports analogy to discuss failures constructively, focusing on improvement rather than blame ## Icebreaker questions - If our team were a volleyball team, what position would you play and why? - What's your favorite sports moment where teamwork made all the difference? --- # Simply Agile Retrospective URL: https://www.teamretro.com/retrospective-templates/simply-agile-retrospective/ Sometimes the best retrospective is the simplest one. The Simply Agile Retrospective strips away the complexity and gets straight to what matters: reflecting on the work, celebrating progress, and deciding what to change next. It's a lightweight, easy-to-facilitate format that keeps the conversation focused and the energy high, making it perfect for teams that want meaningful outcomes without elaborate frameworks. Built around three straightforward prompts — what worked, what didn't, and what we'll do differently — this agile retrospective format encourages open dialogue and continuous improvement at the end of every sprint or iteration. Each team member shares their honest perspective, the group discusses common themes, and together you turn insights into clear, actionable steps. Because it's so approachable, it works well for new Scrum teams finding their rhythm as well as seasoned agile practitioners who value efficiency. The beauty of running a Simply Agile Retrospective in TeamRetro is that the structure does the heavy lifting for you. Facilitators can keep meetings on track, group similar ideas, vote on priorities, and assign actions in minutes. Whether you're a Scrum Master, Agile Coach, or team lead, this template helps you build a habit of regular reflection that fuels healthier, faster-moving teams. ## Topics - **What worked well?**: What went smoothly and is worth repeating? - **What didn't work?**: What slowed us down or caused frustration? - **What will we change?**: What concrete actions will we try next? - **Kudos & shout-outs**: Who or what deserves recognition this sprint? ## When to use - At the end of a sprint or iteration when you want a quick, focused reflection without heavy facilitation overhead. - For new agile or Scrum teams who are building the habit of regular retrospectives and need an easy starting point. - When time is short and you want a format that delivers clear actions in 30 to 45 minutes. - As a reliable default retrospective you can run repeatedly to track improvement over time. ## Tips and tricks - Keep it timeboxed - aim for 30 to 45 minutes so the conversation stays sharp and energy stays high. - Limit the team to one or two concrete actions per retrospective so improvements actually get done. - Use anonymous brainstorming first to encourage honest input, then group and discuss themes together. - Assign a clear owner and due date to each action item so nothing falls through the cracks. - Rotate the facilitator role to keep the format fresh and build facilitation skills across the team. - Revisit the previous retrospective's actions at the start to reinforce accountability and continuous improvement. ## Icebreaker questions - If this sprint were a weather forecast, what would it be? - What's one word that sums up how you felt about this iteration? --- # Blast Off! Launch Retrospective URL: https://www.teamretro.com/retrospective-templates/blast-off-launch-retrospective/ Every great mission needs a moment to look back before the countdown to the next one begins. The Blast Off! Launch Retrospective uses a fun, space-themed framework to help your team reflect on a recent launch, release, or major milestone. By framing your reflection as a rocket journey — from the fuel that powered you forward, to the obstacles that created drag, to the new trajectory ahead — your team can celebrate wins and uncover lessons in an engaging, energizing way. This retrospective works by guiding participants through four mission-focused themes: what gave you lift-off, what slowed your ascent, what you want to course-correct, and where you're aiming next. The playful metaphor lowers the barrier to honest conversation, making it easier for everyone to contribute regardless of role or seniority. It's especially effective for product launches, sprint releases, and project go-lives where energy and morale matter as much as the technical outcome. Run in TeamRetro, the Blast Off! Launch Retrospective keeps your crew aligned, motivated, and ready for the next mission. It transforms post-launch reflection into a shared celebration and a clear, actionable plan, helping teams build continuous improvement habits while keeping spirits high. Whether you're closing out a high-stakes release or simply marking the end of a project phase, this format turns retrospection into rocket fuel for what comes next. ## Topics - **Fuel for Lift-Off**: What powered our launch and gave us momentum? - **Drag & Resistance**: What slowed us down or created friction on the way up? - **Course Corrections**: What should we adjust or steer differently next time? - **Next Destination**: Where are we aiming for our next mission? ## When to use - After a major product launch or release when you want to celebrate wins and capture lessons before the next cycle begins. - At the close of a project phase or go-live milestone where team morale and momentum are as important as technical outcomes. - When a standard retrospective feels stale and you want a fun, themed format to re-energize the team. - Following a high-pressure or high-stakes delivery to help the team decompress, reflect, and reset for the next mission. ## Tips and tricks - Set the scene with the space theme early — a quick mission briefing helps everyone get into a playful, open mindset before diving in. - Keep the 'Drag & Resistance' discussion focused on systems and processes rather than blaming individuals, so the conversation stays psychologically safe. - Timebox each topic to keep momentum high and prevent the retrospective from drifting; aim for around 10 minutes per theme. - Encourage every crew member to contribute by collecting ideas independently first, reducing the influence of louder voices or groupthink. - Turn 'Course Corrections' into concrete, owned action items with clear next steps so improvements actually make it to the next launch. - End on the 'Next Destination' theme to close the session on an energizing, forward-looking note that builds excitement for what's ahead. ## Icebreaker questions - If our team launch were a space mission, would it have been a smooth orbit or a bumpy re-entry, and why? - If you could pack one item for the next mission to make it easier, what would it be? --- # Personal Growth Retrospective URL: https://www.teamretro.com/retrospective-templates/personal-growth-retrospective/ The Personal Growth retrospective is a powerful team activity that focuses on individual development within the context of team success. This format encourages team members to reflect on their personal journey, identify opportunities for improvement, and recognize areas where they can support and be supported by their colleagues. Unlike traditional retrospectives that focus primarily on process and team dynamics, this format creates a safe space for individuals to share their aspirations, challenges, and achievements. It helps build psychological safety by acknowledging that personal growth is integral to team success. By incorporating elements of gratitude and mutual support, this retrospective format strengthens team bonds while empowering individuals to take ownership of their development journey. It's particularly effective for fostering a growth mindset and creating a culture of continuous improvement. ## Topics - **Improve**: What actions can you personally take to improve the next sprint? - **Support**: How can the team help you going forward and why is that important? - **Grateful**: What are you grateful for at work? ## When to use - When team members are seeking direction in their professional development - During performance review periods to gather insights and set personal goals - When the team needs to strengthen interpersonal connections and support systems - After major project milestones to reflect on individual growth and contributions ## Tips and tricks - Create psychological safety by sharing your own growth areas and vulnerabilities first - Encourage specific, actionable items rather than vague statements or wishes - Keep the focus on personal responsibility and growth rather than blame or criticism - Follow up on support requests in subsequent team meetings or one-on-ones - Use this format regularly (quarterly) to track progress and maintain momentum - Consider private sharing options for sensitive personal development topics ## Icebreaker questions - What's one skill you learned as a child that still helps you today? - If you could instantly master any professional skill, what would it be and why? --- # Mid-Year Goal Check-In URL: https://www.teamretro.com/retrospective-templates/mid-year-goal-check-in/ The Mid-Year Goal Check-In is a simple tool for managers and team members to review progress, celebrate achievements, and course-correct where necessary. This collaborative process ensures that individual and team goals remain aligned with organizational values and priorities, fostering a culture of continuous growth and improvement. By conducting a structured mid-year check-in, teams can take a step back and assess their journey so far. They can celebrate wins, identify areas for improvement, and address any hurdles or challenges that may have arisen. This open dialogue promotes transparency, accountability, and a shared understanding of expectations. The Mid-Year Goal Check-In also provides an opportunity to realign goals and priorities, ensuring that efforts remain focused on delivering maximum impact. By reviewing habits, behaviors, and best practices, individual team members can refine their approach and adopt strategies that drive greater efficiency and effectiveness. ## Topics - **Progress Update**: What milestones have you achieved toward your goal/s so far? - **Alignment with Values**: How well do the goal/s still align with your current priorities and values? - **Hurdles and Challenges**: What obstacles have you encountered, and how have you addressed them? - **Habits and Behaviors**: What actions or behaviours have been helping you achieve progress? - **Next Steps**: What's the next specific action you can take to move closer to your goal/s? ## When to use - When you need to conduct a formal mid-year review of individual and team goals, ensuring alignment with organizational priorities. - To celebrate achievements and wins, while also identifying areas for improvement and addressing challenges or hurdles. - To realign goals, priorities, and strategies based on changing circumstances or new insights gained throughout the year. - To promote transparency, accountability, and a shared understanding of expectations among team members and stakeholders. - To foster a culture of continuous growth, learning, and improvement within your team or organization. ## Tips and tricks - Encourage open and honest feedback by creating a safe and judgment-free environment. - Involve stakeholders and cross-functional partners to gain a holistic perspective on progress and challenges. - Use data and metrics to support observations and insights, but also consider qualitative feedback. - Celebrate wins and achievements, no matter how small, to boost morale and motivation. - Assign clear ownership and timelines for action items and follow-up to ensure accountability. - Aim to make this team or individual lead, rather than manager led. - Make sure feedback is constructive and encouraging. ## Icebreaker questions - If you could describe our team's journey so far in one word, what would it be and why? - Share a personal or professional achievement from the past six months that you're particularly proud of. --- # Staff Retention Strategy Workshop URL: https://www.teamretro.com/retrospective-templates/staff-retention/ A staff retention strategy workshop is a structured meeting where HR teams and leaders collaborate to understand what motivates employees, assess the company's capabilities and resources, and develop actionable strategies to improve staff retention rates. By fostering open discussions and gathering diverse perspectives, this activity aims to uncover key drivers of job satisfaction, identify areas for improvement, and implement initiatives that create a more engaging and supportive work environment. This workshop draws upon principles of employee engagement, organizational culture, and talent management. It encourages participants to think critically about the employee experience, from onboarding to career development opportunities, and to propose creative solutions that align with the company's values and goals. Ultimately, a successful staff retention strategy workshop can lead to higher employee satisfaction, reduced turnover costs, and a more committed and productive workforce. ## Topics - **What motivates our employees?**: What factors contribute to job satisfaction and engagement? - **Our Company's Capabilities**: What resources and strengths does our company have? - **Areas for Improvement**: What aspects need attention to enhance retention? - **Retention Strategies**: What initiatives can we implement to improve retention? - **Building a Supportive Culture**: How can we foster a more engaging and supportive culture? ## When to use - When you're experiencing high employee turnover rates and want to identify root causes and potential solutions. - As part of a regular review process to assess the effectiveness of your retention strategies and make improvements. - When introducing significant organizational changes that may impact employee satisfaction and engagement. - After receiving feedback or survey results indicating concerns about job satisfaction or company culture. - As a proactive measure to maintain a motivated and committed workforce. ## Tips and tricks - Encourage open and honest discussions by creating a safe and judgment-free environment. - Involve employees from various levels and departments to gather diverse perspectives. - Use anonymous feedback mechanisms to allow for candid input without fear of repercussions. - Prioritize action items and assign ownership for implementing agreed-upon strategies. - Follow up regularly to assess the effectiveness of implemented initiatives and make adjustments as needed. - Celebrate successes and share positive outcomes with the entire organization to maintain momentum. ## Icebreaker questions - If you could choose any job in the world, what would it be and why? - What's the most valuable lesson you've learned from a previous job or workplace experience? --- # Oktoberfest Brewfest Retrospective URL: https://www.teamretro.com/retrospective-templates/oktoberfest-brewfest-retrospective/ Gather your team around the metaphorical beer hall and celebrate the season with a retrospective that brings the spirit of Oktoberfest to your reflection. Inspired by the world's largest folk festival in Munich, this themed format uses the imagery of brewing, toasting, and harvest to help teams pause, look back, and look ahead in a festive and relaxed atmosphere. It's a playful twist on the traditional sprint or project review, perfect for keeping engagement high during the autumn months. The Oktoberfest Brewfest Retrospective works by guiding participants through a series of beer-themed prompts that map onto familiar retrospective questions. What's been brewing nicely (going well)? What left a bad taste (problems)? What ingredients do we need next time (improvements)? And what should we raise a toast to (celebrations and shout-outs)? This structure makes it easy for everyone to contribute, lowers the barrier to honest feedback, and adds a sense of fun that encourages even quieter team members to join in. By blending celebration with genuine reflection, this template helps teams build psychological safety, recognise wins, and surface improvement opportunities in a memorable way. Whether you're closing out a sprint, wrapping up a quarter, or simply marking the festive season together, the Oktoberfest Brewfest format turns routine retrospectives into something your team will look forward to. Prost! ## Topics - **What's Brewing Nicely**: What has been going well and tastes great? - **What Left a Bad Taste**: What went wrong or felt sour this time around? - **Ingredients to Add**: What should we mix in to brew a better batch next time? - **Raise a Toast**: Who or what deserves a celebratory cheers this round? ## When to use - When you want to add a festive, seasonal twist to your end-of-sprint or end-of-quarter review during the autumn months. - When team morale needs a lift and you want reflection to feel fun and low-pressure. - When onboarding new members and looking for a relaxed format that encourages everyone to contribute. - When celebrating a major milestone or release and you want to balance recognition with honest improvement. - When your usual retrospective format feels stale and you need something fresh to re-energise the team. ## Tips and tricks - Lean into the theme — use beer and festival imagery in your prompts and intro to set a relaxed, playful mood that loosens people up. - Timebox each topic so the festive fun doesn't crowd out the actionable discussion; aim for balanced contribution across all four areas. - Make sure the 'What Left a Bad Taste' section stays blame-free by focusing on processes and situations rather than individuals. - Always close with the 'Raise a Toast' appreciation round so the session ends on a genuinely positive, morale-boosting note. - Encourage quieter members to add their thoughts anonymously first, then group and vote to keep the discussion inclusive. - Turn the top improvement ideas into clear action items with owners so the good intentions don't go flat after the meeting. ## Icebreaker questions - If your last sprint were a beer, what kind would it be and why? - What's one festive tradition you'd love to bring into your team's culture? --- # Operational Efficiency Review URL: https://www.teamretro.com/retrospective-templates/operational-efficiency-review/ The Operational Efficiency Review is a structured retrospective focused on analyzing business operations, processes, and costs to identify opportunities for optimization and increased efficiency. This review encourages cross-functional collaboration, data-driven decision making, and continuous improvement. The retrospective begins by celebrating successes and recognizing efforts that led to operational gains. Teams then dive into areas requiring attention, brainstorming creative solutions and developing actionable plans. The goal is to streamline workflows, reduce redundancies, and implement cost-saving measures while maintaining or enhancing quality and customer satisfaction. Regularly reviewing operational metrics keeps teams aligned on key performance indicators (KPIs) and ensures consistent progress toward strategic objectives. This retrospective can be tailored to various industries and organizational needs. ## Topics - **Operational Wins**: What operational successes did we achieve this period? - **Areas for Improvement**: What operational areas need attention or optimization? - **Potential Solutions**: What ideas do we have to address operational inefficiencies? - **Action Plans**: What specific steps should we take to improve operational efficiency? ## When to use - Conduct this retrospective periodically to maintain a regular cadence of operational reviews and continuous improvement efforts. - Use this template when seeking to optimize processes, reduce costs, and enhance operational efficiency across the organization. - This retrospective is valuable during times of rapid growth, market shifts, or organizational changes that impact operations. - Leverage this format when preparing for annual budgeting and strategic planning cycles to identify areas for cost savings and process improvements. - Implement this retrospective after major system implementations, mergers, or acquisitions to streamline operations and realize synergies. ## Tips and tricks - Encourage data-driven discussions by providing relevant operational metrics and KPIs to inform decision-making. - Foster a blame-free environment where teams can openly discuss challenges without fear of repercussions. - Involve cross-functional teams and subject matter experts to gain diverse perspectives and ensure buy-in. - Prioritize initiatives based on potential impact, feasibility, and alignment with strategic objectives. - Establish clear ownership, timelines, and success criteria for action plans to ensure accountability. - Celebrate quick wins and communicate progress regularly to maintain momentum and engagement. ## Icebreaker questions - If you could eliminate one operational inefficiency with a magic wand, what would it be and why? - Share a personal experience where a process improvement made your life easier or more efficient. --- # Toy Story Tales Retrospective URL: https://www.teamretro.com/retrospective-templates/toy-story-tales-retrospective/ Bring a little Pixar magic to your team reflection with a retrospective inspired by the world of beloved toys. The Toy Story Tales Retrospective uses familiar, friendly characters and themes to help teams open up, share honestly, and reflect on their last sprint or project in a fun, low-pressure way. Just like Woody, Buzz, and the gang learn to work together through adventures and setbacks, your team will explore what brought you joy, what challenged you, and where you want to head next. This themed retrospective works by framing classic reflection prompts around memorable Toy Story moments and characters. Participants share what made them feel like they had "a friend in me," what felt like being "lost in the world," what gave them that "to infinity and beyond" momentum, and what they want to pack in their toy box for the journey ahead. The storytelling angle lowers barriers, sparks creativity, and encourages psychological safety, making it easier for quieter team members to contribute and for everyone to engage with the conversation. Ideal for teams who love a creative twist on their agile rituals, the Toy Story Tales Retrospective keeps engagement high while still surfacing actionable insights. By wrapping serious reflection in a lighthearted narrative, you can break routine, boost morale, and turn your retrospective into a session people actually look forward to, all while capturing the wins, lessons, and next steps that drive continuous improvement. ## Topics - **A Friend in Me**: What support or teamwork helped you most? - **Lost in the World**: Where did you feel stuck, confused or off-track? - **To Infinity and Beyond**: What gave us momentum or a big win? - **Packing the Toy Box**: What should we keep, change or try next? ## When to use - When your team needs a fun, morale-boosting break from the standard retrospective format. - After a long or intense sprint where lightening the mood will help people open up honestly. - For teams who enjoy themed or creative sessions and want to re-energise their agile rituals. - When onboarding new team members and you want a friendly, low-pressure way to encourage participation. ## Tips and tricks - Lean into the theme with character images or quotes to set a playful tone, but keep the reflection meaningful and actionable. - Use the lighthearted framing to draw out quieter voices, but make sure everyone gets a turn to contribute. - Timebox each topic so the fun doesn't crowd out the discussion and action setting. - Keep the focus on situations and behaviours, not blame, especially in the 'Lost in the World' topic. - Close by converting your best 'Packing the Toy Box' ideas into actions with clear owners and due dates. - Rotate facilitation so the theme stays fresh and different people get to add their own creative spin. ## Icebreaker questions - If you were a Toy Story character this sprint, who would you be and why? - What's one toy from your childhood you'd love to have on the team right now? --- # Trick or Treat Retrospective URL: https://www.teamretro.com/retrospective-templates/trick-treat-retrospective/ Embrace the spirit of Halloween to uncover team insights—without the scares! Hallow the spirit of teamwork with a delightfully spooky retrospective that transforms feedback into festive fun. The Trick-or-Treat Retrospective invites your team to don their metaphorical costumes, shine a light into the shadows, and explore the past sprint with curiosity and creativity. Instead of the usual serious reflections, your team steps into a Halloween-themed playground of insights—where challenges, wins, and eerie unknowns are all welcome guests at the party. ## Topics - **Treats**: What sweet successes did we enjoy? - **Tricks**: What obstacles tripped us up? - **Haunting Concerns**: What worries are haunting the team? - **Boo-tiful Ideas**: What magical improvements can we conjure? ## When to use - When your team needs a fun, engaging way to discuss challenges and successes, especially during October or around Halloween when the theme feels natural and timely. - When retrospective fatigue has set in and you need a creative format to re-energize participation and honest feedback from team members. - When you want to create a psychologically safe environment where discussing problems feels less threatening by framing them as playful 'tricks' rather than failures. - For teams with diverse personalities who might respond well to a lighthearted, themed approach that makes serious reflection more accessible and enjoyable. ## Tips and tricks - Set the mood with Halloween-themed visuals or background music to fully embrace the theme and create an engaging atmosphere that encourages participation. - Emphasize that 'tricks' aren't about blaming individuals but about identifying systemic obstacles and challenges the team faced together. - Balance the discussion time between treats and tricks to ensure you celebrate wins while still addressing areas for improvement—don't let the fun theme overshadow serious issues. - Use the 'magic' or AI action items section to ensure the retrospective leads to concrete next steps, not just a fun conversation without outcomes. - Be mindful of cultural differences—not all team members may be familiar with Halloween traditions, so take a moment to explain the theme and make everyone feel included. - Watch for negativity bias where teams focus too heavily on tricks—actively encourage sharing treats first to set a positive tone before diving into challenges. ## Icebreaker questions - If you could dress up as any character for Halloween, who would you be and why? - What's your favorite Halloween candy or treat, and does it say anything about your personality? --- # Love, Wish & Wonderland Retrospective URL: https://www.teamretro.com/retrospective-templates/love-wish-and-wonderland-retrospective/ Love, Wish & Wonderland is a playful yet powerful retrospective format that invites teams to reflect on what they cherish, what they hope to improve, and what curious possibilities lie ahead. By blending appreciation, aspiration, and imagination, it creates a balanced conversation that honors successes while opening space for bold, exploratory thinking. The whimsical framing helps lower defenses, making it easier for teams to share honest feelings and forward-looking ideas. The retrospective works across three lenses. "Love" surfaces the practices, behaviors, and wins the team genuinely values and wants to protect. "Wish" captures the changes, improvements, and unmet needs people would like to see realized. "Wonderland" is the imaginative space where teams dream without constraints — exploring "what if" scenarios, experiments, and ideas that might seem impossible today but could spark breakthrough innovation tomorrow. Together these create a rhythm of gratitude, intention, and creativity. Ideal for teams that want a refreshing alternative to standard sprint retrospectives, Love, Wish & Wonderland builds psychological safety and energizes participants. It is especially effective for celebrating milestones, re-engaging tired teams, or kicking off new initiatives where imagination matters. In TeamRetro, you can run it remotely or in person, grouping themes, voting on priorities, and turning the most promising wishes and wonderland ideas into concrete actions. ## Topics - **Love**: What do you genuinely value and want to keep? - **Wish**: What changes or improvements would you like to see? - **Wonderland**: What bold 'what if' ideas could we explore? - **Actions**: What will we commit to doing next? ## When to use - When a team needs a refreshing, creative alternative to a standard sprint retrospective. - After reaching a milestone or completing a project, to celebrate wins and dream about what's next. - When morale or energy is low and you want to rebuild positivity and engagement. - At the start of a new initiative where imaginative, blue-sky thinking is valuable. - When you want to balance appreciation with both practical improvements and bold innovation. ## Tips and tricks - Set the tone early — explain that Wonderland is judgment-free so people feel safe sharing wild ideas. - Start with Love to build positive energy before moving into wishes and dreams. - Use anonymous contributions to ensure quieter or more junior team members share openly. - Timebox each section so the imaginative Wonderland phase doesn't crowd out concrete actions. - Group and vote on ideas to surface the themes that matter most to the whole team. - Always convert the top wishes and wonderland ideas into owned actions so the session drives real change. ## Icebreaker questions - If your team had a magic wand, what one thing would you instantly change about how you work? - What fictional place or story world best represents your team right now, and why? --- # SWOT Analysis URL: https://www.teamretro.com/retrospective-templates/swot-analysis/ SWOT Analysis is a structured planning method that helps teams evaluate four key areas: Strengths, Weaknesses, Opportunities, and Threats. Originally developed by Albert Humphrey at Stanford University, this powerful framework enables teams to identify internal and external factors that influence their success. During a SWOT analysis, teams collaboratively examine their internal capabilities (Strengths and Weaknesses) and external factors (Opportunities and Threats). This comprehensive approach helps teams leverage their advantages while addressing challenges proactively. The systematic nature of SWOT Analysis makes it particularly valuable for strategic planning, project evaluation, and team development. By considering both positive and negative aspects, teams can develop more balanced and effective action plans. The four quadrants split into two pairs. Strengths and Weaknesses are internal — they describe things inside your team or organisation that you control, such as skills, processes, resources, or reputation. Opportunities and Threats are external — they describe forces in the wider market or environment that you don't control but must respond to, such as competitors, regulation, customer trends, or new technology. Keeping internal and external factors separate is what stops a SWOT from collapsing into a single undifferentiated list. A common point of confusion is the line between a Strength and an Opportunity: a Strength is something you already have, while an Opportunity is an external opening you could take advantage of. The Threats quadrant is often the most overlooked and the most valuable. A useful threat analysis looks across several categories: competitive threats (a rival's new feature or lower price), market threats (shrinking demand or a shifting customer base), regulatory threats (new compliance requirements), and resource threats (key-person dependency, supplier risk, or budget cuts). For example, a SaaS team's SWOT might list "experienced engineering team" as a Strength, "no enterprise sales motion" as a Weakness, "growing demand for our category" as an Opportunity, and "a well-funded competitor moving into our niche" as a Threat. Naming threats early turns them from surprises into planned-for risks. ## Topics - **Strengths**: What advantages do we have over others? - **Weaknesses**: What weaknesses do we have relative to others? - **Opportunities**: What could we do to exploit our advantages? - **Threats**: What external forces could negatively impact us — competitive, market, regulatory, or resource threats? ## When to use - Before starting a new project or initiative to assess readiness and identify potential challenges - During strategic planning sessions to align team goals with organizational objectives - When facing significant changes or challenges to evaluate the team's position and options - Quarterly reviews to track progress and adjust team strategy ## Tips and tricks - Encourage specific, concrete examples rather than general statements - Keep the focus balanced across all four quadrants, spending equal time on each - Use dot voting to prioritize the most important items in each category - Create action items that leverage strengths to address weaknesses - Document and review previous SWOT analyses to track progress over time - Consider both short-term and long-term perspectives when identifying opportunities and threats ## Icebreaker questions - What's one unexpected strength you discovered about our team in the past month? - If you could instantly improve one aspect of our team, what would it be and why? --- # Pizza Party Retrospective URL: https://www.teamretro.com/retrospective-templates/pizza-party-retrospective/ Who doesn't love a good slice? The Pizza Party Retrospective serves up a fun, food-themed twist on the classic team reflection, turning your sprint review into a deliciously memorable experience. By framing feedback around the familiar idea of making and sharing a pizza, this format lowers the barrier to honest conversation and helps teams reflect on what went well, what needs more flavour, and what to leave off the menu next time. Each topic represents an ingredient in your team's pizza, from the cheesy wins everyone loved to the burnt crust that needs attention. This playful metaphor encourages participants to think about quality, balance, and collaboration in a relaxed way, making it especially effective for teams who want to keep retrospectives light without losing depth. The themed approach is a great way to re-energise recurring retrospectives that may have grown stale, while still surfacing meaningful, actionable insights. Whether you're celebrating a successful release or working through a tough sprint, the Pizza Party Retrospective creates a welcoming space for everyone to contribute. Use it to build psychological safety, spark creativity, and end your meeting with a clear set of takeaways, served fresh and ready to action. ## Topics - **Cheesy Goodness**: What went really well and made everyone happy? - **Burnt Crust**: What got overcooked, went wrong, or left a bad taste? - **New Toppings**: What new ideas or experiments should we try next? - **Leave Off the Menu**: What should we stop doing or remove entirely? ## When to use - When recurring retrospectives feel stale and the team needs a fun, fresh format to re-engage. - After completing a major release or milestone you want to celebrate in a relaxed atmosphere. - When you want to build psychological safety and encourage honest feedback from quieter team members. - As a lighthearted way to onboard a new team into the habit of regular reflection. ## Tips and tricks - Lean into the theme. Consider ordering actual pizza or hosting a virtual lunch to set a relaxed, social tone. - Keep the metaphor clear by briefly explaining what each topic represents before voting begins. - Timebox each section so the fun doesn't crowd out actionable takeaways. - Make sure every voice is heard. Use anonymous contributions in TeamRetro to encourage quieter members. - Prioritise a few key actions at the end rather than trying to fix everything at once. - Watch out for the fun overshadowing the purpose. Always close with clear owners and next steps. ## Icebreaker questions - If you were a pizza topping, which one would you be and why? - What's your go-to comfort food after a tough day at work? --- # Star Wars: The Agile Force Awakens Retrospective URL: https://www.teamretro.com/retrospective-templates/star-wars-the-agile-force-awakens-retrospective/ Bring a little intergalactic fun to your team's reflection with a Star Wars-inspired retrospective that channels the spirit of the saga into honest, actionable conversation. Framed around iconic forces from a galaxy far, far away, this themed format invites your team to celebrate their wins (the Force), confront the obstacles that held them back (the Dark Side), set their course (the Jedi Path), and call out the recurring frustrations that keep tripping them up (the Stormtroopers). Themed retrospectives like this one are a proven way to lower the pressure, spark creativity, and get even quiet team members to open up. The format works just like a classic start-stop-continue style retrospective, but with a narrative wrapper that makes participation feel like an adventure rather than an obligation. Each team member adds their reflections to the relevant topic, votes on what matters most, and collaborates on action items to carry forward. Because the playful framing reduces defensiveness, teams often surface deeper insights and have more candid discussions about what's really going on beneath the surface of the sprint. Whether you're a seasoned Scrum Master looking to break up retro fatigue or an Agile coach wanting to energize a tired team, this Star Wars retrospective template helps you turn routine reflection into a memorable, engaging ritual. May the Force — and continuous improvement — be with you. ## Topics - **The Force**: What went well and gave us strength this sprint? - **The Dark Side**: What pulled us off course or held us back? - **The Jedi Path**: What should we start doing to grow stronger? - **The Stormtroopers**: What recurring annoyances keep missing the mark? ## When to use - When your team is experiencing retro fatigue and needs a fresh, playful format to re-energize reflection. - At the end of a sprint or milestone when you want candid, low-pressure conversation about what worked and what didn't. - To build psychological safety in newer teams, where a themed framing makes it easier to raise tough topics. - Around a release, special event, or just for fun when you want a memorable team-building ritual that still drives action items. ## Tips and tricks - Lean into the theme — add a Star Wars soundtrack or invite people to join with themed backgrounds to set the mood, but don't let the fun overshadow the outcomes. - Keep the framing light but the discussion real; remind the team that the Dark Side is a blame-free zone focused on systems and root causes, not individuals. - Timebox each topic so the brainstorm stays energetic and you leave room for grouping, voting, and agreeing on action items. - Use dot voting to prioritize so the most impactful Jedi Path ideas and Stormtrooper fixes rise to the top. - Make sure every reflection leads somewhere — convert the top votes into clear, owned action items with due dates. - Invite quieter team members first or use anonymous mode so the loudest voices don't dominate the galaxy. ## Icebreaker questions - If you could have one Star Wars character on your team this sprint, who would it be and why? - Are you more of a Jedi, a Sith, or a droid when it comes to your work style? --- # Take the Controller Retrospective URL: https://www.teamretro.com/retrospective-templates/take-the-controller-retrospective/ Take the Controller invites your team to view the last sprint like a video game — complete with levels conquered, glitches to fix, power-ups to collect, and the next stage to tackle. By reframing reflection through a playful gaming lens, this format lowers the barrier to honest conversation and energizes teams who might feel fatigued by traditional retrospective formats. It's a great way to spark creativity while still surfacing the practical insights that drive continuous improvement. The retrospective works by guiding participants through four themed prompts that map familiar gaming concepts onto real team experiences. "High Scores" celebrate wins, "Glitches & Bugs" surface problems, "Power-Ups" identify what gave the team a boost, and "Next Level" plans the path forward. Each topic encourages people to think in story-like terms, which makes it easier to recall details and articulate feelings about the work. In TeamRetro, the team adds their thoughts, groups related ideas, votes on what matters most, and turns the highest-priority items into clear actions. Whether your squad ships software, runs campaigns, or manages operations, this gamified retrospective brings fresh energy to your meetings while keeping the focus on learning and momentum. It's especially valuable for teams looking to break out of a rut, build psychological safety through play, and make continuous improvement feel less like a chore and more like leveling up together. ## Topics - **High Scores**: What wins or achievements did we unlock this sprint? - **Glitches & Bugs**: What broke, slowed us down, or didn't behave as expected? - **Power-Ups**: What gave us a boost or helped us perform better? - **Next Level**: What should we do to level up in the next sprint? ## When to use - When your team is feeling fatigued by traditional retrospective formats and needs a fresh, playful change of pace. - After completing a sprint, project milestone, or release where you want to celebrate wins and plan improvements. - When you want to build psychological safety and make it easier for quieter team members to contribute through a fun, low-pressure theme. - With teams that enjoy gaming culture or want to inject more energy and creativity into their continuous improvement rituals. ## Tips and tricks - Set the tone early by leaning into the gaming theme — using playful language helps people relax and share more openly. - Timebox each topic so the energy stays high and no single 'level' dominates the session. - Group similar 'glitches' together before voting so the team focuses on the patterns that matter most, not isolated complaints. - Make sure every player gets a turn at the controller — actively invite quieter members to add their high scores and ideas. - Convert 'Next Level' ideas into clear, owned actions with due dates so improvements actually ship before the next retro. - Avoid letting the fun theme mask real issues — balance celebration with honest reflection on what needs to change. ## Icebreaker questions - If your work this sprint were a video game, what genre would it be and why? - What's the one in-game power-up you wish you could use in real life at work? --- # Reddit Rewind Retrospective URL: https://www.teamretro.com/retrospective-templates/reddit-rewind-retrospective/ Inspired by the playful, community-driven spirit of Reddit, the Reddit Rewind retrospective gives teams a fun and familiar framework to look back on a project, sprint, or year. Borrowing the language of the front page of the internet — upvotes, downvotes, hot takes, and unpopular opinions — this format helps people surface what resonated, what flopped, and what conversations are still worth having. It's a refreshing alternative to traditional formats that often go stale after a few cycles. The activity works by inviting team members to contribute to playful, Reddit-themed prompts that map onto classic retrospective themes. "Most Upvoted" celebrates the wins and highlights worth karma, "Most Downvoted" surfaces frustrations and friction, "Trending Threads" captures the ongoing topics that need more discussion, and "Hot Takes" creates space for bold, honest, even controversial perspectives. Because the framing feels casual and relatable, it lowers the barrier to participation and encourages even quieter team members to weigh in. The benefit of running a Reddit Rewind in TeamRetro is that you get all the structure of a focused retrospective with an energy that keeps people engaged. The themed prompts spark conversation, the voting mirrors the upvote culture everyone already understands, and the action items that emerge are grounded in real, candid feedback. It's especially effective for end-of-year reviews, community team check-ins, or any moment your team needs to reconnect with how they really feel. ## Topics - **Most Upvoted**: What earned the most karma this time around? - **Most Downvoted**: What got buried and left us frustrated? - **Trending Threads**: Which ongoing topics still need more discussion? - **Hot Takes**: Got a bold or unpopular opinion to share? ## When to use - At the end of the year when your team wants a fun, reflective way to look back on the highs and lows. - When traditional retrospective formats are feeling stale and you want to re-energise participation. - For community, content, or social teams who already live in the language of upvotes and threads. - When you want to encourage candid, honest feedback that might not surface in a standard format. ## Tips and tricks - Set the tone early by leaning into the Reddit theme — it signals that playful, honest contributions are welcome. - Use the voting feature to mirror the upvote culture and quickly identify which items the team cares about most. - For 'Hot Takes', explicitly remind everyone that bold opinions are safe to share and won't be held against anyone. - Timebox each category so the conversation stays energetic and you leave room to convert insights into action items. - Encourage quieter team members to contribute by allowing anonymous entries where appropriate. - Close the session by grouping similar items and committing to a small number of concrete actions, not just discussion. ## Icebreaker questions - If your week was a Reddit post, what would the title be and how many upvotes would it get? - What's one subreddit (real or made up) that perfectly describes our team right now? --- # Hot Air Balloon Retrospective URL: https://www.teamretro.com/retrospective-templates/hot-air-balloon-retrospective/ The Hot Air Balloon retrospective uses the metaphor of a hot air balloon to help teams visualize their progress and challenges. Originally popularized in agile coaching circles, this engaging format encourages teams to identify what propels them forward (hot air), what holds them back (sandbags), and who deserves recognition (hugs and kudos). Participants reflect on factors that contribute to the team's success, obstacles that impede progress, and acknowledge team members who have made significant contributions. The visual metaphor makes it easy for teams to understand and relate to the concepts being discussed. This retrospective format is particularly effective for teams who enjoy creative visualization and want to maintain a positive focus while still addressing challenges. It helps create a balanced discussion about team dynamics and performance improvement opportunities. ## Topics - **Hot Air**: What is making us fly? - **Anchors**: What is keeping us down? - **Shout outs and Kudos**: Who do we want to acknowledge? ## When to use - When you want to maintain a positive focus while still addressing challenges in a balanced way - After completing a significant project milestone to reflect on team dynamics and progress - When the team needs to identify both enablers and barriers to their success - When you want to boost team morale by incorporating recognition into the retrospective ## Tips and tricks - Start with the 'Hot Air' section to build positive momentum before addressing challenges - Encourage specific, actionable feedback rather than vague statements - Ensure 'Hugs and Kudos' recognizes a variety of team members and contribution types - Keep a parking lot for items that need further discussion or involve external stakeholders - Use dot voting to prioritize which items to address first if you have many suggestions ## Icebreaker questions - If you could take a hot air balloon ride anywhere in the world, where would you go and why? - What gives you the most lift or energy during your workday? --- # New Year's Resolutions Retrospective URL: https://www.teamretro.com/retrospective-templates/new-years-resolutions-retrospective/ The start of a new year is the perfect moment for teams to pause, look back, and look forward together. The New Year's Resolutions Retrospective gives your team a structured way to celebrate the wins of the past year, acknowledge what held you back, and collectively agree on the goals and habits you want to carry into the months ahead. It blends the reflective power of a traditional retrospective with the optimism and momentum that come with a fresh start. This format works by guiding the team through four connected conversations: reflecting on the year that was, letting go of habits that no longer serve you, defining the resolutions you want to commit to, and naming the support you'll need to make them stick. By moving from reflection to intention, the team builds a shared sense of direction and ownership. It's a powerful way to align on priorities, renew motivation, and turn vague aspirations into concrete, achievable commitments. Whether you run it in early January, at the start of a fiscal year, or at any natural milestone, this retrospective helps teams reset with purpose. Resolutions are most effective when they're specific, shared, and supported — and this template is designed to capture exactly that, so your team begins the new chapter feeling focused, energised, and aligned. ## Topics - **Looking Back**: What are we proud of from the past year? - **Leaving Behind**: What habits or practices should we stop in the new year? - **Resolutions**: What goals or commitments do we want to make this year? - **Support Needed**: What help do we need to make these resolutions stick? ## When to use - At the start of a new calendar or fiscal year, when teams are naturally reflecting and planning ahead. - When you want to combine a year-in-review with forward-looking goal setting in a single session. - To re-energise and re-align a team after a holiday break or a major milestone. - When motivation is dipping and the team needs a renewed sense of shared purpose and direction. ## Tips and tricks - Keep resolutions specific and limited in number — three to five shared goals are far more achievable than a long wish list. - Balance the reflection: spend enough time celebrating wins before moving into what to change, so the session feels positive and motivating. - Assign owners and a check-in cadence to each resolution so commitments don't fade once the meeting ends. - Create psychological safety when discussing what to leave behind — focus on patterns and processes, not individuals. - Revisit these resolutions in future retros to track progress and keep the team accountable throughout the year. - Encourage quieter team members to contribute by using anonymous brainstorming so every voice is heard. ## Icebreaker questions - If you could give the past year a movie title, what would it be? - What's one personal habit you're hoping to start in the new year? --- # Lunar New Year Reflections Retrospective URL: https://www.teamretro.com/retrospective-templates/lunar-new-year-reflections-retrospective/ Ring in the Year ahead with a retrospective that blends cultural celebration with meaningful team reflection. Lunar New Year is a time of fresh starts, gratitude, and renewed hope across many cultures in East and Southeast Asia — a perfect moment for your team to pause, look back on the year that has passed, and look forward to new beginnings. This format channels that spirit of renewal into a structured conversation that helps teams close out the old cycle and step into the new one with clarity and shared purpose. Inspired by traditions such as sweeping out the old to welcome the new, sharing wishes for prosperity, and honouring achievements with red envelopes of good fortune, the activity guides your team through four themed reflections. Participants reflect on what they want to leave behind, what brought them luck and success, what they are grateful for, and what they hope to achieve in the year ahead. Each topic is designed to be inclusive and lighthearted while surfacing genuine insights that drive continuous improvement. Whether your team observes Lunar New Year or simply wants a seasonal, celebratory way to reset, this retrospective creates space for connection, gratitude, and forward planning. By the end, your team will have cleared away lingering frustrations, recognised wins, and committed to clear goals — all framed within the joyful, optimistic mood of the new year. ## Topics - **Sweep It Away**: What old habits or frustrations should we leave behind? - **Lucky Wins**: What went well and brought us fortune this past year? - **Gratitude & Red Envelopes**: Who or what are we grateful for this year? - **Wishes for the New Year**: What do we hope to achieve in the year ahead? ## When to use - At the start of the Lunar New Year period to mark a seasonal reset and welcome new beginnings with your team. - As an end-of-year or year-in-review retrospective when you want a celebratory, reflective tone rather than a standard sprint review. - When team morale needs a boost through gratitude, recognition, and a sense of fresh momentum. - To kick off annual planning by surfacing what to leave behind and what to aim for in the coming year. ## Tips and tricks - Set the scene with festive visuals or a short note about Lunar New Year traditions so everyone understands the theme and intent. - Be inclusive — acknowledge that not everyone celebrates Lunar New Year, and frame the activity as a universal opportunity for reflection and renewal. - Encourage genuine appreciation in the Gratitude topic by giving everyone a moment of quiet thinking time before sharing. - Keep the 'Sweep It Away' discussion blame-free by focusing on processes and habits rather than individuals. - Turn 'Wishes for the New Year' into concrete actions by grouping similar hopes and assigning owners and timelines. - Timebox each topic to keep the energy high and ensure you reach the forward-looking discussion before time runs out. ## Icebreaker questions - Which animal of the Lunar New Year zodiac best matches your work style, and why? - What is one tradition or food you associate with celebrating a fresh start? --- # AI-Accelerated Engineering Retrospective URL: https://www.teamretro.com/retrospective-templates/ai-accelerated-engineering-retrospective/ AI tools like code assistants, automated testing agents, and LLM-powered workflows are transforming how engineering teams design, build, and ship software. The AI-Accelerated Engineering Retrospective gives your team a structured space to step back and examine how these tools are actually affecting your day-to-day work — what's speeding you up, where new friction is appearing, and how trust, quality, and team dynamics are evolving as AI becomes part of the development process. This retrospective works by guiding your team through focused reflection on the real impact of AI adoption: the wins worth scaling, the risks worth watching, and the practices worth standardising. Rather than treating AI as a buzzword, it grounds the conversation in concrete experiences — pair programming with copilots, reviewing AI-generated code, prompt engineering, and the shifting balance between human judgement and machine speed. By surfacing these insights together, teams can make deliberate choices about where to lean into automation and where human craft still matters most. The benefit is a shared, honest understanding of how AI is changing your engineering culture and output. Teams come away with practical agreements on tooling, quality guardrails, and ways of working that capture the productivity gains of AI while protecting code quality, security, and developer growth. It's an ideal format for any modern team navigating the fast-moving world of AI-assisted software development. ## Topics - **AI Wins**: Where did AI speed us up or improve our work? - **Friction & Risks**: Where did AI slow us down or create new problems? - **Trust & Quality**: How is AI affecting our code quality and confidence? - **What Should We Do Next?**: What practices or experiments should we adopt going forward? ## When to use - After your team has been using AI coding tools for a few sprints and you want to assess their real impact. - When code quality, review load, or security concerns have shifted since adopting AI assistants. - To establish shared team agreements and guardrails for responsible AI-assisted development. - When onboarding new AI tooling and you want to capture early wins and pitfalls. - As a regular check-in for engineering teams evolving their AI-augmented workflows. ## Tips and tricks - Ground the discussion in concrete examples — ask for the specific tool, task, and outcome rather than general opinions about AI. - Create psychological safety so skeptics and enthusiasts alike can speak freely; avoid framing AI as something the team must embrace uncritically. - Watch for over-reliance bias — celebrate speed gains but always weigh them against code quality, security, and long-term maintainability. - Give quieter or junior team members a chance to share how AI affects their learning and confidence, not just productivity. - Timebox each topic and prioritise a few high-impact actions so the session ends with clear, owned next steps. - Capture reusable prompts and tooling agreements during the retro so the team's collective learning is preserved. ## Icebreaker questions - If your AI coding assistant had a personality, who or what would it be? - What's the most impressive — or most ridiculous — thing AI has generated for you this sprint? --- # Chinese New Year Retrospective URL: https://www.teamretro.com/retrospective-templates/chinese-new-year-retrospective/ The Chinese New Year Retrospective uses traditional themes of renewal, gratitude, and aspiration to guide teams through a comprehensive review of their work and relationships. By incorporating elements of this ancient tradition, teams explore their achievements and challenges through a fresh cultural lens. The format encourages participants to honor past accomplishments, learn from setbacks, and set intentional goals for the future - mirroring the spirit of new beginnings that Chinese New Year represents. This retrospective is particularly powerful for fostering cultural awareness while maintaining focus on continuous improvement. It helps teams break free from conventional retrospective patterns by introducing rich metaphors and traditions that spark new insights and perspectives. ## Topics - **Year of Achievement**: What accomplishments made you proud this past cycle? - **Fortune and Wisdom**: What valuable lessons did we learn? - **Spring Cleaning**: What should we leave behind as we move forward? - **New Year Wishes**: What positive changes should we implement? ## When to use - When you want to bring a fresh cultural perspective to your team's reflection process - During the actual Chinese New Year period to align with cultural celebrations - When teams need to make a clear break between past practices and future improvements ## Tips and tricks - Share some basic information about Chinese New Year traditions before starting to provide context - Use Chinese zodiac animals as metaphors for different types of challenges or successes - Encourage participants to think in cycles, like the Chinese calendar, rather than linear time - Consider using Chinese proverbs or wisdom as discussion prompts - Keep the atmosphere celebratory while maintaining focus on improvement ## Icebreaker questions - If you were a Chinese zodiac animal, which would you be and why? - What's your favorite way to celebrate new beginnings? --- # Marketing Campaign Retrospective URL: https://www.teamretro.com/retrospective-templates/marketing-campaign-retrospective/ A marketing campaign retrospective is a structured meeting where teams reflect on the outcomes, performance metrics, and lessons learned from a recently completed marketing initiative. By analyzing data, customer feedback, and team experiences, participants can identify areas of success, opportunities for improvement, and actionable insights to enhance future campaigns. This collaborative process encourages open discussion, fosters continuous learning, and drives strategic adjustments for more effective marketing efforts. It aligns teams, reinforces best practices, and empowers data-driven decision-making for optimal return on investment and brand reputation management. The marketing campaign retrospective originated from agile methodologies but has been widely adopted across industries to facilitate post-project reviews and continuous improvement cycles. ## Topics - **Campaign Performance**: How did the campaign perform against its goals and KPIs? - **Customer Feedback**: What did customers appreciate or find challenging about the campaign? - **Return on Investment**: How did the campaign's costs align with the generated revenue and business impact? - **Brand Impact**: How did the campaign affect our brand perception and reputation? - **Lessons Learned**: What insights and actionable learnings can we take from this campaign? ## When to use - After completing a major marketing campaign or initiative to evaluate its effectiveness and identify areas for improvement. - As part of a regular marketing review process to continuously refine strategies and tactics based on real-world performance data and customer insights. - When launching a new product, service, or brand to assess the impact of the go-to-market campaigns and make adjustments for future launches. - Following a significant shift in market conditions, customer behaviors, or competitive landscape to realign marketing efforts with evolving dynamics. - As part of a post-mortem analysis for underperforming or unsuccessful campaigns to diagnose root causes and prevent future missteps. ## Tips and tricks - Encourage open and honest feedback by creating a safe, judgment-free environment for constructive criticism and diverse perspectives. - Supplement quantitative data with qualitative insights from customer interactions, social media sentiment, and anecdotal experiences to gain a holistic understanding. - Involve cross-functional stakeholders, such as sales, product, and customer service teams, to capture a comprehensive view of the campaign's impact. - Prioritize actionable insights over assigning blame, focusing on what can be improved or replicated in future campaigns. - Document key learnings and decisions to build an institutional knowledge base and facilitate knowledge sharing across the organization. - Celebrate successes and recognize outstanding contributions to maintain team morale and motivation for continuous improvement. ## Icebreaker questions - If our marketing campaign was a movie, what genre would it be and why? - Share a creative or unconventional marketing campaign that caught your attention recently, and what made it memorable. --- # 4-Week Sprint Retrospective URL: https://www.teamretro.com/retrospective-templates/4-week-sprint-retrospective/ A four-week sprint covers a meaningful stretch of work, which makes the retrospective a powerful moment to step back and take stock of everything that has happened over the past month. Because the cycle is longer than a typical one- or two-week sprint, there is far more ground to cover — multiple deliverables, shifting priorities, evolving team dynamics, and longer-term trends that only become visible across an extended timeframe. The 4-Week Sprint Retrospective gives teams a structured way to surface what worked, what slowed them down, and what they want to carry forward into the next cycle. This format works by guiding the team through a clear sequence of reflections: celebrating wins, examining challenges, identifying lessons learned, and committing to concrete improvements. By reviewing a full month at once, teams can spot patterns that shorter retrospectives might miss — recurring blockers, gradual process drift, or sustained behaviours worth reinforcing. Running it in TeamRetro keeps everyone aligned, captures input from remote and in-person participants equally, and turns discussion into trackable action items. The benefits are both immediate and cumulative. In the short term, the team leaves with a shared understanding of how the sprint went and a focused list of next steps. Over time, the cadence of monthly reflection builds a culture of continuous improvement, stronger collaboration, and better delivery predictability. It is especially valuable for teams running longer agile or Scrum cycles who want their retrospectives to match the rhythm of their work. ## Topics - **What went well**: What achievements and wins should we celebrate this sprint? - **What slowed us down**: Which blockers, friction points or challenges held us back? - **What we learned**: What insights or lessons can we take from this sprint? - **What to improve next sprint**: What concrete actions will we take into the next cycle? ## When to use - Your team works in monthly or four-week delivery cycles and needs a retrospective that matches that cadence. - You want to spot longer-term trends and recurring blockers that shorter retrospectives tend to miss. - You're wrapping up a significant chunk of work and want to celebrate wins while planning concrete improvements. - Onboarding a new agile or Scrum team that runs longer sprints and needs a structured reflection routine. ## Tips and tricks - Because a month is a long time, ask people to skim their boards, commits or notes beforehand so earlier-week events aren't forgotten. - Timebox each topic to keep the session focused — longer sprints can tempt teams into unfocused, sprawling discussions. - Limit improvement actions to two or three high-impact items so the team can realistically deliver on them. - Assign a clear owner to every action and revisit them at the start of the next retrospective to build accountability. - Rotate the facilitator role each cycle to keep perspectives fresh and reduce facilitator bias. - Use anonymous input to encourage honest feedback about blockers, especially around team dynamics or cross-team dependencies. ## Icebreaker questions - If you had to sum up the last four weeks in a single GIF or emoji, what would it be? - What's one thing outside of work that kept you energised this past month? --- # Bug Busters Retrospective URL: https://www.teamretro.com/retrospective-templates/bug-busters-retrospective/ Every team knows the frustration of recurring defects, sneaky regressions, and the time lost chasing down issues that could have been prevented. The Bug Busters Retrospective puts quality front and centre, giving your team a structured space to investigate what causes bugs, how they slip through the cracks, and what habits or safeguards can keep them out for good. Rather than treating defects as one-off annoyances, this format encourages your team to look at the bigger picture of testing, code quality, and collaboration. Running a Bug Busters session in TeamRetro is simple. The team works through focused columns that explore where bugs come from, how they were caught (or missed), what slowed down resolution, and what improvements can prevent them next time. Ideas are added, grouped, and voted on so the most impactful quality issues rise to the top. From there, you can capture clear, assignable action items to track in your next sprint. It's a practical, collaborative way to turn debugging frustration into continuous improvement. This retrospective is ideal for engineering teams, QA specialists, and product groups who want to reduce defect rates and build a stronger culture of quality. By making bug prevention a shared responsibility, your team strengthens testing practices, improves processes, and ships more reliable software with greater confidence. ## Topics - **Bugs We Squashed**: Which defects did we successfully catch and resolve? - **Bugs That Slipped Through**: Which defects reached production or were caught too late? - **What Slows Us Down**: What makes finding or fixing bugs harder than it should be? - **Prevention Plan**: What can we do to stop these bugs happening again? ## When to use - After a release or sprint with a higher-than-usual number of defects or escaped bugs. - When recurring or regression bugs keep resurfacing and the team wants to understand root causes. - As part of a broader quality initiative to strengthen testing and prevention practices. - Following a production incident where the team wants a blameless review of how the bug slipped through. ## Tips and tricks - Keep the tone blameless. Focus on systems, processes, and gaps rather than individuals who introduced bugs. - Bring data to ground the discussion, such as defect counts, escape rates, or time-to-resolution metrics. - Prioritise ruthlessly. Use voting to focus action items on the bugs and gaps with the biggest impact. - Make action items specific and assignable so prevention measures actually get implemented. - Invite QA, developers, and product together so quality is treated as a shared responsibility. - Revisit prevention actions from previous sessions to check whether they reduced recurring bugs. ## Icebreaker questions - What's the weirdest or funniest bug you've ever encountered? - If you could permanently delete one type of bug from existence, what would it be? --- # Goldilocks Retrospective URL: https://www.teamretro.com/retrospective-templates/goldilocks-retrospective/ The Goldilocks retrospective is a fun, story-based activity that encourages teams to reflect on their processes and identify areas for improvement. Inspired by the classic fairy tale, participants categorize their experiences as 'too hot' (things to stop or take up too much energy and time), 'too cold' (things to start or require more energy and effort), or 'just right' (things to continue). This light-hearted format creates a safe space for open discussion and helps teams find the 'just right' balance in their approach. By aligning their reflections with a familiar narrative, teams can gain valuable insights and develop actionable steps to optimize their workflow. Importantly, this is a chance for your team to discuss what "just right" means to them and that it is aligned with the organization. The Goldilocks retrospective is particularly useful for fostering continuous improvement, enhancing team dynamics, and promoting a culture of constructive feedback with the help of a classic fairy tale. ## Topics - **Too Cold**: What are the things that we should start doing? - **Just Right**: What are the things that we should continue doing? - **Too Hot**: What are the things we should stop doing? ## When to use - When you want to foster a culture of continuous improvement within your team. - After completing a major project or milestone, to reflect on what went well and what could be improved. - When you notice recurring issues or bottlenecks in your team's workflow. - To encourage open communication and constructive feedback among team members. ## Tips and tricks - Set a positive and lighthearted tone by embracing the Goldilocks theme with props or visuals. - Encourage participation from all team members, including quieter individuals. - Remind participants to focus on processes and practices, not individuals. - Rotate the Scrum Master. This will change the voices that are heard and give people a chance to contribute to the retrospective in a different way. - Follow up the retrospective with an action plan to address the identified areas for improvement. - Use a Return on Time Invested (ROTI) tool to monitor the effectiveness of your meeting. ## Icebreaker questions - If you were a character in the Goldilocks story, which one would you be and why? - What's your favorite fairy tale or childhood story, and why does it resonate with you? --- # Artificial Intelligence Arena Retrospective URL: https://www.teamretro.com/retrospective-templates/artificial-intelligence-arena-retrospective/ The Artificial Intelligence Arena retrospective gives teams a dedicated space to step back and reflect on how AI tools and practices are influencing the way they work. As more teams adopt large language models, copilots, automation, and machine learning into their daily routines, it becomes essential to pause and evaluate what's genuinely adding value, where new risks are emerging, and how the team can use these technologies more responsibly and effectively. This format turns the abstract conversation about AI into concrete, actionable insights grounded in your team's real experiences. Structured around four key areas, the retrospective explores the wins AI has delivered, the friction or limitations the team has hit, the risks and ethical considerations worth watching, and the experiments or opportunities the team wants to pursue next. Each participant shares observations and ideas, then the group groups, votes, and discusses the most important themes before committing to clear next steps. The result is a balanced view that celebrates progress while keeping a critical eye on quality, trust, and team well-being. Whether you're piloting a new AI coding assistant, integrating generative content into your workflow, or simply trying to make sense of a fast-moving landscape, the Artificial Intelligence Arena helps your team align on a shared understanding and a practical roadmap. It encourages curiosity, surfaces concerns early, and ensures that human judgement stays at the centre of how AI is adopted. ## Topics - **AI Wins**: Where has AI added real value for us? - **Friction & Limits**: Where has AI slowed us down or fallen short? - **Risks & Watchpoints**: What risks or concerns should we keep an eye on? - **Experiments & Next Steps**: What should we try or improve with AI next? ## When to use - After your team has adopted new AI tools and you want to assess what's working and what isn't. - When you need to align on a responsible AI usage policy or surface risks before they escalate. - Periodically as part of continuous improvement to track how AI is changing your team's workflows. - When deciding which AI experiments or investments to prioritise for the next quarter. ## Tips and tricks - Set clear ground rules that this is a balanced conversation, celebrating wins while honestly naming limits and risks. - Encourage specific, concrete examples rather than broad opinions about AI in general, so insights are actionable. - Give quieter team members and AI sceptics equal airtime, diverse perspectives prevent both hype and unfounded fear. - Timebox each topic so the discussion doesn't get stuck debating the same AI controversy. - Always close with owned, measurable next steps so reflection translates into real change. - Revisit previous experiments and risks at the next session to track progress and accountability. ## Icebreaker questions - If you could hand off one tedious part of your job to an AI tomorrow, what would it be? - What's the most surprising thing an AI tool has helped you with recently? --- # Pre-Launch Futurespective URL: https://www.teamretro.com/retrospective-templates/prelaunch-planning-retrospective/ Launching a new product or feature is one of the most exciting — and nerve-wracking — moments in any team's journey. The Pre-Launch Futurespective is a forward-looking team activity designed to help you step into the future of your launch and work backwards to ensure nothing is left to chance. Rather than reflecting on what has already happened, your team imagines the launch day and beyond, identifying the critical preparations that must be in place, the boosters that will amplify success, and the monitoring systems needed to catch issues early and celebrate wins. This futurespective format draws on the power of prospective thinking — a technique used in risk management and innovation planning — to surface blind spots, align stakeholders, and build shared ownership before the pressure of launch day arrives. By exploring what "ready" truly looks like, what could accelerate momentum, and how the team will know if things are going well (or not), teams leave the session with a clear, prioritized action plan rather than a vague sense of optimism. Whether you're shipping a major product release, rolling out a new feature to customers, or preparing for a go-to-market moment, the Pre-Launch Futurespective gives your team the structured space to think ahead together. It's especially powerful when run one to two sprints before launch, giving you enough runway to act on what you discover. Use it to align cross-functional teams, surface hidden risks, and build the confidence that comes from knowing you've thought it through. ## Topics - **Critical Preparations**: What must be done before we can launch? - **Boosters**: What will accelerate our launch success? - **Monitoring & Signals**: How will we know if the launch is succeeding or struggling? - **Risks & Unknowns**: What could go wrong or catch us off guard? ## When to use - Your team is 1–4 weeks away from a significant product or feature launch and wants to ensure nothing critical has been overlooked. - You're coordinating a cross-functional launch involving engineering, marketing, sales, and support, and need a structured way to align everyone on readiness. - Your team has experienced a difficult launch in the past and wants to be more intentional and proactive in their preparation this time. - You're launching into a new market or to a significantly larger audience than before, and the stakes of getting it wrong are higher than usual. - You want to build a repeatable launch readiness practice within your team and need a consistent framework to run before every major release. ## Tips and tricks - Run this futurespective 1–2 sprints before your target launch date — early enough to act on what you discover, but close enough that the details are real and concrete. - Invite cross-functional participants including engineering, product, design, marketing, and support. Launch readiness is a team sport, and blind spots often live at the boundaries between functions. - Use dot voting or priority ranking on the Critical Preparations and Risks topics to ensure the team focuses on the highest-impact items first, rather than trying to solve everything at once. - Avoid letting the session become a status update meeting. If someone raises a preparation item that's already done, acknowledge it and move on — the goal is to find gaps, not rehearse what's complete. - Assign clear owners and due dates to every action that comes out of the session before you close. A futurespective without follow-through is just wishful thinking. - Revisit the Monitoring & Signals topic outputs after launch to run a quick post-launch review — it's a great way to close the loop and build your team's launch playbook over time. ## Icebreaker questions - If your launch were a rocket, what stage of the countdown are you at right now — and is everything go for launch? - What's the most memorable product launch you've ever witnessed (good or bad), and what made it stick in your memory? --- # Sweet Success Shop Retrospective URL: https://www.teamretro.com/retrospective-templates/sweet-success-shop-retrospective/ Step into the Sweet Success Shop, where your team reflects on the last sprint or project through the delightful lens of a candy store. Each topic represents a different treat on the shelf — the sweet successes worth savoring, the sour moments that left a bad taste, the half-baked ideas still in the oven, and the secret recipes worth sharing. This playful framing lowers defensiveness and invites honest, lighthearted conversation, making it easier for teams to open up about what truly worked and what needs reworking. The Sweet Success Shop retrospective works by guiding participants through a structured set of themed prompts in TeamRetro. Team members add their reflections to each shelf, group similar ideas, vote on the topics that matter most, and turn the richest discussions into clear action items. The metaphor keeps energy high and engagement strong, which is especially valuable for teams that find traditional retrospectives repetitive or stale. Beyond the fun, this format delivers real value: it surfaces both wins and pain points, reinforces a culture of appreciation, and ensures continuous improvement stays on the menu. Whether you run it at the end of a sprint, after a major release, or as a quarterly check-in, the Sweet Success Shop helps teams celebrate progress, learn from setbacks, and leave the meeting feeling motivated and connected. ## Topics - **Sweet Successes**: What went really well that we should celebrate? - **Sour Moments**: What left a bad taste and needs improving? - **Still in the Oven**: What ideas or work are half-baked and need more time? - **Secret Recipes**: What tips or practices should we share with the team? ## When to use - At the end of a sprint when you want a fun, energizing alternative to the standard format. - After a major release or milestone to celebrate wins and capture lessons learned. - When team morale is low and you want to lead with appreciation and positivity. - As a quarterly or end-of-project review to reflect on the bigger picture. - With newer or remote teams who benefit from a relaxed, themed icebreaker to encourage openness. ## Tips and tricks - Lean into the theme — use the candy-store framing to keep the mood light and lower defensiveness around tough topics. - Timebox each shelf so the conversation stays balanced and you don't spend all your time on the 'Sweet Successes'. - Reframe 'Sour Moments' as learning opportunities to keep the discussion blameless and constructive. - Use anonymous entry for sensitive topics so everyone feels safe sharing honestly. - Always convert your top discussions into clear, owned action items before closing the retro. - Rotate the facilitator each time to keep the format fresh and share ownership across the team. ## Icebreaker questions - If you were a candy or dessert, which one would you be and why? - What's the sweetest moment you had at work this sprint? --- # Cricket Retrospective URL: https://www.teamretro.com/retrospective-templates/cricket-retrospective/ The Cricket Retrospective transforms traditional agile retrospectives into an engaging sports-themed discussion using cricket terminology and concepts. Drawing inspiration from the world's second most popular sport, this format helps teams reflect on their performance through familiar cricket metaphors. Participants share their experiences using cricket-inspired categories: Runs represent progress, Boundaries highlight major achievements, Wickets identify obstacles, and Ducks acknowledge learning opportunities from failures. This approach makes retrospectives more engaging for teams, especially those familiar with cricket culture. This format is particularly effective in regions where cricket is popular, such as India, Australia, and the UK, but its clear metaphors make it accessible to anyone. The sports analogy helps create a positive atmosphere where both successes and failures can be discussed openly, much like analyzing a cricket match. ## Topics - **Runs**: What progress did we make? - **Boundaries**: What great outcomes did we deliver? - **Wickets**: What setbacks did we encounter? - **Ducks**: What failures did we learn from? ## When to use - When you want to make retrospectives more engaging for teams familiar with cricket or sports in general - After completing a significant project milestone or sprint where you need to analyze both successes and failures - When team morale needs a boost and you want to create a more playful atmosphere for feedback - In situations where you need to balance serious reflection with an element of fun ## Tips and tricks - Begin with a brief explanation of cricket terms for team members who might be unfamiliar with the sport - Use cricket scoring analogies to help quantify the impact of different observations - Encourage balanced participation by ensuring everyone gets a chance to 'bat' (contribute) - Keep a positive spirit even when discussing 'Wickets' and 'Ducks' by focusing on learning opportunities - Use cricket-themed timekeeping, like 'overs' (sets of 6 deliveries), to manage discussion time effectively - Consider using cricket sound effects or imagery to enhance the theme and maintain engagement ## Icebreaker questions - If your last sprint was a cricket match, what would be your playing position and why? - What's your favorite sporting moment that reminds you of our team's journey? --- # Valentine's Day Retrospective URL: https://www.teamretro.com/retrospective-templates/valentines-day-retrospective/ Spread a little love around your team with a Valentine's Day retrospective that blends celebration with meaningful reflection. Built around the themes of romance, relationships, and heartfelt appreciation, this seasonal format invites your team to recognise what they adore about how they work together, mend the things causing friction, and rekindle practices worth keeping. It's a warm, lighthearted twist on the classic agile retrospective that gets people talking openly while keeping spirits high. The Valentine's Day retrospective works by guiding your team through love-themed prompts that map onto familiar continuous improvement questions. From the things they're crushing on to the relationships that need a little repair, each topic creates a safe space to share genuine feedback wrapped in a fun, festive frame. Because it lowers the emotional barrier to honest conversation, it's especially effective for surfacing appreciation and addressing tension that might otherwise go unspoken. Whether you run it on or around February 14th, this retrospective is a great way to boost morale, strengthen team bonds, and turn a routine check-in into something memorable. The seasonal theming makes participation feel playful, while the underlying structure ensures you still walk away with concrete, actionable improvements to your team's ways of working. ## Topics - **What we love**: What do you adore about how the team worked? - **Crushing on**: What new ideas or practices are you excited to try? - **Heartbreaks**: What caused frustration or let the team down? - **Relationship goals**: What commitments will help us grow stronger together? ## When to use - Around February 14th when you want to add a seasonal, festive flavour to your regular team retrospective. - When team morale needs a lift and you want to emphasise appreciation and positive recognition. - When tension or friction has been building and a lighthearted frame can help surface it safely. - As a change of pace from your standard retrospective format to keep recurring sessions fresh and engaging. ## Tips and tricks - Lean into the theme with festive touches like heart emojis, a themed background, or a short love-song playlist to set a warm, playful mood. - Start with the 'What we love' topic to build psychological safety before moving to more candid feedback about heartbreaks. - Remind the team that heartbreaks are about issues and not individuals — keep feedback blameless and constructive. - Use anonymous brainstorming so quieter team members feel comfortable sharing honest feelings. - Group and vote on the most important items so you focus discussion where it matters most. - Close by turning 'relationship goals' into a small number of owned, time-boxed action items so the love translates into real change. ## Icebreaker questions - If your team had a relationship status this sprint, what would it be and why? - What's one small thing a teammate did recently that made your heart melt? --- # Go-To-Market Strategy Planning URL: https://www.teamretro.com/retrospective-templates/go-to-market-strategy-planning/ A Go-To-Market Strategy Planning session is a collaborative meeting where teams align on the key elements required for a successful product launch. This includes defining target markets, positioning, pricing, promotion strategies, sales channels, and post-launch support. The session aims to create a cohesive go-to-market plan that maximizes the product's potential for adoption and revenue generation. By involving cross-functional teams, it ensures that all aspects of the launch are considered and aligned with the overall business objectives. This template provides a structured framework for teams to explore and discuss critical factors influencing the product's market entry, enabling them to make informed decisions and develop a comprehensive go-to-market strategy. ## Topics - **Target Market**: Who are the ideal customers for this product? - **Positioning & Messaging**: How should we position and differentiate our product? - **Pricing Strategy**: How should we price our product for optimal adoption and revenue? - **Promotion & Marketing**: How can we effectively promote and market our product? - **Sales & Distribution**: How will we sell and distribute our product? - **Launch Roadmap**: What are the key milestones and timelines for our product launch? ## When to use - When preparing for a new product launch or introducing a significant update to an existing product. - When aligning cross-functional teams on the go-to-market strategy and ensuring a cohesive approach. - When evaluating market opportunities, competitive landscape, and customer needs to refine the product positioning and messaging. - When developing a comprehensive marketing and sales plan to drive product adoption and revenue generation. - When establishing timelines, milestones, and resource allocation for a successful product launch. ## Tips and tricks - Involve cross-functional teams, including product management, marketing, sales, and customer support, to ensure a holistic perspective. - Conduct thorough market research and competitive analysis to inform your go-to-market strategy and differentiate your product. - Align on clear objectives and success metrics to measure the effectiveness of your go-to-market efforts. - Be prepared to adapt and pivot your strategy based on market feedback and changing customer needs. - Ensure clear communication and alignment across teams to maintain consistency in messaging and execution. - Continuously monitor and analyze performance data to refine your go-to-market strategy and optimize for better results. ## Icebreaker questions - If our product was a celebrity, who would it be and why? - Share a memorable product launch experience, either as a customer or a team member, and what made it successful or challenging. --- # Logistics and Supply Chain Retrospective URL: https://www.teamretro.com/retrospective-templates/logistics-and-supply-chain/ The Logistics and Supply Chain Retrospective is a structured meeting for teams to review and discuss the performance of their logistics and supply chain operations. It provides an opportunity to identify areas of success, challenges faced, and potential improvements for future cycles. This retrospective follows the classic format of gathering insights into 'what went well', 'what didn't go well', and 'what could be improved'. However, the topics are tailored specifically to logistics and supply chain management, covering areas such as procurement, inventory management, transportation, warehousing, and distribution. By periodically conducting this retrospective, teams can continuously optimize their processes, enhance collaboration, and drive operational excellence within the logistics and supply chain functions. ## Topics - **Successful Deliveries**: What went well with our logistics and delivery operations? - **Inventory Challenges**: What inventory management issues did we face? - **Process Improvements**: What processes or systems need improvement in our supply chain? - **Collaboration and Communication**: How can we improve collaboration and communication within our supply chain team? ## When to use - At the end of a project, product launch, or major supply chain initiative to review the outcomes and identify areas for improvement. - On a regular cadence (e.g., quarterly or bi-annually) to continuously optimize supply chain operations and processes. - After experiencing significant supply chain disruptions or challenges to identify root causes and develop mitigation strategies. - When onboarding new team members or partners to align expectations and share best practices within the supply chain function. ## Tips and tricks - Encourage participation from all stakeholders involved in the supply chain, including procurement, logistics, operations, and customer service teams. - Foster an environment of open and honest feedback, where team members feel comfortable sharing both successes and challenges without fear of blame or criticism. - Use data and metrics to support observations and insights, but also consider qualitative feedback from team members and customers. - Prioritize action items and assign owners for implementing agreed-upon improvements or changes. - Follow up on action items from previous retrospectives to ensure continuous progress and accountability. - Consider inviting external partners, such as suppliers or logistics providers, to gain their perspectives and strengthen collaboration. ## Icebreaker questions - If you could be any mode of transportation, what would you be and why? - Share a memorable or funny experience you've had related to logistics or supply chain operations. --- # Marketing Campaign Futurespective URL: https://www.teamretro.com/retrospective-templates/marketing-campaign-futurespective/ A Marketing Campaign Futurespective is a collaborative planning session that brings together key stakeholders to strategize an upcoming marketing campaign. It combines learnings from past campaigns, brand messaging, target audience insights, and creative ideation to develop a comprehensive plan. The session encourages open discussion, leveraging diverse perspectives to identify effective strategies, techniques, and desired outcomes. Participants explore the brand's unique value proposition, target customer profiles, marketing channels, and performance metrics. By aligning goals and fostering cross-functional collaboration, a Marketing Campaign Futurespective ensures the campaign resonates with the intended audience and drives measurable results. ## Topics - **Campaign Goals**: What are the primary objectives for this marketing campaign? - **Target Audience**: Who are the key customer segments we want to target? - **Brand Messaging**: What are the key brand messages and value propositions we want to communicate? - **Marketing Channels**: Which marketing channels should we prioritize for this campaign? - **Campaign Strategies**: What specific tactics and creative approaches should we consider? - **Metrics and Measurement**: How will we measure the success of this marketing campaign? ## When to use - When planning a new marketing campaign or initiative to align stakeholders and develop a comprehensive strategy. - Before launching a product or service to create an effective go-to-market plan and generate buzz. - When seeking to revamp or refresh an existing marketing strategy to better resonate with the target audience. - When exploring new marketing channels, tactics, or creative approaches to stay ahead of industry trends. - When aligning cross-functional teams to ensure consistent messaging and a cohesive brand experience. ## Tips and tricks - Encourage diverse perspectives and open ideation to foster creativity and innovation. - Ensure alignment between marketing efforts and overall business objectives and KPIs. - Leverage data and insights from past campaigns to inform future strategies and avoid repeating mistakes. - Consider the customer journey and touchpoints to create a seamless, omnichannel experience. - Allocate resources effectively and prioritize high-impact tactics based on budget and timeline constraints. - Establish clear roles, responsibilities, and accountability for campaign execution and measurement. ## Icebreaker questions - If our brand was a famous celebrity, who would it be and why? - Share a memorable marketing campaign that resonated with you personally, and explain what made it impactful. --- # Arctic Expedition Retrospective URL: https://www.teamretro.com/retrospective-templates/arctic-expedition-retrospective/ Embark on a chilly adventure where your team charts its course across uncharted frozen terrain. The Arctic Expedition retrospective uses the metaphor of a polar journey to help teams reflect on what propelled them forward, what slowed them down, and how to survive the next leg of the trek. By framing the sprint or project as an expedition, teams can step back and view their progress with fresh perspective and a sense of shared adventure. This format works by guiding participants through four expedition-themed lenses: the supplies that kept them going, the blizzards that blocked their path, the icebergs that posed hidden risks, and the North Star that keeps them oriented toward their goal. Each lens prompts honest reflection while keeping the mood light and collaborative. The playful theme lowers defensiveness, encourages quieter team members to contribute, and turns problem-solving into a collective quest. The Arctic Expedition retrospective is ideal for teams looking to break out of standard retrospective formats and inject energy into their reflection sessions. It surfaces both achievements and obstacles, helps prioritise risks before they become crises, and aligns the team around a shared destination. Whether you are wrapping up a sprint, closing a project, or simply taking a seasonal pause, this themed retro keeps engagement high while delivering actionable insights. ## Topics - **Supplies**: What kept us going and fuelled our progress? - **Blizzards**: What storms slowed us down or blocked our path? - **Icebergs**: What hidden risks could threaten us ahead? - **North Star**: What goal should keep us oriented going forward? ## When to use - When you want to refresh a standard sprint retrospective with an engaging, themed format that re-energises the team. - When wrapping up a project or milestone and you want to capture both achievements and lurking risks. - When the team needs to proactively identify hidden dangers and technical debt before they cause problems. - When you want to align the team around a shared goal or direction after a period of intense work. - During seasonal or end-of-year sessions where a lighthearted theme boosts participation. ## Tips and tricks - Set the scene at the start by describing the expedition metaphor so everyone understands what each topic represents. - Timebox each column to keep momentum and prevent the discussion from drifting into one area for too long. - Encourage quieter members to contribute by inviting input on the Icebergs column, where surfacing hidden risks is everyone's job. - Group similar ideas together before voting so the team can prioritise the most important blizzards and icebergs. - Turn the North Star reflections into concrete action items with clear owners so insights translate into change. - Keep the tone playful but focused, ensuring blizzards are framed as challenges to solve rather than people to blame. ## Icebreaker questions - If you were heading on a real Arctic expedition, what one item would you absolutely have to pack? - Would you rather face a blizzard, a polar bear, or a week of total darkness, and why? --- # Harry Potter Themed Retrospective URL: https://www.teamretro.com/retrospective-templates/harry-potter-retrospective/ Step into the wizarding world and transform your team retrospective into an enchanting experience with the Harry Potter Retrospective. Inspired by the beloved series by J.K. Rowling, this themed retrospective uses the magic, mystery, and lessons of Hogwarts to help teams reflect on their sprint or project in a fun and memorable way. Whether your team is full of Gryffindors charging boldly ahead or Ravenclaws carefully analysing every detail, this format creates a safe and engaging space for honest conversation. The four topics draw on iconic elements from the Harry Potter universe — from the spells that worked in your favour to the dark forces that slowed you down. Teams explore what magical moments helped them succeed, what dark arts or obstacles got in the way, what potions or remedies could improve things, and what new spells or experiments they'd like to try next. This narrative framework makes it easier for team members to express themselves creatively, especially those who might otherwise hold back in traditional retrospective formats. Beyond the fun theme, the Harry Potter Retrospective drives real outcomes. By framing challenges as "dark forces" and solutions as "spells," teams can discuss difficult topics with a little more psychological safety and levity. It's a fantastic way to re-energise a team that's experiencing retrospective fatigue, onboard new members, or simply inject some magic into your regular agile ceremonies. Accio better teamwork! ## Topics - **Lumos! ✨**: What spells worked? What lit up our path? - **Nox! 🌑**: What dark forces blocked or hindered us? - **Polyjuice Potion 🧪**: What could we transform or improve next time? - **Expecto Patronum! 🦌**: What new spells should we try to protect and guide us? ## When to use - When your team is experiencing retrospective fatigue and needs a creative, themed format to re-engage and spark fresh conversations. - When onboarding new team members and you want an icebreaker-friendly retrospective that encourages participation in a low-pressure way. - When celebrating a major milestone or release and you want to reflect on the journey in a fun and memorable way. - When your team shares a love of Harry Potter or pop culture and you want to leverage that shared interest to build team cohesion. - When you want to encourage psychological safety by using metaphor and storytelling to make it easier to raise difficult topics. ## Tips and tricks - Set the scene before the session — share a Harry Potter-themed image or quote in the meeting invite to get the team in the spirit. A little context goes a long way in making the theme land well. - Encourage participants to lean into the theme when writing their ideas, but reassure them that plain language is equally welcome. The goal is reflection, not a creative writing contest. - Watch out for the theme overshadowing the substance. Keep the focus on actionable outcomes — the magic is a vehicle for honest conversation, not a distraction from it. - Use the Patronus topic (Expecto Patronum) to close the session on a positive, forward-looking note. Ensure every action item has a clear owner and due date before the meeting ends. - Be mindful of team members who may not be familiar with Harry Potter. Briefly explain each topic's metaphor at the start so no one feels excluded or confused. - If the team gets stuck on a topic, use prompting questions like 'What would Dumbledore advise here?' or 'What would a Hogwarts House do differently?' to spark new thinking. ## Icebreaker questions - Which Hogwarts House do you think your team belongs to, and why — Gryffindor, Hufflepuff, Ravenclaw, or Slytherin? - If you could use one spell from the Harry Potter universe to improve how your team works, what would it be and what would it do? --- # Broken Car Breakdown Retrospective URL: https://www.teamretro.com/retrospective-templates/broken-car-breakdown-retrospective/ Ever felt like your team is stuck on the side of the road while everyone else speeds past? The Broken Car Breakdown retrospective uses a vivid car metaphor to help teams pinpoint exactly what's slowing them down, what's broken, and what they need to get back up to speed. By framing your project as a journey, this format makes it easy and engaging for everyone to talk openly about obstacles, mechanical failures, and the fuel needed to keep going. Each part of the car represents a different aspect of your team's performance — the engine that drives you forward, the flat tyres that hold you back, the warning lights that signal trouble ahead, and the fuel that keeps you energised. Participants reflect on these themes and contribute their thoughts, which the team then groups, discusses, and turns into concrete improvements. This playful yet structured approach lowers the barrier to honest conversation, helping surface issues that might otherwise stay hidden under the hood. The Broken Car Breakdown is a fun alternative to a standard sprint retrospective and works brilliantly for teams that need to identify blockers and root out friction. It encourages a shared mental model — everyone understands what a broken car feels like — making it inclusive and approachable for technical and non-technical members alike. Use it to reinvigorate stale retrospectives, diagnose persistent problems, and agree on the maintenance your team needs to keep the journey smooth. ## Topics - **The Engine**: What is driving us forward and keeping us moving? - **Flat Tyres**: What is slowing us down or stopping us completely? - **Warning Lights**: What risks or early warning signs should we watch? - **Fuel**: What do we need to keep going and recover? ## When to use - When your team feels stuck or slowed down and you want a clear way to diagnose the blockers holding you back. - When standard retrospectives have become stale and you want an engaging metaphor to spark honest conversation. - When recurring problems keep resurfacing and you need to identify root causes and early warning signs. - After a difficult sprint or project phase where momentum dropped and the team needs to refuel and reset. - When onboarding new members who benefit from a shared, intuitive way to talk about team friction. ## Tips and tricks - Set the scene with the car metaphor at the start so everyone understands what each part represents before contributing. - Keep Flat Tyres and Warning Lights blameless — focus on processes and situations rather than individuals to avoid defensiveness. - Time-box each section so the team doesn't dwell too long on problems and leaves room to define Fuel actions. - Group similar ideas together before voting to surface the biggest issues and avoid duplicate discussion. - Make sure every Fuel item has a clear owner and next step, otherwise good intentions never leave the garage. - Encourage quieter team members to contribute by allowing anonymous input so all voices are heard. ## Icebreaker questions - If your team were a vehicle right now, what would it be — a sports car, a minivan, or a car up on bricks? - What's the longest road trip you've ever taken, and what kept you going? --- # The Family Circle Retrospective URL: https://www.teamretro.com/retrospective-templates/the-family-circle-retrospective/ The Family Circle retrospective is an innovative approach that uses family role metaphors to examine team dynamics and organizational growth. By mapping different aspects of team performance to familiar family roles, this technique helps teams explore their evolution, relationships, and future potential in an engaging and relatable way. This retrospective framework encourages participants to think about their team's journey through the lens of family dynamics - from new initiatives (Baby) to high-performing elements (Golden Child), established processes (Adult), wisdom gained (Grandparent), and future opportunities (Long Lost Relative). This structure creates a safe and intuitive space for teams to discuss various aspects of their work and relationships. The metaphorical approach helps teams identify patterns in their development, celebrate successes, acknowledge stable practices, learn from experience, and anticipate future challenges or opportunities. It's particularly effective for teams looking to understand their growth trajectory and strengthen their collaborative bonds. ## Topics - **Baby**: What is something new? - **Golden Child**: What is performing well? - **Adult**: What is stable and reliable? - **Grandparent**: What have we learned from? - **Long Lost Relative**: What is on the horizon? ## When to use - When teams need to assess their growth and evolution across different areas of work - During periods of significant change to understand what's new, stable, and changing - To help teams reflect on their journey and plan for future development - When you want to encourage more personal and relatable discussions about team dynamics ## Tips and tricks - Ensure psychological safety by establishing that all family roles are equally valuable and important - Use the family metaphor to make discussions more approachable, but don't force the analogy if it doesn't resonate - Encourage participants to think about the interconnections between different roles, just as in a real family - Keep the focus on constructive discussion rather than getting too caught up in the role metaphors - Consider rotating through topics multiple times to capture different perspectives and insights ## Icebreaker questions - If your current project was a family member, who would it be and why? - What's your favorite family tradition, and how might it apply to our team? --- # Strategic Roadmap Planning URL: https://www.teamretro.com/retrospective-templates/strategic-roadmap-planning/ A strategic roadmap planning retrospective is a collaborative exercise to define key objectives, set long and short-term goals, identify milestones, and establish KPIs for an upcoming initiative or project. This activity ensures alignment on priorities and a shared vision for success. The team works together to map out a comprehensive plan, breaking down complex goals into actionable steps. By involving all stakeholders, you create buy-in, surface potential roadblocks early, and build a roadmap that balances ambition with realistic timelines. This type of retrospective is commonly used in strategic planning cycles, project kickoffs, product roadmap sessions, and when re-evaluating priorities. It provides structure to an otherwise ambiguous process and keeps the team focused on measurable outcomes. ## Topics - **Key Objectives**: What are the core objectives driving this initiative? - **Long-Term Goals**: What major goals need to be accomplished over the next 1-3 years? - **Short-Term Goals**: What are the key deliverables to accomplish in the next 3-6 months? - **Milestones**: What are the major checkpoints or accomplishments along the way? ## When to use - When kicking off a new strategic planning cycle or major initiative that requires cross-functional alignment. - At the beginning of a large, complex project to map out a shared roadmap and success criteria. - When re-evaluating priorities or shifting strategic focus due to changes in the business landscape. - As part of an annual or quarterly planning process to align on the upcoming roadmap. ## Tips and tricks - Involve representatives from all key functions and get buy-in early to increase engagement. - Use visual roadmapping tools to illustrate dependencies, milestones, and progress over time. - Balance ambition with realistic timelines - don't overpromise and underdeliver. - Build in regular checkpoints to review progress, make adjustments, and celebrate wins. - Ensure goals are specific, measurable, and aligned with overall business objectives. - Identify potential risks, dependencies, and mitigation plans upfront. ## Icebreaker questions - If you could pick one superpower to help achieve our roadmap goals, what would it be? - Share a proud accomplishment from a past project that required strategic planning. --- # Basketball Retrospective URL: https://www.teamretro.com/retrospective-templates/basketball-retrospective/ The Basketball Retrospective transforms team reflection into an engaging sports-themed experience that resonates with both basketball fans and newcomers alike. Using familiar basketball terminology and concepts, this retrospective format creates an inviting atmosphere for teams to evaluate their performance and strategize for future success. Drawing inspiration from the dynamic nature of basketball, teams explore their achievements (Slam Dunks), uncertainties (Hang Time), challenges (Out of Bounds), and future strategies (Tactics). This approach encourages participants to think both individually and as a team, much like players on a basketball court. The basketball theme helps break down barriers and makes the retrospective process more approachable and enjoyable. Teams can easily relate their work experiences to basketball concepts, fostering open communication and creative problem-solving while maintaining a fun, competitive spirit. ## Topics - **Slam Dunks**: What were our point-scoring wins? - **Hang Time**: What is still up in the air? - **Out of Bounds**: What did not go so well? - **Tactics**: What play do we want to try next? ## When to use - When you want to energize a team that feels stuck or demotivated - For teams that respond well to sports analogies and competitive environments - During high-intensity project phases where clear wins and challenges need to be identified ## Tips and tricks - Keep the energy high like a basketball game - maintain good pace and engagement throughout the session - Encourage everyone to 'take shots' by contributing their ideas, even if they seem risky - Use the basketball theme to make feedback more playful and less personal - Create a 'timeout' system for when discussions get too heated or off-track ## Icebreaker questions - If your development style was a basketball move, what would it be and why? - Which famous basketball player's qualities would be most valuable in our team? --- # Superhero Retrospective URL: https://www.teamretro.com/retrospective-templates/superhero-retrospective/ The Superhero retrospective is an engaging and imaginative approach that uses superhero metaphors to explore team dynamics and performance. Created to make retrospectives more enjoyable and relatable, this format encourages teams to think about their work through the lens of comic book heroes. By framing the discussion around superhero concepts like powers, values, and nemeses, teams can openly discuss their strengths, challenges, and support systems in a fun and non-threatening way. This approach helps break down barriers and encourages more honest and creative feedback. The template is particularly effective for teams who enjoy creative metaphors and want to add an element of playfulness to their retrospectives while still gathering meaningful insights about their work and collaboration. ## Topics - **Our Values**: What do we stand for? - **Superpowers**: What are our strengths? - **Weaknesses**: Where might we be vulnerable? - **Evil Nemesis**: What makes our role harder? - **Sidekicks and gadgets**: Who or what supports us? ## When to use - When team morale needs a boost and you want to make retrospectives more engaging - After completing a challenging project to celebrate strengths and identify areas for growth - When onboarding new team members to help them understand team dynamics in a fun way - When teams feel stuck in a rut and need a fresh perspective on their challenges ## Tips and tricks - Encourage everyone to embrace the superhero theme and have fun with the metaphors - Keep a balance between playfulness and productive discussion - Use real superhero examples to help illustrate points and spark ideas - Create a psychologically safe environment where people feel comfortable sharing their 'weaknesses' - Document action items that emerge from each topic for follow-up - Consider using superhero-themed props or virtual backgrounds to enhance engagement ## Icebreaker questions - If you could have any superpower to help you in your role, what would it be and why? - Which superhero team (Avengers, Justice League, etc.) does our team most resemble and why? --- # The Master Baker URL: https://www.teamretro.com/retrospective-templates/the-master-baker/ The Master Baker retrospective uses a culinary metaphor to evaluate time management and effort allocation within teams. Drawing inspiration from the precise art of baking, this format helps teams identify activities that received too much attention, too little attention, or just the right amount of focus. Just as a master baker needs to perfectly time their creations, teams need to balance their time and resources effectively. This retrospective format encourages participants to think critically about how they're spending their collective time and energy, using familiar baking concepts to frame the discussion. This approach is particularly effective for teams struggling with time management or those looking to optimize their workflow. By categorizing activities as under-baked, perfectly baked, or overbaked, teams can easily identify areas requiring adjustment in their process. ## Topics - **Under-baked**: What did we not spend enough time on? - **Perfectly Baked**: What did we spend just enough time on? - **Overbaked**: What did we spend too much time on? ## When to use - When the team needs to evaluate and optimize their time management across different activities - After completing a significant project phase to assess time allocation effectiveness - When there's a sense that some activities are getting too much or too little attention - During periods of high workload when prioritization becomes crucial ## Tips and tricks - Encourage specific examples rather than general statements to make the discussion more actionable - Use timeboxing for each topic to avoid the irony of poor time management in a time management retrospective - Keep a parking lot for improvement ideas that arise during the discussion - Focus on systemic patterns rather than one-off incidents - End with clear, actionable items to adjust time allocation in the next sprint - Consider using relative sizing to compare time spent across different activities ## Icebreaker questions - If your last sprint was a baked good, what would it be and why? - What's your favorite recipe for success when working on challenging projects? --- # Sprint Review Feedback URL: https://www.teamretro.com/retrospective-templates/sprint-review-feedback/ The Sprint Review Feedback template helps teams reflect on their sprint review meetings and identify areas for improvement. It encourages open discussion on what went well, what could be improved, and how to make sprint reviews more effective and valuable for the team. This template is designed to foster continuous improvement in the team's agile practices, ensuring that sprint reviews remain a productive and insightful part of the development cycle. By regularly evaluating and refining the sprint review process, teams can enhance collaboration, transparency, and alignment with stakeholders. ## Topics - **What went well?**: Identify the positive aspects of the sprint review. - **What could be improved?**: Discuss areas where the sprint review process can be enhanced. - **How can we improve?**: Identify specific actions to enhance future sprint reviews. - **Additional Feedback**: Share any other thoughts or suggestions related to sprint reviews. ## When to use - After each sprint review meeting, to gather feedback and identify areas for improvement. - When the team feels that the sprint review process could be more effective or valuable. - As part of a regular cadence for continuous improvement of agile practices. - When introducing new team members or stakeholders to the sprint review process. ## Tips and tricks - Encourage open and honest feedback from all participants, fostering a culture of continuous improvement. - Assign a dedicated facilitator or note-taker to ensure all feedback is captured and addressed. - Prioritize and implement actionable improvements based on the feedback received. - Share the feedback and action items with the broader team and stakeholders for transparency. - Celebrate successes and recognize positive aspects of the sprint review process. - Follow up on previous action items to ensure continuous progress ## Icebreaker questions - If the sprint review was a movie, what genre would it be and why? - If you could add one unique element to the sprint review, what would it be? --- # Crisis Management Futurespective URL: https://www.teamretro.com/retrospective-templates/crisis-management-futurespective/ A Crisis Management Futurespective is a proactive exercise to identify potential risks, crises, or challenges that a team or organization may face in the future. It helps teams anticipate issues, develop contingency plans, and establish clear roles and communication channels to effectively manage crises before they occur. This futurespective encourages open discussion about potential threats, vulnerabilities, and areas of concern that could arise. By surfacing these issues in a structured format, teams can collaboratively analyze the likelihood and impact of each crisis scenario. They can then devise strategies to mitigate risks, allocate resources, and outline response protocols proactively. Regularly conducting Crisis Management Futurespectives fosters a culture of preparedness and resilience within an organization. It empowers teams to confidently navigate unforeseen circumstances before they happen, minimizing potential disruptions and protecting stakeholder interests. ## Topics - **Potential Crisis Scenarios**: What potential crises or challenges could our team/organization face? - **Impact Assessment**: What would be the potential impact of each crisis scenario? - **Mitigation Strategies**: What proactive measures can we take to mitigate or prevent each crisis scenario? - **Response Protocols**: How should we respond and communicate during each crisis scenario? ## When to use - When your team or organization operates in a high-risk environment or industry where crises are more likely to occur. - After experiencing a significant crisis or near-miss incident, to identify areas for improvement and better preparedness. - As part of regular risk management and business continuity planning efforts. - When introducing new products, services, or operations that may introduce new risks or vulnerabilities. - During times of organizational change or restructuring, which can create uncertainty and potential crises. ## Tips and tricks - Encourage open and honest discussions by creating a safe environment where participants feel comfortable raising concerns without fear of repercussions. - Involve a diverse range of perspectives, including representatives from different departments, levels, and areas of expertise, to ensure a comprehensive understanding of potential risks. - Regularly review and update crisis management plans as circumstances change, ensuring they remain relevant and effective. - Conduct periodic crisis simulations or tabletop exercises to test response protocols and identify areas for improvement. - Foster a culture of preparedness by regularly communicating the importance of crisis management and providing ongoing training and awareness programs. - Establish clear lines of communication and decision-making authority to enable swift and coordinated responses during actual crises. ## Icebreaker questions - If you could have any superpower to help manage a crisis, what would it be and why? - Share a personal experience where you had to navigate a challenging or unexpected situation. What did you learn from that experience? --- # Quarterly Sales Retrospective URL: https://www.teamretro.com/retrospective-templates/quarterly-sales-retrospective/ A quarterly sales retrospective is a structured meeting where sales teams review their performance over the past quarter, celebrate wins, analyze challenges, and identify actionable improvements for the upcoming quarter. This collaborative process fosters continuous learning, alignment, and strategic adjustments to drive better sales results. The retrospective typically covers key metrics, major deals won or lost, customer feedback, process inefficiencies, and team dynamics. By reflecting openly, teams can reinforce successful practices, address bottlenecks, and implement data-driven changes to their sales strategies, processes, and enablement. Regular sales retrospectives are a vital component of an agile sales methodology, helping teams adapt quickly to market shifts, customer needs, and competitive landscapes. When facilitated effectively, these sessions build trust, accountability, and a growth mindset within high-performing sales organizations. ## Topics - **Wins and Achievements**: What were our biggest sales wins this quarter? - **Challenges Faced**: What were the biggest obstacles or setbacks we encountered? - **Lessons Learned**: What key insights did we gain this quarter? - **Actions for Next Quarter**: What should be our key priorities for improving next quarter? ## When to use - To review your sales team's performance at the end of each quarter. - To identify areas for improvement and develop actionable strategies. - To foster a culture of continuous learning and growth within your sales organization. - To ensure alignment between sales goals, processes, and market dynamics. - To celebrate wins, build team morale, and reinforce successful practices. ## Tips and tricks - Encourage an open and blame-free environment for honest discussion. - Use data and metrics to guide the conversation objectively. - Assign a neutral facilitator to keep the retrospective focused and productive. - Ensure all voices are heard by involving reps from different teams and levels. - Prioritize a few high-impact actions rather than trying to change everything at once. - Follow up on committed actions in subsequent meetings to drive accountability. ## Icebreaker questions - If our sales team was a professional sports team, which one would we be and why? - Share a funny or memorable experience you had with a customer this quarter. --- # Rate of Improvement Retrospective URL: https://www.teamretro.com/retrospective-templates/rate-of-improvement-retrospective/ The Rate of Improvement (ROI) retrospective helps teams assess their velocity of progress across various areas. It encourages reflection on where efforts yielded the highest returns and where more focus is needed to drive faster improvement. By analyzing their rate of change, teams can strategically allocate resources to maximize growth. This retrospective aligns with agile methodologies by promoting continuous inspection and adaptation. It fosters a mindset of constant learning and empowers teams to course-correct swiftly. The ROI framework originated from lean manufacturing principles but translates well to knowledge work by measuring the speed of skill development and process optimization. ## Topics - **Highest ROI**: In which areas did we have the highest ROI? - **Lowest ROI**: In which areas did we have the lowest ROI? - **Potential ROI**: Where can we improve our ROI? ## When to use - When the team feels their progress has stagnated or slowed in certain areas. - After a major project or initiative to assess the efficiency of efforts. - Periodically to ensure continuous improvement and identify growth opportunities. - When a shift in strategy or priorities requires realigning the team's rate of change. ## Tips and tricks - Use quantitative metrics like cycle times, throughput, and escaped defects to substantiate claims of high or low ROI. - Avoid conflating high effort with low ROI - sometimes tackling complex challenges requires more investment. - Ensure psychological safety so the team feels comfortable surfacing areas of suboptimal progress. - Build accountability by converting potential ROI ideas into concrete action items with owners. - Consider this a supplement to other retrospective formats focused on processes, teamwork, or technical practices. ## Icebreaker questions - If our team was a vehicle, what would it be and why? - What's one new skill you've developed recently that boosted your productivity? --- # Sherlock Retrospective URL: https://www.teamretro.com/retrospective-templates/sherlock-retrospective/ The Sherlock Retrospective transforms team reflection into an engaging detective experience, inspired by the methodical problem-solving approach of literature's greatest detective, Sherlock Holmes. Using the power of deductive reasoning and careful observation, teams investigate their work processes, successes, and challenges. This format encourages participants to think like detectives, examining evidence (data and experiences), following clues (patterns and insights), and solving mysteries (challenges and opportunities). By framing retrospective discussions in investigative terms, teams can maintain objectivity while diving deep into complex issues. The structure promotes both analytical thinking and creative problem-solving, making it particularly effective for teams dealing with complex problems or seeking to understand root causes of recurring issues. The detective theme helps maintain engagement while ensuring thorough examination of team dynamics and project outcomes. ## Topics - **Case closed**: What did we solve? - **Clues**: What helped us on the way? - **Elementary**: What have we learned? - **Puzzles**: What remains a mystery? ## When to use - When the team needs to investigate complex problems or recurring issues - After completing a challenging project to understand what led to success or failure - When you want to encourage deeper analytical thinking in your retrospectives - When the team needs a fresh and engaging approach to problem-solving ## Tips and tricks - Encourage participants to bring evidence and observations to support their points, just like a detective would - Use the 'detective' theme to maintain objectivity and avoid blame - focus on facts and patterns - Allow sufficient time for 'investigation' - don't rush to conclusions without examining all the clues - Keep a 'case file' of actions and insights to track progress over time - Use probing questions to dig deeper into issues and uncover root causes - Create a safe space where team members feel comfortable sharing their observations and theories ## Icebreaker questions - If you were a detective, what would be your signature method for solving cases? - What's the biggest mystery you've solved in your professional life? --- # The Time Traveler Retrospective URL: https://www.teamretro.com/retrospective-templates/the-time-traveler-retrospective/ The Time Traveler retrospective offers teams a unique perspective on their work by exploring different temporal dimensions of their project journey. By examining the past, present, and future, teams can create meaningful connections between their experiences and aspirations. This retrospective format encourages participants to think chronologically about their work, helping them identify patterns, recurring challenges, and opportunities for growth. The structure naturally promotes both reflection on past experiences and forward-thinking planning, making it particularly effective for teams looking to bridge the gap between their historical learnings and future goals. The addition of the 'Time Loop' element adds a creative twist, allowing teams to identify valuable practices worth repeating and reinforcing positive behaviors that contribute to their success. ## Topics - **The Past**: What were your key moments in the last sprint? - **The Present**: What are you focused on right now? - **The Future**: What would you want to see in the future? - **Time Loop**: What is something you would do over and over? ## When to use - When the team needs to connect past experiences with future goals - During periods of significant change to maintain perspective on progress - When you want to identify patterns in team behavior and performance over time - To help the team appreciate their journey and envision their future ## Tips and tricks - Encourage participants to be specific with their examples rather than making general statements - Use timeboxing for each temporal dimension to maintain balanced discussion - Keep the focus on actionable insights rather than dwelling too long on past events - Help the team identify connections between past experiences and future aspirations - Use the 'Time Loop' topic to reinforce successful practices and behaviors - Consider using a timeline visualization to help track discussion points ## Icebreaker questions - If you could time travel to any moment in your career, where would you go and why? - What's one work habit you wish you could have started earlier in your career? --- # The Archer Retrospective URL: https://www.teamretro.com/retrospective-templates/the-archer-retrospective/ The Archer Retrospective uses archery metaphors to help teams reflect on their goals, achievements, and challenges. Drawing inspiration from the precise art of archery, this format encourages teams to examine their targets (objectives), celebrate their bulls-eyes (successes), analyze their missed shots (failures), improve their focus (future improvements), and identify external factors (the wind) that might affect their performance. This retrospective format is particularly effective for teams who appreciate visual metaphors and want to maintain a clear line of sight between their intentions and outcomes. By breaking down the retrospective into archery-themed components, teams can better understand their performance trajectory and make targeted adjustments for future success. The structured approach helps teams maintain clarity about their objectives while creating a balanced discussion about successes and areas for improvement. The archery theme naturally promotes concepts of precision, practice, and continuous improvement that are vital for high-performing teams. ## Topics - **The Target**: What were we aiming for? - **Bulls Eye**: Where did we hit the mark? - **Missed Shots**: Where were we off the mark? - **Focus**: What will help us focus for our next shot? - **The Wind**: What can cause us to go off target? ## When to use - When the team needs to clearly align their achievements with intended goals - After completing a significant project milestone or release - When the team wants to improve their precision in hitting targets and deadlines - When external factors are significantly impacting team performance and need to be addressed ## Tips and tricks - Start by clearly defining what success looks like - your target should be visible and understood by everyone - Encourage balanced discussion across all categories - don't spend too much time on missed shots - Use the 'Wind' category to identify risks early and develop mitigation strategies - Keep the focus on actionable improvements rather than dwelling on past misses - Document successful strategies identified in 'Bulls Eye' for future reference - Ensure all team members have a chance to contribute to each category ## Icebreaker questions - If your last sprint was an arrow, what kind of shot would it have been? - What's your favorite precision-requiring activity outside of work? --- # Book Club Retrospective URL: https://www.teamretro.com/retrospective-templates/book-club-retrospective/ The Book Club retrospective transforms your team's sprint review into an engaging literary journey, using storytelling elements to analyze team performance and experiences. By framing the sprint as a book, team members can explore events, challenges, and successes through a creative lens that encourages open dialogue and fresh perspectives. This format leverages familiar literary concepts like genres, plot twists, and character development to help teams reflect on their work in a more engaging and accessible way. It's particularly effective for teams who might feel stuck in conventional retrospective patterns or who want to inject creativity into their continuous improvement process. Originally inspired by the power of storytelling in organizational learning, this retrospective format helps teams identify patterns, celebrate achievements, and plan future improvements while maintaining an enjoyable and collaborative atmosphere. ## Topics - **Genre**: If the last sprint was a book, what genre was it and why? - **Plot Twists**: What were some of the key turning points in the last sprint? - **Key Characters**: Who were the key actors from our team that you want to acknowledge? - **Next Chapter**: What do we want to write in to our next chapter? ## When to use - When teams feel stuck in a rut with traditional retrospective formats and need a creative boost - After a complex sprint with multiple interconnected events that would benefit from a narrative approach - When you want to encourage more metaphorical thinking and creative problem-solving - To help teams that are struggling to open up about challenges in a direct way ## Tips and tricks - Start with a brief explanation of literary genres to help team members think metaphorically - Encourage people to build on each other's narrative elements to create a cohesive story - Keep a balance between creative expression and actionable insights - Use the storytelling format to discuss difficult topics in a less confrontational way - Document the 'story' to track patterns across multiple sprints - Consider reading out some responses in a storytelling voice to maintain the theme ## Icebreaker questions - If you could be any book character, who would you be and why? - What's your favorite plot twist from a book or movie? --- # Sprint Clinic Retrospective URL: https://www.teamretro.com/retrospective-templates/sprint-clinic-retrospective/ The Sprint Clinic retrospective uses a medical consultation metaphor to diagnose and treat team challenges. By framing issues as 'symptoms' and solutions as 'treatments,' teams can systematically identify root causes and develop effective remedies for their sprint challenges. This format helps teams think analytically about their problems while maintaining a lighthearted approach. Just as a doctor examines symptoms, makes a diagnosis, and prescribes treatment, teams work through their sprint issues methodically, from identification to resolution. The medical theme encourages teams to think holistically about their challenges, considering both immediate fixes ('treatments') and long-term improvements ('prevention'). This approach is particularly effective for teams who want to move beyond surface-level problem identification to develop sustainable solutions. ## Topics - **Symptoms**: What pains did you have in the last sprint? - **Diagnosis**: What could be the root causes? - **Treatment**: How can we treat or manage this? - **Follow Up**: How can we track progress and improvement? - **Prevention**: What can we do to stay well? ## When to use - When the team is facing recurring issues that need systematic analysis and resolution - After a particularly challenging sprint where multiple problems need to be addressed - When you want to encourage a more analytical approach to problem-solving - When the team needs to develop both short-term solutions and long-term preventive measures ## Tips and tricks - Keep the medical metaphor light and fun - it's meant to help structure thinking, not to make the session too clinical - Encourage everyone to contribute to each phase, as different team members may notice different symptoms or have unique solution ideas - Use the 'Prevention' phase to build sustainable practices rather than quick fixes - Document all agreed actions and assign owners to ensure follow-through - Consider using visual aids like charts or graphs to track improvements over time - Focus on systemic issues rather than individual performance ## Icebreaker questions - If your last sprint was a patient, what would its health status be on a scale of 1-10? - What's your favorite home remedy for fixing a broken process? --- # RPG Retrospective URL: https://www.teamretro.com/retrospective-templates/rpg-retrospective/ The RPG (Role-Playing Game) Retrospective transforms team reflection into an engaging adventure using familiar gaming concepts. By framing achievements as victories, improvements as character development, and challenges as boss battles, teams can approach retrospectives with renewed enthusiasm and creativity. This format taps into gaming mechanics that motivate players - achievement, progression, and overcoming challenges - and applies them to team improvement. It helps teams view their work through a fresh lens, making the retrospective process more engaging while maintaining its effectiveness. Particularly effective with software development teams and gaming enthusiasts, this format encourages participants to think metaphorically about their work, leading to more creative insights and memorable action items. ## Topics - **For The Win**: What were our achievements in the last sprint? - **Level Up**: What attributes should we level up next? - **Side Quests**: What side quests did we complete? - **Boss Fight**: What are the big challenges coming our way? ## When to use - When team morale needs a boost and you want to make retrospectives more engaging - With teams that enjoy gaming culture or need a fresh perspective on their work - When you want to encourage creative thinking about challenges and improvements - For teams that respond well to metaphors and alternative ways of framing discussions ## Tips and tricks - Keep the gaming references accessible - not everyone may be a hardcore gamer - Use visual aids like health bars or experience points to track progress on action items - Maintain a balance between fun and productivity - the format should enhance, not distract from, the retrospective's purpose - Consider creating character sheets for the team to track improvements over multiple sprints - Use gaming sound effects or music (quietly) to enhance the atmosphere - Rotate the 'Game Master' role to give different team members a chance to facilitate ## Icebreaker questions - If your current project was a video game, what genre would it be and why? - What's your favorite power-up or special ability in a game, and how could we apply that concept to our team? --- # News Magazine Retrospective URL: https://www.teamretro.com/retrospective-templates/news-magazine-retrospective/ The News Magazine retrospective transforms team reflection into an engaging journalistic format, encouraging participants to view their work through the lens of a news publication. This creative approach helps teams document their experiences, challenges, and achievements in a fresh and engaging way. By structuring feedback as headlines, current issues, and quotes, teams can better organize their thoughts and communicate their experiences effectively. This format makes it easier to identify important patterns and trends while maintaining an element of fun and creativity in the retrospective process. This template is particularly effective for teams who want to break away from traditional retrospective formats and encourage more creative expression. It helps surface both significant achievements and areas for improvement in a way that feels less formal and more engaging. ## Topics - **Headlines**: What do we want to tell everyone? - **Current Issues**: What topics are important and relevant? - **Fake News**: What assumptions turned out to be false? - **Quotes**: What would be a quote for the last sprint? - **Next Issue**: What ideas do we have for the next sprint? ## When to use - When you want to make retrospectives more engaging and creative for teams who may be experiencing retrospective fatigue - After completing a significant milestone or project phase where there are many different aspects to review and discuss - When you need to encourage more open and creative expression from team members who might be hesitant to share in traditional formats - For teams who want to practice different ways of articulating and documenting their experiences and learnings ## Tips and tricks - Encourage creativity in headline writing - the more engaging, the better the discussion - Set aside time for teams to 'research' their stories by reviewing sprint metrics and feedback before the session - Rotate the role of 'editor-in-chief' among team members to encourage different perspectives - Use real journalism techniques like the '5 W's' (Who, What, When, Where, Why) to structure discussions - Keep a 'publication archive' of past retrospectives to track patterns and progress over time - Consider creating a physical or digital 'magazine cover' to showcase the team's key achievements ## Icebreaker questions - If your last sprint was a newspaper headline, what would it be? - What's the most surprising 'breaking news' you encountered during this sprint? --- # Psychological Safety Retrospective URL: https://www.teamretro.com/retrospective-templates/psychological-safety-retrospective/ The Psychological Safety retrospective helps teams assess and improve their environment of trust, openness, and mutual respect. Based on Amy Edmondson's research at Harvard Business School, psychological safety is the belief that team members won't be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes. This template enables teams to reflect on current practices that contribute to psychological safety, identify potential threats, and develop actionable strategies to create a more supportive environment. By focusing on these aspects, teams can build stronger relationships, encourage innovation, and improve overall performance. Regular use of this retrospective format helps teams maintain awareness of their interpersonal dynamics and proactively address concerns before they become significant issues. ## Topics - **What have we done to create team safety?**: What actions or behaviors have helped you feel safe speaking up? - **What would make our team feel unsafe?**: Which situations or behaviors might prevent people from speaking up? - **What can we do to improve team safety?**: What specific actions could help build a more supportive environment? ## When to use - When forming a new team or onboarding new team members to establish healthy team dynamics - After experiencing conflicts or communication challenges within the team - During organizational changes that might impact team dynamics and trust - As a regular check-in (quarterly) to maintain and improve team psychological safety ## Tips and tricks - Create a judgment-free zone by establishing ground rules at the start of the session - Consider running this retrospective anonymously for teams that are just beginning to build psychological safety - Focus on behaviors and situations rather than individuals when discussing challenges - Follow up on action items from previous psychological safety retrospectives to show commitment to improvement - Use breakout sessions for larger groups to encourage more intimate discussions ## Icebreaker questions - Share a time when someone helped you feel more confident at work - What's one thing that makes you feel appreciated by your teammates? --- # Music Band Retrospective URL: https://www.teamretro.com/retrospective-templates/music-band-retrospective/ The Music Band Retrospective is a creative approach to help musical groups reflect on their performances, practice sessions, and overall dynamics. Drawing inspiration from the collaborative nature of music-making, this format encourages band members to discuss their experiences using musical metaphors and terminology. This retrospective framework helps bands identify areas of harmony and discord within their performances and relationships. By examining elements like rhythm, timing, and emotional impact, teams can better understand their strengths and areas for improvement. Particularly effective for musical groups, this format can also be adapted for any creative team looking to evaluate their collaboration and output through an artistic lens. It encourages honest feedback while maintaining a positive, constructive atmosphere that promotes group cohesion and artistic growth. ## Topics - **Rhythm And Flow**: What helped you find rhythm? - **Off-Beat**: What made you play off beat? - **Goosebumps**: What was your goosebump moment? - **Next Session**: What should we try for our next jam? ## When to use - After significant performances or recording sessions to evaluate what worked and what didn't - When the band is experiencing challenges with coordination or communication - During regular practice sessions to maintain continuous improvement - Before starting work on new material to align on approach and expectations ## Tips and tricks - Create a safe space where all band members feel comfortable sharing their thoughts, regardless of their role or experience level - Use specific examples from recent performances or practice sessions to make feedback concrete - Balance discussion of technical musical aspects with interpersonal dynamics - Keep a record of action items and review them at the next session - Encourage everyone to contribute, as different perspectives can lead to better solutions ## Icebreaker questions - What's your favorite song we've performed together and why? - If our band was a famous group from history, who would we be and why? --- # Plus Delta Retrospective URL: https://www.teamretro.com/retrospective-templates/plus-delta-retrospective/ The Plus Delta retrospective is a straightforward yet powerful approach to team reflection that focuses on two key aspects: what's working well (Plus) and what needs to change (Delta). Originally adapted from academic feedback methods, this format helps teams identify current strengths while targeting specific areas for improvement. This simple two-column structure makes it particularly effective for teams new to retrospectives or when time is limited. The 'Plus' column celebrates successes and reinforces positive practices, while the 'Delta' column (using the mathematical symbol for change) constructively addresses opportunities for improvement without the negative connotations of traditional 'pros and cons' formats. By maintaining a balanced view between positives and potential changes, teams can have productive conversations that acknowledge progress while driving continuous improvement. The format's simplicity helps keep discussions focused and action-oriented, making it easier to identify concrete next steps. ## Topics - **Plus**: What went well in the last sprint? - **Delta**: What changes could we make? ## When to use - When you need a quick, straightforward format that's easy for everyone to understand - For teams new to retrospectives who need a gentle introduction to structured feedback - When time is limited and you need to focus on essential feedback - During periods of change when you want to maintain what's working while identifying necessary adjustments ## Tips and tricks - Keep the focus on actionable changes rather than dwelling on problems without solutions - Encourage balanced participation by asking quieter team members to share their thoughts first - Use dot voting to prioritize which changes to tackle first if many items are identified - Maintain a positive tone by framing deltas as opportunities for improvement rather than criticisms - Document and follow up on agreed changes in the next retrospective to ensure continuity ## Icebreaker questions - What's one positive change you've noticed in the team since our last retrospective? - If you could instantly change one thing about our work process, what would it be? --- # Sports Day Challenge Retrospective URL: https://www.teamretro.com/retrospective-templates/sports-day-challenge-retrospective/ Bring the energy of a sports day into your team reflection. The Sports Day Challenge Retrospective reframes your meeting as a friendly competition, encouraging teams to celebrate their wins, acknowledge the hurdles they cleared, and plan their next race together. By tapping into the universal spirit of sport — teamwork, perseverance, and a healthy dose of competition — this format keeps reflection lively and inclusive for everyone involved. Each topic mirrors a stage of a sporting event, from warming up and reviewing your personal bests to spotting the hurdles and fouls that slowed you down. This playful structure helps surface honest feedback in a low-pressure way, making it easier for quieter team members to join the conversation. It works equally well for sprint retrospectives, project wrap-ups, or quarterly reviews where you want to boost morale and reconnect as a group. Whether your team thrives on competition or simply enjoys a change of pace from standard retro formats, the Sports Day Challenge keeps engagement high while still driving meaningful action items. Set the timer, line up at the starting blocks, and turn your retrospective into a memorable team event that celebrates progress and fuels continuous improvement. ## Topics - **Personal Bests**: What were our standout wins and achievements? - **Hurdles**: What obstacles slowed us down or tripped us up? - **Team Spirit**: How well did we work and support each other as a team? - **Next Race**: What should we train for and improve before next time? ## When to use - When team morale needs a boost and you want a fun, energising change from standard retrospective formats. - At the end of a sprint or project to celebrate achievements while still identifying blockers and improvements. - For team-building sessions where you want everyone, including quieter members, to engage and contribute. - During quarterly or milestone reviews where reconnecting as a group is as important as reviewing the work. ## Tips and tricks - Lean into the sporting theme — use a stopwatch for timeboxing and frame each topic as a stage of the event to keep energy high. - Start with Personal Bests to set a positive tone before moving into the more challenging Hurdles discussion. - Keep the competition friendly; the goal is collaboration and reflection, not pitting team members against each other. - Make sure remote participants are fully included by giving everyone equal time and using the voting features to surface shared priorities. - Group similar Hurdles together to spot recurring patterns, then turn the top ones into concrete actions in the Next Race section. - Close by celebrating with a few shout-outs so the session ends on an uplifting, motivating note. ## Icebreaker questions - If you could compete in any Olympic sport, which one would you pick and why? - What's your go-to victory celebration when you achieve something at work? --- # Fantasy Football League Retrospective URL: https://www.teamretro.com/retrospective-templates/fantasy-football-league-retrospective/ Every fantasy football season is a rollercoaster of bold drafts, lucky waiver pickups, heartbreaking injuries, and trades that either made you look like a genius or a chump. The Fantasy Football League Retrospective gives your league a fun, structured way to look back on the season together — celebrating the wins, laughing at the losses, and figuring out how to make next year even better. It turns the usual group-chat trash talk into something productive (while still leaving plenty of room for trash talk). Run through key moments of the season as a group: what draft picks paid off, which trades you regret, how your waiver wire strategy held up, and what league rules need tweaking before kickoff next year. Each member shares their reflections, the league votes on what matters most, and you walk away with action items — whether that's adjusting the scoring system, fixing the playoff format, or instituting a proper punishment for the last-place finisher. It's part celebration, part strategy session, and entirely about keeping your league competitive and fun. Whether you're a serious dynasty league or a group of friends in it for the bragging rights, this retrospective helps your commissioner and members align on what worked, what flopped, and what to change. Think of it as your end-of-season "league meeting" — minus the chaos of everyone talking over each other in the group chat. ## Topics - **What helped us win**: Which moves, picks or wins made your season? - **What flopped**: Which picks, trades or decisions backfired badly? - **League rules and format**: What rules, scoring or settings need to change? - **Next season goals**: What should we try or change for the next game? ## When to use - At the end of the fantasy football season to review results before everyone moves on. - During your pre-draft league meeting to lock in rule and format changes for the year ahead. - When the commissioner needs structured input from members instead of chaotic group-chat debates. - After a controversial trade, ruling, or playoff finish that the league needs to discuss as a group. ## Tips and tricks - Keep it fun and lighthearted — the goal is engagement, not a corporate meeting. Lean into the trash talk and inside jokes. - Use anonymous brainstorming so members feel free to call out unpopular rules or admit their own blunders without judgement. - Give every member equal airtime — don't let the loudest or most competitive players dominate the discussion. - Turn rule and format suggestions into clear action items, and use a league vote for anything that affects everyone. - Set a time limit per topic so the session stays snappy and you don't get stuck relitigating one controversial trade. - Capture the season's best and worst moments to build a fun league history that you can revisit year after year. ## Icebreaker questions - If your fantasy team had a walk-up song this season, what would it be and why? - What's the one waiver wire pickup or trade you'd undo if you had a time machine? --- # Independence Day Celebration Retrospective URL: https://www.teamretro.com/retrospective-templates/independence-day-celebration-retrospective/ Independence Day is more than fireworks and parades — it's a moment to pause, celebrate freedom, and appreciate how far we've come together. The Independence Day Celebration retrospective brings that same spirit of reflection and renewal into your team's world. It invites everyone to honor what they've achieved, recognize the freedoms and autonomy that empower great work, and rally around a shared vision for the future. Inspired by the themes of liberty, unity, and progress, this format encourages teams to look back at their declarations and milestones, acknowledge the people and decisions that helped them break free from old constraints, and identify where they still want more independence or support. It blends celebration with honest reflection, making it a feel-good yet purposeful activity that strengthens team bonds while uncovering meaningful insights. Whether you run it around a national holiday, the end of a major project, or simply when your team needs a morale boost, this retrospective creates space for gratitude, recognition, and forward-looking conversations. In TeamRetro, participants can contribute ideas, group similar themes, vote on what matters most, and turn reflections into clear action items that keep the momentum going long after the celebrations end. ## Topics - **Declarations**: What big wins or milestones should we declare and celebrate? - **Freedoms Won**: Where did we gain more autonomy, trust, or flexibility? - **Unsung Heroes**: Who or what deserves recognition for our success? - **Future Horizons**: What do we want to achieve next? ## When to use - Around Independence Day or other national holidays when you want a themed, morale-boosting team session. - At the close of a major project or milestone to celebrate achievements and recognize contributions. - When team energy is low and you want to refocus on wins, gratitude, and shared purpose. - As a quarterly or end-of-year reflection to honor progress and set ambitions for what's next. ## Tips and tricks - Set a celebratory tone from the start — this retrospective is meant to uplift, so lead with appreciation before diving into improvements. - Encourage specific, genuine recognition in the Unsung Heroes topic to avoid generic praise and ensure everyone feels seen. - Timebox each topic so the session stays energetic and balanced between celebration and forward-looking conversation. - Use anonymous contributions if your team is shy about self-praise, then group and discuss themes together. - Make sure quieter voices are heard — invite each person to add at least one declaration or shout-out. - Convert Future Horizons ideas into concrete action items with owners so the momentum continues after the celebration. ## Icebreaker questions - If your team had its own flag, what symbol or color would be on it and why? - What's one freedom — big or small — that makes your workday better? --- # Mother's Day Reflection URL: https://www.teamretro.com/retrospective-templates/mothers-day-retrospective/ Mother's Day is the perfect moment to pause and recognize the remarkable people who nurture, guide, and support us — both at home and in our teams. This reflection brings colleagues together to share heartfelt stories, express gratitude, and celebrate the qualities that great mothers embody, from patience and resilience to unconditional care. It's a warm, inclusive way to honor the influence of mothers and mother-figures while strengthening the bonds that make your team feel like family. Built around themes of appreciation, lessons learned, and acts of kindness, this Mother's Day reflection creates space for genuine connection. Each participant contributes memories, words of thanks, and ideas for paying it forward, helping the group celebrate together regardless of where everyone is located. The result is a meaningful, conversation-rich session that lifts morale and reminds everyone of the people who shape who we are. Whether you're marking Mother's Day with a fully remote team or an in-person gathering, this format helps facilitators guide a thoughtful, lighthearted, and emotionally rewarding discussion. It celebrates the women and caregivers in our lives, encourages empathy, and turns a special occasion into a memorable shared team experience. ## Topics - **Gratitude**: Who are you thankful for and why? - **Lessons learned**: What wisdom did a mother-figure pass on to you? - **Future memories**: How will you pay this kindness forward? ## When to use - Celebrating Mother's Day with your team as part of a community or culture-building activity. - Creating a warm, inclusive moment to recognize the mothers, caregivers, and mentors within and beyond your team. - Boosting morale and connection by sharing personal stories and expressing gratitude. - Marking a seasonal occasion in a way that strengthens team bonds, whether remote or in-person. ## Tips and tricks - Set an inclusive tone from the start — acknowledge that Mother's Day looks different for everyone and that all forms of mothering and caregiving are welcome. - Be sensitive to the fact that this day can be emotional for some. Let people share as much or as little as they feel comfortable with. - Lead by example — share your own reflection first to encourage openness and set a heartfelt tone. - Keep the session lighthearted and celebratory; balance touching moments with humour and warmth. - Capture the 'Paying It Forward' ideas as actions so the appreciation continues beyond the meeting. - Allow plenty of time for storytelling — these conversations are where the real connection happens. ## Icebreaker questions - If you could give every mum in the world one gift, what would it be? - What's a phrase your mum (or a mother-figure) said so often you can still hear it? --- # Hike to a Waterfall Retrospective URL: https://www.teamretro.com/retrospective-templates/waterfall-hike-retrospective/ Imagine your team's journey as a hike to a waterfall—a path filled with challenges, discoveries, and ultimately, a rewarding destination. This retrospective format uses the metaphor of hiking through varied terrain to help teams reflect on their recent work, identifying obstacles they've overcome, resources that sustained them, and the refreshing achievements they've reached together. The Hike to a Waterfall retrospective encourages teams to think about their progress as a journey with different stages. Just as hikers encounter steep climbs, rocky paths, and moments of rest, teams experience challenges, support systems, and victories. By framing reflection through this nature-inspired lens, team members can discuss their experiences in a fresh, engaging way that promotes honest conversation and collaborative problem-solving. This format works particularly well for teams who need to acknowledge both struggles and successes, while looking ahead to the next leg of their journey with renewed energy and clarity. ## Topics - **The Steep Climb**: What obstacles or challenges did we face on our journey? - **The Trail Supplies**: What resources, tools, or support helped us along the way? - **The Waterfall**: What achievements or wins did we reach that feel refreshing? - **The Next Trail**: What should we prepare for or do differently on our next journey? ## When to use - After completing a challenging sprint or project phase where the team encountered significant obstacles but ultimately achieved their goals. - When team morale needs a boost and you want to celebrate the journey while acknowledging the difficulties faced along the way. - For teams transitioning between major milestones who need to reflect on what sustained them and what they learned before moving forward. - When you want to encourage creative thinking and fresh perspectives by using a nature-based metaphor instead of traditional retrospective formats. ## Tips and tricks - Set the scene by briefly describing the hiking metaphor at the start, helping team members understand how each topic relates to different parts of the journey. - Encourage team members to be specific about obstacles rather than vague—just as hikers note particular steep sections or rocky terrain, teams should identify concrete challenges. - Balance the discussion between difficulties and achievements to avoid dwelling too much on problems or glossing over genuine struggles. - Use the waterfall as a celebration moment—take time to acknowledge what the team has accomplished and let everyone share in the success. - Watch for team members who might dominate the conversation and ensure quieter voices are heard, perhaps by using silent reflection time before discussion. - Close the retrospective by looking ahead to the next hike—what will the team pack differently, what route will they take, and how will they support each other on the journey forward? ## Icebreaker questions - What's the most memorable hike or outdoor adventure you've ever been on, and what made it special? - If you could hike to any waterfall in the world, where would it be and who would you bring with you? --- # Tour de France Challenge Retrospective URL: https://www.teamretro.com/retrospective-templates/tour-de-france-challenge-retrospective/ Inspired by the world's most iconic cycling race, the Tour de France Challenge Retrospective turns your team reflection into an exhilarating ride through the peaks, valleys, and sprints of your last sprint or project. Just as cyclists battle gruelling mountain climbs, dangerous descents, and team breakaways, your team will explore the steep challenges they conquered, the moments where momentum carried them forward, and the mechanical breakdowns that slowed them down. This metaphor-driven format makes retrospectives memorable and fun while still surfacing the insights that matter. By mapping their experience onto stages of a race — the climbs, the downhills, the punctures, and the yellow jersey moments — team members are encouraged to think holistically about effort, pacing, teamwork, and recognition. The visual storytelling reduces blame and invites candour, helping even quieter members contribute their perspective. Themed retrospectives like this one keep agile ceremonies engaging and combat retro fatigue. The Tour de France Challenge is ideal when you want a high-energy session that celebrates wins, identifies obstacles, and builds the team spirit needed to keep the peloton moving toward the finish line together. ## Topics - **The Climbs**: What were the toughest uphill challenges we faced? - **The Descents**: Where did we gain momentum and things flowed easily? - **The Punctures**: What slowed us down or caused us to stop unexpectedly? - **The Yellow Jersey**: Who or what deserves recognition this stage? ## When to use - When your team needs a fun, energising retrospective to break the routine and beat retro fatigue. - After completing a demanding sprint or project with a mix of big wins and tough challenges worth celebrating and unpacking. - When you want to encourage recognition and team spirit alongside honest reflection on blockers. - During seasonal or themed sessions, such as around the actual Tour de France, to add extra topical relevance. ## Tips and tricks - Set the scene at the start by briefly explaining each cycling metaphor so everyone understands the stages before they contribute. - Lean into the theme with cycling imagery and language to keep energy high and make the session memorable. - Timebox each stage so the discussion stays balanced and the team doesn't spend the whole session only on The Climbs. - Make sure The Punctures section focuses on root causes and solutions rather than assigning blame to individuals. - Give everyone a chance to award a Yellow Jersey so recognition is distributed and inclusive, not dominated by a few voices. - Convert the biggest climbs and punctures into clear, owned action items so the next stage of the race goes smoother. ## Icebreaker questions - If your week were a Tour de France stage, would it be a flat sprint, a brutal mountain climb, or a relaxing recovery ride? - What's one thing that would have made your ride smoother this sprint — a better bike, a stronger team, or a clearer route? --- # Rings of Power Quest Retrospective URL: https://www.teamretro.com/retrospective-templates/rings-of-power-quest-retrospective/ Embark on an epic journey of team reflection with the Rings of Power Quest retrospective. Inspired by the timeless adventures of fellowship, courage, and overcoming great challenges, this themed retrospective transforms your sprint review into a memorable saga. Teams reflect on their quest by exploring the powers they forged, the perils they faced, the allies who supported them, and the path that lies ahead. It's a playful yet purposeful way to engage your fellowship and uncover meaningful insights. The Rings of Power Quest works by framing your team's recent work as a heroic adventure. Each theme prompts participants to share what empowered them, what dragons or obstacles threatened the mission, who or what helped them along the way, and where the quest should lead next. This narrative structure lowers barriers to honest conversation, sparks creativity, and helps teams discuss successes and challenges in a fresh, engaging context. The fantasy framing is especially effective for re-energizing teams who may feel fatigued by traditional retrospective formats. Beyond the fun, this retrospective delivers real value: it surfaces strengths to amplify, risks to mitigate, and opportunities to celebrate collaboration. By the end of the session, your fellowship will have a shared understanding of their journey and a clear set of actions to carry forward into the next chapter. It's an ideal format for team-building, milestone reviews, or simply injecting some adventure into your regular cadence. ## Topics - **Rings of Power**: What strengths and tools empowered the team? - **Dragons & Perils**: What obstacles or dangers threatened the mission? - **Fellowship & Allies**: Who or what helped the team along the way? - **The Road Ahead**: Where should the quest lead us next? ## When to use - When your team needs a fresh, fun format to break the monotony of standard sprint retrospectives. - After completing a major milestone or epic that feels like the end of a great quest. - For team-building sessions where you want to strengthen bonds and celebrate collaboration. - When morale is low and you want to re-energise the team with a playful, narrative approach. - For distributed or remote teams looking for an engaging way to connect and reflect together. ## Tips and tricks - Set the scene at the start by inviting everyone into the story — a short intro framing the sprint as a quest helps people embrace the theme. - Keep the fantasy framing light; the goal is honest reflection, so don't let the metaphor overshadow real, actionable insights. - Timebox each theme so the fellowship moves steadily and every voice is heard before discussion gets too deep. - Encourage quieter team members to contribute by celebrating allies and powers, which feel safer than naming problems. - Group similar dragons and perils together to find patterns and avoid repeating the same battles each sprint. - Always close with clear actions and owners from The Road Ahead so the quest continues with purpose. ## Icebreaker questions - If you could wield one magical power at work, what would it be and why? - Which fantasy character best represents how your week went, and why? --- # Post-Launch Retrospective URL: https://www.teamretro.com/retrospective-templates/post-launch-retrospective/ A post-launch retrospective is a structured meeting to review and analyze the outcomes of a major project or product release. It provides a valuable opportunity to celebrate successes, identify areas for improvement, and gather insights to inform future initiatives. The retrospective typically covers four key areas: What Went Well, Challenges Faced, Customer Feedback, and Improvements for Next Time. By openly discussing these topics, teams can learn from their experiences, build on strengths, and develop actionable strategies to enhance subsequent launches. Conducting a post-launch retrospective fosters a culture of continuous improvement, promotes transparency, and encourages cross-functional collaboration. It's a useful tool for driving innovation, refining processes, and delivering exceptional products and services that meet customer needs. ## Topics - **What Went Well?**: What aspects of the launch were successful? - **Challenges Faced**: What obstacles or difficulties did we encounter? - **Customer Feedback**: What feedback did we receive from customers? - **Improvements for Next Time**: What can we do better for future launches? ## When to use - After launching a new product, service, or major feature to evaluate the overall success and identify areas for improvement. - Following a significant project or initiative to capture lessons learned and insights for future endeavors. - Periodically, as part of a continuous improvement process, to foster a culture of learning and growth within the organization. ## Tips and tricks - Encourage open and honest feedback by creating a safe and judgment-free environment. - Involve cross-functional teams and stakeholders to gather diverse perspectives and insights. - Assign a dedicated note-taker to capture key points and action items during the retrospective. - Focus on actionable improvements rather than dwelling on past mistakes or assigning blame. - Prioritize the most impactful and feasible improvements for implementation in future launches. - Follow up on the identified improvements and track progress to ensure continuous improvement. ## Icebreaker questions - If you could describe the launch experience in one word, what would it be? - Share a memorable moment or anecdote from the launch that encapsulates the overall experience. --- # Yellowstone Expedition Retrospective URL: https://www.teamretro.com/retrospective-templates/yellowstone-expedition-retrospective/ Picture your team as a band of explorers trekking across the rugged wilds of Yellowstone — navigating geysers, dodging grizzlies, finding hidden trails, and reaching breathtaking summits. The Yellowstone Expedition retrospective turns your sprint or project review into an adventure-themed journey, encouraging your team to reflect on the highs, the hazards, and the surprises encountered along the way. By framing reflection as an expedition, you make it easier for people to open up about challenges and celebrate wins in a fresh, engaging context. This nature-inspired format works by mapping common retrospective themes onto vivid landmarks of the Yellowstone landscape. Geysers represent moments of sudden energy or breakthrough, grizzlies symbolise the risks and obstacles that caught the team off guard, hidden trails capture the unexpected discoveries and opportunities, and summits celebrate the goals you proudly achieved. This storytelling approach reduces meeting fatigue, sparks creativity, and helps quieter team members contribute through a playful, low-pressure lens. The Yellowstone Expedition retrospective is perfect for teams looking to break the monotony of standard retros while still surfacing meaningful, actionable insights. It builds psychological safety, strengthens team bonding, and keeps continuous improvement feeling fun. Whether you run agile sprints or wrap up a long project, this themed retrospective helps your team chart a clear path forward together. ## Topics - **Geysers**: What moments gave us a sudden burst of energy or breakthrough? - **Grizzlies**: What risks or obstacles caught us off guard along the way? - **Hidden Trails**: What unexpected discoveries or opportunities did we find? - **Summits**: What goals did we proudly reach and want to celebrate? ## When to use - When your team needs a refreshing, themed alternative to the standard sprint retrospective to combat meeting fatigue. - After completing a long or challenging project where reflecting on the full journey adds value. - When you want to boost team bonding and psychological safety through a playful, low-pressure format. - When quieter team members need an engaging metaphor to help them open up and contribute. ## Tips and tricks - Set the scene at the start by briefly explaining each landmark metaphor so everyone understands the theme before contributing. - Keep the 'Grizzlies' discussion blame-free — focus on lessons and early warning signs rather than pointing fingers. - Use anonymous brainstorming in TeamRetro to encourage honest input, then group and vote on the most important themes. - Timebox each topic to keep momentum and ensure you reach the action-planning stage. - End with concrete actions tied to the discoveries from 'Hidden Trails' and the obstacles from 'Grizzlies'. - Celebrate the 'Summits' genuinely — recognising wins is just as important as identifying improvements. ## Icebreaker questions - If you could explore any national park or wilderness in the world, where would you trek first? - What's the most adventurous or unexpected thing you've done outdoors? --- # Fairy Tale Adventure Retrospective URL: https://www.teamretro.com/retrospective-templates/fairy-tale-adventure-retrospective/ Once upon a time, your team set off on a quest filled with dragons to slay, treasures to find, and lessons to learn along the way. The Fairy Tale Adventure retrospective reimagines your sprint or project as a storybook journey, inviting teams to reflect through the playful lens of heroes, villains, magical helpers, and happily-ever-afters. By framing real events as narrative beats, this creative format lowers defenses and helps people surface honest insights they might otherwise keep to themselves. This retrospective works by mapping familiar fairy tale elements onto your team's recent experience. Participants describe the heroes who saved the day, the dragons and obstacles they faced, the magic and unexpected wins that helped them, and the moral of the story they want to carry forward. The storytelling structure makes abstract feelings concrete and gives quieter team members an engaging, low-pressure way to contribute. It's especially effective for breaking routine, energizing tired teams, and uncovering both wins and pain points in a memorable way. The beauty of a themed retrospective like this is that it keeps engagement high while still driving meaningful, actionable outcomes. Whether you're closing out a sprint, wrapping a major project, or simply want a fresh approach that sparks creativity and psychological safety, the Fairy Tale Adventure turns reflection into a story your team will actually want to tell — and learn from. ## Topics - **Our Heroes**: Who or what saved the day during this journey? - **Dragons & Obstacles**: What dragons did we have to battle along the way? - **Magic & Surprises**: What unexpected magic or luck helped us along? - **The Moral of the Story**: What lessons will we carry into the next chapter? ## When to use - When your team needs a refreshing break from standard retrospective formats and you want to re-energize engagement. - At the end of a sprint, milestone, or major project where reflecting through storytelling can surface richer insights. - When you want quieter or newer team members to contribute more comfortably through a playful, low-pressure structure. - To celebrate wins and acknowledge struggles in a memorable way that boosts morale and psychological safety. ## Tips and tricks - Set the scene early — open with a short narrative framing so everyone embraces the storybook theme and feels free to be creative. - Keep the playfulness anchored to real events; remind the team that every dragon and hero should map to something that actually happened. - Timebox each chapter so the storytelling stays energizing and you still reach the all-important 'moral of the story' actions. - Encourage equal participation by inviting quieter voices to name a hero or dragon, ensuring the narrative reflects the whole team. - Avoid letting the metaphor turn into finger-pointing — frame dragons as shared obstacles, not individuals. - Close by converting morals into clear, owned action items so the fun translates into real improvement next sprint. ## Icebreaker questions - If you were a character in a fairy tale, who would you be and what would be your superpower? - What's a childhood story or fairy tale that has stuck with you, and why? --- # Norm Kerth's Prime Directive Retrospective - Original Four URL: https://www.teamretro.com/retrospective-templates/norm-kerth-original-four-prime-directive/ The Prime Directive Retrospective, based on Norm Kerth's groundbreaking work in project retrospectives, creates a safe environment for teams to reflect honestly on their performance without blame or judgment. This powerful format centers around Kerth's original four questions that encourage teams to examine their experiences from multiple perspectives. At its core, this retrospective acknowledges that team members did the best they could with the knowledge, skills, and resources available to them at the time. By starting with this fundamental assumption, the Prime Directive creates psychological safety that allows for more honest and productive conversations about what happened and why. Teams can explore successes, challenges, insights, and opportunities for growth without defensiveness. The Prime Directive Retrospective is particularly valuable for teams dealing with challenging projects or difficult transitions, as it balances critical analysis with empathy. By focusing on learning rather than blame, teams can identify actionable improvements while preserving team cohesion and trust. Kerth's approach has become a cornerstone of effective retrospectives across industries because it consistently delivers meaningful insights that drive continuous improvement. ## Topics - **What did we do well?**: What achievements are you most proud of from this period? - **What did we learn?**: What insights or discoveries will you carry forward? - **What should we do differently?**: What changes would improve our performance next time? - **What still puzzles us?**: What questions or uncertainties remain unresolved? ## When to use - After completing a significant project milestone or release to capture learnings while they're still fresh. - When the team has experienced challenges or setbacks and needs a blame-free way to discuss what happened. - For teams that are new to retrospectives, as the structure provides clear guidance while encouraging meaningful reflection. - When team trust needs rebuilding, as the Prime Directive's emphasis on assuming positive intent helps create psychological safety. ## Tips and tricks - Begin by reading Norm Kerth's Prime Directive aloud: 'Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.' - Consider addressing the 'What still puzzles us?' question last, as it often builds on insights from the other questions and can help identify areas for future exploration. - Encourage participants to provide specific examples rather than generalizations to make the discussion more concrete and actionable. - If the team seems hesitant to share, try a round-robin approach where each person contributes at least one item to each category. - After gathering all reflections, prioritize the items in 'What should we do differently?' to create a focused improvement plan with clear owners and timelines. ## Icebreaker questions - If you could have one superpower to help the team perform better, what would it be and why? - What's one unexpected thing you learned during our last work cycle that surprised you? --- # Anchors & Engines Retrospective URL: https://www.teamretro.com/retrospective-templates/anchors-engines-retrospective/ The Anchors & Engines retrospective is a simple yet powerful way to reflect on what's helping or hindering your team's progress. By identifying the 'anchors' that are slowing you down and the 'engines' that are propelling you forward, you can make adjustments to improve your velocity and performance. Using the metaphor of being on a speedboat, the team imagines that they are heading towards their island destination. The boat is then the desired outcome or deliverable. A way to represent a sense of urgency is to imagine that there are people on the island who need to food and medical supplies. The goal is to get to the island on time. This activity encourages open and honest discussion about the factors impacting your team, both positively and negatively. It provides a structured format to gather insights, build shared understanding, and develop actionable steps for optimizing your processes and ways of working. Whether you're facing roadblocks, inefficiencies, or want to capitalize on your momentum, the Anchors & Engines retrospective offers a valuable opportunity for continuous improvement. ## Topics - **Anchors**: What factors are slowing us down or holding us back? - **Engines**: What factors are driving us forward and enabling our success? ## When to use - To identify and address bottlenecks, inefficiencies, or roadblocks impacting your team's progress. - To recognize and reinforce the practices, processes, and behaviors that are driving your team's success. - To foster open communication, shared understanding, and continuous improvement within your team. - To gather insights and perspectives from all team members, promoting inclusivity and diverse viewpoints. ## Tips and tricks - Encourage participation from all team members, ensuring everyone has a chance to contribute their perspectives. - Foster a safe and judgment-free environment where team members feel comfortable sharing honest feedback. - Prioritize the identified anchors and engines based on their impact and feasibility of addressing them. - Develop specific action plans to mitigate the anchors and reinforce the engines, assigning owners and timelines. - Follow up on the action items in subsequent retrospectives to track progress and ensure continuous improvement. - Consider involving stakeholders or subject matter experts if their input could provide valuable insights. ## Icebreaker questions - If our team were a vehicle, what kind would it be and why? - Share a recent 'anchor' or 'engine' moment you experienced outside of work. --- # Roller Coaster Retrospective URL: https://www.teamretro.com/retrospective-templates/roller-coaster-retropective/ The Roller Coaster retrospective transforms team reflection into an engaging adventure using theme park ride metaphors to explore project experiences. Drawing parallels between a roller coaster's dynamic journey and the team's sprint experience, this format helps teams discuss their highs, lows, and unexpected turns in a fun, approachable way. Participants share their experiences through five distinct perspectives: the thrilling 'ups,' challenging 'downs,' surprising 'loops,' successful practices they want to repeat ('again, again!'), and new directions for the future ('next ride'). This structure creates a safe space for honest feedback while maintaining an playful atmosphere that encourages open participation. This format is particularly effective for teams who appreciate creative approaches to reflection and want to maintain high energy levels during retrospectives. It helps transform potentially difficult conversations about challenges into constructive discussions framed within an engaging narrative. ## Topics - **Ups**: What were the high points of our last sprint? - **Downs**: What were the low points of our last sprint? - **Loops**: What surprised us? - **Again, Again!**: What do we want to continue doing? - **Next Ride**: What do we want to try next? ## When to use - When team morale needs a boost and you want to maintain high energy during reflection - After a particularly dynamic sprint with notable highs and lows - When you want to make retrospectives more engaging for teams experiencing meeting fatigue - For teams that respond well to creative and metaphorical approaches to problem-solving ## Tips and tricks - Start with a brief explanation of how roller coasters mirror project experiences - both have excitement, anticipation, challenges, and achievements - Use roller coaster sound effects or visuals to enhance the theme and maintain energy - Encourage participants to think of specific moments rather than general feelings - Keep the momentum going by time-boxing each topic to 5-7 minutes - End with concrete action items for improvement, not just discussion - Consider using virtual backgrounds of roller coasters for remote sessions to enhance the experience ## Icebreaker questions - What's your favorite amusement park ride and why? - If your last sprint was a roller coaster ride, what would you name it? --- # YouTube Creator's Corner Retrospective URL: https://www.teamretro.com/retrospective-templates/youtube-creators-corner-retrospective/ Running a YouTube channel is a creative marathon — between filming, editing, thumbnails, titles, analytics and community engagement, it's easy to keep sprinting without ever pausing to learn from what you've published. The YouTube Creator's Corner Retrospective gives your content team a dedicated space to step back, celebrate the videos that resonated, and unpack the ones that didn't quite land. Built for creators, editors, channel managers and growth strategists, this format walks your team through what performed well, what fell flat, the ideas bubbling up for future content, and the workflow friction slowing down your production pipeline. By reviewing watch time, click-through rates, audience retention and community feedback together, you turn raw analytics into shared insight and concrete next steps. It's equally useful for solo creators with a small support crew or fully-fledged media teams shipping multiple videos a week. The real value comes from turning reflection into momentum. Instead of guessing what your audience wants, you'll build a repeatable rhythm of reviewing, learning and iterating — so every upload gets a little sharper than the last. Run it after a content sprint, a campaign, or on a regular monthly cadence to keep your channel strategy aligned and your creative energy high. ## Topics - **Top Performers**: Which videos or content resonated most with our audience? - **Missed the Mark**: What content underperformed or didn't land as hoped? - **Fresh Ideas**: What new content, formats or experiments should we try? - **Production & Workflow**: What's slowing down our content pipeline or could run smoother? ## When to use - After publishing a batch of videos or completing a content sprint, to review what performed and plan the next round. - On a regular monthly cadence to keep your channel strategy aligned and learn from recent analytics. - Following a campaign, product launch or major collaboration to capture lessons while they're fresh. - When growth has plateaued and the team needs to diagnose what's working and what isn't. - When onboarding new creators or editors and you want to align everyone on content goals and workflow. ## Tips and tricks - Pull real channel analytics — watch time, retention curves, CTR and subscriber growth — into the session so reflections are grounded in data, not gut feeling. - Keep the 'Missed the Mark' discussion blame-free; frame underperformance as a learning opportunity for the whole team. - Timebox the brainstorm in 'Fresh Ideas' so the discussion doesn't spiral — capture everything, then prioritise the top few to action. - Give quieter team members like editors or thumbnail designers explicit space to contribute; their perspective on workflow is invaluable. - Turn the strongest ideas and workflow fixes into clearly owned action items with due dates so the retro drives real change. - Rotate the facilitator role between creators and crew to keep perspectives fresh and shared ownership high. ## Icebreaker questions - If your channel could collaborate with any creator on YouTube, who would it be and why? - What's the most random video you've fallen down a rabbit hole watching this week? --- # Vision and Mission Alignment URL: https://www.teamretro.com/retrospective-templates/vision-and-mission-alignment/ The Vision and Mission Alignment Retrospective is a structured activity that helps teams assess their progress towards achieving the organization's strategic vision and mission. It encourages open discussion around core values, long-term goals, and the steps needed to maintain alignment. By examining what has brought the team closer or further from their objectives, participants can identify key accomplishments, roadblocks, and areas for improvement. This retrospective fosters a shared understanding of the organization's purpose and direction, while generating actionable insights to course-correct as needed. This retrospective technique has proven valuable for teams across industries seeking to stay focused on their 'why' amidst the demands of daily operations. ## Topics - **Guiding Vision & Mission**: What are our organization's core vision and mission statements? - **Progress & Achievements**: What key accomplishments have moved us closer to our vision and mission? - **Obstacles & Misalignment**: What factors or decisions have pushed us away from our vision and mission? - **Path Forward**: What should we start, stop, or continue doing to better align with our vision and mission? ## When to use - When the team needs to realign their day-to-day work with the organization's overarching vision, mission and strategic goals. - After significant organizational changes, strategic shifts or during periods of growth and transformation to reaffirm the guiding principles. - To foster a shared understanding of the 'why' behind the work and reinvigorate commitment to the core purpose across the team. - When there is a perceived disconnect between stated values/goals and actual behaviors, decisions or outcomes within the organization. - To generate insights that can inform future strategic planning and ensure tighter alignment between initiatives and the vision/mission. ## Tips and tricks - Clearly communicate the purpose and importance of this retrospective to encourage open and honest dialogue. - Have the vision, mission and values statements easily accessible to reference throughout the discussion. - Create a safe space where participants feel comfortable respectfully challenging decisions or surfacing concerns. - Encourage diverse perspectives, as differing viewpoints can reveal blind spots or areas for improvement. - Assign a neutral facilitator to keep the conversation focused and productive, preventing conflicts or tangents. - Conclude by summarizing key takeaways and formulating a concrete action plan to address misalignments. ## Icebreaker questions - If our organization was a vehicle, which one would it be and why? - Share a quote, mantra or personal motto that resonates with our vision and mission. --- # Ada Lovelace Retrospective URL: https://www.teamretro.com/retrospective-templates/ada-lovelace-retrospective/ Ada Lovelace Day is the perfect occasion to reflect on your team's coding journey through the lens of the world's first computer programmer. [Ada Lovelace](https://en.wikipedia.org/wiki/Ada_Lovelace) was a visionary mathematician who saw the potential of Charles Babbage's Analytical Engine long before computers existed — and her spirit of curiosity, perseverance, and innovation lives on in every engineering team tackling complex problems. This retrospective invites your team to channel that same energy as you look back on your sprint with creativity and purpose. The Algorithmic Adventures of Ada Lovelace Retrospective is structured around four thematic topics that mirror the highs and lows of software development: celebrating breakthroughs, untangling bugs, powering through blockers, and charting the next algorithm. Each topic encourages honest, reflective conversation in a fun and engaging format that makes technical retrospectives feel fresh and meaningful. Whether your team cracked a tough problem or got stuck in an infinite loop, this template gives everyone a safe space to share and grow. This retrospective is ideal for engineering and development teams who want to go beyond the standard "what went well / what didn't" format. By grounding the conversation in Ada Lovelace's legacy, teams are reminded that even the greatest pioneers faced obstacles — and that learning from them is what drives progress. Use it to celebrate your team's technical wins, surface hidden bugs in your process, and collaboratively design the next iteration of your best work. ## Topics - **Breakthroughs 🚀**: What coding wins or innovations did we achieve? - **Bugs in the System 🐛**: What bugs or mistakes crept into our process or code? - **Infinite Loops 🔄**: What blockers or obstacles kept us stuck in a loop? - **Next Algorithm 📐**: What should we design or improve in our next iteration? ## When to use - Use after a sprint with notable technical achievements or challenges, when the team would benefit from a themed and energising retrospective format. - Ideal for engineering and development teams celebrating Ada Lovelace Day (second Tuesday of October) who want to honour her legacy through meaningful reflection. - Great for teams experiencing recurring technical debt, process bugs, or blockers that need to be surfaced and addressed in a psychologically safe environment. - Use when team morale needs a boost — the celebratory framing of breakthroughs and innovation helps reinforce positive momentum. - Suitable for any sprint retrospective where the team wants to move beyond standard formats and engage with a creative, narrative-driven approach to continuous improvement. ## Tips and tricks - Set the scene before the retrospective by sharing a fun fact about Ada Lovelace — for example, that she wrote what is considered the world's first computer algorithm in 1843. This primes the team for the theme and sparks curiosity. - Encourage a blame-free culture, especially in the 'Bugs in the System' topic. Remind the team that even Ada Lovelace encountered errors — what matters is how we learn from them, not who caused them. - Time-box each topic to keep energy high and avoid dwelling too long on any single issue. Aim for 10–12 minutes per topic, with the final 'Next Algorithm' topic getting slightly more time for action planning. - Make sure the 'Next Algorithm' topic results in concrete, assigned action items — not just vague intentions. Use TeamRetro's action item feature to capture owners and due dates before the session ends. - Watch out for the team focusing only on technical bugs and missing process or communication issues. Gently prompt participants to think beyond code: 'Are there any bugs in how we work together?' - If the team is large, consider grouping similar ideas before discussion to avoid repetition and keep the conversation focused. Dot voting can help prioritise which bugs and blockers to address first. ## Icebreaker questions - If you could give your code from this sprint a dramatic Ada Lovelace-era title — like 'A Note Upon the Analytical Engine's Capacity for Infinite Loops' — what would it be? - If Ada Lovelace could join your team for a day, which part of your tech stack do you think would impress her most — and which would horrify her? --- # Definition of Ready Retrospective URL: https://www.teamretro.com/retrospective-templates/definition-of-ready-retrospective/ A strong sprint begins long before the first line of code is written — it starts with a shared understanding of what "ready" really means. The Definition of Ready (DoR) Retrospective helps agile teams reflect on whether their backlog items are truly prepared before being pulled into a sprint. By examining the criteria that define a well-groomed story, teams can reduce mid-sprint surprises, minimize rework, and improve overall sprint predictability. This retrospective format guides teams through four key lenses: what their current Definition of Ready looks like, what's working well when stories meet it, what gaps or pain points arise when items aren't ready, and what changes the team should make to strengthen their DoR going forward. Whether you're a Scrum team, Kanban team, or any agile squad, this structured reflection helps you align on entry criteria and build a healthier, more efficient workflow. Inspired by the principles of Scrum and continuous improvement, the Definition of Ready Retrospective is ideal for teams that want to reduce sprint planning friction and deliver more consistently. Running this session in TeamRetro makes it easy to gather honest, anonymous feedback from every team member, surface patterns, and turn insights into actionable improvements — all in one collaborative space. ## Topics - **Our Current DoR**: What does our Definition of Ready look like today? - **When It Works**: What goes well when stories meet our Definition of Ready? - **When It Breaks Down**: What problems arise when stories aren't truly ready? - **Improve Our DoR**: What changes should we make to strengthen our Definition of Ready? ## When to use - Your team frequently encounters mid-sprint blockers, scope creep, or stories that can't be completed within the sprint — often a sign that items weren't truly ready when planned. - Sprint planning sessions are running long or feeling chaotic, suggesting the backlog isn't sufficiently groomed before the team commits to work. - You're onboarding new team members and want to establish or document a shared understanding of what 'ready' means in your context. - Your team has a Definition of Ready but hasn't reviewed it in a while, and it may no longer reflect how the team actually works. - After a particularly difficult sprint where unclear requirements or missing information caused significant delays or rework. ## Tips and tricks - Review your DoR before the session — share it with the team ahead of time so everyone comes prepared with concrete examples rather than vague impressions. - Avoid blame when discussing breakdowns. Frame the conversation around process gaps rather than individual mistakes to keep the discussion psychologically safe and productive. - Time-box each topic to keep the session focused. Definition of Ready discussions can easily spiral into full refinement debates — keep the retro at the meta level, not the story level. - Aim for 1–3 actionable DoR changes per session. Trying to overhaul everything at once leads to a DoR that's too complex to follow. Small, iterative improvements are more sustainable. - Involve the whole team, not just the Scrum Master or Product Owner. Developers, QA, and designers all experience the impact of unready stories differently — their perspectives are essential. - Follow up in the next retrospective. Check whether the DoR changes you agreed on actually improved sprint planning and delivery. Continuous refinement of the DoR is itself an agile practice. ## Icebreaker questions - If your backlog were a kitchen, would it be a well-stocked, organised pantry or a chaotic fridge full of mystery leftovers — and why? - What's one thing you wish you knew at the start of a task that you always seem to find out halfway through? --- # World Mental Health Day Retrospective URL: https://www.teamretro.com/retrospective-templates/world-mental-health-day-retrospective/ World Mental Health Day Retrospective creates a safe space for teams to discuss mental health challenges and support systems in the workplace. This structured dialogue helps teams identify stressors, celebrate positive mental health practices, and develop actionable strategies for improving workplace wellbeing. By focusing on mental health awareness and support, teams can build psychological safety and create an environment where everyone feels comfortable discussing their challenges. The format encourages honest conversations about work-life balance, stress management, and team support mechanisms. This retrospective helps organizations acknowledge the importance of mental health, reduce stigma, and implement practical solutions for maintaining team wellbeing. It aligns with modern workplace values and demonstrates commitment to employee mental health. ## Topics - **Mental Health Challenges**: What workplace factors are affecting your mental wellbeing? - **Current Support Systems**: What resources or practices help support your mental health? - **Improvement Ideas**: What changes could better support mental health at work? - **Personal Commitments**: What actions will you take to support mental health? ## When to use - During World Mental Health Day or Mental Health Awareness Week to align with global mental health initiatives - When teams are experiencing high stress or significant changes that impact wellbeing - As part of regular wellness check-ins to maintain focus on mental health support ## Tips and tricks - Create psychological safety by sharing guidelines for respectful discussion at the start - Remind participants that they can share at their comfort level - no pressure to disclose personal information - Have mental health resources readily available to share with the team - Focus on actionable improvements rather than dwelling on problems - Consider following up individually with team members who might need additional support ## Icebreaker questions - What's one small thing you did recently that positively impacted your wellbeing? - Share a wellness tip that has worked well for you in the past month --- # Content Strategy Retrospective URL: https://www.teamretro.com/retrospective-templates/content-strategy-retrospective/ A content strategy retrospective is a structured meeting where teams reflect on their content planning, creation, and distribution processes. It provides an opportunity to identify areas for improvement, celebrate successes, and align on future goals. This retrospective template is designed to facilitate open discussions around content strategy, including topics like audience engagement, content quality, channel effectiveness, and workflow optimization. By fostering honest feedback and collaboration, teams can refine their content strategy to better resonate with their target audiences and drive desired outcomes. ## Topics - **Audience Engagement**: How well did our content resonate with our target audiences? - **Content Quality**: How well did our content meet quality standards and expectations? - **Channel Effectiveness**: How effective were our content distribution channels? - **Workflow Optimization**: How can we improve our content planning and creation processes? ## When to use - When you want to evaluate the effectiveness of your content strategy and identify areas for improvement. - After completing a major content initiative or campaign, to assess its impact and learn from the experience. - At regular intervals (e.g., quarterly or annually) to ensure your content strategy remains aligned with your goals and audience needs. - When onboarding new team members or stakeholders, to align on current processes and gather fresh perspectives. - When considering significant changes to your content strategy, distribution channels, or target audiences. ## Tips and tricks - Encourage open and honest feedback by creating a safe, judgment-free environment. - Use data and metrics to support observations and insights, but also value qualitative feedback and personal experiences. - Assign a dedicated note-taker to capture key discussion points and action items. - Involve cross-functional team members and stakeholders to gather diverse perspectives. - Balance constructive criticism with celebrating successes and recognizing team efforts. - Prioritize actionable takeaways and assign owners for follow-up tasks or process improvements. ## Icebreaker questions - If our content strategy was a movie, what genre would it be and why? - Share a recent piece of content (from any source) that you found particularly engaging or memorable, and explain what made it stand out. --- # WRAP Retrospective URL: https://www.teamretro.com/retrospective-templates/wrap-retrospective/ The WRAP retrospective is a versatile reflection framework that helps teams explore four key dimensions of their work experience: Wishes, Risks, Appreciations, and Puzzles. This balanced approach combines forward-thinking aspirations with practical risk assessment, while fostering team recognition and addressing uncertainties. By examining wishes, teams can articulate their aspirations and improvements. The risks component helps identify potential obstacles and challenges. Appreciations create a positive atmosphere by acknowledging contributions, while puzzles surface areas that need clarification or resolution. This easy retrospective idea is based on a concept by Nick Oostvogel and aims to explore different aspects of a sprint or event. ## Topics - **Wishes**: Wishes for a perfect world going forward. - **Risks**: Things that could bring chaos. - **Appreciations**: People, teams or things you want to recognize. - **Puzzles**: Questions that remain unanswered. ## When to use - When you want to balance positive recognition with practical problem-solving - After completing a significant project milestone or release - When the team needs to address both opportunities and challenges - When you want to encourage both forward-thinking and risk awareness ## Tips and tricks - Start with Appreciations to create a positive atmosphere before diving into more challenging topics - Keep a parking lot for items that need further discussion or don't fit neatly into any category - Use dot voting to prioritize which items to discuss in detail if time is limited - Encourage everyone to contribute to each category to ensure diverse perspectives - Consider breaking larger teams into smaller groups for initial brainstorming - End by creating specific action items for addressing key risks and puzzles ## Icebreaker questions - If you could have one wish granted for the team right now, what would it be? - What's something you've been puzzled about lately that turned out to have a simple solution? --- # Strategic Alignment Review URL: https://www.teamretro.com/retrospective-templates/strategic-alignment-review/ A Strategic Alignment Review is a structured process for leadership teams to evaluate their organization's strategic direction, priorities, and readiness for execution. It provides a forum to reflect on progress, identify gaps, and realign efforts for maximum impact. This activity guides teams through a comprehensive analysis of their strategy, examining key areas such as vision, goals, resources, and capabilities. By fostering open dialogue and leveraging diverse perspectives, teams can uncover insights, address challenges, and ensure alignment across all levels of the organization. Regularly conducting Strategic Alignment Reviews is crucial for maintaining strategic focus, adapting to changing market conditions, and driving sustainable growth. This template draws inspiration from various strategic planning frameworks and is designed to facilitate productive discussions and actionable outcomes. ## Topics - **Vision**: Is our strategic vision still relevant and inspiring? - **Goals**: Are our strategic goals well-defined and achievable? - **Current Priorities**: Are our strategic priorities clearly defined and aligned? - **Organizational Capabilities**: Do we have the right capabilities to execute our strategy? - **Stakeholder Engagement**: Are we effectively engaging and aligning with key stakeholders? - **Risks and opportunities**: Are we effectively identifying and mitigating risks and seizing opportunities? ## When to use - During annual or biannual strategic planning cycles to review and realign organizational priorities and initiatives. - When facing significant market shifts, disruptive forces, or changes in the competitive landscape that necessitate a strategic realignment. - After major organizational changes, such as mergers, acquisitions, or leadership transitions, to ensure strategic alignment across the new entity. - As part of a comprehensive organizational transformation or change management initiative to ensure strategic alignment and buy-in across all levels. - When launching new strategic initiatives or entering new markets, to assess organizational readiness and identify potential gaps or risks. ## Tips and tricks - Encourage open and honest dialogue by creating a safe and inclusive environment for diverse perspectives to be shared. - Leverage data and insights from various sources, such as market research, customer feedback, and internal performance metrics, to inform the discussions and decision-making. - Involve cross-functional teams and subject matter experts to ensure a comprehensive understanding of the organization's capabilities, challenges, and opportunities. - Consider engaging external facilitators or consultants to provide an objective and fresh perspective on the organization's strategic alignment. - Establish clear action items and accountability measures to ensure that the insights and decisions from the Strategic Alignment Review are effectively implemented and monitored. - Schedule regular follow-up sessions to track progress, address emerging issues, and maintain strategic alignment as the organization evolves. ## Icebreaker questions - If our organization were an animal, what animal would it be and why? - If you could add one word to our organization's vision statement, what would it be and why? --- # Organizational Communication Review URL: https://www.teamretro.com/retrospective-templates/organizational-communication-review/ An Organizational Communication Review is a retrospective activity that helps teams evaluate the effectiveness of their communication practices and identify areas for improvement. It encourages open discussion about communication challenges, successes, and opportunities within the team and across the organization. This review promotes self-reflection and constructive feedback on communication channels, information flow, collaboration tools, and interpersonal dynamics. By addressing communication gaps and misalignments, teams can enhance transparency, alignment, and overall productivity. The activity originated from the principles of organizational communication theory, which emphasizes the importance of clear and effective communication for organizational success. It has been adapted for agile teams to foster continuous improvement in their communication practices. ## Topics - **Communication Channels**: How effective are our current communication channels? - **Information Flow**: How well does information flow within and across teams? - **Collaboration and Feedback**: How well do we collaborate and provide constructive feedback? - **Interpersonal Dynamics**: How well do we navigate interpersonal dynamics and conflicts? ## When to use - When there are recurring communication breakdowns or misunderstandings within the team or across the organization. - After a major organizational change or restructuring that may have impacted communication channels and information flow. - As part of a regular cadence (e.g., quarterly or annually) to proactively assess and improve communication practices. - When onboarding new team members or integrating teams after a merger or acquisition, to align on communication norms and expectations. - When there are signs of siloed thinking, lack of transparency, or misalignment across teams or departments. ## Tips and tricks - Encourage open and honest feedback by creating a safe and non-judgmental environment. - Involve representatives from different teams or departments to gain diverse perspectives on communication challenges. - Consider using anonymous feedback mechanisms to allow for more candid responses. - Prioritize action items and assign owners to ensure follow-through on identified improvements. - Revisit and refine communication practices regularly, as needs and team dynamics evolve over time. - Celebrate communication successes and share best practices across the organization. ## Icebreaker questions - If our team was a communication channel, which one would it be and why? - Share a funny or memorable miscommunication story from your experience. --- # Mid-Year Retrospective URL: https://www.teamretro.com/retrospective-templates/mid-year-retrospective/ The midway point of the year is the perfect moment to step back, take stock, and set your team up for a stronger finish. A Mid-Year Retrospective gives teams a structured way to celebrate progress, surface lessons learned, and recalibrate goals before the months ahead slip away. Rather than waiting until December to look back, this format encourages teams to course-correct while there is still plenty of runway to make meaningful change. Working through four focused areas — wins worth celebrating, challenges that held you back, lessons learned, and priorities for the rest of the year — the team builds a shared picture of where things stand and where they want to go. Each participant contributes their perspective, ideas are grouped and discussed openly, and the conversation naturally moves from reflection to action. The result is a clear, agreed-upon set of priorities that keeps everyone aligned and motivated. Whether you are a project team, a department, or an entire organisation, running a mid-year review in TeamRetro turns a routine check-in into an energising planning session. It reinforces what is working, addresses what is not, and re-engages everyone around the goals that matter most for the second half of the year. ## Topics - **Wins to celebrate**: What achievements and progress are we most proud of so far? - **Challenges faced**: What obstacles or setbacks slowed us down this year? - **Lessons learned**: What insights have we gained that should guide us going forward? - **Priorities for the second half**: What should we focus on to finish the year strong? ## When to use - At the midpoint of the year when teams want to assess progress against annual goals and recalibrate before the second half. - After a busy first half that leaves the team needing to celebrate wins and process challenges together. - When priorities have shifted and leadership wants to realign everyone around what matters most for the rest of the year. - As an alternative to waiting for an end-of-year review, giving the team time to course-correct while change is still possible. ## Tips and tricks - Set the context up front by sharing the goals or themes that were set at the start of the year, so reflections are anchored to real objectives. - Start with wins before moving to challenges — celebrating success first builds psychological safety and keeps energy positive. - Use anonymous brainstorming so quieter team members and dissenting views surface honestly, reducing groupthink and bias. - Time-box each topic to keep the conversation moving and ensure you reach planning rather than getting stuck in reflection. - Close by converting priorities into specific action items with owners and due dates so the retrospective drives real change. - Keep the priority list short and realistic — a focused handful of commitments is far more achievable than a long wish list. ## Icebreaker questions - If the first half of your year had a movie title, what would it be? - What is one word you'd use to describe your year so far, and why? --- # Summer Adventure Retrospective URL: https://www.teamretro.com/retrospective-templates/summer-adventure-retrospective/ Picture your team gathered around a campfire after a long expedition, swapping stories about the trails you conquered, the gear that saved the day, and the unexpected storms you weathered. The Summer Adventure Retrospective brings that same spirit of exploration to your team's reflection, using a sunny, journey-themed framework to make looking back feel more like an adventure than a chore. It's a refreshing way to break the routine of standard sprint reviews and inject some seasonal energy into your team's continuous improvement. The retrospective works by guiding your team through four themed topics inspired by a summer expedition — celebrating the high points you reached, identifying the obstacles that slowed you down, packing the essentials worth keeping, and mapping out where you want to explore next. Each metaphor invites honest, lighthearted conversation while still surfacing the actionable insights that drive real change. By framing reflection as a shared journey, teams often find it easier to speak openly, build trust, and walk away genuinely motivated. Whether you're wrapping up a sprint, closing out a quarter, or simply looking for a creative team-building activity during the warmer months, this engaging format helps you capture lessons learned and turn them into clear next steps. It's perfect for keeping morale high and momentum strong, ensuring every team member feels heard and every great idea makes it onto the map for the next leg of the adventure. ## Topics - **Sunny Summits**: What high points did we reach this time? - **Rocky Trails**: What obstacles slowed us down on the journey? - **Trusty Gear**: What essentials worked well and should we keep? - **Next Destination**: Where do we want to explore or improve next? ## When to use - At the end of a sprint or project when you want a refreshing, themed alternative to your usual retrospective format. - During the summer months or warmer seasons to boost morale and add seasonal energy to team reflection. - When team engagement feels low and you want a lighthearted way to encourage open, honest conversation. - As a quarterly or milestone review to celebrate the journey so far and map out the next leg. - For team-building sessions where you want reflection to feel fun and collaborative rather than routine. ## Tips and tricks - Lean into the adventure theme with summery visuals or a relaxed tone to set a playful, safe atmosphere from the start. - Time-box each topic so the session stays energetic and you leave enough room to agree on action items. - Make sure quieter team members get a chance to contribute by using silent brainstorming before group discussion. - Frame the 'Rocky Trails' topic around obstacles and learning rather than blame to keep psychological safety high. - Always convert the best ideas from 'Next Destination' into clear, owned actions with due dates so momentum carries forward. - Revisit the previous retro's actions at the start to celebrate progress and reinforce accountability. ## Icebreaker questions - If this past sprint were a holiday destination, where would it be and why? - What's the one item you'd never leave behind on a summer adventure? --- # Mountain Climber Retrospective URL: https://www.teamretro.com/retrospective-templates/mountain-climber-retrospective/ The Mountain Climber Retrospective transforms your team's journey into an engaging metaphorical climb to the summit. This powerful visualization technique helps teams identify their current position, obstacles ahead, and the tools needed for success. Teams collaborate to map their progress like mountaineers planning an ascent. By visualizing goals as peaks to conquer, teams gain clarity on their challenges, resources, and desired achievements. This approach makes abstract concepts tangible and creates a shared understanding of the path forward. The mountain climbing metaphor resonates particularly well with teams working on complex, long-term projects. It encourages both strategic thinking about the overall journey and tactical planning for immediate challenges while fostering a spirit of teamwork and resilience essential for reaching ambitious goals. ## Topics - **Base Camp**: Where are we now in our journey? - **Obstacles Ahead**: What challenges do we see on our path to the summit? - **Climbing Gear**: What tools and resources will help us succeed? - **Summit Goals**: What does success look like at the peak? ## When to use - When the team needs to visualize long-term goals and break them down into achievable milestones - After completing a major project phase to plan the next significant challenge - When team morale needs boosting through an inspiring goal-setting exercise ## Tips and tricks - Encourage the team to think both short-term (next steps) and long-term (summit goals) during the discussion - Use the mountain climbing metaphor to discuss the importance of team support and collaboration - Keep a parking lot for ideas that might be useful for future climbs or expeditions - Focus on actionable items that can be implemented in the next sprint or phase - Document the team's journey to reference and celebrate progress in future sessions ## Icebreaker questions - What's the most challenging goal you've ever achieved, and what helped you reach it? - If you could climb any mountain in the world, which would it be and why? --- # Team Icebreaker URL: https://www.teamretro.com/retrospective-templates/team-icebreaker-retrospective/ Every great team session starts with a moment of genuine connection. The Icebreaker Expedition guides your group through a series of light, playful prompts that help people open up, share a little about themselves, and arrive fully present before the real work begins. Think of it as a warm-up journey — a quick adventure that breaks down social barriers and sets a tone of trust and openness. Working through each topic, participants reveal something new about how they think, feel, and operate. The structure moves from simple, low-stakes questions toward more reflective and forward-looking prompts, gradually deepening engagement without ever feeling like an interrogation. This makes it ideal for newly formed teams, distributed groups who rarely meet face-to-face, or any meeting where energy and psychological safety could use a boost. The benefits go well beyond a few laughs. Strong icebreakers improve communication, surface shared interests, and reduce the friction that holds people back from contributing. By investing just a few minutes at the start, you create the conditions for more honest conversation, better collaboration, and a team that genuinely enjoys spending time together. ## Topics - **Set the Scene**: What's one word to describe how you arrived today? - **Share a Story**: What's a small win or fun moment from your week? - **Discover Common Ground**: What's something you'd love to learn or try this year? - **Look Ahead Together**: What are you most looking forward to as a team? ## When to use - At the start of a meeting or retrospective when you want to build energy and presence before diving into the work. - With newly formed teams who are still getting to know each other and building trust. - For distributed or remote teams who rarely meet face-to-face and need help feeling connected. - When team energy is low or engagement has been dropping and you want to re-spark enthusiasm. - Ahead of difficult or high-stakes conversations to establish psychological safety first. ## Tips and tricks - Keep it short and snappy — aim for five to ten minutes so the warm-up energises rather than eats into the main agenda. - Go first as the facilitator to model the level of openness you're hoping for and to put quieter members at ease. - Make sure everyone contributes, but never force anyone to overshare — keep prompts low-stakes and voluntary. - Match the tone to your team; a brand new group may need gentler prompts than a team that's worked together for years. - Call out shared interests and common ground as they emerge to spark connection and conversation. - Rotate who picks the icebreaker each session to keep things fresh and give everyone a sense of ownership. ## Icebreaker questions - If you could instantly master one skill for your next adventure, what would it be? - What's the most memorable trip or expedition you've ever been on? --- # Aussie Outback Escape Retrospective URL: https://www.teamretro.com/retrospective-templates/aussie-outback-escape-retrospective/ G'day mate! Chuck on a back pack and head bush with the Aussie Outback Escape, a themed team retrospective that turns your sprint reflection into a rugged adventure across the red dirt. Inspired by the vast, unpredictable Australian outback, this format invites your crew to map the terrain they've crossed, spot the watering holes that kept them going, dodge the dangers lurking in the scrub, and chart a course toward the next horizon. It's a refreshing change of scenery from the standard retrospective, giving teams a memorable narrative to hang their honest reflections on. The retrospective works by guiding participants through four outback-inspired themes that mirror the natural rhythm of a project review: celebrating progress, recognising what sustains the team, surfacing risks and obstacles, and setting a clear direction forward. This storytelling approach lowers the barrier to candid conversation, encourages playful yet meaningful input, and helps quieter team members engage through metaphor. By framing challenges as part of an expedition, teams build a shared sense of resilience and camaraderie. ## Topics - **Trails Blazed**: What progress and wins did we make this journey? - **Watering Holes**: What kept us refreshed, supported and going strong? - **Dangers in the Scrub**: What risks, blockers or hazards slowed us down? - **The Next Horizon**: Where do we head next and what should we change? ## When to use - When your team has grown tired of the same retrospective format and needs a creative, engaging way to re-energise reflection. - At the end of a long or particularly challenging sprint or project phase, to map the journey and reset for the road ahead. - When you want to build camaraderie and psychological safety through a playful, metaphor-driven conversation. - For teams looking to balance celebrating wins with honestly surfacing risks and blockers in a low-pressure setting. ## Tips and tricks - Set the scene at the start — lean into the outback theme with a short story to get everyone into the adventurous mindset. - Timebox each stage so the team spends enough energy on 'Dangers in the Scrub' and 'The Next Horizon' rather than only dwelling on wins. - Use anonymous brainstorming for the 'Dangers' topic so quieter or newer members feel safe raising hard truths. - Group and vote on ideas before discussing, so the team focuses its limited time on the highest-impact themes. - Always close by converting horizon ideas into clear, owned action items with due dates to ensure follow-through. - Keep the metaphor light — if it ever gets in the way of clarity, encourage people to speak plainly. ## Icebreaker questions - If you could survive the outback with only one item from your desk, what would it be and why? - What's the most adventurous or unexpected place you've ever worked from? --- # Witches and Warlocks Retrospective URL: https://www.teamretro.com/retrospective-templates/witches-and-warlocks-retrospective/ The Witches and Warlocks retrospective adds a magical twist to team reflection sessions, making the process more engaging and creative. By incorporating mystical elements like potions, spells, and crystal balls, this template encourages teams to think imaginatively about their experiences and future aspirations. This format transforms standard retrospective categories into magical elements: achievements become Love Potions, areas for improvement become targets for the Magic Wand, and future goals are viewed through the Crystal Ball. This playful approach helps teams break free from conventional thinking patterns and often leads to more honest and creative feedback. Particularly effective during Halloween season or when teams need to inject some fun into their retrospectives, this format maintains the serious purpose of continuous improvement while creating an atmosphere of creativity and engagement. ## Topics - **Love Potion**: What did we love about the last sprint? - **Magic Wand**: What do we want to transform? - **The Perfect Spell**: What should we aim for? - **Crystal Ball**: What do we see in our future? - **Owl**: What shout-outs do we want to send? ## When to use - When you want to make retrospectives more engaging and fun for teams feeling retrospective fatigue - During Halloween season or when you want to inject some creativity into your regular retrospective routine - When introducing new team members to retrospectives and want to make it less intimidating - When teams need encouragement to think more creatively about solutions and improvements ## Tips and tricks - Consider using magical sound effects or themed virtual backgrounds to enhance the experience - Encourage participants to use magical metaphors when describing their experiences - Keep a balance between fun and productivity - the magical theme should enhance, not distract from, the retrospective's purpose - Use the magical theme to help team members feel more comfortable sharing difficult feedback - Consider creating a 'spell book' of action items to track improvements over time - Rotate topic facilitation among team members to maintain engagement and shared ownership ## Icebreaker questions - If you could have any magical power to improve our team's work, what would it be and why? - What's your favorite magical creature and how does it represent your role in the team? --- # Fantasy Quest Retrospective URL: https://www.teamretro.com/retrospective-templates/fantasy-quest-retrospective/ Embark on an epic adventure to reflect on your team's journey through the lens of a fantasy quest. By reimagining your sprint or project as a heroic expedition, the Fantasy Quest retrospective invites teams to think creatively about the treasures they've gathered, the dragons they've battled, the allies who helped along the way, and the uncharted lands still ahead. This playful framing lowers defenses and encourages honest, imaginative reflection that traditional formats sometimes struggle to surface. The Fantasy Quest retrospective works by mapping familiar agile reflection themes onto a storytelling metaphor. Team members contribute ideas under each quest-themed topic — celebrating wins as treasures, naming challenges as dragons, recognising support as fellow adventurers, and looking forward to the next leg of the journey. The narrative structure makes retrospectives more memorable and engaging, which is especially valuable for teams that have grown weary of the same old "what went well / what didn't" format. It taps into the proven power of gamification and storytelling to boost participation and psychological safety. The goal is to keep teams energised about continuous improvement while still capturing actionable insights. Whether you run it at the end of a sprint, a major milestone, or a project launch, the Fantasy Quest format helps surface meaningful learnings in a way that feels collaborative and fun. It's ideal for community groups, creative teams, and any group looking to inject a little magic into their retrospective ritual. ## Topics - **Treasures Found**: What wins and victories did we collect on our quest? - **Dragons Faced**: What challenges and obstacles threatened our journey? - **Fellow Adventurers**: Who helped us along the way and how can we thank them? - **The Road Ahead**: What lands and quests await us next? ## When to use - When your team needs a fresh, fun twist to re-energise tired retrospective routines. - At the end of a sprint, major milestone, or completed project to reflect on the journey. - When you want to boost participation and psychological safety through playful storytelling. - With community groups or creative teams who enjoy gamified, narrative-driven reflection. ## Tips and tricks - Set the scene at the start — invite everyone to imagine the sprint as a heroic adventure to get into the spirit. - Keep the metaphor light and inclusive; if someone prefers plain language, let their contributions stand alongside the themed ones. - Timebox each quest stage so the storytelling stays fun without running long. - Use the 'Dragons Faced' stage to focus on problems, not people, keeping discussion blame-free. - Convert insights from 'The Road Ahead' into clear, owned action items before closing the retro. - Rotate the facilitator role so different team members can play the storyteller and keep the format fresh. ## Icebreaker questions - If you were a character in a fantasy quest, would you be the warrior, the wizard, the rogue, or the healer — and why? - What's one magical power you wish you had during the last sprint? --- # Battlefield Strategy Retrospective URL: https://www.teamretro.com/retrospective-templates/battlefield-strategy-retrospective/ Borrowing language from military strategy, the Battlefield Strategy retrospective reframes your team's work as a campaign with terrain to navigate, enemies to outmaneuver, and ground to capture. By looking at the last sprint or project through a tactical lens, teams gain a fresh, high-energy way to assess what helped them advance, what slowed them down, and where to concentrate their forces next. It's an engaging metaphor that cuts through routine and helps teams think strategically about both their wins and their obstacles. This format works by mapping reflections onto four strategic themes — the victories you secured, the enemy forces that resisted you, the allies and resources that gave you an edge, and the battle plan for the next campaign. Each theme invites the team to surface honest observations and then prioritise the moves that will have the biggest impact. The metaphor naturally encourages systems thinking: instead of listing isolated issues, participants consider position, momentum, and the alliances that determine whether a team wins or loses ground. The benefit of running Battlefield Strategy is that it makes retrospectives memorable and decisive. The vivid framing helps quieter team members contribute, sparks lively discussion, and turns vague frustrations into concrete tactical decisions. Run it in TeamRetro to capture ideas, group them by theme, vote on priorities, and walk away with a clear plan of attack for the next iteration. ## Topics - **Victories Won**: What battles did we win this campaign? - **Enemy Forces**: What obstacles fought back against us? - **Allies & Arsenal**: What support and tools gave us an edge? - **Battle Plan**: What is our strategy for the next campaign? ## When to use - When a team wants a fresh, energising alternative to a standard sprint retrospective. - After completing a major project or release that involved significant challenges and wins. - When the team needs to think strategically about obstacles and prioritise where to focus next. - To re-engage a team that has grown bored with routine retrospective formats. - When you want to turn recurring frustrations into a concrete, owned plan of action. ## Tips and tricks - Frame 'enemy forces' as situations and systems, never as individuals, to keep the conversation safe and constructive. - Set a time box for each theme so the discussion stays focused and the battle plan gets the time it deserves. - Use dot voting to prioritise which obstacles to tackle first — you can't fight every battle at once. - Make sure every action in the Battle Plan has a clear owner and a target date so it actually advances. - Invite quieter team members to contribute first; the playful metaphor lowers the barrier to speaking up. - Revisit the previous campaign's Battle Plan at the start to track progress and build accountability. ## Icebreaker questions - If your team were a military unit, what would your battle cry be? - Which historical or fictional commander would you want leading your next sprint, and why? --- # Incident Response Retrospective URL: https://www.teamretro.com/retrospective-templates/incident-response-retrospective/ An Incident Response Retrospective is a structured meeting to analyze recent incidents, identify areas for improvement, and develop action plans to enhance incident response processes. By reflecting on what went well, what didn't, and what could be done better, teams can continuously refine their incident management strategies. This retrospective format encourages open discussion, facilitates learning from experiences, and promotes a culture of continuous improvement within incident response teams. It helps teams identify root causes, streamline communication channels, optimize resource allocation, and implement preventive measures for future incidents. Regular Incident Response Retrospectives foster a proactive approach to incident management, enabling teams to stay agile and adapt to evolving challenges effectively. ## Topics - **Incident Overview**: What incidents occurred during the review period? - **What Went Well**: What aspects of the incident response were effective? - **Areas for Improvement**: What aspects of the incident response could be improved? - **Action Items**: What specific actions can we take to improve our incident response capabilities? - **Lessons Learned**: What valuable lessons can we take away from this incident? - **Stakeholder Feedback**: How can we improve communication and collaboration with stakeholders during incidents? ## When to use - After experiencing a significant incident or security breach to analyze the response and identify areas for improvement. - On a regular basis (e.g., quarterly or annually) to review incident response processes and ensure continuous improvement. - When introducing new technologies, systems, or processes that may impact incident response capabilities. - After major organizational changes or restructuring that affect incident response teams or processes. - As part of a comprehensive incident response training and preparedness program. ## Tips and tricks - Encourage an open and blameless environment to foster honest and constructive feedback. - Involve representatives from all relevant teams and stakeholders to gather diverse perspectives. - Use data and metrics from the incident to support observations and recommendations. - Prioritize action items based on their potential impact and feasibility of implementation. - Assign clear ownership and timelines for implementing agreed-upon improvements. - Follow up on action items from previous retrospectives to ensure continuous progress. ## Icebreaker questions - If you could have a superpower to help with incident response, what would it be and why? - Share a funny or memorable incident response experience (without revealing sensitive information). --- # Year in Review Retrospective URL: https://www.teamretro.com/retrospective-templates/year-in-review-retro-retrospective/ Wrapping up a year is the perfect moment to pause, celebrate wins, and learn from the bumps along the way. The Year in Review Retrospective gives your team a structured space to look back across the last twelve months, recognise the milestones that mattered, and surface the lessons that will shape a stronger year ahead. Unlike a fast-paced sprint retrospective, this format zooms out to the big picture so everyone can appreciate just how far they've come. Running a Year in Review in TeamRetro is simple and inclusive. Each participant reflects on highlights, challenges, lessons learned, and ambitions for the coming year, then the team groups, votes on, and discusses the themes that resonate most. This annual retrospective encourages honest dialogue, builds shared memory, and turns reflection into momentum. It's a great way to close out a year on a high note while setting clear intentions for what comes next. Whether you're a product team, leadership group, or community gathering, the Year in Review helps celebrate achievements, acknowledge growth, and align on priorities. By the end of the session your team will have a meaningful record of the year, a renewed sense of connection, and a list of action items to carry into the months ahead. ## Topics - **Highlights & Wins**: What were our proudest moments this year? - **Lessons Learned**: What did we learn that we'll carry forward? - **Goals for Next Year**: What do we want to achieve in the year ahead? ## When to use - At the close of a calendar or fiscal year to reflect on the past twelve months and set direction for the next. - When a team has completed a major program or initiative and wants to capture the bigger-picture learnings. - To re-energise and reconnect a team after a long, demanding period of work. - When onboarding new leadership who want to understand the team's recent history and trajectory. - For communities or organisations wanting to celebrate collective achievements and align on shared goals. ## Tips and tricks - Send a prompt ahead of time so participants can reflect on the whole year before the session — memories from January can be easy to forget. - Keep the celebration of wins front and centre; starting on a positive note sets the tone for honest conversation about challenges. - Timebox each topic so you don't spend the whole session reminiscing and run out of time for forward-looking goals. - Encourage equal participation by giving everyone quiet time to add ideas privately before grouping and discussing. - Turn 'Goals for Next Year' into clear, owned action items so the reflection translates into real momentum. - Capture a summary or export the board so the team has a lasting record of the year to revisit later. ## Icebreaker questions - If you could sum up your year in a single emoji, which one would it be and why? - What's one song that would be on the soundtrack of your past year? --- # Aussie Rules (AFL) Retrospective URL: https://www.teamretro.com/retrospective-templates/afl-retrospective/ The AFL Retrospective transforms team reflection into an engaging session using Australian Rules Football metaphors. Drawing inspiration from Australia's most popular sport, this format helps teams analyze their performance through familiar sporting concepts. Just as AFL teams review their game performance, this retrospective encourages participants to examine their achievements (goals), challenges (tackles), team excellence (Brownlow nominations), and overall objectives (Premiership Cup). The format creates an inclusive environment where team members can share feedback and insights using relatable sporting analogies. This approach is particularly effective in Australian workplaces and sports-minded teams, making the retrospective process more accessible and engaging through the lens of a beloved national sport. ## Topics - **Premiership Cup**: What are we striving to achieve? - **Goals**: What did we achieve? - **Tackles**: What obstacles and roadblocks did we encounter? - **Brownlow Nomination**: Who has performed well? ## When to use - When working with teams that have an interest in sports or AFL in particular - When you want to make retrospectives more engaging by using familiar sporting metaphors - When the team needs a fresh and fun approach to reflection - When you want to encourage healthy competition and team spirit ## Tips and tricks - Ensure all team members understand the AFL metaphors, or provide quick explanations for those unfamiliar with the sport - Keep the sporting analogies light and fun - don't let them overshadow the actual retrospective goals - Encourage balanced participation, just as a successful AFL team needs all players to contribute - Use visual aids like AFL imagery or team colors to enhance engagement - Maintain focus on constructive feedback rather than turning it into a blame game - Consider rotating the 'team captain' role for facilitating future retrospectives ## Icebreaker questions - If our team was an AFL team, what would be our team colors and why? - What's your most memorable moment of teamwork, either in sports or at work? --- # Post-Mortem Retrospective URL: https://www.teamretro.com/retrospective-templates/post-mortem-retrospective/ A post-mortem retrospective gives teams a structured, blame-free way to examine an incident, project, or release after it has concluded and capture exactly what happened, why it happened, and what should change. Rather than pointing fingers, the focus is on understanding the timeline of events, surfacing the contributing factors, and translating those insights into concrete actions that prevent the same problems from recurring. It works equally well for engineering incidents and outages, missed deadlines, or the close-out of a major initiative. The format guides participants through a shared reconstruction of events, an honest look at what went well and what went wrong, an exploration of root causes, and finally a set of agreed-upon improvements with clear ownership. By documenting everything in one place, the team builds an institutional memory it can return to and learn from over time. Conducting the session in TeamRetro keeps everyone aligned in real time, makes it easy to group related observations, prioritise the most impactful issues, and assign follow-up actions before the meeting ends. The real value of a post-mortem lies in its commitment to psychological safety and continuous improvement. When teams treat failure as data rather than fault, they uncover systemic weaknesses, strengthen processes, and respond faster next time. Popularised by site reliability and incident-management practices at companies like Google, the blameless post-mortem has become an essential ritual for high-performing teams who want to grow stronger with every event. ## Topics - **Root Causes**: How would you describe the timeline of events? - **What went well?**: What worked and helped us respond effectively? - **What went wrong?**: Where did things break down or fall short? - **Action items**: What will we do to prevent this in future? ## When to use - After a production incident or outage, to understand the cause and prevent it from happening again. - At the close of a major project or release, to capture lessons learned while details are fresh. - When a deadline was missed or an initiative underdelivered and the team needs an honest review. - Whenever a recurring problem keeps resurfacing and you want to get to its true root cause. - To build a culture of blameless learning and continuous improvement across teams. ## Tips and tricks - Set a blameless tone from the very start so people feel safe sharing what really happened. - Build a shared, factual timeline before jumping into analysis to keep everyone aligned. - Use the Five Whys to push past symptoms and uncover genuine root causes. - Make every action item specific, owned, and time-bound so follow-through actually happens. - Invite the right mix of people who were involved, but keep the group small enough to stay focused. - Document the outcome and revisit past action items in future sessions to confirm fixes stuck. ## Icebreaker questions - What's the most memorable 'oops' moment you've had that turned into a great lesson? - If this incident were a movie title, what would you call it? --- # Leadership Effectiveness Retrospective URL: https://www.teamretro.com/retrospective-templates/leadership-effectiveness-retrospective/ The Leadership Effectiveness Retrospective is a structured activity designed to help leadership teams reflect on their performance, team dynamics, and overall effectiveness. It provides a safe space for open and honest discussions, allowing leaders to identify strengths, areas for improvement, and actionable steps to enhance their collective leadership capabilities. This retrospective follows the classic retrospective format, with tailored topics that encourage leaders to analyze their decision-making processes, communication styles, conflict resolution approaches, and alignment with organizational goals. By fostering self-awareness and constructive feedback, the activity aims to strengthen the leadership team's cohesion, accountability, and ability to drive positive change. The Leadership Effectiveness Retrospective has been widely adopted by companies seeking to cultivate high-performing and self-reflective leadership teams. ## Topics - **Our Achievements**: What were our most significant accomplishments as a leadership team? - **Areas for Improvement**: What aspects of our leadership could be enhanced or improved? - **Strategic Alignment**: How well did our actions and decisions align with the organization's vision and goals? - **Stakeholder Feedback**: How well did we incorporate feedback from key stakeholders into our decisions? - **Team Dynamics**: How well did we collaborate and leverage our collective strengths as a team? ## When to use - When the leadership team wants to reflect on their collective performance and identify areas for growth and improvement. - After completing a significant project, initiative, or organizational change, to assess the leadership team's effectiveness and lessons learned. - As part of a regular cadence (e.g., quarterly or annually) to foster continuous improvement and maintain high-performing team dynamics. - When onboarding new members to the leadership team, to align expectations, establish team norms, and promote cohesion. - During times of transition or organizational restructuring, to ensure the leadership team remains aligned and effective. ## Tips and tricks - Encourage open and honest feedback by creating a safe and non-judgmental environment. - Ensure all voices are heard and valued, regardless of position or tenure within the leadership team. - Focus on constructive criticism and actionable solutions, rather than dwelling on past mistakes or assigning blame. - Consider involving an external facilitator or coach to provide an objective perspective and ensure impartiality. - Follow up on the insights and action items identified during the retrospective to drive continuous improvement. - Celebrate successes and achievements, but also embrace opportunities for growth and development. ## Icebreaker questions - If our leadership team were a famous band or musical group, which one would we be and why? - Share a leadership lesson or experience that has significantly shaped your approach as a leader. --- # Design Team Retrospective URL: https://www.teamretro.com/retrospective-templates/design-team-retrospective/ Great design isn't just about pixels and prototypes—it's about how a team collaborates, critiques, and continuously improves the way they create. The Design Team Retrospective gives designers, researchers, and design leads a dedicated space to step back from the daily flow of work and reflect on what's shaping their craft, their process, and their working relationships. Rather than focusing purely on delivery metrics, this format invites the team to consider the quality of design outcomes, the health of their feedback culture, and the systems that support (or hinder) creative work. Running this retrospective in TeamRetro is simple and inclusive. Each team member contributes their reflections across focused themes—celebrating strong design decisions, surfacing friction in handoffs and reviews, and uncovering opportunities to refine the design system and tooling. Grouping, voting, and discussion features make it easy to move from scattered observations to shared insights, and from insights to clear, ownable actions. Anonymous input ensures even quieter voices and constructive critiques are heard. The goal is continuous improvement of both the design product and the design practice. Whether you're a product design team inside an agile squad, a brand studio, or a UX research group, this retrospective helps you align on craft standards, smooth cross-functional collaboration with engineering and product, and build a healthier creative environment. Use it at the end of a design sprint, after a major launch, or on a regular cadence to keep your design team learning and growing together. ## Topics - **Design Wins**: Which design decisions or outcomes are we proud of? - **Friction Points**: Where did our design process or collaboration slow down? - **Craft & Quality**: How can we raise the bar on our design craft? - **Ideas & Experiments**: What should we try to improve how we work? ## When to use - At the end of a design sprint or major project to review what worked and what didn't in the design process. - After a significant product launch or release to capture lessons about craft, collaboration, and handoffs. - On a regular cadence to maintain a healthy critique culture and keep raising design quality. - When cross-functional friction with engineering or product is affecting design outcomes. - When onboarding new designers or evolving your design system and want shared alignment on standards. ## Tips and tricks - Frame critique around the work, not the person—keep feedback specific, kind, and actionable to protect a healthy creative culture. - Use anonymous input so quieter designers and constructive criticisms surface without fear of stepping on toes. - Invite cross-functional partners like engineers and PMs occasionally to address handoff and collaboration friction directly. - Timebox each topic and use voting to focus discussion on the highest-impact themes rather than every comment. - Always close with clear, owned action items and revisit them at the start of the next retro to build accountability. - Balance celebrating design wins with surfacing problems so the session feels motivating, not just critical. ## Icebreaker questions - If your design style were a font, which one would it be and why? - What's one piece of design—an app, poster, or product—that's caught your eye recently? --- # Baseball Retrospective URL: https://www.teamretro.com/retrospective-templates/baseball-retrospective/ The Baseball Retrospective is an engaging way to reflect on team performance using America's favorite pastime as a metaphor. Drawing parallels between baseball and project delivery, this format helps teams identify successes (home runs), missed opportunities (strikes), challenges (curveballs), and future strategies (batting up). This retrospective format makes feedback sessions more approachable and fun by leveraging familiar baseball terminology. It encourages team members to think about their work in terms of hits, misses, and upcoming plays, creating a playful atmosphere while maintaining professional focus. Originally adapted from sporting metaphor retrospectives, this format works particularly well with teams who enjoy sports analogies or need a fresh perspective on their regular retrospective meetings. ## Topics - **Home Runs**: What were some great outcomes? - **Strikes**: What did we miss? - **Curveballs**: What was tricky? - **Batter Up**: What should be our next play? ## When to use - When you want to make retrospectives more engaging for sports-minded team members - After completing a major project milestone or release to evaluate team performance - When the team needs a fresh perspective on their regular retrospective format - When you want to encourage more metaphorical thinking about successes and failures - When team morale needs a boost through a more playful retrospective format ## Tips and tricks - Keep the baseball metaphor consistent but don't overdo it - focus on the core concepts rather than forcing every baseball term to fit - Consider using baseball sound effects or visuals to enhance the experience and make it more immersive - Rotate who 'pitches' topics first to ensure everyone gets a chance to lead the discussion - Use a 'dugout' approach where team members can take a moment to reflect before sharing - Keep a 'scorecard' of action items and follow up on them in the next retrospective - Ensure the baseball theme doesn't exclude team members who aren't familiar with the sport ## Icebreaker questions - If your last sprint was a baseball game, what position would you have played and why? - What's your favorite sports memory that taught you something about teamwork? --- # Social Media Retrospective URL: https://www.teamretro.com/retrospective-templates/social-media-retrospective/ A Social Media Retrospective is a structured meeting for teams to analyze their social media activities, campaigns, and performance over a given period. It provides an opportunity to celebrate successes, identify areas for improvement, and plan future strategies. The retrospective typically covers topics like content performance, audience engagement, platform trends, and campaign effectiveness. By reflecting on what worked well, what didn't, and gathering insights, teams can make data-driven decisions to optimize their social media presence and achieve better results. This template is designed to facilitate an open and constructive discussion, fostering continuous learning and improvement in social media management. ## Topics - **What went well?**: Which social media activities or campaigns were successful? - **What could be improved?**: Which areas of our social media efforts need attention? - **What should we start doing?**: What new strategies or tactics should we explore? - **What should we stop doing?**: Which activities or tactics are no longer effective or aligned with our goals? ## When to use - At the end of a marketing campaign or quarter to evaluate performance and gather insights. - When launching a new product or service to assess social media strategies and adjust as needed. - After significant changes in the social media landscape or platform updates to realign strategies. - Periodically (e.g., quarterly or bi-annually) to maintain a continuous improvement mindset and stay agile. ## Tips and tricks - Encourage open and honest feedback by creating a safe and judgment-free environment. - Use data and metrics to support observations and recommendations, but also consider qualitative feedback. - Assign a dedicated note-taker to capture key insights and action items for future reference. - Involve cross-functional team members (e.g., marketing, customer service, product) for diverse perspectives. - Set clear goals and objectives for the retrospective to keep the discussion focused and productive. - Follow up on action items and ensure accountability for implementing agreed-upon changes or strategies. ## Icebreaker questions - If our brand was a social media influencer, what type of content would they create? - Share a recent social media trend or meme that caught your attention. How could we leverage it for our brand? --- # Project Wrap Up Retrospective URL: https://www.teamretro.com/retrospective-templates/project-wrap-up-retrospective/ The Project Wrap Up Retrospective is a collaborative meeting designed to review and reflect on the outcomes, processes, and learnings from a recently completed project or major initiative. This retrospective provides a structured way for teams to celebrate successes, identify areas for improvement, and capture valuable insights to inform future endeavors. By taking the time to thoughtfully examine what went well, what didn't go as planned, and what could be done differently next time, teams can foster a culture of continuous improvement and knowledge sharing. The Project Wrap Up Retrospective encourages open and honest discussions, allowing teams to extract meaningful lessons and actionable takeaways. This retrospective format is particularly valuable for agile teams working on complex, long-term projects or epics, as it helps consolidate learnings and facilitates the transition to new initiatives. ## Topics - **Successes and Wins**: What went particularly well during this project? - **Challenges and Obstacles**: What were the biggest hurdles or pain points faced? - **Lessons Learned**: What valuable insights or takeaways did we gain? - **Process Improvements**: What processes or practices should we refine or implement? - **Team Dynamics and Culture**: How can we foster a more positive and productive team environment? ## When to use - At the conclusion of a major project, epic, or initiative to capture learnings and insights. - When transitioning to a new phase or project, to reflect on the previous experience and identify areas for improvement. - As part of a regular cadence (e.g., quarterly or annually) to review completed projects and foster continuous improvement. - After encountering significant challenges or roadblocks during a project, to identify root causes and preventative measures. ## Tips and tricks - Encourage open and honest discussions by creating a safe, judgment-free environment. - Assign a dedicated facilitator to guide the retrospective and ensure productive conversations. - Use anonymous feedback mechanisms if needed to gather candid insights. - Prioritize actionable takeaways and assign owners for implementing process improvements. - Celebrate successes and recognize team members' contributions to boost morale. - Follow up on action items and learnings in subsequent retrospectives or project kickoffs. ## Icebreaker questions - If this project were a movie, what genre would it be and why? - Share a fun or memorable moment from this project that brought the team together. --- # The Good Gardener Retrospective URL: https://www.teamretro.com/retrospective-templates/the-good-gardener-retrospective/ The Good Gardener retrospective uses gardening metaphors to help teams reflect on their growth and development. Drawing inspiration from the natural cycles of planting and harvesting, this template encourages teams to think about what they want to start (sow), what they want to nurture (grow), and what benefits they've reaped (harvest). This approach is particularly effective for teams focused on long-term development and continuous improvement. By framing team activities in terms of gardening cycles, participants can easily visualize the progression from initial ideas to mature outcomes. The metaphor of gardening helps teams understand that success requires patience, consistent care, and the right conditions to thrive. It emphasizes that some initiatives need time to develop, while others might be ready to deliver value. ## Topics - **Sow**: What should we start or experiment with? - **Grow**: What do we want to continue investing in? - **Harvest**: What have we gained? ## When to use - When you want to focus on long-term growth and continuous improvement - During times of organizational change when you need to balance new initiatives with existing processes - When the team needs a fresh perspective on progress and development - For teams that respond well to nature-based metaphors and organic growth concepts ## Tips and tricks - Use real gardening examples to explain the cycle of growth and how it relates to team development - Encourage participants to think about the resources and conditions needed for their ideas to flourish - Remember that like plants, some initiatives need more time than others to show results - Consider seasonal patterns in your team's work when discussing what to sow or harvest - Help the team understand that not everything planted will grow, and that's part of the learning process ## Icebreaker questions - If your team were a garden, what kind of plant would each person be and why? - What's your favorite season, and how does it reflect your approach to work? --- # Easter Egg Hunt Retrospective URL: https://www.teamretro.com/retrospective-templates/easter-egg-hunt-retrospective/ Easter Egg Hunt brings a seasonal sense of fun and curiosity to your team reflection. Inspired by the joy of searching for hidden treasures, this retrospective invites your team to "hunt" through a recent sprint, project, or quarter to surface the good eggs (wins worth celebrating), the cracked eggs (things that went wrong), the golden eggs (unexpected delights), and the eggs still waiting to be found (opportunities and next steps). It's a lighthearted format that keeps energy high while still driving meaningful conversation and continuous improvement. The hunt works because metaphors lower the barrier to participation. Rather than asking pointed questions, you encourage people to share discoveries — making it easier for quieter team members to contribute and for everyone to approach challenges with a positive, exploratory mindset. As the team collects and groups their findings in TeamRetro, you can vote on the most important eggs and turn the best discoveries into clear, trackable actions. Perfect for the spring season, team morale boosts, or any time your retros feel a little stale, the Easter Egg Hunt Retrospective combines celebration with honest reflection. It helps teams recognise hidden value, learn from mistakes, and plan their next steps — all while having a bit of seasonal fun together. ## Topics - **Good Eggs**: What went well and deserves to be celebrated? - **Cracked Eggs**: What broke, went wrong, or caused frustration? - **Golden Eggs**: What pleasant surprises or unexpected wins did we find? - **Eggs Still Hidden**: What opportunities or next steps are waiting to be found? ## When to use - Around the Easter or spring season when you want a themed, energising retrospective. - When team morale or engagement in retros has dipped and you need a fresh, fun format. - After a sprint or project to celebrate wins while still surfacing honest problems. - When you want a low-pressure way to encourage quieter team members to contribute. - As a quarterly or milestone reflection that balances celebration with forward planning. ## Tips and tricks - Set the theme early with a fun intro so the team embraces the metaphor and relaxes into the conversation. - Timebox each 'hunt' so you keep energy high and don't spend too long in any one basket. - Start with Good Eggs and Golden Eggs to build positive momentum before tackling Cracked Eggs. - Group similar eggs together and use dot voting to focus on the discoveries that matter most. - Always close by turning the best Hidden Eggs into clear, assigned actions so the hunt drives real change. - Keep the tone safe and blameless when discussing Cracked Eggs — focus on the process, not the person. ## Icebreaker questions - What's the best hidden treasure or unexpected gift you've ever stumbled upon? - If you could hide one 'golden egg' surprise for your team, what would be inside it? --- # Mad Sad Glad Retrospective URL: https://www.teamretro.com/retrospective-templates/mad-sad-glad-retrospective/ The mad sad glad retrospective frames discussion around the emotional journey of by your team during the previous sprint, and is a great way to identify opportunities to improve team morale and job satisfaction. The retrospective asks participants to share what made them feel frustrated or annoyed (mad), disappointed (sad) and what made them feel happy or proud (glad). This mad sad glad style retrospective encourages your team to be more emotionally-aware to help build a positive team dynamic, and provides an opportunity to reflect on issues and opportunities from a different perspective. It is important you remember the retrospective prime directive and focus on events, behaviours and processes – not on assigning blame or ‘guilting’ individuals. By regularly conducting Mad Sad Glad retrospectives, teams can continuously improve, build trust, and maintain a healthy team dynamic focused on growth. ## Topics - **Mad**: What is driving you crazy? - **Sad**: What is disappointing you? - **Glad**: What is making you happy? ## When to use - To promote transparency and open discussion within an agile team after completing a sprint or project. - To surface areas for improvement, frustrations, and sources of dissatisfaction in a constructive manner. - To celebrate successes, positive experiences, and exceptional work from the team. - To maintain a healthy team dynamic focused on continuous improvement and growth. - To gather diverse perspectives and create a safe space for honest feedback. ## Tips and tricks - Set a positive tone and create a safe, judgment-free environment for open and honest discussion. - Encourage participation from all team members, including introverts and new hires. - Look for patterns and root causes behind frustrations or disappointments raised. - Avoid getting defensive or making excuses - focus on understanding different perspectives. - Capture key points and action items, but don't try to solve every issue during the retrospective. - End on a positive note by discussing 'Glad' items and recognizing exceptional work. ## Icebreaker questions - If you could add one 'rule' that everyone had to follow, what would it be? - What's the most 'mad', 'sad', or 'glad' movie you've seen recently? --- # Hopes & Fears Retrospective URL: https://www.teamretro.com/retrospective-templates/hopes-and-fears-retrospective/ The Hopes and Fears retrospective is a powerful team alignment exercise that creates psychological safety by encouraging participants to openly share their aspirations and concerns about upcoming changes, projects, or initiatives. By structuring discussion around positive expectations (hopes) and potential challenges (fears), teams can proactively address concerns while building on shared optimism. This format helps surface unspoken worries that might otherwise hinder progress, while also highlighting opportunities that energize the team. This retrospective is particularly valuable during times of change or at the start of new initiatives, as it allows teams to build trust through vulnerability and create action plans that address both opportunities and risks. ## Topics - **Hopes**: What do we want to happen? - **Fears**: What don't we want to happen? ## When to use - When kicking off a new project or initiative to understand team sentiment and address concerns early - During organizational changes to surface and address anxieties while building on positive expectations - Before making significant process changes to gather input and create buy-in - When team morale seems low and you need to understand underlying concerns while identifying opportunities ## Tips and tricks - Start with hopes to set a positive tone, then move to fears to ensure balanced discussion - Group similar items together to identify patterns and prioritize actions - Create specific action items to address fears and support hopes - Follow up on previous hopes and fears in future retrospectives to show progress - Encourage participation from quieter team members by using round-robin sharing - Keep the focus on constructive discussion rather than dwelling on negative aspects ## Icebreaker questions - What was your biggest fear that turned out to be not so scary after all? - What's one hope you had that came true in your career? --- # DevOps Retrospective URL: https://www.teamretro.com/retrospective-templates/devops-retrospective/ DevOps (a portmanteau of "development" and "operations") is the combination of practices and tools designed to increase an organization's ability to deliver applications and services faster than traditional software development processes. A DevOps retrospective is a structured meeting where development and operations teams reflect on their recent work, processes, and collaboration. It provides an opportunity to identify what went well, areas for improvement, and actionable steps to enhance DevOps practices. This retrospective template is designed to facilitate open discussions, foster continuous improvement, and strengthen the synergy between development and operations teams. By regularly reviewing successes, challenges, and lessons learned, teams can adapt their workflows, tools, and communication to deliver high-quality software more efficiently. The origins of retrospectives can be traced back to Agile methodologies, but their value extends to any cross-functional team seeking to optimize their processes and teamwork. ## Topics - **Successful Deployments**: What went well during recent deployments? - **Areas for Improvement**: What challenges did we face, and how can we do better? - **Collaboration and Culture**: How can we improve teamwork and foster a DevOps culture? - **Tools and Processes**: How can we optimize our tools, technologies, and processes? ## When to use - After major releases or deployments to review the process and outcomes. - At regular intervals (e.g., monthly or quarterly) to continuously improve DevOps practices. - When facing recurring issues or bottlenecks in the development and deployment workflows. - When introducing new tools, technologies, or processes to assess their impact and effectiveness. - After significant incidents or outages to identify root causes and preventive measures. ## Tips and tricks - Encourage open and honest feedback by creating a safe and blameless environment. - Involve both development and operations teams to gain diverse perspectives. - Focus on actionable improvements rather than dwelling on past mistakes. - Assign clear owners and timelines for implementing agreed-upon actions. - Celebrate successes and recognize contributions to boost morale and engagement. - Regularly review and adjust the retrospective format to keep it fresh and relevant. ## Icebreaker questions - If you could automate one manual task, what would it be and why? - Share a recent 'aha' moment or learning experience related to DevOps practices. --- # Friday the 13th Horror Sprint Retrospective URL: https://www.teamretro.com/retrospective-templates/friday-the-13th-horror-sprint-retrospective/ Every sprint has its share of jump scares, lurking monsters and survivors who lived to tell the tale. The Friday the 13th Horror Sprint Retrospective brings a playful horror theme to your team reflection, turning the usual review into a thrilling adventure where the team hunts down the things that went bump in the night. By framing setbacks as "frights" and successes as "survivors," teams can talk about even the most uncomfortable issues in a fun, low-pressure way. The format works by guiding your team through a spooky narrative: what scared us, what monsters are still lurking, who survived the chaos and what spells (improvements) we can cast to protect ourselves next time. Each topic invites honest, candid input while the lighthearted theme reduces defensiveness and encourages participation. It's a great way to keep engagement high during seasonal events, end-of-quarter reviews or simply to shake up a retrospective routine that has grown stale. Beyond the costumes and creepy metaphors, this retrospective delivers real value: it surfaces hidden risks, celebrates resilience and produces clear, actionable improvements. Whether you run it around Halloween, on an actual Friday the 13th, or any time your team needs a morale boost, this themed retrospective helps you confront problems head-on while having a few laughs along the way. ## Topics - **The Frights**: What scared us or went terribly wrong this sprint? - **The Survivors**: What went well and helped us live to tell the tale? - **Lurking Monsters**: What risks or problems are still hiding in the shadows? - **Protective Spells**: What actions or improvements will keep us safe next sprint? ## When to use - Around Halloween or on an actual Friday the 13th when you want a seasonal, morale-boosting twist on your usual sprint review. - When your retrospectives have become routine and the team needs a fresh, engaging format to spark participation. - After a particularly chaotic or difficult sprint, where a playful theme helps the team discuss tough issues without defensiveness. - To balance celebrating wins with proactively surfacing hidden risks before they become real problems. ## Tips and tricks - Set the mood with a spooky theme — encourage costumes, virtual backgrounds or eerie music to get everyone in the spirit. - Lean into the metaphor but keep the conversation grounded; make sure each fright and monster maps to a real, actionable insight. - Timebox each topic so the fun doesn't run away with you and you still reach the Protective Spells action items. - Reassure the team that the horror framing makes it safe to raise scary or sensitive issues without blame. - Give everyone time to add ideas independently before grouping and discussing, so quieter voices aren't drowned out. - End by assigning clear owners and due dates to your Protective Spells so the improvements actually happen. ## Icebreaker questions - If this sprint were a horror movie, what would its title be and who would be the first to go? - What's the scariest bug, outage or surprise you've ever survived at work? --- # Ice Cream Dream Sprint Retrospective URL: https://www.teamretro.com/retrospective-templates/ice-cream-dream-sprint-retrospective/ Looking for a refreshing way to reflect on your last sprint? The Ice Cream Dream Sprint retrospective turns reflection into a fun, dessert-themed experience that keeps your team engaged while still surfacing meaningful insights. Using familiar ice cream metaphors, teams explore the sweet wins, the melting messes, the toppings that made things better, and the new flavors they want to try next. This playful format works because it lowers the barrier to honest feedback. When teams frame their sprint through lighthearted imagery, they are more likely to open up, share candid reflections, and approach problem-solving with creativity rather than defensiveness. Each topic maps to a classic retrospective theme — celebrating successes, identifying problems, recognizing helpful factors, and brainstorming improvements — wrapped in a theme that energizes the room. Ideal for agile teams who want to break the monotony of repetitive sprint retrospectives, the Ice Cream Dream Sprint helps build psychological safety, boost participation, and end every meeting on a positive, action-oriented note. Run it in TeamRetro to collaboratively brainstorm, group, vote, and turn the best ideas into clear action items for your next iteration. ## Topics - **The Sweet Scoops**: What went really well and tasted great this sprint? - **The Melting Mess**: What turned into a sticky mess or slowed us down? - **The Tasty Toppings**: What extras or support made things better and sweeter? - **New Flavors to Try**: What new ideas or experiments should we taste next? ## When to use - When your team's regular sprint retrospectives are feeling repetitive and you want to re-energize participation with a fun, themed format. - After a particularly intense or stressful sprint, when a lighter tone can help the team reflect honestly without defensiveness. - When onboarding new team members and you want a welcoming, low-pressure way to gather everyone's perspective. - For end-of-quarter or celebratory retros where you want to balance recognition of wins with constructive improvement ideas. ## Tips and tricks - Set the theme early — a quick ice cream image or emoji in the intro helps everyone embrace the playful tone and relax. - Time-box each topic so the fun doesn't crowd out the substance; aim to leave enough time for prioritizing and assigning action items. - Encourage quieter team members to contribute by reminding everyone that even small scoops of feedback matter. - Keep the 'Melting Mess' focused on issues and systems rather than individuals to maintain psychological safety. - Use voting to surface the most important 'New Flavors' so the team commits to a realistic number of experiments. - Close by capturing clear, owned action items — a fun retro still needs concrete follow-through to drive improvement. ## Icebreaker questions - If this sprint were an ice cream flavor, what would it be and why? - What's your all-time favorite ice cream topping, and what does it say about your work style? --- # Cyber Security Ops Retrospective URL: https://www.teamretro.com/retrospective-templates/cyber-security-ops-retrospective/ Cyber Security Ops brings your security operations team together to review how well you detected, responded to, and recovered from threats over the past cycle. Rather than waiting for the next incident to expose weaknesses, this retrospective creates a safe, blameless space to examine what your defenses caught, what slipped through, and where your processes need reinforcing. It is designed for SOC analysts, incident responders, threat hunters, and security engineers who want to turn lessons from alerts, incidents, and near-misses into concrete improvements. The format guides teams through four focused lenses: the threats and incidents you handled, the controls and tooling that worked, the gaps and vulnerabilities that emerged, and the actions you will take to harden your posture. By structuring the conversation this way, teams move beyond firefighting and start building resilient, repeatable practices. It pairs naturally with frameworks like NIST and MITRE ATT&CK, helping you map findings to recognized standards and measure progress over time. Running this retrospective regularly helps security teams reduce mean time to detect and respond, eliminate recurring blind spots, and foster the kind of open communication that high-performing SecOps cultures depend on. Whether you run it after a major incident, at the end of an on-call rotation, or as a routine cadence, it keeps continuous improvement at the heart of your security program. ## Topics - **Threats & Incidents**: What threats or incidents did we handle this cycle? - **Controls & Wins**: Which defenses, tools, or processes worked well? - **Gaps & Vulnerabilities**: Where did we have blind spots or weaknesses? - **Actions & Hardening**: What will we do to improve our security posture? ## When to use - After a significant security incident or breach to capture lessons learned in a blameless way. - At the end of an on-call or SOC shift rotation to review handled alerts and handovers. - On a regular cadence (monthly or quarterly) to track security posture and recurring gaps. - Following a tabletop exercise, red team engagement, or penetration test to align on findings. - When onboarding new SecOps practices or tooling and you want to validate they are working. ## Tips and tricks - Keep the conversation blameless—focus on systems and processes, not individuals, so people share openly about mistakes and near-misses. - Map findings to a framework like MITRE ATT&CK or NIST CSF so improvements connect to recognized standards and are easy to track over time. - Invite a cross-section of roles (analysts, responders, engineers, management) to surface blind spots a single perspective would miss. - Anonymous or private brainstorming first reduces hierarchy bias and encourages junior team members to flag uncomfortable truths. - Timebox each topic to keep momentum and reserve dedicated time for converting gaps into owned, dated actions. - Track action items across retrospectives so recurring vulnerabilities don't quietly persist between cycles. ## Icebreaker questions - If you were a hacker for a day, what would be your weapon of choice and why? - What's the most creative phishing attempt you've ever seen—and did it almost work? --- # Technical Debt Retrospective URL: https://www.teamretro.com/retrospective-templates/technical-debt-retrospective/ A Technical Debt Retrospective is a focused meeting to identify areas of technical debt within a codebase or system. It allows teams to openly discuss sources of debt, prioritize which items should be addressed, and create an action plan for paying down that debt over time. Technical debt refers to the accumulation of less-than-optimal solutions within a codebase. This debt may arise from prioritizing short-term delivery over long-term code quality, lack of understanding, or deferring refactoring. Left unchecked, technical debt increases complexity and slows down future development. By regularly conducting Technical Debt Retrospectives, teams can maintain awareness of their debt, prevent it from becoming unmanageable, and allocate time for incremental improvements. This proactive approach enhances code quality, reduces bugs, and improves overall productivity. ## Topics - **Sources of Debt**: What areas of the codebase have accumulated technical debt? - **Impact and Risks**: How is this technical debt impacting the team and product? - **Prioritization**: Which areas of debt should be tackled first? - **Action Plan**: How can we systematically address the prioritized debt? ## When to use - When your team is struggling with an aging, complex codebase that is becoming increasingly difficult to maintain and extend. - If you're constantly fighting fires and unable to deliver new features at a reasonable pace due to instability caused by technical debt. - When onboarding new developers is extremely challenging due to lack of documentation and convoluted code in certain areas. - If you're spending more time on maintenance and bug fixes than working on innovative new capabilities due to technical debt. - When morale is suffering as developers become frustrated with the constant challenges posed by an accumulating codebase. ## Tips and tricks - Encourage open and honest discussion without blame or finger-pointing. Technical debt is a natural byproduct of software development. - Ensure all team members, including non-technical roles, understand the concept of technical debt and its potential impacts. - Prioritize debt items based on impact, effort required, and strategic importance, rather than trying to tackle everything at once. - Create a concrete action plan with timelines, responsibilities, and regular check-ins to ensure accountability and progress. - Consider allocating a dedicated portion of each sprint or cycle to focus on technical debt reduction efforts. - Explore automating processes like linting, testing, and code reviews to prevent the introduction of new debt over time. ## Icebreaker questions - If our codebase was a physical structure, what would it look like and why? - Share a humorous story or experience related to dealing with technical debt in the past. --- # Content Strategy Retrospective URL: https://www.teamretro.com/retrospective-templates/content-strategy-retrospective/ A Content Strategy Retrospective is a focused review of how well an organization's content aligns with its goals, resonates with its audience, and drives success through quality, relevance, and discoverability. It examines the processes involved in creating, delivering, and optimizing content across channels. This retrospective provides insights into the effectiveness of your content strategy, identifying areas for improvement and opportunities to better engage your audience. It encourages cross-functional collaboration and a holistic view of content's role in achieving business objectives. By regularly conducting Content Strategy Retrospectives, organizations can continuously refine their approach, ensuring their content remains impactful, valuable, and aligned with evolving needs and trends. ## Topics - **Content Alignment**: How well does our content align with our goals? - **Audience Resonance**: How well does our content resonate with our audience? - **Content Quality**: How do we ensure the quality of our content? - **Content Discoverability**: How discoverable is our content? - **Content Creation Process**: How effective is our content creation process? ## When to use - When you want to evaluate the effectiveness of your content strategy and identify areas for improvement. - When you need to align your content efforts with your organization's goals and audience needs. - When you want to foster cross-functional collaboration and a holistic view of content's role in driving success. - When you want to continuously refine your content creation processes and optimize content performance. - When you need to assess the quality, relevance, and discoverability of your content across various channels. ## Tips and tricks - Encourage open and honest feedback from all stakeholders involved in the content lifecycle. - Use data and metrics to support qualitative observations and anecdotal evidence. - Involve representatives from different teams and departments to gain diverse perspectives. - Foster a culture of continuous improvement and embrace constructive criticism. - Prioritize action items and establish clear ownership and timelines for implementing changes. - Schedule regular Content Strategy Retrospectives to maintain momentum and ensure ongoing alignment. ## Icebreaker questions - If our content strategy was a movie, what genre would it be and why? - Share an example of a piece of content (from any source) that truly resonated with you recently, and explain what made it impactful. --- # Haunted House Halloween Retrospective URL: https://www.teamretro.com/retrospective-templates/haunted-house-halloween-retrospective/ Step inside the haunted house of team reflection — where every room reveals a secret about your sprint! Welcome to the Haunted House, where the echoes of past sprints linger in the halls. In this retrospective, your team explores each eerie room to uncover lessons, celebrate wins, and chase out the ghosts of old habits. It’s a frightfully fun way to reflect — less about finger-pointing, more about ghost-busting and growth. Perfect for teams looking to break away from routine retrospectives, this format uses the metaphor of a haunted house to create psychological safety and encourage creative thinking. The Hall of Mirrors reflects distorted perceptions and communication challenges, the Cobwebbed Corridor reveals neglected issues, the Dungeon uncovers what's holding the team back, the Secret Lab celebrates hidden experiments and innovations, and the Graveyard Garden honors what should be laid to rest. This approach helps teams address difficult topics with a lighter touch while maintaining meaningful dialogue. ## Topics - **Hall of Mirrors**: What reflections do we see about ourselves and our teamwork? - **Cobwebbed Corridor**: Which tasks or processes have gathered dust and need clearing out? - **The Dungeon**: What’s been dragging us down or haunting our progress? - **The Secret Lab**: What weird and wonderful experiments should we try next? - **Graveyard Garden**: What old habits, tools, or rituals should we finally bury? ## When to use - Your team is experiencing retrospective fatigue and needs a fresh, engaging format to reinvigorate participation and honest reflection. - You're running a retrospective during October or around Halloween and want to embrace the seasonal theme while maintaining meaningful team dialogue. - The team needs to address difficult or uncomfortable topics, and the playful haunted house metaphor provides psychological safety to discuss challenges. - You want to encourage creative thinking and help team members see familiar problems from new perspectives through the lens of different 'haunted rooms.' - Your distributed or remote team needs a memorable, themed activity that creates shared experience and boosts engagement in virtual meetings. ## Tips and tricks - Set the spooky atmosphere by encouraging team members to use Halloween-themed virtual backgrounds, play eerie background music, or even dress up if they're comfortable - the more immersive the experience, the more engaged participants will be. - Start by 'touring' each room briefly, explaining the metaphor before diving into reflection. This helps everyone understand the theme and gets them thinking creatively about how to frame their contributions. - Balance the fun Halloween theme with serious reflection - while the format is playful, remind the team that the insights shared are valuable and should be treated with respect, especially in the Dungeon and Cobwebbed Corridor. - Watch for teams that might overload the Dungeon with complaints. If this happens, redirect energy toward the Secret Lab and encourage solution-focused thinking about what experiments might help escape the dungeon. - When discussing the Graveyard Garden, frame it positively as making space for new growth rather than dwelling on failures. Celebrate the courage it takes to let go of familiar practices. - Don't skip the Cobwebbed Corridor even if it feels uncomfortable - neglected issues rarely resolve themselves. Create safety by acknowledging that accumulation is normal and the goal is progress, not blame. ## Icebreaker questions - What's your favorite Halloween candy, and does your preference reveal anything about your personality? - If you had to spend a night in one room of a real haunted house, which would you choose and why? --- # Plus Minus Interesting (PMI) URL: https://www.teamretro.com/retrospective-templates/plus-minus-interesting-pmi/ Plus Minus Interesting (PMI) is a powerful evaluation tool developed by Edward de Bono to help teams analyze ideas, decisions, or changes from multiple angles. This systematic approach encourages participants to consider positive aspects (Plus), negative aspects (Minus), and intriguing possibilities (Interesting) before making conclusions. Unlike simple pros and cons analysis, PMI adds a third dimension of 'Interesting' observations that captures neutral points, uncertainties, and opportunities for innovation. This additional perspective helps teams move beyond binary thinking and discover unexpected insights. The structured nature of PMI makes it particularly effective for reducing cognitive bias, as it requires equal attention to all perspectives. Teams using this method often uncover valuable insights they might have missed with more traditional evaluation approaches. ## Topics - **Plus**: What are the positive aspects? - **Minus**: What are the negatives aspects? - **Interesting**: What is unknown or makes us curious? ## When to use - When evaluating significant changes or new initiatives that affect the team or organization - During decision-making processes where multiple stakeholders or perspectives need to be considered - For breaking down complex problems into manageable components for analysis - When you need to ensure thorough consideration of all aspects before making important decisions ## Tips and tricks - Encourage participants to add items to all three columns, even if their initial reaction is strongly positive or negative - Use timeboxing for each column to ensure balanced attention to all perspectives - Consider using dot voting after collection to identify the most significant points in each category - Avoid debating points during the collection phase - focus on gathering all perspectives first - Keep the energy neutral when discussing 'Minus' points to maintain psychological safety - Document all insights for future reference, as the 'Interesting' column often contains valuable innovation seeds ## Icebreaker questions - What's the most interesting decision you've made that initially seemed negative but turned out positive? - If you could instantly know the outcome of any decision, what would you want to evaluate first? --- # Voyage to the New World Retrospective URL: https://www.teamretro.com/retrospective-templates/voyage-to-the-new-world-retrospective/ Set sail on a reflective adventure with the Voyage to the New World retrospective, a metaphorical exploration that frames your team's recent work as an ocean crossing toward uncharted lands. Just as early explorers braved storms, navigated by the stars and discovered new territories, your team can use this nautical theme to examine the winds that propelled progress, the storms that slowed momentum, the treasures uncovered along the way and the unexplored horizons still ahead. This format works by inviting participants to map their experiences onto the stages of a great expedition. By stepping into the role of explorers and navigators, team members gain a fresh perspective on familiar challenges, making it easier to surface honest feedback in a playful, low-pressure setting. The metaphor encourages storytelling, which often unlocks insights that more conventional retrospective formats can miss, while keeping everyone engaged and focused on a shared destination. The real benefit lies in balancing celebration with critical reflection. Teams identify what helped them sail smoothly, confront the obstacles that threw them off course, recognise the wins worth treasuring and align on where to explore next. It's an ideal choice for teams wanting to break out of routine retrospectives, foster creative thinking and build a forward-looking action plan that keeps the whole crew moving toward the New World together. ## Topics - **Favourable Winds**: What propelled the team forward this voyage? - **Stormy Seas**: What slowed us down or threw us off course? - **Treasure Found**: What wins and discoveries are worth celebrating? - **Uncharted Horizons**: Where should we explore or improve next? ## When to use - When your team wants a fresh, story-driven alternative to standard sprint retrospectives. - At the end of a major project or milestone to reflect on the full journey. - When morale needs a lift and you want a playful, engaging format that still surfaces real issues. - When onboarding a newly formed team and you want to map their shared experience and set a forward course. - Quarterly or release-based reviews where you want to balance celebration with planning ahead. ## Tips and tricks - Set the scene early by introducing the voyage metaphor so everyone embraces the theme and feels free to be playful. - Timebox each section to keep the voyage moving and ensure you reach the action-planning of Uncharted Horizons. - Encourage quieter crew members to contribute by allowing silent, independent input before discussion to reduce bias. - Focus the Stormy Seas discussion on situations and systems, not individuals, to keep psychological safety high. - Group similar ideas and dot-vote to prioritise so you focus action on the issues that matter most. - Always convert Uncharted Horizons ideas into clear, owned actions with due dates so insights lead to real change. ## Icebreaker questions - If you were an explorer in any era, which voyage would you most want to join and why? - What's one 'treasure' you'd want to bring back from a journey to a brand new world? --- # Zombie Apocalypse Retrospective URL: https://www.teamretro.com/retrospective-templates/zombie-apocalypse-retrospective/ Survive. Adapt. Rebuild. Together. When the sprint gets chaotic and deadlines start to bite, it’s time to gather your survival squad and face the undead challenges head-on. Picture your team navigating a zombie apocalypse—where survival depends on quick thinking, collaboration, and learning from every encounter. The Zombie Apocalypse Retrospective transforms your team's reflection session into an engaging, thematic adventure that makes discussing challenges, successes, and improvements feel fresh and exciting. Instead of the usual retrospective format, team members explore what helped them "survive" (succeed), what "zombies" (obstacles) they encountered, what "supplies" (resources) they need, and how to "fortify their base" (improve processes). The Zombie Apocalypse Retrospective is perfect for teams who want to inject energy and creativity into their reflection process. By framing challenges as survival scenarios, teams often discover insights they might miss in traditional formats. The theme encourages creative thinking, builds team camaraderie through shared storytelling, and makes action items feel like critical survival strategies rather than mundane tasks. ## Topics - **Survival Wins**: What helped us survive and succeed this sprint? - **Zombie Horde**: What obstacles and challenges attacked us? - **Survival Supplies**: What resources or support do we need? - **Fortify the Base**: How can we strengthen our defenses and improve? ## When to use - When your team is experiencing retrospective fatigue and needs a fresh, engaging format to reinvigorate the reflection process and boost participation. - For teams working through particularly challenging sprints or projects where the apocalypse metaphor helps create psychological safety to discuss difficult issues without blame. - When you want to build team camaraderie and inject fun into your retrospectives while still achieving meaningful insights and actionable improvements. - For creative or gaming-oriented teams who respond well to thematic approaches and storytelling as a way to frame their work experiences. - When introducing retrospectives to a new team and you want to make a memorable first impression that shows reflection can be both productive and enjoyable. ## Tips and tricks - Embrace the theme fully by using apocalypse language throughout the session. Refer to yourself as the 'survivor leader' and encourage team members to stay in character—it increases engagement and psychological safety. - Watch for blame language disguised as zombie talk. If someone says 'the zombie that is John's code,' redirect to focus on the situation, not individuals. Keep zombies external and systemic. - Time-box each section to maintain energy and momentum. Apocalypse scenarios are urgent—use a visible timer to create that sense of focused intensity without letting discussions drag. - Prioritize the 'Fortify the Base' actions ruthlessly. Not every fortification can be built immediately. Help the team identify the 2-3 most critical improvements that will have the biggest impact on survival. - Use voting or dot-voting to identify which zombies were most threatening and which fortifications are most urgent. This ensures the team focuses on what matters most rather than trying to address everything. - End on a high note by reviewing the Survival Wins and celebrating the team's resilience. Acknowledge that they've survived another sprint and are stronger for it—this builds momentum for the next iteration. ## Icebreaker questions - If the zombie apocalypse started right now, what one item from your desk would you grab as your survival tool? - Which team member would you want in your zombie apocalypse survival group and why? What's their special skill? --- # Weather Forecast Retrospective URL: https://www.teamretro.com/retrospective-templates/weather-forecast-retrospective/ The Weather Forecast Retrospective turns reflection into a visual, intuitive experience by mapping your team's recent journey onto familiar weather patterns. Just as a meteorologist reads the skies, your team uses sunshine, storms, clouds, and forecasts to express how things felt during the last sprint or project phase — making it easy for everyone to share their mood and observations in a relatable, low-pressure way. The format works by inviting participants to reflect across four weather-inspired themes: what's been bright and going well (Sunshine), what's been stormy and challenging (Storms), what's uncertain or unclear (Clouds), and what they predict is coming next (Forecast). This blend of looking back and looking forward helps teams celebrate wins, surface problems, and proactively plan for what's ahead. Because the metaphor is universal and approachable, it lowers the barrier for honest conversation and works especially well for teams who want a fresh, engaging alternative to traditional retrospective formats. Whether you're running an agile sprint retrospective or a broader project review, the Weather Forecast Retro encourages emotional honesty, shared understanding, and forward-thinking action items. It's a creative way to read the team climate, identify the storms before they hit, and steer toward clearer skies — all within TeamRetro's collaborative space. ## Topics - **Sunshine**: What went brightly and made the team shine? - **Clouds**: What felt unclear, uncertain or murky? - **Storms**: What was stormy, painful or held us back? - **Forecast**: What do we predict or want for the road ahead? ## When to use - At the end of a sprint when you want an engaging, visual alternative to a standard 'what went well / what didn't' retrospective. - When team morale or mood is a key factor and you want to surface how people are feeling alongside the facts. - For project milestones or quarterly reviews where looking back and forecasting ahead are both valuable. - When a team feels fatigued by repetitive retrospective formats and needs a fresh, playful way to reflect. - After a turbulent period to safely name the storms, clear the clouds, and rebuild a positive outlook. ## Tips and tricks - Start with Sunshine to build a positive atmosphere before diving into the tougher Storms and Clouds. - Lean into the weather metaphor to keep things light, but make sure conversations still land on concrete, actionable outcomes. - Encourage everyone to contribute to each theme so the forecast reflects the whole team, not just the loudest voices. - Frame Storms around processes and systems rather than individuals to avoid blame and keep the discussion psychologically safe. - Use the Forecast theme to convert reflections into clear action items with owners before closing the session. - Timebox each theme so you cover the full forecast and leave room to agree on next steps. ## Icebreaker questions - If your week was a type of weather, what would the forecast say? - What's your favourite kind of weather and does it match your current mood at work? --- # Magical Hogwarts Retrospective URL: https://www.teamretro.com/retrospective-templates/magical-hogwarts-retrospective/ Step through the enchanted doors of Hogwarts and transform your team reflection into a magical adventure. The Magical Hogwarts Retrospective wraps the familiar rhythm of agile reflection in the wonder of the Wizarding World, inviting your team to celebrate spells that worked, banish the dark arts that held them back, and dream up the magic they want to conjure next. By trading dry status updates for a playful, story-driven theme, you create a safe and energising space where every voice feels welcome to speak up. It works by guiding your team through a series of magically themed prompts — from the triumphant "Spells That Worked" to the lurking "Dark Arts" and the hopeful "Wishes from the Sorting Hat". Each topic maps to a core part of a healthy retrospective: recognising successes, surfacing problems, identifying lessons learned and committing to actions. Inspired by the beloved world created by J.K. Rowling, this themed format taps into shared cultural storytelling to lower defences, spark creativity and make tough conversations easier to have. The benefits go well beyond the fun. Themed retrospectives like this one are a proven antidote to retro fatigue, boosting participation, psychological safety and engagement across remote and co-located teams alike. Whether you're celebrating a successful sprint, onboarding a new squad or simply wanting to shake up your routine, the Magical Hogwarts Retrospective helps your team reflect deeply, laugh together and leave with clear, actionable magic to carry forward. ## Topics - **Spells That Worked**: What magic helped the team succeed this time? - **The Dark Arts**: What problems or blockers cast a shadow over us? - **Lessons from Dumbledore**: What wisdom or insights did we gain along the way? - **Wishes from the Sorting Hat**: What magic do we want to conjure for next time? ## When to use - When your team is experiencing retro fatigue and needs a fresh, playful format to re-energise reflection. - During milestone or end-of-quarter celebrations where you want to recognise wins in a memorable way. - When onboarding a new or cross-functional team and you want a low-pressure icebreaker that builds psychological safety. - Around themed events, holidays or team socials where a creative, story-driven retrospective fits the mood. - When difficult issues need surfacing and a lighthearted metaphor helps lower defences and encourage honesty. ## Tips and tricks - Set the scene before you start — a short intro 'sorting' the team into houses or a themed background gets everyone in the magical mood. - Keep the metaphor light and inclusive; not everyone is a die-hard fan, so explain each topic clearly so no one feels left out. - Timebox each column to keep the energy high and prevent the fun theme from drifting into off-topic chatter. - Use anonymous contributions for the 'Dark Arts' topic so people feel safe raising sensitive or uncomfortable issues. - Group and vote on ideas before discussing, so the team focuses its limited time on the most impactful magic. - Always convert 'Wishes from the Sorting Hat' into concrete, owned action items so the magic translates into real change. ## Icebreaker questions - Which Hogwarts house would the Sorting Hat place you in, and why? - If you could cast one real-life spell to improve your workday, what would it do? --- # Vacation Retrospective URL: https://www.teamretro.com/retrospective-templates/vacation/ The Vacation Retrospective helps teams and families review their travel experiences to create more enjoyable future trips. By examining various aspects of the journey, from initial planning to return travel, participants can identify successful strategies and areas for improvement. This retrospective format breaks down the travel experience into key phases, allowing everyone to share their perspectives on preparation, transportation, accommodation, and activities. The structured approach helps capture both practical logistics and emotional experiences, making it easier to implement improvements for future adventures. Whether reviewing a family holiday, business trip, or team retreat, this template helps participants celebrate memorable moments while addressing challenges that arose during their travels. The insights gathered can lead to better planning, smoother execution, and more memorable experiences in future trips. ## Topics - **The Destination**: Where were we traveling to? - **Packing**: What needed to be done beforehand? - **Lost Luggage**: What issues did we encounter on the way? - **Vacation Snaps**: What were the highlights of our journey? ## When to use - After returning from a team retreat or business trip to improve future travel planning - Following a family vacation to capture lessons learned and memorable moments - When planning future trips and wanting to avoid past challenges - To collect feedback about group travel experiences and improve coordination ## Tips and tricks - Schedule the retrospective within a week of return while memories are fresh - Encourage participants to bring photos to help trigger memories and discussions - Create a safe space for sharing both positive and negative experiences - Focus on actionable improvements rather than dwelling on unavoidable issues - Document specific recommendations for future trip planning - Consider different perspectives as travelers may have varying priorities and experiences ## Icebreaker questions - If you could instantly teleport to any destination right now, where would you go and why? - What's the most unusual food you've ever tried while traveling? --- # Brainstorm Blitz URL: https://www.teamretro.com/retrospective-templates/brainstorm-blitz-retrospective/ Brainstorm Blitz is a high-energy ideation session designed to unlock your team's creative potential in a short, focused burst. By encouraging participants to generate as many ideas as possible without judgment, this format breaks through mental blocks and surfaces the bold, unexpected thinking that often gets lost in slower, more structured meetings. The "blitz" approach taps into the proven principle that quantity breeds quality — the more ideas a team puts forward, the greater the chance of discovering a genuinely innovative solution. Rooted in classic brainstorming techniques pioneered by advertising executive Alex Osborn in the 1950s, this template modernizes the practice for distributed and hybrid teams. Each round focuses on a different lens — diverging to gather wild ideas, capturing quick wins, identifying obstacles, and converging on the best opportunities to pursue. Teams move quickly through each topic, building on one another's contributions and deferring criticism until the ideas have had room to breathe. The result is a collaborative, inclusive session where every voice contributes and the best concepts rise to the top through group prioritization. Whether you're tackling a product challenge, planning a campaign, or simply shaking up routine thinking, Brainstorm Blitz delivers a structured yet playful space to think big, decide fast, and turn raw ideas into actionable next steps. ## Topics - **Big Ideas**: What bold or wild ideas could we explore? - **Quick Wins**: Which ideas could we act on right away? - **Roadblocks**: What might get in the way of our ideas? - **Next Steps**: Which ideas should we commit to and who owns them? ## When to use - At the start of a new project or quarter when you need fresh ideas and a clear set of priorities to pursue. - When the team feels stuck on a problem and needs a creative jolt to break out of conventional thinking. - Ahead of planning a campaign, feature, or initiative where gathering a wide range of options quickly is valuable. - When you want an inclusive way for every team member to contribute ideas, including quieter voices in distributed teams. ## Tips and tricks - Set a tight timer for each round to keep the energy high and prevent overthinking — speed is part of what makes a blitz effective. - Defer all judgment during the idea-generation phases; critiquing too early shuts down creativity and discourages participation. - Encourage building on others' ideas rather than only adding new ones — combining concepts often produces the strongest results. - Use anonymous brainstorming where appropriate so seniority and personality don't bias which ideas get shared. - Always end with voting and clear action items so the session produces real commitments, not just a list of ideas. - Capture parked or 'too big for now' ideas in a backlog so good thinking isn't lost between sessions. ## Icebreaker questions - If you could instantly master any new skill to use at work tomorrow, what would it be? - What's the most creative idea you've ever had — at work or otherwise — that you wish you'd acted on? --- # Christmas Retrospective URL: https://www.teamretro.com/retrospective-templates/christmas-retrospective/ The Christmas Agile Retrospective brings seasonal cheer to your team's reflection process, using holiday-themed categories to structure meaningful discussions about your recent work period. This festive format transforms standard retrospective elements into engaging Christmas metaphors: Gifts represent valuable learnings, Joy highlights positive experiences, the Grinch symbolizes challenges, Elves acknowledge helpful contributions, and Wishes capture future aspirations. This approach creates a relaxed atmosphere that encourages open communication while maintaining focus on continuous improvement. By framing feedback within familiar holiday concepts, teams can have more comfortable conversations about successes and setbacks. The Christmas theme works particularly well for end-of-year retrospectives or when teams need a morale boost during challenging periods, helping to end sprints or projects on a positive note while gathering actionable insights for the future. ## Topics - **Gifts**: What have we learned and received as gifts during this period? - **Joy**: What has brought us happiness and joy in our work? - **Grinches**: What has caused us troubles or issues during this period? - **Elves**: Who or what has helped us succeed in our work? - **Wishes**: What do we wish for in our future work together? ## When to use - At the end of the year to combine reflection with seasonal festivities and close the year on a positive note - When team morale needs a boost and a more lighthearted approach to retrospection would be beneficial - After completing a significant milestone or project phase during the holiday season - When you want to refresh your retrospective format with a thematic approach that still covers all essential reflection areas ## Tips and tricks - Consider using festive visual cues like holiday icons or a winter-themed virtual background to enhance the Christmas atmosphere - Balance the fun elements with structured action items to ensure the retrospective leads to meaningful improvements - Encourage team members to prepare their thoughts in advance for each category to maximize productive discussion time - Set a positive tone by starting with 'Gifts' and 'Joy' before moving to the more challenging 'Grinch' topics - End the session by converting 'Wishes' into concrete action items with owners and timelines to ensure follow-through - Consider adding a brief festive activity at the beginning or end to reinforce team bonding during the holiday season ## Icebreaker questions - If your recent work experience was a Christmas movie, which one would it be and why? - What's one 'gift' (skill or knowledge) you'd like to receive to help you in your role next year? --- # Man of Steel Retrospective URL: https://www.teamretro.com/retrospective-templates/man-of-steel-retrospective/ Inspired by the iconic superhero, the Man of Steel Retrospective invites your team to reflect on their work through a heroic lens. Just as Superman draws strength from the sun and faces challenges with courage, your team will explore the powers that propel them forward, the kryptonite that holds them back, and the missions worth fighting for. This themed retrospective turns a routine review into an engaging, story-driven session that energizes participants and sparks honest conversation. The format works by guiding teams through a set of metaphor-rich topics that map to real project dynamics — superpowers represent strengths and wins, kryptonite surfaces weaknesses and blockers, and the call to action defines the next heroic steps. By framing reflection in playful, relatable language, teams lower their defenses, share more openly, and uncover insights they might otherwise overlook. It's a refreshing way to maintain momentum across sprints while keeping engagement high. Beyond the fun, the Man of Steel Retrospective delivers tangible value: it helps teams celebrate achievements, diagnose recurring obstacles, and commit to concrete improvements. Whether you run it after a major release or as a periodic team health check, this template balances levity with meaningful continuous improvement, making it perfect for agile teams looking to break the monotony of standard retrospectives. ## Topics - **Superpowers**: What strengths and wins powered the team forward? - **Kryptonite**: What weakened the team or slowed us down? - **Source of Power**: What energizes and motivates the team to keep going? - **Call to Action**: What heroic steps will we take next? ## When to use - Use it when standard retrospectives feel stale and your team needs a fun, themed format to re-energize participation. - Ideal after a major release or milestone to celebrate wins and openly identify what held the team back. - Great for newer or distributed teams where a playful metaphor helps lower barriers and encourage honest sharing. - Run it as a periodic team health check to track strengths, blockers, and motivation over time. ## Tips and tricks - Set the scene with the superhero theme up front so everyone understands the metaphor before contributing. - Keep the Kryptonite discussion focused on processes and situations, not individuals, to maintain psychological safety. - Timebox each topic to keep energy high and prevent the session from dragging. - Use anonymous contributions if your team is new or sensitive topics may arise, so everyone feels safe to speak up. - Limit your Call to Action items to two or three so the team can realistically deliver them before the next retro. - Revisit previous Call to Action items at the start to hold the team accountable and show progress over time. ## Icebreaker questions - If you could have one superpower at work, what would it be and why? - What's your personal kryptonite — the one thing that instantly derails your productivity? --- # AI Innovation Lab Retrospective URL: https://www.teamretro.com/retrospective-templates/ai-innovation-lab-retrospective/ The AI Innovation Lab retrospective gives teams a dedicated space to step back from the rapid pace of experimentation and reflect on what they are learning as they build with artificial intelligence. As AI tools, models, and use cases evolve almost weekly, teams need a structured rhythm to capture what worked, what surprised them, and where the real value is emerging. This format helps innovation teams, data scientists, product managers, and engineers turn a stream of disconnected experiments into a coherent story of progress and direction. It works by guiding the team through four lenses: the discoveries and breakthroughs they made, the experiments that stalled or failed, the risks and ethical considerations they need to watch, and the bold ideas worth pursuing next. By naming both wins and dead ends openly, teams build a culture where intelligent risk-taking is celebrated and failure is treated as data rather than blame. The conversation naturally connects technical findings to business and user outcomes, keeping AI work grounded in real value. Ideal for cross-functional R&D groups, hackathon teams, and AI centers of excellence, this retrospective keeps innovation momentum high while ensuring responsible, well-governed adoption. Running it in TeamRetro lets everyone contribute ideas in parallel, group related themes, vote on the most promising directions, and walk away with clear, prioritized actions that fuel the next cycle of experimentation. ## Topics - **Breakthroughs & Discoveries**: What AI experiments worked or revealed real value? - **Dead Ends & Failed Experiments**: Which experiments stalled, failed, or didn't pan out? - **Risks & Responsible AI**: What risks, ethics, or governance concerns need attention? - **Next Bold Ideas**: What experiments or ideas should we pursue next? ## When to use - At the end of an AI or machine learning experimentation cycle to consolidate learnings before planning the next. - During hackathons or innovation sprints to capture discoveries and decide which prototypes to advance. - When an AI center of excellence or R&D team wants a regular cadence to review experiments and manage risk. - After piloting a new AI tool or model to evaluate whether it delivered real value and should scale. - When cross-functional teams need to align technical findings with business outcomes and responsible AI practices. ## Tips and tricks - Set the tone early by framing failed experiments as valuable data, not personal shortcomings, so people share openly. - Invite a mix of roles such as data scientists, engineers, product, and design to keep AI work grounded in real value. - Use anonymous submissions when discussing risks or ethical concerns so people feel safe raising sensitive issues. - Timebox the ideation topic and use dot voting to prioritize the most promising experiments rather than chasing every idea. - Keep findings concrete by asking for evidence or metrics behind each breakthrough or dead end. - Capture clear, owned action items for each prioritized idea and risk so the next cycle starts with momentum. ## Icebreaker questions - If you could give your team one AI superpower for the next sprint, what would it be? - What's the most surprising thing an AI tool has done for you recently, good or bad? --- # Build-a-Bear Workshop Retrospective URL: https://www.teamretro.com/retrospective-templates/build-a-bear-workshop-retrospective/ Inspired by the playful, hands-on experience of crafting your own teddy bear, the Build-a-Bear Workshop retrospective turns reflection into a creative team-building exercise. Just as you select a body, stuff it with heart, dress it up, and give it a name, your team will reflect on the building blocks of your work together — laying the foundation, adding the meaningful core, refining the details, and celebrating what you've created. It's a fun, metaphor-driven format that lowers barriers and helps teams open up. This retrospective works by guiding participants through four stages that mirror building a custom bear. Each stage maps to a familiar part of a team's working rhythm: the foundation you stand on, the heart that motivates you, the finishing touches that add polish, and the celebration of the final product. By framing serious conversations around an approachable, lighthearted metaphor, teams find it easier to surface honest feedback, identify gaps, and recognise achievements without feeling like they're filling out a checklist. The format is especially valuable for newer teams, cross-functional groups, or any squad that wants a refreshing alternative to standard sprint retrospectives. It encourages creativity, builds psychological safety, and ends on a high note by celebrating shared accomplishments. Use it to break routine, energise your team, and craft actionable improvements that are genuinely your own. ## Topics - **Choose the Body**: What foundations supported our work this time? - **Add the Heart**: What motivated and energised us the most? - **Dress It Up**: What finishing touches and improvements should we add? - **Name and Celebrate**: What achievements deserve to be celebrated? ## When to use - When you want a fun, creative alternative to a standard sprint retrospective to re-energise your team. - With newer or cross-functional teams that are still building psychological safety and rapport. - After completing a significant project or milestone you want to celebrate while reflecting on how it was built. - When team morale is low and you want a lighthearted format that still surfaces meaningful, actionable feedback. ## Tips and tricks - Lean into the metaphor — encourage playful language about building, stuffing, and dressing the bear to keep the mood light and creative. - Use anonymous brainstorming in TeamRetro so quieter team members feel safe sharing honest foundational concerns. - Timebox each of the four stages to keep momentum and avoid spending all your energy on the first topic. - Make sure the 'Name and Celebrate' stage gets enough time — ending on genuine celebration boosts morale and reinforces positive habits. - Group and vote on ideas in the 'Dress It Up' stage to prioritise the finishing touches that become real action items. - Rotate the facilitator each session so the metaphor stays fresh and everyone shares ownership of the team's improvement. ## Icebreaker questions - If your team were a stuffed animal, what would it be and why? - What was the first soft toy you remember owning, and did it have a name? --- # Customer Feedback Retrospective URL: https://www.teamretro.com/retrospective-templates/customer-feedback-retrospective/ A Customer Feedback Retrospective is a structured meeting where teams reflect on customer feedback, identify areas for improvement, and plan actions to enhance the customer experience. By analyzing feedback from various sources, teams gain valuable insights into customer needs, pain points, and opportunities for growth. This retrospective encourages open discussion, empathy for the customer's perspective, and a commitment to continuous improvement. It fosters a customer-centric mindset and drives teams to deliver exceptional products or services that delight customers. The retrospective format typically includes reviewing customer feedback data, discussing recurring themes or issues, brainstorming solutions, and prioritizing actionable steps. It's a powerful tool for building stronger customer relationships and driving business success through customer satisfaction. ## Topics - **Positive Feedback**: What positive feedback did we receive from customers? - **Areas for Improvement**: What areas did customers identify as needing improvement? - **Innovative Ideas**: What innovative ideas or suggestions did customers propose? - **Action Plan**: What specific actions can we take to address customer feedback? ## When to use - When you want to gather customer feedback and insights to drive product or service improvements. - After launching a new product, feature, or marketing campaign to evaluate customer reception. - On a regular cadence (e.g., quarterly) to continuously monitor and enhance the customer experience. - When customer satisfaction metrics or reviews indicate areas for improvement. - As part of a customer-centric culture, prioritizing customer needs and expectations. ## Tips and tricks - Gather customer feedback from various sources (surveys, reviews, support tickets, social media, etc.) to get a comprehensive view. - Encourage open and honest discussions, creating a safe space for constructive criticism. - Involve cross-functional teams (product, marketing, support, etc.) to gain diverse perspectives. - Prioritize actionable steps and assign clear ownership for implementation. - Follow up on action items and communicate progress to customers to build trust and loyalty. - Continuously seek customer feedback and make it a regular practice to foster a customer-centric culture. ## Icebreaker questions - If you could change one thing about our product or service, what would it be? - Share a recent positive or negative experience you had as a customer with any company. --- # Cross-Functional Strategy Planning URL: https://www.teamretro.com/retrospective-templates/cross-functional-strategy-planning/ A Cross-Functional Strategy Planning session brings together stakeholders from different teams to collaboratively define strategic goals, align on key initiatives, and develop actionable plans. This interactive activity fosters cross-departmental collaboration, ensures organizational alignment, and drives focused execution. The session begins by reviewing the organization's mission, vision, and high-level objectives. Participants then identify strategic priorities, potential roadblocks, and opportunities for synergy across teams. Through facilitated discussions and activities, the group develops a cohesive strategy with clear goals, roles, and timelines. By involving diverse perspectives, this approach builds shared understanding, maximizes resource utilization, and empowers teams to drive meaningful change together. ## Topics - **Mission and Vision**: What is our organization's mission and vision? - **Strategic Priorities**: What are our top strategic priorities for the next 12-18 months? - **Cross-Team Collaboration**: How can we better collaborate across teams to achieve our goals? - **Action Planning**: What specific actions and timelines should we set to execute our strategy? ## When to use - When your organization needs to define or revisit its strategic direction and priorities. - When there is a need for better alignment and collaboration across different teams or departments. - When launching a new product, service, or initiative that requires cross-functional coordination and buy-in. - During periods of organizational change or transformation, to ensure everyone is working towards the same goals. - Annually or bi-annually, to review progress, adjust course if needed, and plan for the upcoming period. ## Tips and tricks - Ensure representation from all relevant teams and stakeholders to gather diverse perspectives. - Clearly communicate the purpose and desired outcomes of the session to set expectations. - Encourage open and honest discussions, and create a safe space for constructive feedback. - Use visual aids, such as whiteboards or digital collaboration tools, to capture ideas and action items. - Assign clear ownership and deadlines for follow-up tasks to maintain accountability and momentum. - Schedule regular check-ins or follow-up sessions to track progress and address any roadblocks. ## Icebreaker questions - If our organization was an animal, what would it be and why? - Share a time when you experienced exceptional cross-team collaboration, and what made it successful. --- # Zombie Outbreak Retrospective URL: https://www.teamretro.com/retrospective-templates/zombie-outbreak-retrospective/ When the dead rise, only the prepared survive — and the same is true for your team. The Zombie Outbreak Retrospective turns reflection into a thrilling survival scenario, where teams imagine their project as a fight for survival against the undead. By framing recent work through a playful apocalypse lens, this themed retrospective helps teams identify the "infections" slowing them down, the "weapons" that kept them alive, and the "safe zones" where things went well. It's an energising way to break routine and spark honest, creative conversations. This format works by mapping familiar retrospective questions onto a zombie survival storyline. Teams identify what threatened their survival (problems and blockers), what helped them fight back (wins and tools), who or what they need to recruit (improvements and support), and how to fortify their base for the next outbreak (action items). The metaphor lowers the stakes of difficult conversations, making it easier for everyone to speak up about challenges without finger-pointing. It's particularly effective for teams that have grown bored of standard sprint retrospectives and need a jolt of fun to re-engage. Beyond the entertainment value, themed retrospectives like this one boost participation, build psychological safety, and improve team morale. Running a Zombie Outbreak Retrospective in TeamRetro gives you the structure of a proven agile ceremony with the engagement of a team-building game — helping you surface real insights, agree on practical improvements, and keep your survivors coming back for more. ## Topics - **Zombie Threats**: What infected our progress or threatened our survival? - **Survival Weapons**: What kept us alive and helped us fight back? - **Recruit Survivors**: What or who do we need to strengthen our team? - **Fortify the Base**: What actions will we take to prepare for next time? ## When to use - Around Halloween or whenever your team needs a fun, themed twist on the usual sprint retrospective. - When team energy is low or standard retrospectives feel repetitive and you want to boost engagement. - When difficult issues need surfacing and a playful metaphor can lower defensiveness and encourage honesty. - As a team-building exercise that still produces real, actionable improvements. - With newly formed teams looking for a relaxed way to build psychological safety and rapport. ## Tips and tricks - Set the scene with a short story prompt — describe the outbreak scenario before opening the board to get everyone into the playful mindset. - Keep the metaphor light and inclusive; the goal is real insight, so steer conversations back to concrete examples if they drift too far into the theme. - Timebox each topic to keep momentum and prevent the most talkative survivors from dominating the discussion. - Use anonymous brainstorming so people feel safe naming the scariest 'zombie threats' without fear of blame. - Group and vote on items before discussion to focus on the highest-impact threats and defences. - Always close by assigning clear owners and due dates to your 'Fortify the Base' actions so the retrospective drives real change. ## Icebreaker questions - If a zombie apocalypse hit the office, which teammate would you want by your side and why? - What one item from your desk would be your weapon of choice for survival? --- # Bug Fixing Retrospective URL: https://www.teamretro.com/retrospective-templates/bug-fixing-retrospective/ The Bug Fixing Retrospective is a focused meeting for agile teams to review recent bugs, identify root causes, and implement preventative measures. By analyzing defects in a structured way, teams can improve code quality, enhance testing practices, and streamline development workflows. This retrospective leverages the collective insights of the team to foster a blameless culture of continuous learning. It encourages open discussion around technical debt, coding standards, and quality assurance processes. The goal is to emerge with actionable steps to reduce bugs and rework in future sprints. Originally outlined in the book 'Agile Retrospectives' by Esther Derby and Diana Larsen, this activity adapts the classic '5 Whys' technique to software development. It provides a systematic approach to uncovering the underlying reasons behind defects and prioritizing improvements. ## Topics - **Recent Bugs**: What significant bugs were encountered during the last sprint? - **Root Causes**: What were the underlying reasons behind each major bug? - **Preventative Actions**: What steps can we take to prevent similar bugs going forward? - **Quality Targets**: What metrics or goals should we set to measure improvement? - **Our Learnings**: What key lessons did we take away from this retrospective? ## When to use - After a sprint or project phase with a high number of reported bugs or defects. - When technical debt or accumulating defects are impacting productivity and release quality. - To analyze recurring issues and identify systemic process failures leading to bugs. - As a focused quality improvement exercise for teams struggling with code quality. ## Tips and tricks - Foster a blameless environment focused on learning, not finger-pointing. - Involve cross-functional team members like QA, DevOps, and product owners for diverse perspectives. - Prioritize high-impact or frequently occurring bugs over minor or one-off issues. - Dig deep using the '5 Whys' approach to uncover root causes beyond surface-level symptoms. - Assign clear owners and deadlines for all preventative actions and quality targets. - Follow up in subsequent retrospectives to review progress on committed improvements. ## Icebreaker questions - If you could eliminate one bug from existence, which would it be and why? - Share a funny or embarrassing experience involving a bug you've encountered. --- # Down the Rabbit Hole Retrospective URL: https://www.teamretro.com/retrospective-templates/down-the-rabbit-hole-retro/ Inspired by Alice's whimsical journey in Wonderland, the Down the Rabbit Hole Retrospective invites teams to venture beyond surface-level observations and explore the curious, often overlooked corners of how they work. Rather than stopping at the first answer, this format encourages curiosity and continued questioning — peeling back each layer to reveal what's really driving outcomes, behaviours, and surprises along the way. This retrospective works by guiding teams through a series of exploratory prompts: spotting the rabbit hole worth following, descending deeper through layered "why" questions, mapping what was discovered in Wonderland, and finally finding the way back out with actionable next steps. By embracing a sense of adventure and wonder, teams move past blame and assumptions to develop a shared, deeper understanding of complex problems and pleasant surprises alike. The benefit of this approach is that it transforms root cause analysis into an engaging, story-driven experience. It pairs naturally with techniques like the 5 Whys and is especially valuable when a recurring issue keeps resurfacing or when a team feels stuck on the obvious. In TeamRetro, the playful framing keeps energy high while the structured topics ensure the conversation stays productive and leads to meaningful, lasting improvements. ## Topics - **The Rabbit Hole**: What curious problem or surprise should we explore? - **Falling Deeper**: Why did it happen? Keep asking why beneath the surface. - **Wonderland**: What did we discover along the way, good or bad? - **Finding the Way Out**: How do we act on what we found and climb back up? ## When to use - When a recurring problem keeps resurfacing despite previous fixes and you need to understand the true root cause. - When the team tends to stop at surface-level symptoms and you want to encourage deeper, curiosity-driven analysis. - When you want a more playful, engaging alternative to a standard root cause analysis session. - When a surprising outcome — good or bad — warrants a thorough exploration before deciding on action. ## Tips and tricks - Lean into the Wonderland theme to keep things light, but make sure each rabbit hole leads to a genuine root cause and not just a fun tangent. - Use the '5 Whys' mindset in the Falling Deeper stage — keep asking why until you hit something actionable rather than stopping at the first plausible answer. - Focus on one or two rabbit holes rather than trying to explore everything; depth beats breadth in this format. - Keep the conversation blameless by focusing on systems and processes rather than individuals. - Timebox each stage so the team doesn't get lost in the rabbit hole and always makes it back out with clear actions. - Capture discoveries even if they don't lead to immediate action — they may reveal valuable patterns over time. ## Icebreaker questions - If you could follow any white rabbit into a mystery, what would you most want to discover? - What's one thing you were endlessly curious about as a child? --- # Sesame Street Shuffle Retrospective URL: https://www.teamretro.com/retrospective-templates/sesame-street-shuffle-retrospective/ Inspired by the beloved characters of Sesame Street, the Sesame Street Shuffle is a lighthearted retrospective format that uses familiar, friendly personalities to help teams reflect on their work in a fun and approachable way. By framing feedback through well-known characters, this retrospective lowers psychological barriers and invites team members to share thoughts they might otherwise hold back. It's a great way to bring energy and laughter into your meeting while still surfacing meaningful insights about how the team is performing. Each character represents a different lens for reflection: what made the team genuinely happy, what felt grumpy or frustrating, what they're curious to learn more about, and what they want to count and celebrate. This structure gives every voice a chance to be heard and keeps discussion balanced between positives, challenges, and forward-looking curiosity. The whimsical theme makes it especially effective for newer teams, distributed teams looking to build rapport, or any group that needs a morale boost after a tough sprint. Run entirely in TeamRetro, the Sesame Street Shuffle makes it easy to gather ideas, group similar themes, vote on what matters most, and turn discussion into clear action items. Whether you're wrapping up a sprint or pausing to check in on team health, this retrospective combines a sense of play with practical outcomes, helping teams continuously improve while having a little fun along the way. ## Topics - **Sunny Days (What made us happy?)**: What brought sunshine and good vibes to our work? - **Grouchy Bins (What frustrated us?)**: What felt grumpy, annoying, or got in our way? - **Curious Questions (What do we want to learn?)**: What are we curious about or want to explore further? - **Count On It (What should we commit to?)**: What actions can we count on and commit to next? ## When to use - When your team needs a morale boost or a lighter, more playful retrospective after an intense sprint. - When working with newer or distributed teams that are still building trust and rapport. - When you want to lower psychological barriers so quieter team members feel comfortable sharing. - When standard retro formats feel stale and you want to re-energize participation. ## Tips and tricks - Set the tone early by leaning into the playful theme — it gives people permission to be candid without feeling pressured. - Time-box each character topic so the fun doesn't crowd out the serious discussion and action setting. - Use anonymous idea entry in TeamRetro for the 'Grouchy Bins' topic to encourage honest feedback about frustrations. - Group similar ideas before voting so the team focuses discussion on the themes that matter most. - Limit 'Count On It' commitments to two or three actions with clear owners so they actually get done. - Keep an eye on participation balance — gently invite quieter voices so the loudest characters don't dominate. ## Icebreaker questions - Which Sesame Street character best matches your mood this sprint, and why? - If your team were a Sesame Street duo, who would you be and who's your partner? --- # Top Gun Squadron Retrospective URL: https://www.teamretro.com/retrospective-templates/top-gun-squadron-retrospective/ Strap in, throttle up, and prepare for a debrief worthy of an elite fighter squadron. The Top Gun Squadron retrospective borrows the discipline and camaraderie of a top-tier flight crew to help your team review a sprint or project with energy, focus, and a healthy dose of fun. Just as pilots gather after every mission to dissect what happened, this format gives your squadron a structured space to celebrate dogfight victories, learn from near-misses, and chart the heading for the next operation. The format works through four themed flight stations: your "Top Guns" (standout wins), your "Turbulence" (challenges and friction), your "Wingman Support" (collaboration and teamwork), and your "Next Mission" (actions and goals). Each member contributes observations, the team groups and votes on the most important themes, and together you commit to concrete actions before the next flight. The mission metaphor lowers defenses, encourages candid feedback, and keeps morale high — making it easier to surface the truth without anyone feeling shot down. Perfect for agile teams craving variety in their retrospective rotation, the Top Gun Squadron format injects momentum into post-sprint reviews while still delivering the substance of a serious continuous-improvement session. It celebrates the people behind the results, reinforces a culture of mutual support, and ensures every debrief ends with a clear flight plan. Whether you're cooling off after a turbulent release or basking in the glory of a flawless deployment, this retrospective helps your squadron fly higher together. ## Topics - **Top Guns**: What were our standout wins this mission? - **Turbulence**: Where did we hit friction or run into trouble? - **Wingman Support**: How well did we back each other up as a team? - **Next Mission**: What actions will set us up for the next flight? ## When to use - When your team's retrospectives feel stale and you want to inject fresh energy with a fun, themed format. - After a high-stakes release or sprint where celebrating wins and learning from challenges is equally important. - When you want to strengthen teamwork and reinforce a culture of mutual support among squadron members. - For teams that respond well to gamified, metaphor-driven sessions that lower defensiveness and encourage candid feedback. ## Tips and tricks - Set the scene early — a quick callsign or aviator theme in the intro gets everyone in the squadron mindset and lifts engagement. - Keep the metaphor playful but make sure the actual takeaways are concrete; fun should support honest reflection, not replace it. - Use anonymous contributions where needed so the 'Turbulence' station surfaces real issues without anyone feeling singled out. - Timebox each station to keep the debrief moving and avoid getting stuck circling one topic. - Always close by assigning a pilot (owner) and a due date to every Next Mission action so nothing stalls on the runway. - Rotate the facilitator role between sessions so the squadron shares ownership of the debrief and brings new perspectives. ## Icebreaker questions - If you had a fighter pilot callsign, what would it be and why? - What's one mission (project or task) you felt like an ace flying through recently? --- # Fast & Furious Pit Stop Retrospective URL: https://www.teamretro.com/retrospective-templates/fast-and-furious-pit-stop-retrospective/ Borrowing its energy from the high-octane world of motorsport, the Fast & Furious Pit Stop retrospective treats your team like a championship racing crew. Just as a pit crew has only seconds to refuel, change tyres, and send a car back onto the track at top speed, your team takes a focused moment to assess what's keeping you fast, what's slowing you down, and what adjustments will get you back in the race even stronger. It's a playful, fast-paced format that injects fun into reflection while still surfacing meaningful insights. The retrospective works by guiding your crew through a series of racing-themed lanes — celebrating wins that gave you speed, identifying the friction that caused drag, spotting the hazards on the track ahead, and agreeing on the tune-ups that will give you a competitive edge. This metaphor-driven approach lowers the barrier to honest conversation, helping teams discuss problems and improvements without finger-pointing. It's especially effective for teams who want to break free from the standard "what went well / what didn't" routine and re-energise their continuous improvement habit. By the end of the session your crew leaves the garage with a clear, prioritised set of action items and a renewed sense of momentum. The Fast & Furious Pit Stop is ideal for keeping team retrospectives engaging over the long term, making it a great rotation choice for agile teams, scrum masters, and facilitators looking to keep reflection fresh, collaborative, and genuinely useful. ## Topics - **Full Speed Ahead**: What gave us speed and momentum this sprint? - **Drag & Friction**: What slowed us down or created resistance? - **Hazards on the Track**: What risks or obstacles are coming up ahead? - **Tune-Ups**: What adjustments will make us faster next lap? ## When to use - When your team's standard retrospectives have gone stale and you want to re-energise reflection with a fun, themed format. - At the end of a sprint or iteration where the team wants to celebrate speed, address friction and agree on concrete tune-ups. - When you want a lighthearted way to surface blockers and risks without it feeling like blame. - For teams focused on continuous improvement who like rotating engaging formats to keep participation high. ## Tips and tricks - Lean into the racing metaphor to set the mood — a quick intro framing the team as a championship pit crew gets everyone in the spirit. - Timebox each lane so the session stays fast-paced and energetic, just like a real pit stop. - Keep the 'Drag & Friction' lane blame-free by focusing on the system and process rather than individuals. - Make sure every 'Tune-Up' has a clear owner and a realistic next step so improvements actually happen. - Use anonymous brainstorming first so quieter crew members contribute before group discussion and louder voices dominate. - Revisit last sprint's tune-ups at the start to check which adjustments actually made the team faster. ## Icebreaker questions - If your work this sprint were a vehicle, would it be a Formula 1 car, a reliable sedan, or a car running on fumes — and why? - What's one thing that would have made your sprint feel like crossing the finish line first? --- # Aladdin's Agile Adventure Retrospective URL: https://www.teamretro.com/retrospective-templates/aladdin-agile-adventure-retrospective/ Step aboard the magic carpet and take your team on a journey of reflection with Aladdin's Agile Adventure. Inspired by the timeless tale of wishes, wonders, and lessons learned, this story-driven retrospective format invites teams to explore their sprint or project through the lens of an enchanting adventure. By framing reflection around familiar narrative elements — the genie's wishes, hidden treasures, sneaky traps, and the open road ahead — teams can break out of routine thinking and engage in honest, creative conversation. This themed retrospective works by mapping each part of the Aladdin story to a meaningful area of reflection. Teams celebrate their treasures (wins), identify the traps and tricks (obstacles and blockers), make their three wishes (improvements they wish for), and look toward the magic carpet ride (next steps and aspirations). The playful framing lowers defensiveness, encourages participation from quieter team members, and makes it easier to surface insights that a standard sprint retrospective might miss. It is especially effective for keeping engagement high in long-running teams who may find traditional formats repetitive. The benefits go beyond fun. Story-based retrospectives like this one tap into the way humans naturally make sense of experiences — through narrative. They help teams build psychological safety, foster shared ownership of improvements, and convert reflection into concrete actions. Whether you run agile sprints, kanban flows, or project milestones, Aladdin's Agile Adventure gives your continuous improvement ritual a creative spark while still delivering the structured, actionable outcomes a great retrospective should. ## Topics - **Treasures Found**: What wins or successes did we discover this sprint? - **Traps and Tricks**: What obstacles, blockers or sneaky problems slowed us down? - **Three Wishes**: If the genie granted three wishes, what would we improve? - **Magic Carpet Ride**: Where do we want to go next and what's our first step? ## When to use - When your team's standard sprint retrospective has gone stale and you want to re-energise engagement with a creative theme. - After completing a major project milestone or release, to reflect on the journey in a fun and memorable way. - When you want quieter team members to open up, as the playful storytelling lowers defensiveness. - For end-of-quarter or seasonal retrospectives where a themed format adds a sense of celebration. - When onboarding a newer team to retrospectives and you want an approachable, low-pressure format. ## Tips and tricks - Set the scene with a quick line of story framing at the start so everyone understands how each topic maps to the Aladdin theme. - Keep the fun without losing focus — the goal is still real, actionable insights, so timebox each section to stay on track. - Encourage specificity in the Treasures and Traps so wins can be repeated and obstacles genuinely fixed. - Use dot voting to prioritise the Three Wishes so the team focuses energy on the improvements that matter most. - Make sure every Magic Carpet Ride action has a clear owner and a due date before you close the session. - Rotate the facilitator role each time you run a themed retro to keep perspectives and energy fresh. ## Icebreaker questions - If a genie granted you one work-related wish right now, what would you ask for? - Which fictional character would you most want on your team and why? --- # Three Wishes Retrospective URL: https://www.teamretro.com/retrospective-templates/three-wishes-retrospective/ Imagine your team had a magic lamp and could change anything about how you work together — what would you ask for? The Three Wishes retrospective taps into that playful, imaginative energy to uncover what your team truly wants to improve. By framing reflection as wishes rather than problems, it invites people to think big, dream freely, and express aspirations they might otherwise hold back. This positive, future-focused framing makes it especially effective for teams that feel stuck in cycles of complaint or want a fresh way to spark honest conversation. The format is refreshingly simple: each participant shares three wishes for the team, the product, the process, or the way they collaborate. These wishes are then grouped, discussed, and prioritised, with the most compelling ones converted into concrete actions. Because wishes naturally reveal underlying needs and frustrations, this approach helps facilitators get to the heart of what matters without putting anyone on the defensive. It works beautifully across agile sprint retrospectives, project wrap-ups, and team health checks. The real value of the Three Wishes retrospective lies in its balance of creativity and pragmatism. It encourages psychological safety by lowering the barrier to speaking up, surfaces hidden ambitions and pain points, and channels that energy into meaningful change. In TeamRetro, you can capture, group, vote on, and action your team's wishes all in one place — turning a moment of imagination into measurable improvement for your next sprint. ## Topics - **My First Wish**: What is the one thing you most want to change? - **My Second Wish**: What would make your day-to-day work easier? - **My Third Wish**: What would help the team grow or feel better? - **Granting the Wishes**: Which wishes can we turn into action right now? ## When to use - When your team feels stuck in negative cycles and you want a more positive, forward-looking way to reflect. - At the end of a sprint or project when you want to surface aspirations and convert them into concrete improvements. - During team health checks or culture conversations where you want people to share what they truly want. - When onboarding a new team or restarting retrospectives, as the playful framing lowers the barrier to honest input. ## Tips and tricks - Set the scene by reminding the team there are no bad wishes — encourage big, bold thinking before narrowing down to what's actionable. - Use anonymous brainstorming so quieter team members feel safe sharing wishes they might otherwise hold back. - Group similar wishes together to reveal shared themes and avoid discussing the same idea multiple times. - Use dot voting to prioritise so the team focuses energy on the wishes that matter most. - Be transparent about wishes that can't be granted right away — park them visibly rather than dismissing them. - Always close by assigning owners and next steps so wishes become real change, not just a wishlist. ## Icebreaker questions - If you found a magic lamp today, what's the first non-work wish you'd make? - What's one childhood wish that actually came true for you? --- # Escape Room Challenge Retrospective URL: https://www.teamretro.com/retrospective-templates/escape-room-challenge/ The Escape Room Challenge retrospective invites teams to break free from recurring problems by uncovering useful experiments, ditching blockers, and celebrating effective collaboration. Inspired by the thrill of escape rooms — where teams must work together, think creatively, and solve puzzles under pressure — this retrospective format transforms the standard team review into an engaging, problem-solving adventure. It's perfect for teams that want to shake up their usual retrospective routine and approach continuous improvement with fresh energy and a sense of fun. Much like a real escape room, this retrospective challenges your team to examine the "locks" holding them back, find the "keys" that unlock better ways of working, and celebrate the "clues" that led to recent wins. Each topic is designed to surface meaningful insights: what's trapping the team, what tools or strategies are helping them escape, what experiments they want to try, and what collaborative moments deserve recognition. The format encourages psychological safety by framing challenges as puzzles to solve together rather than problems to assign blame for. Whether you're running a sprint retrospective, a project post-mortem, or a quarterly team health check, the Escape Room Challenge retrospective brings a creative twist to structured reflection. Teams that use this format often find it easier to surface difficult conversations in a low-pressure, gamified context — making it a powerful tool for building trust, driving action, and fostering a culture of continuous improvement. ## Topics - **Locked In**: What blockers or recurring problems are trapping the team? - **Found the Key**: What strategies, tools, or behaviours helped the team escape challenges? - **Hidden Clues**: What subtle signals or insights should the team pay more attention to? - **Escape Plan**: What experiments or actions will help the team level up next sprint? ## When to use - When a team is experiencing recurring blockers or frustrations and needs a fresh, engaging format to surface and address them. - When team energy or engagement in retrospectives has been low and you want to inject some fun and creativity into the process. - After a particularly challenging sprint or project phase where the team needs to decompress, reflect, and reset. - When onboarding new team members and wanting to establish a culture of open, collaborative problem-solving from the start. - When a team is ready to move beyond surface-level retrospectives and wants to dig deeper into systemic issues and meaningful experiments. ## Tips and tricks - Set the scene! Briefly introduce the escape room metaphor at the start of the session — remind the team that they're all in the room together and the only way out is to work as a team. This framing helps build psychological safety and a sense of shared purpose. - Timebox each topic to keep energy high. Escape rooms are time-pressured by nature, so use a visible timer for each section to maintain momentum and prevent any single topic from dominating the session. - Encourage specificity over generality. Vague feedback like 'communication could be better' is hard to act on. Prompt participants to share concrete examples — the more specific the clue, the easier it is to find the key. - Don't skip the 'Hidden Clues' topic. Teams often rush to solutions without fully exploring the signals they've been ignoring. This topic can surface some of the most valuable insights of the session if given enough time and attention. - Make sure every 'Escape Plan' action has a clear owner and a follow-up date. Actions without owners rarely get completed. Use TeamRetro's action tracking features to assign and monitor commitments between sessions. - Watch out for dominant voices drowning out quieter team members. Use anonymous idea submission and dot voting in TeamRetro to ensure everyone's perspective is captured before group discussion begins. ## Icebreaker questions - If your team were actually locked in an escape room together, who would be the first to solve a puzzle — and who would be the one accidentally making things harder? - What's one 'cheat code' or shortcut you wish existed in your day-to-day work life? --- # Portugal Day Celebration Retrospective URL: https://www.teamretro.com/retrospective-templates/portugal-day-celebration-retrospective/ Portugal Day, or Dia de Portugal, celebrated on June 10th, honors the rich culture, history, and global community of Portuguese people around the world. Bring that same spirit of pride and togetherness into your team with a reflective celebration that recognizes shared values, achievements, and the connections that bind your group together. Whether your team is based in Lisbon, Porto, or spread across the globe, this is a wonderful moment to pause and appreciate what makes your community special. Running this celebration in TeamRetro gives everyone an equal voice to share their reflections, traditions, and hopes. Participants contribute ideas anonymously or openly, group related themes together, and vote on the things that resonate most. The structured yet relaxed format keeps the conversation flowing while ensuring every cultural perspective and personal story is heard and valued. Beyond the festivities, this format helps teams build empathy, strengthen relationships, and uncover ways to keep celebrating diversity throughout the year. It is an ideal way to commemorate Dia de Portugal, foster a sense of belonging, and turn shared heritage into lasting team spirit and actionable goals for the future. ## Topics - **What We Celebrate**: What aspects of Portuguese culture or heritage make you proud? - **Traditions & Stories**: What traditions, foods, or stories would you like to share? - **Our Team Connection**: How does our team reflect a sense of community and belonging? - **Keeping the Spirit Alive**: How can we keep celebrating culture and connection year-round? ## When to use - On or around June 10th to celebrate Dia de Portugal and honor Portuguese heritage with your team. - When you want to foster a sense of belonging and community within a diverse or distributed team. - As a culturally themed team-building session to strengthen relationships and shared values. - Whenever you want to recognize and celebrate the cultural backgrounds that make your team unique. ## Tips and tricks - Set an inclusive tone by welcoming all participants, whether or not they have Portuguese heritage, so everyone feels invited to contribute. - Add a festive atmosphere with Portuguese music, imagery, or a virtual background to spark the celebratory spirit. - Encourage personal stories and traditions, as these create the strongest connections and most memorable moments. - Give quieter team members space to contribute by using anonymous input and equal speaking time. - Capture concrete actions from the 'Keeping the Spirit Alive' topic so the celebration leads to lasting change. - Keep the session relaxed and time-boxed so it feels like a celebration rather than a meeting. ## Icebreaker questions - If you could visit any place in Portugal right now, where would you go and why? - What is one dish, song, or tradition from your own culture that you would love to share with the team? --- # Rock 'n' Retrospective URL: https://www.teamretro.com/retrospective-templates/rock-n-retrospective/ Crank up the energy in your next team reflection with the Rock 'n' Retrospective, a music-themed format that turns the sometimes routine retrospective into a memorable jam session. Using the universal language of rock music as a metaphor, this retrospective invites your team to riff on what hit the high notes, what fell flat, and what could become the next chart-topping improvement. It's a refreshing way to keep retrospectives fun while still surfacing meaningful insights about how the team is performing. The format works by mapping familiar musical concepts to the realities of teamwork. Your "Greatest Hits" celebrate wins worth replaying, the "Off-Key Notes" capture moments that didn't quite resonate, the "New Tracks" surface fresh ideas to experiment with, and the "Encore" focuses on the actions the team commits to bringing back next sprint. This playful structure lowers the barrier to honest conversation and helps quieter team members find their voice, all while keeping the discussion grounded in continuous improvement. Ideal for teams who appreciate a creative twist on agile ceremonies, the Rock 'n' Retrospective is perfect for breaking out of retro fatigue and re-energizing the group. Whether you run it at the end of a sprint, a project milestone, or a release, this template helps your team reflect, recognize achievements, and tune up the way they work together, one set list at a time. ## Topics - **Greatest Hits**: What went well that we'd love to play again? - **Off-Key Notes**: What fell flat or didn't quite hit the right note? - **New Tracks**: What new ideas or experiments should we try? - **Encore**: What actions do we commit to bringing back next sprint? ## When to use - When your team is experiencing retro fatigue and needs a fresh, energizing format to re-engage everyone. - At the end of a sprint, release, or project milestone to celebrate wins and identify improvements. - When you want a low-pressure, fun structure that encourages quieter team members to contribute. - For teams that enjoy creative, themed ceremonies and want to mix up their regular agile cadence. ## Tips and tricks - Set the mood by playing some upbeat music before the session starts to lean into the theme and get people relaxed. - Keep the celebration of Greatest Hits genuine, naming specific people and contributions makes recognition more meaningful. - Frame Off-Key Notes constructively so the conversation stays focused on improvement rather than blame. - Limit your Encore actions to two or three commitments so the team isn't overwhelmed and can actually follow through. - Rotate the facilitator each time you run it to keep perspectives fresh and share ownership of the ceremony. - Use dot voting to prioritise ideas when there are more suggestions than you have time to discuss. ## Icebreaker questions - If our last sprint had a theme song, what would it be and why? - What's the first concert you ever attended, or the one you wish you had? --- # Scrum Values URL: https://www.teamretro.com/retrospective-templates/scrum-values/ The Scrum Values Retrospective is a focused session that helps teams evaluate and strengthen their alignment with the five fundamental values that form the foundation of Scrum: Courage, Focus, Openness, Respect, and Commitment. This retrospective format encourages team members to reflect on how well they embody these values in their daily work and identify opportunities for improvement. By examining each value separately, teams can have meaningful discussions about their behaviors, challenges, and successes in living up to these principles. Originally outlined in the Scrum Guide by Ken Schwaber and Jeff Sutherland, these values are essential for building trust, fostering collaboration, and creating a healthy team culture. This retrospective helps teams move beyond mechanical process adoption to embrace the true spirit of Scrum. ## Topics - **Courage**: How do we tackle tough problems? - **Focus**: How can we improve focus on our goals? - **Openness**: How do we stay open to new things? - **Respect**: How do we respect each other? - **Commitment**: How can we make our commitments a reality? ## When to use - When the team is new to Scrum and needs to understand the values better - During times when team dynamics or performance issues suggest a disconnect from core values - As part of quarterly team health checks to ensure alignment with Scrum principles - When preparing for significant changes or challenges that will test the team's foundation ## Tips and tricks - Encourage specific examples rather than general statements to make the discussion more actionable - Use the Values Radar technique to visualize the team's current state for each value - Create a safe space for honest discussion by acknowledging that living these values is a journey - Consider discussing one value per day leading up to the retrospective to allow deeper reflection - Document concrete actions for improvement for each value to track progress - Use real scenarios from recent sprints to illustrate how values are being lived (or not) ## Icebreaker questions - Which Scrum value do you find easiest to practice and why? - Share a recent moment when you saw a teammate exemplify one of these values --- # Father's Day Reflections URL: https://www.teamretro.com/retrospective-templates/fathers-day-reflections-retrospective/ Father's Day is the perfect moment to pause and celebrate the dads, father figures, mentors, and role models who shape our lives and our teams. This warm, community-focused activity invites everyone to share stories, lessons, and appreciation in a way that builds connection and brings a little humanity into the workplace. It's a refreshing change of pace from the typical work-focused retrospective, giving teams space to bond over shared experiences and meaningful memories. It works by guiding participants through a series of reflective prompts — from favorite memories and lessons learned to the qualities that great father figures embody. Everyone contributes their thoughts, votes on the ones that resonate most, and discusses the themes that emerge. The format is intentionally lighthearted yet sincere, making it easy for people of all backgrounds and family situations to take part comfortably. Beyond the smiles and stories, this Father's Day reflection helps strengthen team culture, foster empathy, and remind everyone that the relationships and wisdom we carry outside of work often make us better collaborators within it. Whether your team is fully remote or sharing a room, it's an inclusive way to mark the occasion and celebrate the values that fatherhood inspires. ## Topics - **Favorite Memories**: What is a favorite memory of your dad or a father figure? - **Lessons Learned**: What valuable lesson did a father figure pass on to you? - **Qualities We Admire**: What qualities of a great father figure do you most admire? - **Appreciation & Thanks**: Who would you like to thank and what would you say? ## When to use - Around Father's Day to celebrate dads, father figures, and mentors as a team. - When you want a lighthearted, human-centered break from work-focused retrospectives. - To strengthen team culture and connection through shared personal stories. - As an inclusive seasonal activity that brings remote and in-person teams together. ## Tips and tricks - Set an inclusive tone from the start — acknowledge that 'father figure' can mean a dad, grandfather, uncle, mentor, or anyone who provided guidance. - Be sensitive to the fact that not everyone has a positive or present father figure; keep participation optional and judgment-free. - Keep it lighthearted and warm rather than overly formal — humor and storytelling make the session memorable. - Use the icebreaker to ease people in before moving to more personal reflections. - Allocate enough time for sharing; these conversations are richer when not rushed. - Consider sharing a group highlight or summary afterward to capture the warmth and gratitude expressed. ## Icebreaker questions - What's the best (or cheesiest) 'dad joke' you've ever heard? - If you could give your dad or a father figure any gift in the world, what would it be? --- # Back to the Future Retrospective URL: https://www.teamretro.com/retrospective-templates/back-to-the-future-retrospective/ Jump into your team's DeLorean and explore the past, present, and future of your work in one engaging retrospective. The Back to the Future format invites teams to revisit what happened in a previous period, take stock of where they are right now, and look ahead to where they want to go. By framing reflection as a time-travel adventure, it turns an everyday review into a memorable and creative session that keeps people energized and engaged. Inspired by the timeless appeal of the classic film, this retrospective works because it naturally connects lessons learned with forward-looking action. Looking back surfaces achievements and challenges, examining the present grounds the conversation in today's reality, and imagining the future motivates the team to set meaningful goals and commitments. This balance of hindsight, awareness, and foresight makes it ideal for sprint reviews, project milestones, or quarterly planning sessions. Run entirely in TeamRetro, this template helps facilitators guide teams through structured reflection, group similar ideas, vote on what matters most, and capture clear action items. Whether your team is celebrating a successful release or recovering from a tough sprint, the Back to the Future retrospective gives everyone a fun and meaningful way to learn from history and shape what comes next. ## Topics - **The Past**: What happened that shaped where we are now? - **The Present**: Where do we stand right now as a team? - **The Future**: Where do we want to go from here? - **The Action Plan**: What will we do to make that future happen? ## When to use - At the end of a sprint or project milestone when you want to connect lessons learned with future goals. - During quarterly or annual planning sessions to balance reflection with forward-looking commitments. - When team energy feels flat and a themed, creative retrospective format could re-engage participants. - After a major release or significant change, to assess how far you've come and where to head next. ## Tips and tricks - Set the scene with the time-travel theme to create a fun, relaxed atmosphere that encourages open sharing. - Timebox each phase—past, present, and future—so the conversation flows and you leave enough room for the action plan. - Encourage everyone to contribute privately before discussing, so quieter voices and diverse perspectives are captured. - Keep reflections on the past focused on learning, not blame, to maintain psychological safety. - Use dot voting to prioritize the future ideas and action items so the team focuses on what matters most. - Make sure every action item has a clear owner and due date so the future you imagine actually arrives. ## Icebreaker questions - If you had a time machine, which moment in your career would you go back and relive? - What's one piece of future technology you wish existed to make your work easier today? --- # Stranger Things: The Upside Down Retrospective URL: https://www.teamretro.com/retrospective-templates/stranger-things-the-upside-down-retro/ Step into the parallel world of your sprint with the Stranger Things: The Upside Down Retrospective — a playfully themed format inspired by the hit Netflix series. Just as the residents of Hawkins navigate between the everyday world and the eerie Upside Down, your team will explore both the bright, successful side of your work ("The Real World") and the lurking dangers, blockers, and hidden problems that pull you down ("The Upside Down"). This themed approach lowers the emotional barrier to discussing difficult topics, making it easier for teams to name the "Demogorgons" — the threats and risks they might otherwise avoid raising. The retrospective works by guiding your team through four themed quadrants: celebrating what went well, confronting the problems dragging you down, identifying the monsters and risks on the horizon, and arming yourselves with the tools and allies needed to fight back. Each topic invites honest reflection wrapped in a familiar, engaging narrative that keeps energy high and participation strong. By framing challenges as monsters to defeat rather than failures to dwell on, teams build psychological safety and a shared sense of mission. Perfect for teams looking to break the routine of standard sprint retrospectives, this pop-culture format is especially effective around Halloween, after a tough sprint, or whenever you want to inject some fun while still driving meaningful improvement. In TeamRetro, you can run it asynchronously or live, group similar ideas, vote on the biggest monsters to tackle, and turn insights into actionable next steps — all while having a great time exploring the Upside Down together. ## Topics - **The Real World**: What went well and kept us grounded this sprint? - **The Upside Down**: What problems dragged us down or felt darker than expected? - **The Demogorgons**: What monsters, risks or threats are lurking ahead? - **The Party's Arsenal**: What tools, allies or actions will help us fight back? ## When to use - Around Halloween or whenever you want to add a fun, themed twist to your regular sprint retrospective. - After a particularly tough or chaotic sprint where naming problems feels emotionally charged — the playful framing makes hard topics easier to raise. - When team energy is low and you want a creative format to boost engagement and participation. - To help newer or quieter team members open up by lowering the seriousness of discussing risks and blockers. ## Tips and tricks - Set the scene with a quick intro to the theme so everyone understands the metaphor — the Real World, the Upside Down, the Demogorgons, and the Party's Arsenal. - Keep the fun light but the insights real — make sure themed language doesn't trivialise genuine concerns or dismiss serious risks. - Use voting to prioritise which Demogorgons (risks) and Upside Down problems to tackle first, so you focus on what matters most. - Always close by converting the Party's Arsenal ideas into clear, owned action items with due dates. - Encourage equal participation by timeboxing brainstorming and inviting quieter members to share their monsters and wins. - Consider a themed background or playing the Stranger Things soundtrack to set the mood for an in-person or video session. ## Icebreaker questions - If you could have one Stranger Things character on your team this sprint, who would it be and why? - What's one 'monster' (work or otherwise) you defeated recently that you're proud of? --- # Motivation & Development Sprint Retrospective URL: https://www.teamretro.com/retrospective-templates/motivation-and-development-sprint-retrospective/ Keeping a team motivated while helping each person grow can feel like balancing two competing priorities, but they actually reinforce one another. The Motivation & Development Sprint Retrospective brings these themes together, giving your team space to reflect on what energized them, what drained them, and where they want to grow next. By connecting day-to-day sprint experiences with longer-term aspirations, this format helps teams stay engaged while building a culture of continuous improvement. During the session, participants explore the sources of their motivation, identify obstacles that sap their enthusiasm, and surface concrete development opportunities. This dual focus encourages honest conversations about workload, recognition, and career progression — topics that often get overlooked in a standard sprint retrospective. The result is a more human, well-rounded reflection that addresses both how the work felt and how people can stretch their skills. Ideal for agile teams, people managers, and anyone invested in employee engagement, this retrospective transforms feedback into action. Teams leave with a shared understanding of what keeps them inspired and a clear set of growth-oriented next steps, making it a powerful tool for boosting morale, retention, and performance over the long run. ## Topics - **What energized us?**: What boosted your motivation this sprint? - **What drained us?**: What sapped your energy or motivation? - **Where can we grow?**: What skills or areas do you want to develop? - **What will we commit to?**: What actions will sustain motivation and growth? ## When to use - When team morale or engagement feels low and you want to understand and reverse the cause. - At the end of a sprint when you want to combine performance reflection with personal growth planning. - During quarterly check-ins to align individual development goals with team motivation. - After a period of intense delivery or burnout to recharge and refocus the team. ## Tips and tricks - Set a positive, psychologically safe tone up front so people feel comfortable sharing what drained them without fear of blame. - Balance the conversation — don't let the 'what drained us' topic dominate; give equal weight to energy and growth. - Encourage participants to make development goals specific and personal rather than generic, so follow-through is more likely. - Assign clear owners and deadlines to every commitment to ensure motivation insights translate into real change. - Watch for dominant voices and use anonymous input to give quieter or more junior team members an equal say. - Revisit previous commitments at the start of the session to build accountability and momentum over time. ## Icebreaker questions - If your energy this sprint were a weather forecast, what would it be? - What's one small thing that always puts you in a good mood at work? --- # Innovation Lab Retreat URL: https://www.teamretro.com/retrospective-templates/innovation-lab-retreat/ Innovation thrives when teams step away from the day-to-day and give themselves permission to dream big, challenge assumptions, and experiment freely. The Innovation Lab Retreat is a structured space for teams to surface fresh ideas, evaluate what's worth pursuing, and map a path from concept to reality. It blends creative divergence with practical convergence, helping groups balance imaginative thinking with the discipline needed to actually ship something new. The format works by guiding participants through four connected stages: generating wild ideas, identifying what's holding innovation back, prioritising the most promising opportunities, and committing to concrete next steps. By moving through these phases together in TeamRetro, teams build shared ownership of their innovation pipeline and avoid the common trap of brainstorms that fizzle out with no follow-through. Anonymous contributions, grouping, and voting make it easy for every voice to be heard, including quieter team members who often hold the most original ideas. Whether you're hosting an offsite, kicking off a new product cycle, or simply trying to reignite your team's creative energy, this retreat gives you a repeatable framework for innovation. The goal is to leave with a curated set of ideas, a clear understanding of the obstacles in your way, and a prioritised list of actions you're excited to take forward. ## Topics - **Wild Ideas**: What bold or unconventional ideas could we explore? - **What's Holding Us Back**: What barriers stop us from innovating today? - **Worth Pursuing**: Which ideas show the most promise and potential? - **Launch Plan**: What concrete next steps will we commit to? ## When to use - Hosting a team offsite or retreat where creative thinking and fresh ideas are the focus. - Kicking off a new product cycle, quarter, or strategic initiative that needs fresh direction. - Reigniting a team's creative energy after a period of heavy delivery or routine work. - Building an innovation pipeline and wanting a repeatable way to generate, evaluate and act on ideas. ## Tips and tricks - Protect the divergent phase from criticism. Make it explicit that all ideas are welcome and judgement comes later, so people feel safe sharing bold thoughts. - Use anonymous contributions to reduce hierarchy bias and ensure junior voices and unconventional ideas get equal airtime. - Timebox each stage tightly. Innovation sessions can sprawl, so keep energy high by moving briskly from ideation to barriers to prioritisation. - Balance dreamers and pragmatists by valuing both the 'what's holding us back' realism and the 'wild ideas' optimism rather than letting one dominate. - Always close with owned, dated action items. The biggest risk of an innovation retreat is leaving inspired but doing nothing differently. - Capture parked ideas in a backlog so promising-but-premature concepts can resurface in a future cycle rather than being lost. ## Icebreaker questions - If you had unlimited budget and no fear of failure, what's the first thing you'd build? - What's the most creative idea you've ever had that never saw the light of day? --- # FLAP Retrospective URL: https://www.teamretro.com/retrospective-templates/flap-retrospective/ The FLAP retrospective is a comprehensive team reflection framework that examines four key areas: Future considerations, Lessons learned, Accomplishments, and Problem areas. This balanced approach helps teams celebrate successes while addressing challenges and planning ahead. By structuring discussion around these four dimensions, teams can effectively analyze their performance, extract valuable insights from their experiences, and create actionable plans for improvement. The framework encourages both forward-thinking and reflection on past events, making it particularly valuable for teams looking to maintain continuous improvement. The FLAP format creates a safe space for open dialogue about both achievements and challenges, while maintaining a strong focus on future growth and development. This makes it especially useful for teams who want to maintain momentum while addressing obstacles in their path. ## Topics - **Future considerations**: What direction do we want to take? - **Lessons learned**: What have our experiences taught us? - **Accomplishments**: What are we proud of? - **Problem areas**: What have we struggled with? ## When to use - When you want to balance reflection on past performance with future planning - After completing a significant project milestone or release - When the team needs to address ongoing challenges while maintaining motivation - During quarterly reviews to assess progress and plan improvements ## Tips and tricks - Start with Accomplishments to build positive energy before addressing challenges - Use dot voting to prioritize which items to discuss in detail - Ensure Future considerations are translated into specific, actionable items - Keep a parking lot for discussions that need to be continued outside the retrospective - Document lessons learned in a shared knowledge base for future reference - Set time boxes for each quadrant to maintain balanced discussion ## Icebreaker questions - What's one thing you learned last week that surprised you? - If you could instantly master one new skill, what would it be and why? --- # Treasure Hunt Retrospective URL: https://www.teamretro.com/retrospective-templates/treasure-hunt-retrospective/ The Treasure Hunt retrospective transforms strategic planning into an engaging adventure that helps teams identify their ultimate goals and chart a course to achieve them. Using the metaphor of a treasure expedition, teams explore valuable objectives, potential obstacles, navigation strategies, and required resources. This creative format encourages teams to think metaphorically about their journey, viewing challenges as 'rocks' to navigate around and team capabilities as their 'crew' strengths. The approach makes abstract concepts more tangible and memorable, while promoting creative problem-solving and team alignment. Particularly effective for long-term planning and team building, this retrospective helps teams maintain focus on their primary objectives while acknowledging potential risks and identifying the resources needed for success. The adventure theme creates an engaging atmosphere that encourages open dialogue and creative thinking. ## Topics - **Treasure**: What is our ultimate treasure? - **Rocks**: What risks and issues could we face? - **Navigation**: What will guide our way forward? - **Crew**: What skills and tools do we need? ## When to use - When starting a new project or initiative that requires clear goal setting and risk assessment - During strategic planning sessions where team engagement and creative thinking are crucial - When teams need to align on objectives and identify resource requirements - When you want to make a planning session more engaging and memorable ## Tips and tricks - Set the scene by using maritime or adventure terminology throughout the session to maintain the theme - Use visual aids like maps or treasure charts to track progress and capture insights - Ensure all team members contribute by going around the room for each topic - Keep a parking lot for detailed discussions that might derail the main session - Document action items clearly with owners and timelines - End the session by creating a 'treasure map' that outlines the path forward ## Icebreaker questions - If you could discover any treasure in the world, what would it be and why? - What's the most valuable thing you've ever found unexpectedly? --- # Birthday Bash Retrospective URL: https://www.teamretro.com/retrospective-templates/birthday-bash-retrospective/ There's nothing quite like a birthday to bring people together — and the Birthday Bash Retrospective channels that same spirit of celebration into a meaningful team reflection. Whether you're marking a team anniversary, a project launch, a year of working together, or simply someone's actual birthday, this format blends gratitude, fun, and forward-looking energy. It encourages teams to pause, appreciate how far they've come, and set intentions for the year ahead, all wrapped in a light and joyful theme. The Birthday Bash works by guiding participants through party-inspired prompts: the gifts (what we're grateful for), the candles (wishes for the future), the cake (sweet wins worth savouring), and the party fouls (things that didn't go to plan). Each metaphor lowers the barrier to honest conversation while keeping the mood upbeat. In TeamRetro, everyone adds their thoughts independently, then groups and votes on the themes that matter most before turning insights into clear actions. The benefit of a themed retrospective like this is that it re-energises teams who may feel fatigued by routine sprint reviews. By celebrating achievements alongside identifying improvements, you build psychological safety, strengthen team bonds, and ensure that recognition and growth go hand in hand. It's a perfect way to close out a meaningful period on a high note while still capturing the learnings that drive continuous improvement. ## Topics - **Gifts**: What are you grateful for from this period? - **Candles**: What do you wish for in the period ahead? - **The Cake**: Which sweet wins are worth savouring? - **Party Spoilers**: What didn't go to plan and how can we improve? ## When to use - Marking a team anniversary, project launch, or a full year of working together. - Closing out a major milestone where celebration and reflection should sit side by side. - Re-energising a team that feels fatigued by routine sprint retrospectives. - Building team morale and psychological safety through gratitude and recognition. - Setting shared intentions and wishes for the period ahead. ## Tips and tricks - Lean into the theme — use party emojis, a festive virtual background, or even a real cake to set the celebratory mood. - Start with The Gifts to anchor the session in positivity before exploring what didn't go well. - Keep The Party Fouls blameless by focusing on situations and systems, not individuals. - Timebox each topic so the fun energy keeps moving and no single section dominates. - Make sure every wish and improvement converts into a clear, owned action before you close. - Invite quieter members to share first or use anonymous entry so all voices are celebrated equally. ## Icebreaker questions - What's the best birthday gift you've ever received, and why did it mean so much? - If our team threw a party to celebrate this milestone, what would the theme be? --- # Employee Engagement Retrospective URL: https://www.teamretro.com/retrospective-templates/employee-engagement-retrospective/ An employee engagement retrospective is a structured meeting where team members reflect on factors influencing their motivation, satisfaction, and commitment at work. By openly discussing positives and areas for improvement, teams can pinpoint engagement strengths and roadblocks. This collaborative exercise helps build trust, gives employees a voice, and provides valuable insights for leaders. When facilitated effectively, it can boost morale, reduce turnover risks, and drive positive change. The retrospective format encourages diverse perspectives through a series of focused topics. Participants share candid reflections, which are captured and synthesized to inform action plans. ## Topics - **What energizes you?**: What aspects of your work or team environment make you feel motivated and engaged? - **What drains your energy?**: What workplace factors or experiences leave you feeling disengaged or demotivated? - **How can we improve teamwork?**: What changes could enhance collaboration, communication, and team dynamics? - **How can leadership support us?**: What could managers or leadership do to better engage and enable the team? ## When to use - To proactively identify factors impacting employee motivation, job satisfaction and retention. - After a period of high turnover, low morale or signs of disengagement to course-correct. - When undergoing organizational changes that could influence the employee experience. - As part of regular team health checks to keep a pulse on engagement levels. - To gather candid feedback and give employees a voice in shaping their work environment. ## Tips and tricks - Create a safe, judgment-free space for open and honest dialogue. - Encourage participation from all team members, including introverts and remote workers. - Have a neutral facilitator to keep discussions constructive and on track. - Capture all reflections anonymously to reduce bias or fear of repercussions. - Avoid becoming overly negative - balance criticism with suggested improvements. - Develop concrete action plans based on the insights to show commitment to change. ## Icebreaker questions - If you could switch roles with anyone on the team for a day, whose job would you want and why? - What's one small change that would make a big impact on your engagement and motivation? --- # Incident Response Planning URL: https://www.teamretro.com/retrospective-templates/incident-response-planning/ An Incident Response Planning exercise is a structured activity that helps teams proactively identify potential risks, vulnerabilities, and incidents that could impact their operations. By brainstorming and discussing various scenarios, teams can develop comprehensive incident response plans to mitigate risks, minimize downtime, and ensure business continuity. This desktop activity encourages cross-functional collaboration, fosters a culture of preparedness, and aligns teams on roles, responsibilities, and communication protocols during crises. It empowers teams to anticipate challenges, streamline decision-making processes, and enhance their overall resilience. ## Topics - **Potential Incidents**: What types of incidents could potentially impact our operations? - **Response Strategies**: How should we respond to these potential incidents? - **Roles and Responsibilities**: Who should be involved in incident response, and what are their roles? - **Communication Protocols**: How should we communicate during an incident? - **Recovery and Continuity**: How can we ensure business continuity and recovery after an incident? - **Continuous Improvement**: How can we learn and improve from incidents? ## When to use - When developing or updating your organization's incident response plan. - After experiencing a significant incident or near-miss, to identify areas for improvement. - As part of regular risk management and business continuity planning exercises. - When onboarding new team members or stakeholders involved in incident response efforts. - When introducing new systems, processes, or technologies that may impact incident response procedures. ## Tips and tricks - Involve cross-functional teams and stakeholders to ensure a comprehensive perspective and buy-in. - Encourage open and honest discussions, without fear of blame or retribution, to foster a culture of continuous improvement. - Regularly review and update incident response plans to align with changing business needs, technologies, and industry best practices. - Conduct regular training and simulations to validate plans and ensure team preparedness. - Establish clear communication protocols and designated spokespersons to maintain transparency and control messaging during incidents. - Prioritize critical systems, functions, and stakeholders for efficient resource allocation and recovery efforts. ## Icebreaker questions - If you could have any superpower during an incident response, what would it be and why? - Share a memorable incident or crisis you've experienced (personal or professional) and how it was handled. --- # Red Alert Retrospective URL: https://www.teamretro.com/retrospective-templates/red-alert-retrospective/ When something feels off, it pays to stop and sound the alarm before small problems become full-blown crises. The Red Alert retrospective is a focused, high-urgency format designed to help teams quickly identify the most pressing risks, blockers, and warning signs that threaten their goals. Rather than reviewing a sprint in broad strokes, this format zeroes in on what's burning, what's about to break, and what needs immediate attention so your team can act decisively. The session works by guiding participants through escalating levels of concern — from early warning signals to active emergencies — and then channeling that energy into clear, prioritized actions. Teams brainstorm issues, group related themes, vote on the most critical items, and assign owners to resolve them. Because it emphasizes urgency and accountability, the Red Alert format is especially valuable during incidents, troubled projects, or periods of rapid change where clarity and speed matter most. The real benefit is that it transforms anxiety and uncertainty into a structured, actionable plan. By openly naming risks and giving them a place to be discussed, teams reduce the chance that critical problems stay hidden until it's too late. Run it in TeamRetro to capture every alert, prioritize collectively, and walk away with a concrete response plan that keeps your team out of the danger zone. ## Topics - **Critical Emergencies**: What is on fire right now and needs immediate action? - **Warning Signs**: What early signals suggest trouble could be coming? - **Defuse & Stabilise**: What can we do to reduce risk and regain control? - **Action Plan & Owners**: Who will do what, and by when, to resolve these alerts? ## When to use - During or immediately after an incident or outage, when the team needs to rapidly identify what went wrong and stabilise the situation. - When a project is veering off track and you need to surface critical risks and blockers before they derail delivery. - In high-pressure periods of rapid change, where hidden problems are likely to escalate without focused attention. - As a periodic risk check-in for teams operating in volatile or high-stakes environments. ## Tips and tricks - Set the tone early that raising alarms is encouraged and blame-free — psychological safety is essential when discussing critical issues. - Keep the session tightly time-boxed; the urgency of a Red Alert works best when energy stays high and focused. - Use dot voting to quickly prioritise the most critical items so you don't try to fix everything at once. - Always close with clear owners and deadlines — a Red Alert without follow-up actions just creates more anxiety. - Watch for the loudest voices dominating; invite quieter members to share warning signs they may have noticed. - Revisit unresolved alerts at the next retrospective to ensure critical items don't quietly disappear. ## Icebreaker questions - What's the most dramatic 'red alert' moment you've experienced in a movie, game, or TV show? - If your week had a warning light on a dashboard, what colour would it be flashing right now? --- # Tennis Retrospective URL: https://www.teamretro.com/retrospective-templates/tennis/ The Tennis Retrospective is an engaging format that uses tennis terminology and concepts to structure team reflection sessions. Drawing parallels between tennis match dynamics and project execution, this retrospective helps teams analyze their performance through familiar sporting metaphors. Just as tennis players review their match performance, teams use this framework to examine their 'ground strokes' (foundational practices), celebrate their 'aces' (major wins), address 'unforced errors' (preventable mistakes), discuss 'deuce' situations (areas of uncertainty), and identify 'wild cards' (unexpected challenges). This format is particularly effective for teams who appreciate sports analogies or need a fresh perspective on their retrospective discussions. It encourages participants to think about their work in terms of both individual performance and team dynamics, much like the interplay between single matches and overall tournament success in tennis. ## Topics - **Ground Strokes**: What set us up for success? - **Aces**: What great wins did we deliver? - **Unforced Errors**: What mistakes did we make? - **Deuce**: What things could go either way? - **Wild Cards**: What unknowns did we encounter? ## When to use - When the team needs a fresh and engaging approach to their regular retrospective routine - After completing a major project milestone or release where various aspects of performance need to be analyzed - When you want to encourage more balanced discussions about both successes and areas for improvement - In situations where the team might benefit from using familiar sports metaphors to discuss their work ## Tips and tricks - Maintain the tennis theme throughout the session by using related terminology to keep engagement high - Encourage participants to think about both individual and team performance, just as tennis has singles and doubles matches - Use the concept of 'rally' to build upon others' ideas and maintain constructive discussion flow - Set a clear time 'match duration' for each topic to ensure balanced coverage of all areas - Consider using tennis scoring terminology (15-30-40) to prioritize action items - Create a safe space where 'unforced errors' can be discussed without blame or judgment ## Icebreaker questions - If your last sprint was a tennis match, what would the score be and why? - Which tennis player's qualities (persistence, precision, adaptability) best describes your team's current strengths? --- # Lean Coffee URL: https://www.teamretro.com/retrospective-templates/lean-coffee/ Lean Coffee is a structured, agenda-less meeting format that encourages open conversation and collaboration. Participants democratically build the agenda at the start by proposing topics they'd like to discuss. The group then votes on which topics to cover, allowing the most relevant discussions to emerge organically. This format promotes active engagement, knowledge sharing, and problem-solving within teams. It's particularly useful for surfacing new ideas, addressing challenges, and fostering continuous improvement. ## Topics - **To Discuss**: What topics should we discuss? - **In Progress**: This is currently being discussed. - **Discussed**: These topics have been discussed. ## When to use - When you want to encourage open discussion and collaboration within your team. - When you need to surface new ideas, address challenges, or explore opportunities for improvement. - When you want to foster continuous learning and knowledge sharing among team members. - When you prefer a flexible, democratic approach to setting the meeting agenda. ## Tips and tricks - Encourage participants to propose a wide range of topics, both technical and non-technical. - Use a timer to ensure discussions stay focused and move at a good pace. - Rotate the facilitator role among team members to promote shared ownership. - Follow up on action items or decisions made during the meeting. - Consider using an online board or tool to capture and vote on topics remotely. ## Icebreaker questions - If you could learn any new skill instantly, what would it be? - What's the most interesting or unusual hobby you've tried? --- # Rose Bud Thorn Retrospective URL: https://www.teamretro.com/retrospective-templates/rose-bud-thorn-retrospective/ The Rose Bud Thorn retrospective uses a garden metaphor to help teams reflect on their experiences in an intuitive and engaging way. Developed as a design thinking tool, this format encourages participants to view their work through three distinct lenses: successes (Roses), opportunities (Buds), and challenges (Thorns). Participants identify their 'Roses' - the things that went well and brought joy to their work, 'Buds' - emerging opportunities or ideas that show promise for growth, and 'Thorns' - the obstacles or challenges that caused difficulty. This natural metaphor makes the retrospective format accessible and memorable, helping teams maintain a balanced perspective of their experiences. The simplicity of the Rose Bud Thorn format makes it particularly effective for teams new to retrospectives or when working with cross-functional groups. It provides a structured yet creative way to gather insights and plan improvements while maintaining a positive outlook even when discussing challenges. You will see this exercise written as both "Rose Bud Thorn" and "Rose Thorn Bud" — they are the same activity, just listed in a different order, and the meaning of each term never changes. The Rose is always a success or highlight, the Thorn is always a challenge or pain point, and the Bud is always an opportunity or something showing early promise. Some facilitators prefer the "Rose Thorn Bud" ordering because it ends on the forward-looking Bud, finishing the reflection on a hopeful, future-focused note. Use whichever order your team finds most natural. The format grew out of the design-thinking and facilitation world — it is widely associated with the LUMA Institute's set of human-centred design methods — and it travels well beyond software retrospectives. Teachers use Rose Thorn Bud as a daily classroom check-in, managers use it to open one-on-ones, and families use it around the dinner table. For example, after a project sprint a team member's Rose might be "we shipped the new onboarding flow on time," their Thorn "QA was rushed in the last two days," and their Bud "the new analytics could tell us which step loses users." Its simplicity and the warmth of the garden metaphor are exactly why it works for groups who are new to structured reflection. ## Topics - **Rose**: Our positive outcomes, successes and wins. - **Bud**: Areas of opportunity waiting to blossom. - **Thorn**: Challenges and issues that are causing us pain. ## When to use - When you want a balanced view of team performance that includes both positives and negatives - During project milestones to assess progress and identify course corrections - With teams new to retrospectives who need an intuitive format - When you want to maintain a solution-oriented mindset while addressing challenges ## Tips and tricks - Start with Roses to build positive energy before addressing challenges - Encourage participants to be specific and provide concrete examples - Keep a balanced discussion time between all three categories - Look for connections between Thorns and Buds - challenges often contain opportunities - Document action items for nurturing Buds and addressing Thorns - Consider using dot voting to prioritize which Buds to focus on developing ## Icebreaker questions - If your week was a garden, what would be growing in it right now? - What's your favorite flower and why does it represent you? --- # Starfish Retrospective URL: https://www.teamretro.com/retrospective-templates/starfish-retrospective/ The Starfish retrospective is a technique developed by Patrick Kua to help teams reflect on varying degrees of actions and activities rather than simply the traditional what went well or what did not go well. The five key areas explored are: 1. Start: New practices or initiatives to begin. 2. More of: Existing strengths to amplify. 3. Continue: Positive aspects to maintain. 4. Less of: Areas that need scaling back. 5. Stop: Unproductive or detrimental activities to discontinue. By categorizing feedback into these actionable sections, teams can easily pinpoint growth opportunities and develop a clear plan for the next iteration. The Starfish retrospective promotes open discussion, continuous improvement, and team alignment. ## Topics - **Start**: What new practices or initiatives should we start? - **More of**: What existing strengths should we do more of? - **Continue**: What positive aspects should we continue? - **Less of**: What areas need to be scaled back or reduced? - **Stop**: What unproductive practices should we stop? ## When to use - At the end of a project or major milestone to identify areas for improvement in the next phase. - During a process review to optimize workflows and eliminate inefficiencies. - After a team restructuring or change in leadership to realign and set new goals. - Periodically (e.g., quarterly) to maintain a culture of continuous learning and growth. ## Tips and tricks - Encourage open and honest feedback by creating a safe, judgment-free environment. - Assign a dedicated facilitator to guide the discussion and ensure all voices are heard. - Focus on actionable items rather than dwelling on past mistakes or assigning blame. - Prioritize the most impactful items and create a clear action plan for addressing them. - Follow up on action items in subsequent meetings to ensure accountability and progress. ## Icebreaker questions - If our team was a type of fish, what kind would we be and why? - What's one thing you've learned recently that has made you more effective at work? --- # KFC Bucket Challenge Retrospective URL: https://www.teamretro.com/retrospective-templates/kfc-bucket-challenge-retrospective/ Bring some flavour to your team reflection with the KFC Bucket Challenge, a fun, food-themed retrospective that uses the iconic bucket of fried chicken as a playful metaphor for evaluating your team's recent work. Just as a great bucket combines the right ingredients, secret seasoning, and a crispy finish, a high-performing team blends the right practices, hidden strengths, and tasty wins. This lighthearted format lowers the barrier to honest conversation and helps even quieter team members open up. The retrospective is organised around four bucket-inspired themes: the Secret Recipe (what made us successful), the Soggy Pieces (what didn't quite work), the Extra Crispy (standout moments worth celebrating), and the Refill (what we want more of next time). By framing feedback through a familiar and fun lens, teams can spot patterns, surface improvements, and celebrate wins without the discussion feeling like a chore. Each idea can be grouped, voted on, and turned into clear action items inside TeamRetro. Ideal for teams looking to shake up their usual cadence, the KFC Bucket Challenge keeps energy high while still driving meaningful outcomes. It works especially well for sprint reviews, project wrap-ups, or any moment when you want reflection to feel rewarding rather than routine. Serve up better collaboration, one bucket at a time. ## Topics - **The Secret Recipe**: What practices made us successful this time? - **The Soggy Pieces**: What didn't quite work or left a bad taste? - **The Extra Crispy**: Which standout moments are worth celebrating? - **The Refill**: What do we want more of next time? ## When to use - When your team's regular retrospectives feel stale and you want to inject some fun and energy. - At the end of a sprint or project when you want to balance celebrating wins with identifying improvements. - For distributed or hybrid teams who could use a lighthearted, food-themed icebreaker to encourage open participation. - When you want quieter team members to feel more comfortable sharing honest feedback through a playful metaphor. ## Tips and tricks - Set the scene with the food theme up front, a fun framing helps the team relax and engage more openly. - Timebox each bucket-themed column so the conversation stays balanced and you don't spend all your time on the soggy pieces. - Make sure The Extra Crispy gets real attention, celebrating wins is just as important as fixing problems. - Use dot voting to prioritise which Soggy Pieces and Refill ideas matter most before turning them into action items. - Keep the tone blame-free, focus on practices and processes rather than individuals when discussing what didn't work. - End by assigning clear owners and due dates to action items so The Refill ideas actually make it onto the menu next time. ## Icebreaker questions - If you could only eat one fast food meal for the rest of your life, what would it be? - What's your secret ingredient that makes you a great teammate? --- # F-1 Grand Prix Retrospective URL: https://www.teamretro.com/retrospective-templates/f1-grand-prix-retrospective/ Buckle up and feel the adrenaline of the track with the F-1 Grand Prix Retrospective — a fast-paced, metaphor-driven format that turns your team's review into a thrilling pit-stop analysis. Inspired by the world of Formula 1 racing, this retrospective frames your sprint as a Grand Prix: where did you accelerate, what slowed you down, where did you need a pit stop, and how do you cross the finish line stronger next time? It's an energising way to reflect that resonates with motorsport fans and competitive teams alike. The Grand Prix metaphor works because racing mirrors how teams operate under pressure — speed, precision, teamwork, and constant tuning all matter. By mapping each part of the race to your working process, participants can articulate momentum, obstacles, and opportunities in a fun, shared language. The pit crew element naturally surfaces conversations about collaboration and support, while the finish line keeps everyone focused on outcomes and continuous improvement. Run this retrospective in TeamRetro to keep your team engaged and your meeting moving at full throttle. It's perfect for sprint reviews, project wrap-ups, or any moment when you want to inject some momentum into your reflection. Identify what's driving performance, fine-tune your engine, and get your team back on the grid ready to win the next race. ## Topics - **Full Throttle**: Where did we accelerate and gain speed? - **Yellow Flags**: What slowed us down or caused caution? - **Pit Stop**: What needs a tune-up or repair to keep racing? - **Finish Line**: What will help us cross the line and win next time? ## When to use - When your standard sprint retrospectives feel stale and you want to re-energise the team with a themed format. - At the end of a fast-paced or high-pressure sprint where speed, blockers and recovery were defining factors. - When wrapping up a project and you want a fun, metaphor-rich way to capture wins, obstacles and next steps. - With teams that enjoy competition or motorsport, to boost engagement and participation. - As a quarterly or milestone review to reflect on overall momentum and plan the next leg of the race. ## Tips and tricks - Lean into the racing metaphor — use language like laps, pit crew and racing line to keep the energy high and the framing consistent. - Set a clear time box for each topic so the session keeps moving at race pace rather than idling on one point. - Keep the Yellow Flags discussion blameless — focus on the obstacles and conditions, not on blaming individual drivers. - Make sure the Finish Line topic produces a small number of concrete, owned actions so insights turn into momentum. - Use anonymous brainstorming first to give quieter team members an equal voice before group discussion. - Group and vote on similar ideas to focus the conversation on the highest-impact pit stops and improvements. ## Icebreaker questions - If your work week were a race track, would it be a smooth straightaway or a series of hairpin turns? - Which Formula 1 driver or team best represents how you tackled this sprint, and why? --- # KALM Retrospective URL: https://www.teamretro.com/retrospective-templates/kalm-retrospective/ The KALM Retrospective gives teams a simple, balanced way to reflect on their practices through four lenses: Keep, Add, Less, and More. Rather than framing everything as good or bad, KALM invites people to think about behaviors and processes along a spectrum — what's working well and should continue, what's missing and should be introduced, what's draining energy and should be reduced, and what's valuable and deserves more attention. This nuanced approach surfaces insights that simple "what went well / what didn't" formats often miss. KALM works by gathering team feedback across these four categories, then grouping, discussing, and voting on the ideas that matter most. The strength of this format lies in the "Less" and "More" columns, which acknowledge that many team practices aren't entirely good or bad — they just need to be dialed up or down. This makes it especially powerful for mature teams who have already addressed the obvious wins and blockers and want to fine-tune their ways of working with greater precision. Popularized within the agile and Scrum communities as a refreshing alternative to the classic Start/Stop/Continue retrospective, KALM helps teams generate actionable, calibrated improvements. By framing reflection around continuation and intensity rather than absolute judgments, teams build a culture of continuous improvement that feels constructive rather than critical — making it an excellent choice for recurring sprint retrospectives. ## Topics - **Keep**: What is working well that we should continue doing? - **Add**: What is missing that we should introduce or start doing? - **Less**: What should we reduce because it's draining time or value? - **More**: What valuable thing deserves more time or focus? ## When to use - When your team has outgrown basic Start/Stop/Continue formats and wants a more nuanced way to calibrate their practices. - For recurring sprint retrospectives where the obvious wins and blockers have already been addressed and you want to fine-tune how the team works. - When you want to balance positive reflection with constructive change without framing things as simply good or bad. - For mature agile teams looking to drive continuous improvement by adjusting the intensity of existing practices. ## Tips and tricks - Start with the Keep column to set a positive, affirming tone before moving into areas that need change. - Encourage specificity — vague items like 'more communication' are hard to action, so push for concrete examples. - Use the Less and More columns to capture nuance; not everything is binary, and many practices just need dialing up or down. - Give everyone quiet time to add their own ideas before discussion to reduce groupthink and ensure quieter voices are heard. - Group similar items, then dot-vote to focus discussion on the highest-impact themes rather than trying to cover everything. - Close the session by turning the top voted items into clear, owned action items with due dates so insights lead to change. ## Icebreaker questions - If your week were a thermostat, would it have been set to too hot, too cold, or just right? - What's one habit you'd like to keep doing and one you'd happily do less of in everyday life? --- # Definition of Done URL: https://www.teamretro.com/retrospective-templates/definition-of-done-retrospective/ Ever shipped something only to discover it wasn't really finished? The Definition of Done (DoD) brings clarity to one of the most important shared agreements a team can have. It establishes a clear, collective understanding of the criteria that must be met before any piece of work — a user story, a feature, or an entire sprint — can be considered truly complete. By making these expectations explicit, teams reduce rework, improve quality, and create a reliable, repeatable standard for delivery. Rooted in agile and Scrum practices, the Definition of Done acts as a quality checklist that everyone agrees to before work begins. It removes the guesswork from "is this finished?" conversations and helps teams avoid the trap of carrying hidden work forward into future sprints. Whether you're defining done for the first time or revisiting an existing agreement, this collaborative session encourages every voice to contribute — from developers and testers to designers and product owners — so the result reflects the whole team's perspective. Running this session in TeamRetro makes it easy to capture, discuss, group, and prioritize the criteria that matter most to your team. The outcome is a living document that grows with your team's maturity and standards. The result is more predictable delivery, fewer surprises in review, and a shared sense of accountability that lifts the quality of everything you ship. Learn more about the concept from the Scrum.org guide to the Definition of Done. ## Topics - **Quality Criteria**: What quality standards must work meet to be done? - **Documentation & Communication**: What needs to be documented or shared before done? - **Testing & Validation**: How do we verify the work actually works? - **Deployment & Readiness**: What must be true to safely release the work? ## When to use - When a new team is forming and needs to establish shared quality standards from the start. - When work is frequently being reopened or bugs are slipping into production, signaling unclear completion criteria. - Before starting a new project or sprint to ensure everyone agrees on what finished looks like. - When onboarding new members who need to understand the team's quality expectations. - During a retrospective when the team identifies inconsistency in how work is considered complete. ## Tips and tricks - Co-create the Definition of Done with the whole team so everyone feels ownership — avoid letting one person dictate the standards. - Keep criteria realistic and achievable; an overly ambitious DoD that's never met undermines its purpose. - Make each criterion specific and verifiable so there's no ambiguity about whether it has been satisfied. - Treat the Definition of Done as a living document and revisit it periodically as your team's standards and tooling evolve. - Encourage quieter team members to contribute by giving everyone time to add ideas independently before group discussion. - Distinguish between the Definition of Done and acceptance criteria — the DoD applies to all work, while acceptance criteria are story-specific. ## Icebreaker questions - If 'done' had a personality, what would it be like — perfectionist, pragmatist, or last-minute hero? - What's the most surprising thing you once discovered was NOT actually finished? --- # Anime Adventure Retrospective URL: https://www.teamretro.com/retrospective-templates/anime-adventure-retrospective/ Every great anime tells the story of a hero who faces trials, gains powerful allies, battles fearsome villains, and levels up along the way — and your team's sprint is no different. The Anime Adventure retrospective reimagines your iteration as a thrilling shōnen arc, where wins become epic power-ups, obstacles become formidable bosses, and the team's mission moves ever closer to its goal. By wrapping reflection in a fun, story-driven theme, this format lowers the barrier to honest conversation and energises teams that might be feeling fatigued by traditional retro formats. The retrospective works by guiding the team through four themed stages: celebrating the victories and power-ups that propelled them forward, naming the villains and obstacles that stood in the way, recognising the allies and teamwork that made a difference, and charting the next quest ahead. Each prompt invites participants to share candid reflections through the lens of an adventure narrative, making it easier to surface both successes and frustrations without finger-pointing. Once ideas are added and grouped in TeamRetro, the team votes on the most important themes and turns insights into clear, trackable action items. Ideal for teams who enjoy a creative, playful approach to continuous improvement, the Anime Adventure retrospective is a memorable way to break routine while still delivering the substance of a great sprint review. It builds psychological safety, celebrates progress, and keeps everyone engaged — proving that meaningful reflection and a bit of fun can go hand in hand. ## Topics - **Power-Ups & Victories**: What wins and breakthroughs powered the team forward? - **Villains & Obstacles**: Which bosses and challenges blocked the team's progress? - **Allies & Teamwork**: Who and what supported the team on the journey? - **The Next Quest**: What's the mission and plan for the next adventure? ## When to use - When your team is feeling fatigued by traditional retrospective formats and needs a fresh, playful approach to re-energise reflection. - After completing a particularly challenging or eventful sprint that feels worthy of an epic story. - For teams that share a love of anime, gaming or storytelling and respond well to themed, narrative-driven activities. - As a fun way to build psychological safety in newer teams by framing problems as 'bosses to defeat' rather than failures. ## Tips and tricks - Set the scene at the start by briefly framing the sprint as an anime arc — it helps everyone get into the storytelling mindset. - Encourage playful language but keep the focus on real, actionable insights so the fun doesn't dilute the substance. - Use the 'villains' framing to depersonalise problems — it makes it safer for people to raise frustrations without blame. - Timebox each stage so the adventure keeps moving and quieter voices get equal airtime. - Group similar ideas before voting to spot recurring 'bosses' or repeated power-ups worth acting on. - Always convert the top themes from 'The Next Quest' into clear, owned action items before closing the session. ## Icebreaker questions - If your team were an anime party, which character archetype would you be — the hero, the strategist, the comic relief or the wise mentor? - What anime power or special ability would help you most in your day-to-day work? --- # Oscar Academy Retrospective URL: https://www.teamretro.com/retrospective-templates/oscar-academy-retrospective/ The Oscar Academy retrospective transforms team reflection into an engaging awards ceremony format, celebrating achievements and learning opportunities through the lens of movie industry recognition. Drawing inspiration from the prestigious Academy Awards, this innovative approach encourages teams to acknowledge outstanding contributions and memorable moments from their recent work period. Teams evaluate their experiences across four key categories: Best Performance (standout achievements), Best Actions (effective strategies), Best Story (learning experiences), and Best Supporting Roles (valuable resources and support). This format creates an atmosphere of appreciation while maintaining the serious purpose of continuous improvement. By structuring feedback in this entertaining way, teams can overcome reluctance to share feedback and create a psychologically safe environment where both successes and challenges can be discussed openly. The familiar awards ceremony concept helps make the retrospective more approachable and memorable. ## Topics - **Best Performance**: What should we shine a light on? - **Best Actions**: What contributed strongly to our outcomes? - **Best Story**: What stories did we learn from? - **Best Supporting Roles**: What tools, people or resources supported us? ## When to use - When you want to make your retrospective more engaging and fun while maintaining its effectiveness - After completing a significant project milestone or achievement that deserves celebration - When team morale needs a boost and you want to focus on recognition and appreciation - When you want to encourage more participation and openness in retrospective discussions ## Tips and tricks - Consider creating physical awards or certificates to make the recognition more tangible and memorable - Rotate the role of 'ceremony host' among team members to increase engagement and ownership - Keep the tone light and fun, but ensure important lessons and feedback aren't lost in the entertainment - Use movie-industry terminology to maintain the theme (e.g., 'That's a wrap!' to close the session) - Consider adding sound effects or music to enhance the awards ceremony atmosphere - Set a time limit for each 'award category' to maintain good pacing and energy ## Icebreaker questions - If your last sprint was a movie, what would its title be and why? - Which famous movie quote best describes your work this past week? --- # Agile Delivery Maturity Model URL: https://www.teamretro.com/health-check-templates/agile-delivery-maturity-model/ Strong agile delivery depends on more than ceremonies and tooling — it requires a backlog that is ready, work that flows predictably, teams that collaborate across disciplines, and a habit of learning from every iteration. This maturity model helps agile teams assess how they plan, prioritize, deliver, and improve, mapping each practice across five stages from ad hoc to optimized. By rating each dimension together, teams build a shared picture of where delivery is strong and where focused investment will unlock faster, more reliable outcomes. ## Planning & Prioritization How well the team prepares, decomposes, and aligns on the work it takes on. - **Backlog Readiness**: How prepared and refined is the team's backlog for upcoming work? - **Work Decomposition**: How effectively does the team break down work into manageable pieces? - **Prioritization Alignment**: How well aligned is the team on priorities with stakeholders and business goals? ## Delivery Flow How smoothly and predictably work moves from start to released value. - **Work-in-Progress Management**: How well does the team manage the amount of work in progress? - **Cycle Time Predictability**: How predictable is the time from starting work to completion? - **Release Cadence**: How regularly and reliably does the team release working software? ## Team Collaboration How effectively the team works together, shares knowledge, and makes decisions. - **Cross-Functional Cooperation**: How well do team members with different skills collaborate? - **Knowledge Sharing**: How effectively does the team share knowledge and reduce silos? - **Decision-Making Efficiency**: How quickly and effectively does the team make decisions? ## Continuous Feedback & Improvement How consistently the team reflects, learns, and uses data to get better over time. - **Retrospective Effectiveness**: How valuable and actionable are the team's retrospectives? - **Metrics-Driven Improvement**: How well does the team use data and metrics to guide improvement? --- # Agile Manifesto Principles URL: https://www.teamretro.com/health-check-templates/agile-manifesto-principles/ Grounded in the twelve principles behind the Agile Manifesto, this assessment helps teams gauge how well their day-to-day practices reflect the values that make agile work. Each statement maps directly to one of the original principles — from continuous delivery and welcoming change to sustainable pace, technical excellence, and regular reflection. By rating their level of agreement across all twelve, teams surface where they are living the agile mindset and where habits have drifted from intent, sparking honest conversations about how to improve. ## Agile Principles The twelve principles behind the Agile Manifesto, rated by how strongly your team agrees that each reflects the way you actually work. - **Continuous Delivery**: *Principle 1*. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. - **Openness to Change**: *Principle 2*. We welcome changing requirements, even late in development. Our agile processes harness change for the customer’s competitive advantage. - **Frequent Releases**: *Principle 3*. We deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. - **Collaboration**: *Principle 4*. Our business people and developers work together daily throughout the project. - **Team Enablement**: *Principle 5*. We build projects around motivated individuals. We give them the environment and support they need, and trust them to get the job done. - **Communication**: *Principle 6*. We have efficient and effective face-to-face conversations to convey information to and within a development team. - **Working Software**: *Principle 7*. Our working software is the primary measure of progress. - **Sustainable Development**: *Principle 8*. Our agile processes promote sustainable development. Our sponsors, developers, and users can maintain a constant pace indefinitely. - **Quality**: *Principle 9*. We pay continuous attention to technical excellence and good design to enhance agility. - **Simplicity**: *Principle 10*. We embrace simplicity – the art of maximizing the amount of work not done. - **Self-Organization**: *Principle 11*. The best architectures, requirements, and designs emerge because we are a self-organizing team. - **Continuous Improvement**: *Principle 12*. At regular intervals, our team reflects on how to become more effective, then tunes and adjusts our behavior accordingly. --- # Agile Manifesto Values URL: https://www.teamretro.com/health-check-templates/agile-manifesto-values/ Grounded in the four core values of the Agile Manifesto, this assessment helps teams reflect on how strongly they live out agile principles in their day-to-day work. By weighing individuals and interactions, working software, customer collaboration, and responding to change against their traditional counterparts, teams gain a shared understanding of where their mindset truly sits. Use the results to spark honest conversations, surface hidden tensions, and align on the behaviours that make agility real rather than aspirational. ## Agile Manifesto Values The four foundational values from the Agile Manifesto that guide how agile teams prioritise their work and collaborate. - **Individuals and Interactions**: Reflects whether the team prioritises people and direct communication over rigid processes and tooling. - **Working Software**: Reflects whether the team prioritises delivering functional software over producing extensive documentation. - **Customer Collaboration**: Reflects whether the team prioritises ongoing collaboration with customers over fixed contract terms. - **Responding to Change**: Reflects whether the team prioritises adapting to change over strictly adhering to a predefined plan. --- # Agile Teams Maturity Model URL: https://www.teamretro.com/health-check-templates/agile-teams/ Strong agile teams blend healthy collaboration, disciplined ways of working, and a culture of continuous improvement to deliver customer value predictably. This assessment helps agile teams reflect across six dimensions — from teamwork and ceremonies to technical excellence and mindset — using a staged maturity scale that runs from Ad Hoc to Optimized. By rating where they sit today, teams uncover their strengths, surface hidden blockers, and agree on the practices worth investing in next. Use it as a recurring agile health check to track progress over time, spark honest retrospective conversations, and build a shared roadmap toward higher-performing, self-organizing delivery. ## Teamwork & Collaboration How well the team communicates, shares ownership, and works together to deliver value. - **Team Communication**: Team members communicate openly and effectively. - **Collaborative Problem Solving**: The team collaborates to solve problems rather than working in silos. - **Raising Blockers Early**: Team members are comfortable raising blockers and challenges early. - **Cross-Functionality**: The team is cross-functional enough to deliver work end-to-end. - **Self-Organization & Ownership**: The team is self-organizing and takes ownership of how work gets done. ## Agile Ways of Working (Processes & Ceremonies) How effectively the team uses agile ceremonies and processes to stay aligned and keep work flowing. - **Daily Standups**: Daily standups help us synchronize effectively. - **Backlog Refinement**: Backlog refinement keeps upcoming work understood and ready. - **Sprint Reviews & Demos**: Sprint reviews (or demos) help us share progress and gather feedback. - **Retrospectives & Improvement**: Retrospectives lead to useful insights for improving how we work. - **Flow of Work**: Work items flow smoothly through our process without unnecessary delays. ## Planning & Prioritization How well the team plans, prioritizes, and forecasts work to maximize value and predictability. - **Value-Driven Backlog**: The product backlog is prioritized and reflects customer value. - **Team Involvement in Planning**: The team participates meaningfully in planning work. - **Estimation & Forecasting**: The team's estimates or forecasts help guide realistic commitments. - **Adaptive Planning**: Plans adapt based on new information without excessive disruption. - **Definition of Done**: We understand what "done" means and use it consistently. ## Technical Excellence & Quality How consistently the team builds in quality, manages technical debt, and sustains a healthy codebase. - **Quality Built-In**: Quality is built into our work through testing and review practices. - **Technical Debt Management**: The team addresses technical debt proactively. - **Test Automation**: Automated tests or checks support our development process. - **Continuous Integration**: We integrate and test code frequently to avoid large integration issues. - **Maintainable Codebase**: The team maintains a sustainable, maintainable codebase. ## Product Delivery & Customer Value How frequently and reliably the team delivers valuable increments and learns from customer feedback. - **Delivery Frequency**: We deliver working software or product increments frequently. - **Value Alignment**: Our work directly contributes to customer or business value. - **Feedback Loops**: We gather customer or stakeholder feedback regularly. - **Speed to Release Change**: Changes and improvements can be released quickly when needed. ## Agile Mindset, Culture & Continuous Improvement How deeply the team lives agile values — sustainable pace, learning, adaptability, and a drive to keep improving. - **Sustainable Pace**: The team maintains a sustainable work pace. - **Continuous Improvement Mindset**: We actively look for ways to improve our process or outcomes. - **Learning from Mistakes**: Mistakes are treated as learning opportunities rather than blame events. - **Embracing Change**: The team embraces change and adapts when needed. --- # AI Adoption Maturity URL: https://www.teamretro.com/health-check-templates/ai-adoption-maturity/ Adopting AI is rarely about the tools alone — it depends on strategy, skills, trust, governance, and the everyday habits that make AI a dependable part of how a team works. This assessment maps your team's AI adoption maturity across nine connected areas, from leadership and tooling to skills, workflow integration, data, governance, output quality, collaboration, and impact. Using a staged maturity scale that runs from Ad Hoc to Optimized, it gives teams a shared, honest picture of where they stand today and a clear sense of what 'better' looks like next. The result is a grounded conversation that turns AI enthusiasm into deliberate, responsible, and measurable progress. ## AI Strategy & Leadership How clearly AI use connects to goals, how use cases are chosen, and how actively leaders support and own responsible adoption. - **Strategic Alignment**: Our use of AI clearly supports our team, department, or organizational goals. - **Use Case Prioritization**: We choose AI use cases based on value, feasibility, and risk. - **Leadership Support**: Leaders actively encourage and guide responsible AI adoption. - **Ownership & Accountability**: Responsibilities for AI decisions, usage, and outcomes are clearly defined. ## Tool Adoption & Access Whether the team can get the right AI tools, whether those tools fit the work, and how consistently they're used. - **Tool Availability**: Team members can access the AI tools they need to do their work well. - **Tool Fit**: Our AI tools fit the tasks, workflows, and needs of our team. - **Adoption Consistency**: Team members use AI tools consistently where they add value. - **Tool Awareness**: We stay informed about new AI capabilities relevant to our work. ## AI Skills & Confidence The team's understanding of AI, its prompting and critical-thinking skills, and how deliberately it grows them. - **AI Literacy**: We understand what AI can and cannot do. - **Prompting Skill**: We give AI clear instructions, context, and constraints. - **Critical Thinking**: We question, check, and refine AI-generated outputs. - **Learning & Development**: We invest deliberately in growing our AI skills. ## Workflow Integration How naturally AI fits into daily work, standard processes, the human-AI balance, and redesigned ways of working. - **Daily Use**: AI is naturally part of our everyday work. - **Process Integration**: AI is built into our standard processes, not bolted on. - **Human-AI Balance**: We know when to rely on AI and when human judgment, expertise, or review is essential. - **Work Redesign**: We rethink tasks, roles, and workflows to take advantage of AI. ## Data, Knowledge & Context Whether the team feeds AI reliable data, can reach the knowledge it needs, provides good context, and stewards its assets. - **Data Quality**: The information we use with AI tools is reliable, accurate, and up to date. - **Knowledge Access**: We can easily access the internal knowledge needed for AI-assisted work. - **Context Provision**: We provide AI with the right background, examples, and constraints. - **Data Stewardship**: We manage ownership, accuracy, and appropriate use of data and knowledge assets. ## Governance, Risk & Compliance Awareness of AI policy, protection of privacy, attention to bias and fairness, and the auditability of AI use. - **Policy Awareness**: We understand the organization's AI policies, boundaries, and approvals. - **Privacy & Confidentiality**: We avoid entering sensitive, personal, or restricted information into AI tools. - **Bias & Fairness**: We consider bias, fairness, and potential harm in AI-assisted outputs. - **Auditability**: We document when, how, and why AI is used for important work. ## Output Quality & Human Review How well the team verifies accuracy, upholds quality standards, applies human oversight, and learns from AI errors. - **Accuracy Checking**: We verify AI-generated information before using it. - **Quality Standards**: AI-assisted outputs meet our standards for clarity, accuracy, and professionalism. - **Human Oversight**: We have clarity on when human review or approval is required. - **Error Learning**: We learn from AI mistakes, hallucinations, and poor outputs. ## Collaboration & Knowledge Sharing Whether the team shares practices, experiments safely, learns across teams, and builds reusable AI assets. - **Shared Practices**: We share useful prompts, examples, workflows, and lessons learned. - **Experimentation Culture**: Team members feel safe and encouraged to experiment with AI responsibly. - **Cross-Team Learning**: We learn from other teams, departments, and external examples of AI adoption. - **Reusable Assets**: We build reusable AI templates, prompt libraries, checklists, and playbooks. ## Impact Measurement & Improvement Whether the team measures AI's effect on productivity, quality, and business value — and uses what it learns to improve. - **Productivity Impact**: We assess whether AI saves time or increases team capacity. - **Quality Impact**: We assess whether AI improves the quality, consistency, and usefulness of our work. - **Business Value**: We connect AI use to measurable outcomes such as customer value, cost savings, or speed. - **Continuous Improvement**: We use feedback, results, and lessons learned to improve how we use AI. --- # AI-Assisted Coding Maturity URL: https://www.teamretro.com/health-check-templates/ai-assisted-coding-maturity/ AI coding assistants have moved from novelty to daily tool, but adoption alone doesn't make a team effective. This maturity model helps engineering teams take an honest look at how they use AI across the development lifecycle — from tool adoption and prompting skill to output validation, security, and measurable impact. By rating each dimension on a five-stage scale from Ad Hoc to Optimized, teams build a shared picture of where they are strong, where AI introduces risk, and where deliberate investment will pay off. Use it to spark candid conversation, set a baseline, and track how your AI-assisted development practice grows over time. ## Tool Adoption How broadly and thoughtfully AI coding tools are taken up, configured, and kept current across the team. - **Tool Coverage**: We use AI coding tools consistently across our daily development work. - **Configuration Quality**: Our AI tools are well-configured for our codebase, workflows, and project context. - **Onboarding Support**: New team members get up to speed quickly on our AI tooling and practices. - **Tool Awareness**: We stay informed about new AI coding capabilities and reassess our toolchain. ## Prompting Skills How well the team communicates with AI tools — through clear prompts, good context, refinement, and right-sized tasks. - **Prompt Clarity**: We describe tasks to AI tools clearly and precisely. - **Context Provision**: We give AI tools the right context — code, constraints, and intent — to do their best work. - **Iterative Refinement**: We refine and redirect AI responses effectively when the first try misses. - **Task Decomposition**: We break complex work into AI-sized pieces that produce reliable results. ## Output Validation How rigorously the team reviews, tests, and questions AI-generated code before trusting it. - **Code Review Rigor**: We review AI-generated code as carefully as human-written code. - **Test Coverage**: Our AI-generated code is backed by automated tests. - **Critical Evaluation**: We question and verify AI output rather than accepting it at face value. - **Bug Attribution**: We can tell when a defect originated from AI-assisted code. ## Workflow Integration How naturally AI assistance fits into daily habits, the toolchain, team processes, and the human-AI balance. - **Daily Habit**: AI assistance is naturally part of our day-to-day engineering work. - **Pipeline Fit**: AI tools fit smoothly into our development environment and CI/CD pipeline. - **Process Adaptation**: We have adapted our processes to get the most from AI-assisted development. - **Human-AI Balance**: We know when to rely on AI and when to lean on our own judgment. ## Security & Compliance How well the team protects sensitive data, follows policy, and manages IP, licensing, and security risks in AI-generated code. - **Data Handling**: We avoid exposing sensitive or confidential information to AI tools. - **Policy Adherence**: We consistently follow organizational AI usage policies. - **IP & Licensing Awareness**: We understand intellectual-property and licensing risks in AI-generated code. - **Vulnerability Vigilance**: We actively check AI-generated code for security issues. ## Knowledge Sharing How openly the team captures prompts, shares wins and failures, collaborates across teams, and grows its AI skills. - **Prompt Libraries**: We document and share effective prompts and AI patterns. - **Learning Culture**: We openly share wins, failures, and experiments with AI-assisted development. - **Cross-Team Collaboration**: We exchange AI coding practices with people outside our immediate team. - **Skill Development**: We invest deliberately in growing our AI-assisted development skills. ## Impact Measurement How honestly the team tracks AI's effect on productivity and quality, and folds those lessons back into how it works. - **Productivity Tracking**: We assess whether AI tools genuinely improve our delivery speed. - **Quality Metrics**: We evaluate whether AI assistance helps or hurts the quality of our work. - **Retrospective Integration**: We reflect on AI-assisted development during our retrospectives. - **Continuous Improvement**: We adjust our AI usage based on feedback, outcomes, and lessons learned. --- # Community of Practice URL: https://www.teamretro.com/health-check-templates/community-of-practice/ Communities of Practice thrive when members feel connected, aligned, and energized to learn together. Use this check to explore how well your community shares knowledge, collaborates, stays focused on common goals, and keeps people motivated to grow. The results reveal where your community is working well and where small changes could unlock greater participation, trust, and shared value across the group. ## Community of Practice Explore the health of your Community of Practice across knowledge sharing, alignment, collaboration, feedback, and motivation. - **Knowledge Sharing**: Gauges whether members have the opportunity, means, and willingness to share and learn from one another. - **Alignment**: Reflects how clearly the community shares a common focus on its goals and challenges. - **Collaboration**: Measures how effectively members work together to solve complex problems. - **Feedback**: Assesses whether members feel safe and are encouraged to give and receive feedback. - **Motivation and Fun**: Captures how engaged and inspired members feel to learn and grow within the community. --- # Customer Support URL: https://www.teamretro.com/health-check-templates/customer-support/ Great customer experiences depend on more than fast replies — they require consistent processes, proactive success management, strong knowledge resources, and a clear line back to the voice of the customer. This maturity assessment helps support and customer success teams gauge where they stand today and what "good" looks like as they grow. Spanning support operations, customer success outcomes, knowledge and enablement, and voice of customer, it maps each capability across five maturity levels from Ad Hoc to Optimized. Teams use the results to surface gaps, align on priorities, and build a shared roadmap toward scalable, customer-centric service. ## Support Operations Evaluate how efficiently and consistently the team resolves customer issues, applies support workflows, and manages escalations. - **Issue Resolution Effectiveness**: How quickly and effectively customer issues are resolved. - **Support Workflow Consistency**: Quality and consistency of support processes across the team. - **Escalation Management**: How well the team handles complex or high-severity issues. ## Customer Success Outcomes Assess how well the team drives customer adoption, monitors account health, and manages renewals and retention. - **Success Planning & Goal Alignment**: How well success plans guide customers toward meaningful outcomes. - **Account Health Monitoring**: Visibility into customer health and risk indicators. - **Renewal & Retention Management**: How effectively the team retains customers and manages renewals. ## Knowledge & Enablement Examine the quality of customer-facing knowledge, enablement resources, and how insights are shared internally. - **Knowledge Base Quality**: Accuracy, usefulness, and accessibility of customer-facing knowledge resources. - **Customer Enablement Resources**: How effectively customers are taught to use the product. - **Internal Knowledge Sharing**: How well support and success teams share insights internally. ## Voice of Customer (VOC) Gauge how systematically customer feedback is captured, shared across teams, and used to track and improve satisfaction. - **Feedback Collection & Analysis**: How effectively customer feedback is gathered, processed, and understood. - **Cross-Functional Insight Sharing**: How VOC insights influence product, engineering, and business decisions. - **Customer Satisfaction Tracking**: How effectively customer sentiment is monitored and acted upon. --- # Data & Analytics URL: https://www.teamretro.com/health-check-templates/data-and-analytics/ Strong data and analytics capabilities are what separate organizations that react from those that anticipate. This maturity model helps teams evaluate where they stand across the full data lifecycle — from how trustworthy and well-governed their data is, through the reliability of reporting and insight, to the infrastructure that powers access, the rigor of experimentation, and the culture that turns numbers into decisions. By rating each dimension on a five-stage scale from Ad Hoc to Optimized, teams build a shared understanding of their current state, surface the gaps holding them back, and prioritize the investments that will move them toward a confident, data-driven way of working. ## Data Quality & Governance How accurate, well-governed, and secure your data is across the organization. - **Data Accuracy & Reliability**: How trustworthy, consistent, and error-free data is across systems. - **Data Governance & Ownership**: How clearly data responsibilities, rules, and standards are defined. - **Data Security & Access Control**: How well data is protected while remaining accessible to authorized users. ## Reporting & Insight How reliably reporting, dashboards, and insights support confident decisions. - **Reporting Reliability**: How consistently reporting is available, accurate, and timely. - **Dashboard & Insight Usability**: How easy it is for teams to interpret and act on insights. - **Decision Support**: How effectively data informs strategic and operational decisions. ## Infrastructure & Accessibility How well data infrastructure scales, integrates, and serves the people who need it. - **Data Infrastructure Scalability**: How well data systems scale and perform as the business grows. - **Self-Service Accessibility**: How easily teams can access the data they need without bottlenecks. - **System Integration**: How well data flows between tools, systems, and teams. ## Experimentation & Optimization How rigorously the organization tests, measures, and acts to improve outcomes. - **Experiment Framework & Rigor**: How structured and rigorous experimentation practices are. - **Conversion & Funnel Analysis**: How well the organization measures and optimizes user journeys. - **Insight-to-Action Speed**: How quickly insights lead to changes in product or process. ## Data Literacy & Culture How confidently and consistently people across the organization use data in their work. - **Data Literacy Across Teams**: How confident teams are in reading, interpreting, and using data. - **Cultural Adoption of Analytics**: How deeply data-driven decision-making is embedded in the culture. - **Continuous Improvement Mindset**: How actively teams seek to improve using data and insights. --- # Development Practices Radar URL: https://www.teamretro.com/health-check-templates/development-practices-radar/ Strong engineering teams are built on consistent, well-understood development practices. The Development Practices Radar gives software teams a structured way to reflect on how they plan, build, test, and ship their work. By rating dimensions such as scope clarity, coding standards, technical debt, testing, and deployment, teams surface where their craft is solid and where friction is slowing them down. Use the results to spark honest conversations, agree on improvements, and track how your development practices mature over time. ## Development Practices Core engineering practices that influence how effectively the team plans, builds, tests, and delivers quality software. - **Clarity of Scope**: Our scope of work is clear and well-defined. - **Shared Coding Standards**: We have an agreed set of coding standards that are defined and adhered to. - **Ability to Focus**: We have the time and opportunity to focus on the work we have planned. - **Managing Technical Debt**: We monitor and manage our technical debt. - **Testing Practices**: We have functional test automation for time consuming, high stake features. - **Deployment Process**: We have automated deployment that is reliable and quality assured. --- # DevOps & Continuous Delivery URL: https://www.teamretro.com/health-check-templates/devops-continuous-delivery/ Strong DevOps practices and continuous delivery capabilities are what separate teams that ship safely and rapidly from those bogged down by manual toil and fragile releases. Spanning the full delivery lifecycle — from CI/CD pipelines and automated deployments to reliability, security, and platform engineering — this assessment helps teams see where they sit on the maturity curve, from ad hoc effort to fully optimized, automated flow. By rating each capability against clear maturity levels, teams uncover bottlenecks, align on priorities, and chart a practical path toward faster, safer, and more sustainable software delivery. ## CI/CD Pipeline How effectively the team builds, integrates, and gains feedback through automated pipelines. - **Build Automation**: How reliably and automatically software builds are generated and validated. - **Integration Frequency**: How often developers integrate changes into the shared codebase. - **Pipeline Feedback**: Speed and clarity of information returned to developers from the pipeline. ## Release & Deployment How safely, predictably, and frequently the team ships changes to users. - **Deployment Automation**: Level of automation and repeatability of deployments. - **Deployment Risk Reduction**: How effectively the team minimizes risk during release. - **Delivery Frequency**: How often value is shipped to users. ## Reliability & Operations How well the team observes, responds to, and sustains the health of running systems. - **Monitoring & Observability**: How well the team understands system health and behavior. - **Incident Response**: How efficiently the team responds to and resolves incidents. - **On-Call Sustainability**: Fairness and effectiveness of on-call processes. ## Security & Compliance Automation How deeply security and compliance are automated and embedded across the delivery pipeline. - **Security Integration**: How effectively security practices are embedded into development workflows. - **Vulnerability Management**: How quickly and effectively vulnerabilities are discovered and addressed. - **Compliance as Code**: Use of automation to enforce regulatory, security, and policy requirements. ## Platform & Infrastructure How automated, consistent, and resilient the underlying platform and infrastructure are. - **Infrastructure Automation**: How infrastructure is provisioned, managed, and scaled. - **Environment Consistency**: How consistent development, staging, and production environments are. - **Platform Reliability**: System uptime, resilience, and fault tolerance. --- # Engineering Excellence Maturity Model URL: https://www.teamretro.com/health-check-templates/engineering-excellence/ Strong engineering practices are the foundation of sustainable software delivery, yet teams often lack a clear view of where they truly stand. Engineering Excellence gives your team a structured way to assess the technical health that underpins quality, speed, and resilience. By examining code quality, architecture, technical debt, and collaboration through a maturity lens, teams can pinpoint exactly where practices are ad hoc and where they have become optimized. Each dimension moves along a five-level scale, helping engineers and leaders build a shared language for what good looks like. The result is a candid, data-informed conversation that turns vague feelings about quality into concrete, prioritized improvements. Use it regularly to track progress, celebrate gains, and keep engineering excellence a living part of your team culture. ## Code Quality & Standards How consistently the team writes clean, maintainable, well-reviewed code guided by shared standards. - **Coding Standards Consistency**: How consistently the team applies shared coding guidelines. - **Code Maintainability**: The ease with which code can be read, understood, modified, and extended. - **Code Review Quality**: How effectively code reviews improve quality and team learning. ## Architecture & Scalability How clearly the system is architected and how well it scales, performs, and manages technical risk. - **Architectural Clarity**: How well the system's architecture is defined, documented, and understood. - **Scalability & Robustness**: Ability of the system to handle growth, performance demands, and reliability needs. - **Technical Risk Management**: How effectively engineering risks are identified, assessed, and mitigated. ## Technical Debt Management How visibly technical debt is tracked, reduced, and connected to its impact on delivery. - **Debt Visibility**: How technical debt is identified, tracked, and communicated. - **Debt Reduction Practices**: How effectively the team addresses and reduces technical debt. - **Impact Awareness**: Understanding of how technical debt affects velocity, quality, and risk. ## Engineering Collaboration & Enablement How effectively the team shares knowledge, spreads skills, and equips developers with the tools to do great work. - **Knowledge Sharing**: How effectively engineering knowledge and expertise are shared across the team. - **Skill Breadth & Flexibility**: The team's ability to work across multiple areas of the system. - **Developer Enablement**: Quality of tools, processes, and environment supporting developer productivity. --- # Feedback and Innovation Culture URL: https://www.teamretro.com/health-check-templates/feedback-and-innovation-culture/ Innovation thrives when teams can share ideas freely, give and receive constructive feedback, and validate assumptions before committing to a solution. This set of questions explores how comfortable team members feel offering early input, how actionable that feedback is, and whether people are trusted to own ideas and learn openly from mistakes. By measuring the everyday behaviours behind a healthy feedback loop, teams can pinpoint where their innovation culture is flourishing and where psychological safety, ownership, or evidence-based decision making could be strengthened. Use the results to spark honest conversations about how ideas move from spark to reality and how the team rewards initiative. ## Feedback and Innovation How the team gives and receives feedback, validates ideas, and takes ownership to drive innovation. - **Early Feedback**: When an idea arises, I can give early feedback that is positive and constructive, even if not all feedback is accepted. - **Motivation to Give Feedback**: I can easily give feedback that is appreciated and well-received. - **Benefit from Feedback**: My feedback on ideas is actionable and helps improve the idea. - **Validate Ideas Early**: I focus on removing uncertainty and proving assumptions before I implement ideas. - **Openness to Evidence**: I have the opportunity to test and gather data for ideas and to provide evidence within certain constraints. - **Objectivity**: My decisions are weighted more toward objective results rather than individual opinions. - **Individual Agency**: I am free to own and implement ideas and solutions independently, without undue barriers. - **Taking Responsibility**: I am happy to take full responsibility for the implementation of our projects. - **Appreciation for Taking Responsibility**: I experience open appreciation for taking responsibility and initiative. - **Learning from Mistakes**: I can share my learnings, including failures without fear or judgment to help others avoid making the same mistake. --- # Financial Managment Maturity Model URL: https://www.teamretro.com/health-check-templates/finance-maturity-model/ Strong financial management is the backbone of a resilient, growth-ready organization — yet many teams struggle to know where their budgeting, forecasting, controls, and cash flow practices truly stand. Use this finance maturity assessment to take an honest, structured look across planning, compliance, and financial health, and to map a clear path from reactive, ad hoc habits toward optimized, strategy-aligned financial operations. By rating each dimension on a shared maturity scale, finance leaders and cross-functional teams build a common language for where they are today and what good looks like next. The results highlight where processes are reliable and where risk, inefficiency, or missed opportunity may be hiding. Run it periodically to track progress, prioritize improvements, and align spending and forecasting with strategic goals. ## Financial Planning & Forecasting Evaluate how well budgets, forecasts, and financial decisions are connected to strategic priorities and reliable enough to guide the business. - **Budgeting Process**: How clearly budgets are created and followed. - **Forecast Accuracy**: How well financial forecasts predict actual performance. - **Strategic Financial Alignment**: How well finances support strategic goals. ## Financial Control & Compliance Gauge the strength of expense management, internal controls, and audit readiness that keep the organization compliant and protected from risk. - **Expense Management**: Effectiveness of tracking and controlling expenses. - **Compliance & Audit Readiness**: How well financial processes meet compliance standards. - **Internal Controls**: Strength of internal financial controls. ## Cash Flow & Financial Health Assess how confidently the organization manages cash, revenue, and costs to stay resilient and fund sustainable growth. - **Cash Flow Management**: Effectiveness of managing cash inflows and outflows. - **Revenue Management**: How effectively revenue is tracked, recognized, and optimized. - **Cost Optimization**: How effectively costs are optimized without sacrificing value. --- # The Five Ideals of DevOps URL: https://www.teamretro.com/health-check-templates/five-ideals-of-devops/ Inspired by Gene Kim's bestselling novel The Unicorn Project, the Five Ideals offer a powerful lens for examining how your team builds, ships, and improves software. Use this check to surface where developers feel blocked by complexity, where daily work could be made easier, and whether psychological safety and customer focus are guiding your DevOps practices. Honest conversation across these five ideals helps teams remove friction, restore flow, and reconnect technical work to the value it delivers. ## The Five Ideals The five guiding principles from The Unicorn Project that shape high-performing DevOps cultures. - **Local and Simple**: We can make local code changes in a simple way without impacting others. - **Focus and Flow**: Our work environment is engaging and even joyful. We have small batching, single piece flow with continual feedback. - **Improvement of Daily Work**: We have limited technical debt and our architecture lets us work efficiently, deliver value faster, and benefit the business. - **Psychological Safety**: Our team members feel safe to talk about problems openly and to address issues without fear. - **Customer Focus**: We value the context (systems that deliver the core product) to the customer as essential and resource them appropriately, but also understand the core (what customers are willing and able to pay for). --- # Great Teams Health Check URL: https://www.teamretro.com/health-check-templates/great-teams-health-check/ Built on the research behind what makes teams truly effective, this check helps groups reflect on the conditions that drive high performance. It surfaces how safe, dependable, clear, meaningful, and impactful work feels for every member, giving teams a shared language to talk about what's working and where to grow. Use it regularly to track team health, spark honest conversation, and turn insights into concrete improvements that lift collaboration and results. ## Team Effectiveness The core conditions that enable a team to do meaningful, dependable, and high-impact work together. - **Psychological Safety**: I feel safe voicing my opinion freely and honestly. I can ask questions without judgment. - **Dependability**: I produce high-quality work in a timely manner. - **Role Clarity**: I have specific and clear performance standards and understand my role, objectives, and key results. - **Meaning**: I find that my work has meaning and a purpose. - **Value**: My efforts, along with the team, help advance our goals, missions, and vision. --- # Individual AI Self-Assessment URL: https://www.teamretro.com/health-check-templates/individual-ai-self-assessment/ Effective AI adoption starts with the individual. This self-assessment helps team members honestly evaluate where they stand across nine dimensions of personal AI maturity — from strategic alignment and tool adoption through to governance, output quality, and continuous improvement. Each dimension follows a five-stage progression from Ad Hoc to Optimized, giving individuals a clear picture of their current practice and a concrete path forward. Use this assessment to spark meaningful conversations about AI skills, identify personal development priorities, and build a shared language for what good AI use looks like at the individual level. Whether you're just starting out or already embedding AI deeply into your daily work, this health check surfaces the gaps and strengths that matter most. ## AI Strategy & Leadership How well your AI use is aligned to organisational goals, prioritised thoughtfully, and owned with accountability. - **Strategic Alignment**: I use AI in ways that clearly support my team, department, or organisational goals. - **Use Case Prioritisation**: I choose where to apply AI based on value, feasibility, and risk — not on novelty. - **Leadership Awareness**: My manager and leadership know how I use AI and have given clear expectations about it. - **Personal Ownership**: I take responsibility for what AI does on my behalf — the outputs, the decisions, and the consequences. ## Tool Adoption & Access Whether you have the right AI tools, use them consistently, and stay current on new capabilities relevant to your work. - **Tool Availability**: I have access to the AI tools I need to do my work well. - **Tool Fit**: The AI tools I use fit the tasks I actually do. - **Personal Adoption Consistency**: I use AI consistently in the places it adds value, rather than reaching for it only occasionally. - **Awareness of New Capabilities**: I keep myself current on what AI can newly do that is relevant to my work. ## AI Skills & Confidence Your ability to understand AI, craft effective prompts, think critically about outputs, and grow your skills over time. - **AI Literacy**: I understand what AI can and cannot do, and where its limits sit. - **Prompting Skill**: I give AI clear instructions, context, and constraints to get useful output. - **Critical Thinking**: I question, check, and refine AI-generated outputs rather than taking them at face value. - **Personal Learning & Development**: I invest deliberately in growing my AI skills. ## Workflow Integration How deeply AI is embedded in your daily work, standard processes, and the balance between AI and human judgment. - **Daily Use**: AI is naturally part of my everyday work. - **Process Integration**: AI is built into my standard ways of working, not bolted on at the edges. - **Human–AI Balance**: I know when to rely on AI and when my own judgment, expertise, or review is essential. - **Work Redesign**: I rethink how I work to take advantage of what AI changes — not just add AI to old habits. ## Data, Knowledge & Context The quality of information you bring to AI, your access to internal knowledge, and how responsibly you handle data. - **Data Quality**: The information I use with AI tools is reliable, accurate, and up to date. - **Knowledge Access**: I can easily get to the internal knowledge I need for AI-assisted work. - **Context Provision**: I give AI the right background, examples, and constraints so its output fits my situation. - **Personal Data Stewardship**: I manage the data and knowledge I work with responsibly — accuracy, ownership, and appropriate use. ## Governance, Risk & Compliance Your awareness of AI policy, privacy obligations, bias risks, and your ability to account for how AI was used. - **Policy Awareness**: I know my organisation's AI policies, boundaries, and approval requirements. - **Privacy & Confidentiality**: I keep sensitive, personal, or restricted information out of AI tools that shouldn't see it. - **Bias & Fairness**: I think about bias, fairness, and potential harm in AI-assisted output before using it. - **Auditability**: I keep enough of a trail to explain when, how, and why I used AI for work that matters. ## Output Quality & Human Review How rigorously you verify AI-generated content, maintain your quality standards, and learn from AI errors. - **Accuracy Checking**: I verify AI-generated information before relying on it. - **Personal Quality Standards**: My AI-assisted output meets my standards for clarity, accuracy, and professionalism. - **Human Oversight**: I have a clear sense of when human review or approval is required for AI-assisted work. - **Error Learning**: I learn from AI mistakes, hallucinations, and poor outputs rather than just moving on. ## Collaboration & Knowledge Sharing How actively you share AI knowledge, experiment with new approaches, learn from others, and build reusable assets. - **Sharing What Works**: I share useful prompts, examples, workflows, and lessons with my team rather than hoarding them. - **Personal Experimentation**: I feel safe trying new things with AI and learning from what doesn't work. - **Learning From Others**: I learn from how other people, teams, and external examples use AI well. - **Reusable Personal Assets**: I build reusable AI templates, prompt libraries, checklists, or playbooks for the work I do often. ## Impact Measurement & Improvement Whether you track the real impact of your AI use on productivity and quality, and continuously improve your practice. - **Personal Productivity Impact**: I notice whether AI is actually saving me time or increasing my capacity. - **Quality Impact**: I notice whether AI improves the quality, consistency, or usefulness of my work. - **Outcome Connection**: I can connect my AI use to outcomes that matter — customer value, time saved, mistakes avoided, work shipped. - **Continuous Improvement of My AI Practice**: I use feedback, results, and lessons to keep improving how I use AI. --- # Leadership Maturity Model URL: https://www.teamretro.com/health-check-templates/leadership-maturity-model/ Strong leadership shapes how teams set direction, communicate, develop people, and adapt to change. This maturity model helps organizations assess leadership effectiveness across the capabilities that drive alignment, engagement, and sustainable performance — from how clearly a vision is shared to how well leaders coach, collaborate, and lead through change. By rating each dimension against a staged scale from Ad Hoc to Optimized, leaders and teams gain a shared, honest picture of current strengths and the gaps holding them back. The results spark focused conversations about where to invest in leadership growth, helping you build a more capable, resilient, and inspiring leadership culture over time. ## Vision & Strategic Alignment How clearly leaders set direction, align teams to strategy, and make effective decisions. - **Clarity of Vision**: How clearly leadership communicates direction and purpose. - **Strategic Alignment**: How well teams and leaders align to strategic goals. - **Decision-Making Effectiveness**: How effectively leaders make timely, informed decisions. ## Communication & Influence How effectively leaders communicate, collaborate with stakeholders, and inspire others. - **Communication Quality**: How effectively leaders communicate with their teams. - **Stakeholder Collaboration**: How well leaders collaborate with other departments and stakeholders. - **Influence & Motivation**: How well leaders inspire and influence others positively. ## Team Development & Support How well leaders coach, develop talent, and recognize and support their people. - **Coaching & Mentoring**: How well leaders support employee growth. - **Talent Development**: How effectively leaders develop future leaders and capabilities. - **Recognition & Support**: How effectively leaders provide recognition and support. ## Adaptability & Innovation How effectively leaders guide change, encourage innovation, and drive continuous improvement. - **Change Leadership**: How effectively leaders guide teams through change. - **Innovation Support**: How well leaders encourage new ideas and experimentation. - **Continuous Improvement Leadership**: How committed leaders are to improving processes and outcomes. --- # Marketing Maturity URL: https://www.teamretro.com/health-check-templates/marketing-maturity/ Evaluate how your marketing function performs across strategy, content, campaigns, and analytics. Spanning five maturity levels from Ad Hoc to Optimized, this assessment helps marketing teams pinpoint where they excel and where focused investment will lift performance. Use the structured ratings to surface honest team perspectives, align on priorities, and chart a clear path toward a data-driven, high-performing marketing engine. ## Strategy & Positioning Examine how clearly marketing strategy, value proposition, and market understanding guide decisions and differentiate the business. - **Marketing Strategy Clarity**: How clearly marketing goals and strategy are defined and understood. - **Value Proposition Strength**: How clearly the product's value is articulated. - **Market Understanding**: Depth of understanding of market size, trends, and competitive landscape. ## Content & Messaging Assess how well content and messaging align to the customer journey and reinforce a consistent, high-quality brand voice. - **Content Strategy Alignment**: How well content supports the customer journey. - **Messaging Consistency**: How consistent messaging is across channels. - **Content Quality & Production**: Quality and cadence of content creation. ## Campaign Execution Review how campaigns are planned and run, how channels perform, and how effectively leads are qualified and nurtured. - **Campaign Planning & Execution**: How well campaigns are scoped, planned, and executed. - **Channel Effectiveness**: Effectiveness of chosen channels in reaching target audiences. - **Lead Quality & Nurturing**: How effectively leads are qualified and nurtured. ## Analytics & Performance Gauge how marketing performance is measured, attributed to ROI, and improved through structured experimentation. - **Marketing Metrics & Reporting**: How consistently marketing performance is measured and reported. - **Attribution & ROI Clarity**: Understanding of which activities drive results. - **Experimentation & Optimization**: How effectively experiments improve marketing performance. --- # Organisational AI Adoption Maturity URL: https://www.teamretro.com/health-check-templates/organisational-ai-adoption-maturity/ Adopting AI well across an organisation is rarely about the technology alone — it depends on strategy, leadership, capability, data, governance, and a clear line of sight to value. The Organisational AI Adoption Maturity model gives leadership teams a structured way to assess how mature their AI adoption really is, function by function and capability by capability. Spanning seven areas — from AI strategy and executive sponsorship through to adoption breadth, people and capability, data foundations, governance, and value realisation — it surfaces where AI is genuinely embedded, where it is improvised, and where attention is overdue. Each dimension is rated against a five-stage maturity scale, from Ad Hoc through to Optimized, so teams can have an honest, shared conversation about their current state and agree where to invest next. Use it to baseline AI maturity, align leaders on ambition versus risk, and track progress as adoption deepens over time. ## AI Strategy & Vision Whether the organisation has a clear, shared direction for AI — why it matters, how far to push it, and which use cases to back. - **Strategic Direction on AI**: The organisation has a clear, articulated view of why AI matters, where it fits, and what it is meant to change. - **Ambition vs Risk Posture**: The organisation has settled how far it is willing to push AI adoption and how much risk it accepts in doing so. - **Use-Case Portfolio**: The organisation knows which AI use cases it is investing in across functions and why those cases were chosen. ## Leadership & Sponsorship Whether senior leaders own AI, fund it credibly, use it themselves, and coordinate it across the business. - **Executive Ownership**: A senior leader is accountable for AI as a whole, with the authority to make decisions across functions. - **Investment Commitment**: The organisation invests in AI at a level matched to its stated ambition, and the investment is funded predictably. - **Visible Leadership Use**: Leaders use AI themselves and talk about it openly; AI adoption isn't something they ask of others without doing. - **Cross-Function Coordination**: AI work is coordinated across functions rather than each team buying tools, writing policy, and running pilots on its own. ## Adoption Across Functions How broadly and deeply AI is actually used across the business — and whether adoption is balanced across customer-facing and internal work. - **Breadth of Function Coverage**: AI is in active use across the major functions of the business (people, finance, operations, sales, marketing, support, product) — not just one or two. - **Depth Within Functions**: Where AI is used, it is used substantively — embedded in workflows, not bolted on at the edges. - **Front-Office vs Back-Office Balance**: AI adoption is balanced between customer-facing work and internal operations, rather than concentrated in one side of the business. ## People & Capability Whether the organisation has the AI literacy, specialist skills, shared learning, and talent pathways to do AI well and keep getting better. - **Baseline AI Literacy**: Employees across the organisation have the baseline AI literacy expected of their role — they can use AI tools sensibly and know their limits. - **Specialist Capability**: The organisation has the specialist AI capability it needs (data, ML/ops, prompt design, governance) to do AI well in the areas that warrant it. - **Internal Community & Knowledge Sharing**: People learning about AI find each other, share what works, and lift the organisation's collective skill faster than individuals could alone. - **Hiring & Career Pathways**: The organisation hires for AI capability where it matters and offers career pathways that retain the people it develops. ## Data & Foundations Whether the data, platforms, and vendor estate AI depends on are ready, shared, and managed at the organisation level. - **Data Readiness**: The data AI needs to do useful work — accurate, accessible, well-governed — is in a state to support the AI use cases the organisation has chosen. - **Technology Foundations**: The platforms, integrations, and tooling AI relies on are in place — not improvised under each new initiative. - **Vendor & Tool Management**: AI vendors and tools are chosen, integrated, and rationalised at the organisation level — not bought one team at a time. ## Governance, Risk & Compliance Whether AI is governed responsibly — clear policy, managed risk, regulatory compliance, and ethics applied in real decisions. - **AI Policy & Acceptable Use**: The organisation has a clear, current, and known policy on what AI tools people can use, on what data, and for what purposes. - **Risk Management**: AI-specific risks (hallucination, bias, data leakage, model drift, vendor dependency) are recognised, assessed, and managed alongside other organisational risks. - **Regulatory & Compliance Posture**: The organisation tracks the regulations that apply to its AI use, complies with them, and adapts as the rules change. - **Ethics & Responsible Use**: The organisation has a working position on AI ethics — fairness, transparency, human oversight, impact on people — and applies it in actual decisions. ## Value Realisation Whether the organisation measures what AI actually delivers, understands its cost and ROI, learns from failure, and keeps improving its AI practice. - **Outcome Measurement**: The organisation measures what AI is actually delivering — productivity, quality, revenue, cost, customer experience — not just adoption metrics. - **Cost & ROI Visibility**: The organisation knows what it is spending on AI in total and what it is getting back, well enough to make sensible scale-up and scale-down decisions. - **Failure Capture & Learning**: When AI initiatives underperform or fail, the organisation captures what happened and uses it to improve later work. - **Continuous Improvement of AI Practice**: The way the organisation does AI work — strategy, governance, capability, delivery — is itself reviewed and improved as the field changes. --- # People Operations Maturity Model URL: https://www.teamretro.com/health-check-templates/people-operations-maturity-model/ Strong people operations are the backbone of a thriving organization, shaping how talent is hired, developed, retained, and engaged. This maturity model helps HR leaders and people teams assess where they stand across the full employee lifecycle — from hiring and onboarding through performance, culture, retention, and workforce planning. By rating each dimension from Ad Hoc to Optimized, teams gain a shared, honest picture of their strengths and the gaps that hold them back. Use the results to prioritize improvements, align leadership, and build a deliberate roadmap toward a more capable, people-centered organization. ## Hiring & Onboarding How effectively the organization attracts, selects, and integrates new talent into the team. - **Hiring Process Effectiveness**: How consistently and effectively the organization attracts and selects qualified candidates. - **Candidate Experience**: How positive and clear the hiring experience is for candidates. - **Onboarding Quality**: How well new hires are integrated into their roles and the organization. ## Performance & Growth How clearly performance is managed and how well employees are supported to grow and develop. - **Performance Management Process**: The clarity, fairness, and effectiveness of performance evaluation. - **Feedback & Coaching**: How regularly and constructively feedback is exchanged. - **Career Development**: How well employees understand and pursue growth opportunities. ## Culture & Engagement How connected, safe, and collaborative people feel within the organization. - **Employee Engagement**: How connected, motivated, and committed employees feel. - **Psychological Safety**: How safe employees feel to speak up, take risks, and raise concerns. - **Collaboration & Team Dynamics**: How well teams work together to achieve shared goals. ## People Operations Excellence How well HR policies, systems, and retention practices support a reliable, fair employee experience. - **Policy Clarity & Consistency**: How well HR policies are documented, communicated, and applied. - **HR Systems & Tools**: How effectively HR technologies support people operations. - **Retention & Workforce Stability**: How well the organization retains strong talent. ## Workforce Planning & Capability How well the organization plans staffing, builds skills, and prepares for future role transitions. - **Strategic Workforce Planning**: How well staffing plans align with long-term organizational needs. - **Capability Development**: How effectively the organization builds required skills and competencies. - **Succession & Role Coverage**: How well the organization prepares for role transitions and continuity. --- # Product Discovery URL: https://www.teamretro.com/health-check-templates/product-discovery/ Strong product discovery separates teams that build the right things from those that simply build things. Use this maturity assessment to evaluate how well your team understands customers, validates ideas, runs research, and learns across the product lifecycle. Spanning four dimension groups — Customer Understanding, Experimentation & Validation, Research Practices, and Lifecycle Learning — it surfaces where discovery habits are ad hoc versus optimized, sparking honest conversations about how your team can reduce risk, cut waste, and ship features that deliver real outcomes. ## Customer Understanding How deeply the team knows its customers — their needs, segments, and the context in which they experience the problem. - **Depth of Customer Insight**: How well the team understands user needs, behaviors, motivations, and pain points. --- # Product Management URL: https://www.teamretro.com/health-check-templates/product-management/ Strong product management is the difference between shipping features and delivering outcomes that customers and the business genuinely value. This maturity model helps product teams take an honest look at how they set direction, prioritize work, collaborate across functions, and learn from data and customers. By rating each capability from Ad Hoc to Optimized, teams uncover where their product practice is thriving and where it needs investment. Spanning vision and strategy, roadmapping and prioritization, execution and collaboration, data and customer insight, and market and stakeholder alignment, the assessment surfaces a shared view of product maturity. The result is a focused conversation that turns scattered opinions into a clear, prioritized improvement plan the whole team can rally behind. ## Vision & Strategy How clearly the product direction is defined, aligned to business goals, and measured for success. - **Product Vision Clarity**: How clearly the long-term product direction is articulated and understood. - **Strategic Alignment**: How effectively product goals map to business objectives. - **Success Metrics**: How well outcomes are defined, measured, and used to guide decisions. ## Roadmapping & Prioritization How effectively the team communicates direction, sequences work by value, and keeps stakeholders aligned. - **Roadmap Clarity**: How clearly the roadmap communicates direction and expectations. - **Prioritization Discipline**: How effectively the team selects work based on value and trade-offs. - **Stakeholder Alignment**: Quality of alignment between product, engineering, and business stakeholders. ## Execution & Collaboration How well the team turns clear requirements into incremental value through strong cross-functional teamwork. - **Requirement Clarity**: How well the team understands the problems to solve and the intended outcomes. - **Cross-Functional Collaboration**: How effectively PMs, engineering, and design collaborate. - **Incremental Delivery**: Ability to break work into small, testable, valuable increments. ## Data & Customer Insight How deeply the team grounds decisions in evidence, customer understanding, and ongoing feedback. - **Evidence-Based Decision Making**: Use of analytics, measurements, and insights in product planning. - **Customer Understanding**: Depth of understanding of customer needs, context, and behaviors. - **Feedback Integration**: How effectively customer and stakeholder feedback informs product direction. ## Market & Stakeholder Alignment How well the team reads the market, validates product–market fit, and communicates with stakeholders. - **Competitive Awareness**: Understanding of market trends, competitor activity, and opportunities. - **Stakeholder Communication**: Clarity, transparency, and effectiveness of communication with stakeholders. - **Market Fit Validation**: How effectively product decisions are validated with real market needs. --- # Product Strategy & Customer Value URL: https://www.teamretro.com/health-check-templates/product-strategy-customer-value/ Building products customers love takes more than a strong roadmap — it requires clear vision, deep customer understanding, disciplined discovery, engineering excellence, and the data to prove value is being delivered. This maturity model helps product, engineering, and customer success teams assess how well they connect strategy to outcomes across the full product lifecycle. By rating each dimension on a journey from Ad Hoc to Optimized, teams uncover where direction is fuzzy, where validation is missing, and where operational and technical foundations need strengthening. The result is a shared, honest picture of product maturity that guides focused improvement and aligns everyone around delivering measurable customer value. ## Product Strategy & Customer Value How clearly product direction is set, how deeply customers are understood, and how reliably work is prioritized around value and outcomes. - **Product Vision & Direction**: Product direction is clear, strategic, and aligned with customer needs. - **Customer Understanding**: Teams deeply understand user needs, behaviors, and motivations. - **Value Prioritization**: Work is prioritized based on customer and business value. - **Outcome Measurement**: Success defined by outcomes rather than output volume. - **Market & Stakeholder Alignment**: Product decisions consider competition, trends, and stakeholder needs. ## Discovery, Innovation & Experimentation How well teams test assumptions, validate ideas early, share learning, and create the conditions for innovation to thrive. - **Hypothesis & Experimentation Discipline**: Teams test assumptions through structured experiments before committing to solutions. - **Prototype & Concept Validation**: Teams validate ideas early through prototypes and user tests. - **Insight Sharing & Knowledge Management**: Research insights are captured, shared, and used across teams. - **Learning Culture**: Teams and leaders embrace learning, reflection, and adaptation. - **Innovation Enablement**: The organization encourages experimentation, creativity, and new ideas. ## Engineering Excellence, Platform & DevOps How strong the technical foundations are across code quality, automation, delivery pipelines, architecture, and technical debt. - **Code Quality & Maintainability**: Engineering teams write clean, maintainable code aligned to standards. - **Automation & Test Coverage**: Automated tests ensure quality, reduce regression, and support rapid delivery. - **Continuous Integration & Deployment**: Teams integrate and deploy frequently with minimal risk. - **Architecture & Scalability**: Systems are robust, scalable, and designed for long-term sustainability. - **Technical Debt Management**: Technical debt is visible, prioritized, and intentionally reduced. ## Customer Success & Market Performance How effectively the organization listens to customers, drives engagement and retention, supports users, and positions itself in the market. - **Customer Feedback & Voice of Customer**: Feedback is gathered regularly and informs product and service decisions. - **Customer Engagement & Retention**: Customers actively use and gain value from the product or service. - **Support Efficiency & Quality**: Customer issues are resolved quickly and effectively. - **Customer Health Insights**: The organization monitors and understands customer risk and adoption. - **Market Positioning & Fit**: The organization understands its competitive landscape and product-market fit. ## Data, Measurement & Enterprise Operations How well data is governed and trusted, how insights and experiments inform decisions, and how efficiently operations run at scale. - **Data Quality & Governance**: Data is accurate, accessible, and trusted across the organization. - **Reporting & Insights**: Performance is measured with meaningful, timely dashboards and reports. - **Experimentation & Data-Driven Decisions**: Data and experiments inform decisions across teams. - **Operational Efficiency**: Processes are standardized, efficient, and continuously improved. - **Automation & Tooling**: Automation supports quality, scalability, and operational excellence. --- # Psychological Safety Check URL: https://www.teamretro.com/health-check-templates/psychological-safety-check/ Psychological safety is the foundation of high-performing teams, where people feel free to speak up, take risks, and learn from mistakes without fear of blame or ridicule. This check measures how safe team members feel to be themselves, voice concerns, and contribute their best work. By surfacing where trust is strong and where it needs attention, teams can build the conditions for honest dialogue, innovation, and continuous growth. Use the results to spark open conversations and strengthen the everyday behaviours that make people feel respected, valued, and heard. ## Psychological Safety How safe team members feel to take interpersonal risks, share ideas, and be their authentic selves. - **Learning and Growth**: Mistakes are treated as opportunities to learn rather than reasons for blame. - **Tough Issues**: Team members can openly raise problems and difficult topics without hesitation. - **Feeling Heard**: Every voice is respected, and no one is dismissed or rejected for being different. - **Risk Taking**: It feels safe to try new approaches and take risks without fear of negative consequences. - **Asking for Help**: Team members can comfortably reach out to one another for support when needed. - **Team Support**: Colleagues act with good intent and do not undermine each other's efforts. - **Skills and Talents**: Each person's unique strengths are recognised, valued, and put to good use. --- # Quick Pulse Check URL: https://www.teamretro.com/health-check-templates/quick-pulse-check/ Get a fast, honest read on how your team is feeling across the moments that matter most — from the pace and quality of work to autonomy, collaboration, learning, and the value being delivered. Designed as a lightweight pulse check, it surfaces sentiment in minutes so you can spot trends, open up meaningful conversations, and act before small frustrations become big blockers. Run it regularly to keep a finger on your team's mood and momentum. ## Team Pulse Capture how the team feels across the core drivers of a healthy, productive working environment. - **Speed and Quality**: How do you feel about the speed and quality of our work? - **Autonomy**: How do you feel about the freedom you have to do your job well? - **Team Work**: How do you feel about how well the team is working together? - **Learning**: How do you feel about the sharing and growth opportunities in the team? - **Value**: How do you feel about the value that the team creates? --- # Remote Team Happiness URL: https://www.teamretro.com/health-check-templates/remote-team-happiness/ Remote work brings flexibility and freedom, but it can also blur role boundaries, weaken connection, and quietly erode well-being. Remote Team Happiness gives distributed teams a structured way to surface how members really feel about their roles, autonomy, impact, and sense of belonging. By measuring the human factors that drive engagement and trust, teams can spot early signs of isolation or burnout and take action before they affect morale and performance. Run this check regularly to keep a finger on the pulse of remote team happiness, build psychological safety, and create a healthier, more connected way of working. ## Remote Team Happiness Explore the factors that shape how happy, engaged, and supported people feel while working remotely, from role clarity and autonomy to connection and personal well-being. - **Role Clarity**: Reflects how clearly each person understands their role and what is expected of them. - **Autonomy**: Captures whether people have the freedom and flexibility to do their job without unnecessary blockers. - **Impact**: Measures how meaningful and valuable people feel their work is toward shared goals. - **Engagement**: Indicates whether people can deliver outcomes effectively with the right time and resources. - **Support**: Reflects how well people feel supported by colleagues, processes, tools, and resources. - **Connectedness**: Captures how connected people feel to their team and the wider organization. - **Psychological Safety**: Measures the level of trust and safety people feel in their everyday team interactions. - **Personal Well-being**: Reflects whether people have routines that support positive mental and physical health. --- # SaaS Growth & Lifecycle URL: https://www.teamretro.com/health-check-templates/saas-growth-lifecycle/ Evaluate your SaaS team's maturity across the full customer lifecycle — from acquisition and activation through retention, monetization, and growth strategy. This health check surfaces strengths and gaps across five critical domains, helping product, growth, and customer success teams align on priorities and drive sustainable SaaS growth. Each dimension is rated on a five-level maturity scale — from Ad Hoc to Optimized — giving teams a clear picture of where they stand today and a shared language for improvement. Use it to benchmark progress, focus quarterly planning, and build a roadmap toward scalable, data-driven growth. ## Acquisition & Activation Assess how well the team attracts the right customers and successfully guides them to initial product value. - **Ideal Customer Profile Clarity**: How well the team understands who the product is designed for and why. - **Onboarding Effectiveness**: How well onboarding helps users reach initial value. - **Activation Metrics & Tracking**: How activation is measured and used to drive improvements. ## Engagement & Retention Evaluate how effectively the team monitors user engagement, reduces churn, and maintains long-term customer health. - **Customer Engagement Insight**: Visibility into how users interact with the product over time. - **Retention Practices**: Processes and mechanisms supporting long-term user retention. - **Customer Health Visibility**: How well the team understands account health and risk signals. ## Monetization & Billing Assess the maturity of pricing strategy, billing operations, and the team's ability to identify and capture expansion revenue. - **Pricing Clarity & Fit**: How well pricing aligns with customer value and market expectations. - **Billing Reliability**: Consistency and effectiveness of subscription and billing operations. - **Expansion Opportunity Identification**: How effectively upsell and cross-sell opportunities are identified and acted upon. ## Analytics & Lifecycle Optimization Evaluate the team's ability to instrument funnels, run experiments, and personalize the customer lifecycle using data. - **Funnel Visibility**: How well acquisition, activation, retention, and revenue funnels are understood. - **Experimentation Capability**: The team's ability to run meaningful A/B tests, trials, and lifecycle experiments. - **Lifecycle Personalization**: How well the experience adapts to user stage, segment, and behavior. ## Growth Strategy & Market Fit Assess the clarity of market positioning, the repeatability of the growth strategy, and how rigorously product-market fit is validated. - **Market Positioning**: How clearly the product is positioned relative to competitors and market needs. - **Growth Framework & Strategy**: The clarity and execution of a repeatable growth strategy. - **Market Fit Validation**: How effectively product-market fit is measured and strengthened over time. --- # Sales & Marketing AI Maturity Model URL: https://www.teamretro.com/health-check-templates/sales-marketing-ai-maturity/ AI is reshaping how revenue teams prospect, create content, score leads, and reach buyers — but the gap between experimenting with tools and running a disciplined, trustworthy AI operation is wide. This maturity model helps sales and marketing teams take an honest look at where AI genuinely earns its place across their workflows. Spanning seven dimension groups — from adoption and daily tool practice through brand voice, personalisation, accuracy, compliance, and measurement — it surfaces where AI is adding value, where it is creating risk, and where volume has quietly outrun quality. Each dimension is scored on a five-stage scale from Ad Hoc to Optimized, giving teams a shared language for the conversation and a clear picture of what "better" looks like. Use the results to focus effort on the workflows where AI matters most, to protect brand integrity and customer trust, and to make confident, evidence-led decisions about where to scale AI and where to hold back. ## AI Adoption in Sales & Marketing Workflows How deliberately AI is applied across the sales and marketing workflows where it can genuinely help, and how well the automation level fits each one. - **Workflow Coverage**: AI is deployed across the sales and marketing workflows where it can plausibly help (prospect research, outreach drafting, content generation, lead scoring, call analysis, personalisation). - **Workflow-Fit of Tools**: The AI tools we use are well-suited to the sales and marketing tasks we actually do. - **Automation Stage**: We have a clear, deliberate stance on which workflows AI advises, which AI drafts, and which AI handles end-to-end. - **Outbound Volume Discipline**: AI's ability to generate volume is matched by deliberate limits on what we send, so output stays purposeful. ## Tool Usage & Daily Practice How deeply AI tools are woven into everyday work across roles, kept lean and consolidated, and used inside the systems where work actually happens. - **Daily Adoption Across Roles**: AI tools are part of the daily work of sellers, marketers, and support roles across the team — not the preserve of a few enthusiasts. - **Tool Sprawl vs Consolidation**: We use a sensible number of AI tools, not a sprawling collection that overlaps and confuses. - **In-System vs Side-of-Desk**: AI is used inside the primary system of record (CRM, marketing automation platform, support tool) — not in a separate browser tab. - **License Utilisation**: The AI licences we pay for are used by the people they were intended for. ## Brand Voice & Content Integrity Whether AI-touched content stays on-brand, original, properly attributed, and honestly disclosed to the people who receive it. - **Voice Consistency on AI-Touched Outbound**: AI-drafted or AI-touched outbound (email, ads, posts, chat) sounds like our brand, not like generic AI. - **Originality & Attribution**: AI-generated content is sufficiently original and properly attributed where required; we don't republish model output as if it were ours when it isn't. - **AI Disclosure to Recipients**: We disclose AI involvement in outbound and on-site content where policy, regulation, or audience expectations call for it. ## Personalisation & Targeting Whether AI-driven personalisation rests on clear audiences and real signals, optimising for relevance and reply quality rather than raw volume. - **Audience & Segment Discipline**: AI-driven personalisation rests on clear audience and segment definitions, not on whatever fields happen to be in the CRM. - **Signal-Driven Personalisation**: AI uses real signals (behaviour, company data, intent) to personalise — not just merging in a name and company. - **Relevance Over Volume**: We optimise AI-driven outreach for relevance and reply quality, not raw volume. ## Accuracy & Fairness Whether AI-generated claims are verified, lead scoring is checked for bias, and models are caught when they drift from the current audience and positioning. - **Hallucinated Prospect Facts**: AI-generated claims about prospects, companies, and markets are verified before they reach a customer-facing channel. - **Bias in Lead Scoring & Routing**: AI-driven lead scoring and routing are checked for systematic bias against segments that should be in scope. - **Model Drift on Audience Fit**: We notice when AI scoring or content generation drifts away from our current target audience and product positioning, and we correct it. ## Outbound Compliance & Data Boundaries Whether AI outbound stays within regulation, respects opt-outs, uses data with known provenance, and keeps sensitive customer data out of reach by design. - **Regulatory Posture**: AI-generated outbound complies with the regulations that apply to our markets — data protection, anti-spam, consent, AI disclosure, and any rules specific to AI-generated voice or content. - **Opt-Out Hygiene**: AI doesn't re-engage opted-out prospects, send to suppressed domains, or otherwise undo the team's preference work. - **Training-Data Provenance**: We know what data the AI tools were trained on or are using at runtime, and we're comfortable with the provenance (own data, licensed sources, public web, customer data with consent). - **Customer Data Boundaries**: Customer and prospect data classes that should not reach AI (regulated identifiers, payment data, sensitive company detail) are kept out by design. ## Measurement & Improvement Whether the team measures how AI affects content engagement, the funnel, and ROI, and feeds failures back into a loop that makes AI sharper over time. - **Content & Outbound Engagement Tracking**: We track how AI-touched content and outbound actually perform — open rate, reply rate, content engagement, deliverability — and act on what we see. - **Funnel & Pipeline Impact**: We can say how AI changes the funnel — lead volume and quality, conversion at each stage, win rate, deal velocity — not just vanity metrics. - **Failure Capture Loop**: When AI fails (off-brand content, bad email, broken targeting, compliance miss), the failure is captured and feeds an improvement loop. - **ROI & Cost Awareness**: We know what we're spending on AI tools and what we're getting back in pipeline and revenue terms. --- # Scrum Ceremonies Radar URL: https://www.teamretro.com/health-check-templates/scrum-ceremonies-radar/ Scrum ceremonies are the heartbeat of an agile team, yet they can quietly drift into routine, run long, or lose their purpose over time. This radar gives your team a structured way to reflect on each Scrum event — from backlog grooming through to the retrospective — and surface where ceremonies are adding value and where they need a tune-up. By rating each event together, teams build a shared picture of how well their cadence supports planning, transparency, and continuous improvement, then turn those insights into focused actions. ## Scrum Ceremonies Evaluate how effectively each core Scrum event supports your team's flow, alignment, and ability to deliver. - **Backlog Grooming**: Our approach and tools keep the backlog up to date and prioritized for future sprints. - **Sprint Planning**: Our planning sets our team up for success throughout our sprints. - **Daily Scrum**: Our stand-ups are short, to the point, and helpful. - **Sprint Review**: Our showcases reflect the sprint goals and the team's effort and velocity. - **Sprint Retrospective**: Our retros are meaningful and enable us to continuously improve and overcome obstacles. --- # Scrum Health Check URL: https://www.teamretro.com/health-check-templates/scrum-health-check/ Scrum thrives when every part of the framework is working in harmony — from a well-groomed product backlog to focused events and sustainable delivery. This health check helps Scrum teams reflect honestly on how they are applying Scrum in practice, surfacing what is working well and where the framework is breaking down. By rating product ownership, teamwork, events, technical debt, and tooling, your team gains a shared, data-driven view of its agile maturity and a clear starting point for continuous improvement. ## Scrum Practices Assess the core pillars of how your team applies the Scrum framework day to day, from product ownership through to delivery and tooling. - **Product Ownership**: Rate the current state of our product backlog, user stories, acceptance criteria, and relevance to the business. - **Team Work**: Rate the current state of our collaboration, communication, participation, and our ability to own the process and overcome impediments. - **Events**: Rate the cadence and effectiveness of our meetings including standups, planning, reviews, retrospectives, and refining. - **Product and Technical Debt**: Rate our burn rate, the definition of done, the value of increments, and technical debt. - **Tooling**: Rate our ability to use agile tools and to automate testing. --- # Scrum Values Radar URL: https://www.teamretro.com/health-check-templates/scrum-values-radar/ The five Scrum Values — Commitment, Focus, Openness, Respect, and Courage — are the heartbeat of every high-performing Scrum team, shaping how people collaborate, make decisions, and respond to challenges. This check gives your team a structured way to reflect on how strongly each value shows up in everyday practice, surfacing where behaviours are thriving and where they need nurturing. By rating each value together, teams open an honest conversation about culture and ways of working, then agree on concrete actions to live the Scrum Values more fully. Use it during retrospectives or as a periodic pulse to track how your team culture matures over time. ## Scrum Values The five foundational values that guide how a Scrum team works together and builds trust. - **Commitment**: We personally commit to achieving the goals of the scrum team. - **Focus**: We focus on the work of the sprint and the goals of the scrum team. - **Openness**: We are open about all the work and challenges we face during the sprint. - **Respect**: We respect and encourage one another. - **Courage**: We are willing to do the right thing and work on tough problems. --- # Squad Health Check URL: https://www.teamretro.com/health-check-templates/squad-health-check/ Inspired by the model Spotify popularised, the Squad Health Check gives agile teams a fast, honest way to gauge how they feel across the dimensions that matter most to delivery and morale. Squads rate everything from delivering value and codebase health to fun, learning, and teamwork, sparking the conversations that turn quiet frustrations into shared improvements. Run it regularly to track trends over time, surface where a squad needs support, and help leaders see patterns across multiple teams without losing the nuance of each one. ## Squad Health The core dimensions of squad health, spanning what the team delivers, how it works, and how it feels to be part of the squad. - **Delivering Value**: How proud the squad is of what it delivers and how happy stakeholders are with the results. - **Easy to Release**: How simple, safe, and automated it is for the squad to ship its work to production. - **Fun**: How much the squad enjoys coming to work and collaborating together. - **Health of Codebase**: How clean, readable, and well-tested the squad's code is, and how much technical debt it carries. - **Learning**: How much time and opportunity the squad has to learn new and interesting things. - **Mission**: How clear and inspiring the squad finds its higher purpose and focus. - **Pawns or Players**: How much control the squad has over what it builds and how it builds it. - **Speed**: How quickly the squad gets work done without waiting, delays, or blocking dependencies. - **Suitable Process**: How well the squad's way of working fits the team and the work it does. - **Support**: How readily the squad gets the help and support it needs when it asks for it. - **Team Work**: How well the squad collaborates and looks out for one another as a team. --- # Team Barometer URL: https://www.teamretro.com/health-check-templates/team-barometer/ Strong agile teams are built on more than process — they run on trust, collaboration, and a shared sense of ownership. The Team Barometer health check gives teams a regular pulse on the human dynamics that drive performance, surfacing how members feel about working together and where the relationships behind the work need attention. By rating dimensions such as trust, participation, and passion, teams open honest conversations, celebrate what's working, and pinpoint the behaviours worth strengthening. Run it periodically to track how team health evolves over time and to keep continuous improvement focused on people, not just delivery. ## Team Health The core relational and behavioural qualities that determine how effectively your team works together day to day. - **Trust**: There is a high level of trust in our team. People can speak their mind freely. - **Collaboration**: We work together well on issues that come up and can solve complex problems. - **Participation**: We are engaged and active in our Agile ceremonies and everyone is contributing. - **Responsibility**: We take ownership of our tasks and actions and can depend on each other to get the job done. - **Relationships**: We support and boost each other and provide backup and motivation to help each other. - **Passion**: We take pride in our work and are driven by our work and our outcomes. - **Integrity**: We behave in a way that demonstrates good decision-making, communication, and respect. --- # Team Dysfunction Radar URL: https://www.teamretro.com/health-check-templates/team-dysfunction-radar/ Built on the model of the five dysfunctions that undermine teams, this assessment helps groups surface the hidden behaviors that erode trust, stall decisions, and weaken results. By rating each dimension honestly, teams can pinpoint where vulnerability, healthy conflict, commitment, accountability, and a shared focus on results are breaking down. The conversations it sparks turn uncomfortable patterns into clear, actionable steps for building a more cohesive and high-performing team. ## Team Dysfunctions The five interrelated behaviors that determine whether a team builds trust and delivers results together. - **Absence of Trust**: The fear of being vulnerable stops us from building trust with each other. - **Fear of Conflict**: There is artificial harmony which can stifle constructive conflict in the team. - **Lack of Commitment**: Team members do not follow through on actions due to the lack of clarity or buy in. - **Avoidance of Accountability**: We do not hold each other accountable for behaviors and performance because we want to avoid interpersonal issues. - **Inattention to Results**: There is a focus on individual goals, rather than the collective success of the whole team. --- # Team Effectiveness Health Check URL: https://www.teamretro.com/health-check-templates/team-effectiveness-health-check/ Strong teams don't happen by accident — they grow from clear collaboration, healthy dynamics, and a shared understanding of what good looks like. This team effectiveness health check helps groups reflect on how well they work together, how confidently members contribute, and how they measure and improve their performance. By surfacing honest perceptions across collaboration, psychological safety, and performance metrics, teams can pinpoint where they thrive and where they need to invest. Use the results to spark meaningful conversations, align on team needs, and build a more cohesive, high-performing unit. ## Team Effectiveness Factors Explore the collaboration, dynamics, and measurement practices that shape how effectively your team performs together. - **Team Collaboration**: Team collaboration and addressing team dynamics are critical for success in any organization. - **Differentiation**: Workgroups are less reliant on each other, while teams rely on strong collaboration for project success. - **Performance Metrics**: Effective teams can be assessed using various evaluations and metrics, while recognizing differing perspectives on what makes a team effective. - **Data Gathering**: Collecting and analyzing data to assess team effectiveness combines both quantitative and qualitative methods. - **Team Dynamics**: Effective team dynamics emerge from examining critical factors and acknowledging that team size and consensus-based decisions have limited impact. - **Needs Assessment**: Gauging our team's needs through surveys and valuable discussions with our leaders helps us improve. - **Psychological Safety**: I feel confident sharing my ideas within the team, unafraid of making mistakes as I see them as opportunities for learning, and I'm comfortable asking questions openly. --- # Team Health Check URL: https://www.teamretro.com/health-check-templates/team-health-check/ Strong teams don't happen by accident — they're built on clarity, trust, and the right conditions to do great work. This team health check gives agile teams a shared language to reflect on how they're really doing across ownership, value, alignment, communication, and the everyday experience of working together. By rating each dimension on a simple scale, team members surface what's working well and what needs attention, turning gut feelings into honest, actionable conversations. Use it regularly to track progress over time, spark meaningful retrospectives, and help your team stay healthy, motivated, and high-performing. ## Team Health Dimensions Core dimensions that shape how a team performs, collaborates, and stays motivated — from clear ownership and shared goals through to process, support, and the enjoyment of working together. - **Ownership**: The team has clear ownership or a dedicated product owner who is accountable for the team's results and champions the mission inside and outside of the team. - **Value**: We can define and measure the value we provide to the business and the user. - **Goal Alignment**: Everyone understands why they are here, supports the idea, and believes they have what it takes to create solutions that add value. - **Communication**: We have clear and consistent communication that ensures that issues are shared, conflict is reduced, and everyone can work with greater efficiency. - **Team Roles**: The current team skill set is right for the current stage and there are clear roles and responsibilities for each person in the team. - **Velocity**: We learn and implement lessons leading to incremental progress in iterations and production as we go. - **Support and Resources**: We are equipped with the right tools and resources and can easily access support from within and outside the team. - **Process**: Our processes are aligned, effective, and free of unnecessary delays and blocks. We have metrics in place to measure our goals. - **Fun**: We enjoy our work and working as a team. We are being challenged and can develop our skill set or acquire new ones. --- # Team Health Radar URL: https://www.teamretro.com/health-check-templates/team-health-radar/ Give your team a shared, honest snapshot of how things really feel across the dimensions that matter most. Team Health Radar guides members through reflecting on ownership, value, alignment, communication, and more — surfacing strengths to celebrate and friction points to address before they become blockers. By making the conversation visible and repeatable, teams build the trust and clarity needed to improve together, sprint after sprint. ## Team Health Core dimensions that capture how the team is performing, collaborating, and feeling about their work. - **Ownership**: The team has clear ownership or a dedicated product owner who is accountable for the team's results and champions the mission inside and outside of the team. - **Value**: We can define and measure the value we provide to the business and the user. - **Goal Alignment**: Everyone understands why they are here, supports the idea, and believes they have what it takes to create solutions that add value. - **Communication**: We have clear and consistent communication that ensures that issues are shared, conflict is reduced, and everyone can work with greater efficiency. - **Team Roles**: The current team skill set is right for the current stage and there are clear roles and responsibilities for each person in the team. - **Velocity**: We learn and implement lessons leading to incremental progress in iterations and production as we go. - **Support and Resources**: We are equipped with the right tools and resources and can easily access support from within and outside the team. - **Process**: Our processes are aligned, effective, and free of unnecessary delays and blocks. We have metrics in place to measure our goals. - **Fun**: We enjoy our work and working as a team. We are being challenged and can develop our skill set or acquire new ones. --- # Work Happiness Radar URL: https://www.teamretro.com/health-check-templates/work-happiness-radar/ Happy teams are productive teams, and understanding what drives wellbeing at work is the first step to building an environment where people thrive. The Work Happiness Radar gives teams a structured way to measure the human factors that fuel motivation and satisfaction — from role clarity and autonomy to meaning, mastery, support, and engagement. By surfacing how each person experiences their day-to-day work, this health check helps leaders and teams pinpoint what's working, spot early signs of disengagement, and have honest conversations about how to make work more fulfilling. Run it regularly to track work happiness trends over time and turn employee wellbeing into a shared, actionable priority. ## Work Happiness Drivers The core factors that shape how motivated, supported, and fulfilled team members feel in their roles. - **Clarity**: I have clear understanding of my role, my tasks and what outcomes I have to achieve. - **Autonomy**: I have the freedom to do my job and make decisions. - **Meaning**: I find my work meaningful and helps to achieve goals. - **Mastery**: I can continually develop my skills and expertise in my role to improve my capability. - **Support**: I am supported, resourced and provided with the things I need to do my job well. - **Engagement**: I can easily, safely and freely engage in the team processes. ---