Sprint Retrospective

Establish a culture of transparency and continuous learning in your team.


Sprint Retrospective

Date: 16 Jan 2023
Participants: @Luke, @Han, @Leia

Issues & epics





Action items (previous retrospective)

  • Update the roadmap for our technical debt: @Luke

  • Revise the team handbook based on the results of the team discussion: @Han

  • Update the release process to prevent unverified items from rolling over to next RC: @Leia


What went well

Please note down how you think we exceeded expectations either individually or as a team.

  • We were able to accelerate delivery of certain features thanks to community contributions and collaboration.

  • Newly onboarded engineers are doing well and have been collaborating well with each other and existing members in order to solve problems.

  • The release process has become well-documented and ran smoother than it ever has.

What went badly

Please note down the areas where we made mistakes or otherwise didn't meet our expectations.

  • We regularly are starting work on issues that turn out to take several months to complete. Sometimes we realize midway through we could have broken down issues into smaller deliverables that add value on their own.

  • We still don’t have a reliable way to test large data sets.

  • Changes were made to planned feature releases at the last minute. Created scramble to change the blog post, home page, and tweet, etc.

Ideas for improvement

Please add your ideas below. Discuss the lessons we learned in this release and how we can use those learnings to improve.

  • Be more proactive with communication on issues that stay open for a while.

  • Communication needs to happen in public channels, such as Nuclino, not via DMs, to make sure we can all work together in getting our deliverables done.

  • There is some tribal knowledge in our team that should be documented to help with onboarding and knowledge sharing generally.

Action items

  • Create 2-3 examples of Good code reviews to help set expectations of newly hired engineers around what our process looks like when it's functioning well: @Luke

  • Better define the security release process, make it repeatable, and document in the Handbook: @Han

  • Investigate time series data about regressions per release: @Leia

Live Preview

About this template


Studies show that teams that conduct retrospectives are typically 25% more effective. Retrospectives are a fundamental part of doing agile “right” and are increasingly used in non-technical environments as well.

Retrospectives offer a great way to learn from experience, giving teams the opportunity to pause and reflect on how things have been going and continuously make improvements. It's a widely used method of continuously improving team performance.

There are countless different ways to do agile retrospectives, and depending on your team size and workflow, some might work better than others. We have put together a simple template to help you get started.

How to run an agile retrospective meeting

There are many alternative ways to structure your retrospective document, for example, creating sections titled 'More of', 'Same of', and 'Less of', or 'Start', 'Continue' and 'Stop'. It's up to you and your team which format to choose.

Once you have settled on a specific retrospective format, you can start collaborating with your team in real time. Using video chat or @-mentioning your teammates in comments is a great way to increase engagement. Upload images, videos, GIFs, or embed files to make your retrospectives more visual.

To get started, simply copy this agile retrospective template and customize it to match your team's needs.

Related templates

Character illustration