Agile Retrospectives

Not sure how often to run retrospectives? Discover our simple three-step process to figure out a meeting cadence that optimises your team’s performance.

Never have enough time to discuss everything? Retrospectives always running too long? Here are 9 tips to help you run more efficient retros.

Spice up your retrospective meeting with games designed to help you overcome blockers, learn about working preferences and make continuous improvement.

Find the perfect retrospective idea for your team, whether it's Spring, Summer, Autumn, or Winter. Enjoy Parabol's pre-built templates.

The Prime Directive is a simple statement to start sprint retrospectives with. Here's how to improve your retrospectives with it.

Discover 7 futurespective, retrospective and pre-mortem ideas to start your year off the right way. Get together and clarify your goals for the year ahead.

Whether you’re new to retros or are just a bit rusty, here’s the quickest way to get started and make continuous improvement a reality for your team.

Not sure if that exec should really be attending your retro? We've got some hard and fast rules to follow and guides for navigating tricky conversations.

Both meetings take place at the end of the sprint. But Sprint Reviews focus on the product, while Sprint Retrospectives focus on improving work processes.

Manage retrospectives with lots of reflections or lots of prompts more easily: expand & collapse columns to suit your needs.

Ever noticed how retrospectives tend to bias towards the most recent things that happened? Find out how to counter bias and improve your retrospectives.

Spice up your year-end retrospective with templates that help consolidate learnings, boost morale, and chart a bold course for the new year.

There's lots of advice about being a good facilitator, but most folks in a retrospective are participants. Try these 9 tips to upgrade your participation.

New agile teams face unique challenges when they set out on their journey together. These retrospective ideas help you tackle them directly.

You should budget at least 30 minutes for each 1 week of Sprinting. So for a 2 week sprint, teams should aim for a 1 hour sprint retrospective.

Whether you moved forward accidentally or realized too late that your groups weren’t ideal, we could all use a redo sometimes. Now you can have one.

Whether a sprint retrospective is meaningful or boring hinges on the skill of the facilitator. With these 8 tips, you can make your next retro worth it.

Many teams want to improve how they work, but get stuck figuring out what format or process is right for them. Find out which one is right for you!

Finding new tools and remote working methods has been a necessity. Find out how using a remote meeting tool could improve your in-person retrospectives.

Async retrospectives help remote or hybrid teams improve their flexibility and get on the same page about work no matter where they are in the world.

The number of votes per team member and max votes per topic can drastically change how effective a retro is. Customize these settings to suit your needs.

From fostering inclusion to maintaining anonymity, our experience & data suggest these 5 tips for deciding who to invite to your remote retrospective.

Teams run async retros to give more time for feedback or include members in other time zones. Discussion threads and time limits in Parabol make it easier.

Updates to our online retrospective meeting app: add items during grouping, group by prompt and across prompts, enterprise single sign on, and much more