We’re happy to visit another sprint retrospective format, so we can have plenty of retrospectives to choose from and find what is best for your dev team.

This time around we’re looking at the Quick Retrospective.  

What is the Quick Sprint Retrospective?

This retro format, as the name suggests, dives right into discussing the previous sprint. It gets straight to the point and allows the team to discuss what went well, what did not go so well, and to draw ideas from that. Essentially, there are four topics that need to be discussed:

●     What was good?

●     What was bad?

●     Ideas

●     Actions

The best way to hold this retrospective meeting is by having a whiteboard divided into four sections and giving each team member a stack of sticky notes. You can have them write the answers to the four topics on sticky notes and then stick them in the appropriate square on the board. Once everyone is done, then you can have a discussion and come up with ideas about how the following sprint can be improved.

The quick retrospective is an excellent way to be straightforward and get right to the point in order to get everyone on the same page and ensure that everyone is in agreement with how things can be improved in the future. The important part of this format is to give each team member the chance to voice their opinions on what was good, what was bad, and to give their ideas and then work together to come up with an action plan.

When should you use the Quick Agile Retrospective?

This is a great retrospective format for teams who are not familiar with retrospective meetings because it dives right in and is easy to understand and use. It is best used at he end of a sprint so that the team can reflect on each of these aspects and come up with a solid action plan for the next sprint.

Image Credit

‍