Continuous Retrospective

Poor quality feedback makes sprint retrospectives ineffective

Teams get very low constructive feedback to discuss in retrospectives, making meetings ineffective 😥 This is a widespread problem among software engineering teams.

Bad user experience in feedback collection is the root cause

It's not that teams are perfect and have no problems to discuss. People have a tough time remembering what happened 🤷

We ask team members to share feedback right before the retro. They are:

🥱Tired after work

A lot of teams do retrospectives after they finished work

⏱️Time pressure

Everyone is waiting on the call. No time time to gather their thoughts about what happened in the last week or two.

👀Peer pressure

Feedback is shared publicly. Most people don't feel comfortable sharing honest feedback when everyone is looking.

How can I significantly improve retrospective meeting quality and outcomes?

Start gathering feedback not before the start of the retrospective but during the whole sprint. Continuously.

This is very easy to do:

Create a new retrospective right after you finish your current one;
Share a link with your team;
Let the team know that they can share feedback whenever they experience something great or awful in their work.

Now, when the time comes, you will have more quality feedback to discuss and have a more productive retrospective. Win!🎉

Pro tips

Copy the permalink from your team hub in Codigy and add this link to your Slack bookmarks. This makes feedback sharing super easy for your team.

Share feedback any time during the sprint

Try in your free account View free resources Discuss on Discord