No need to be a scrum expert to conduct sprints. In fact, many teams borrow sprints, a foundational concept in agile project-management methodologies, as a standalone way to complete work. If you’re not familiar with the concept, a sprint is simply a set period of time during which work has to be completed and reviewed. But without a crucial step called a sprint review, it’s also easy for many teams to miss out on the benefits of conducting sprints.

“I would love it if both leaders and teams were more aware of the need to recap a sprint in order to effectively communicate what was accomplished, what still needs to be done, and how everyone can move forward,” says Mark Koning, Chief Human Resources Officer at Discover Business, an MBA resource for graduate students. “I’ve seen so many productive reviews wasted because a team didn’t take five minutes in the end to revisit the main points.”

What is a sprint review?

According to Scrum.org, the purpose of a sprint review is to inspect the outcome of a sprint and determine future adaptations of it. During the event, stakeholders review “what was accomplished and what has changed in the environment.” Then, based on this information, your team collaborates and makes decisions on what to do next. It is a work session–not a presentation.

In other words, a sprint review is an actionable debrief. It’s about taking an honest look at how your plan unfolded, whether you reached your goal as far as the work you wanted to complete within the set duration of your sprint, and using that information to improve teamwork in the future.

Common sprint review mistakes

Before diving into the most important things you should include in your sprint review, make sure to avoid some of the most common sprint review mistakes.

“The two biggest mistakes I see are a lack of meeting minutes and a disproportionate focus on the future rather than the past and present,” says Koning.

“Meeting minutes might seem like a mundane task, but they’re crucial for documenting what was discussed decisions that were made, and next steps. Without them, everyone is left to rely on their memory which often leads to confusion and frustration.”

So document, document, document. It’s so easy to forget what was discussed in your sprint review and lose precious, actionable information.

Another common mistake is getting too focused on the future. While it matters, the purpose of a sprint is to deconstruct first, then plan forward. “It’s natural to want to look ahead and start dreaming up new features, but it’s essential to take a step back and understand the impact of your work in the present,” adds Koning.

Topics to cover in every sprint review

Use the checklist below to cover the essentials during your next sprint review.

1. The basics

First things first, start your sprint review with the intention to discuss what was done, what still needs to get done, and who will be involved in doing it.

“The most important things to cover in a spring review are what was accomplished, what still needs to be done, and how everyone can move forward,” says Koning.

2. The pitfalls

You’ll also want to include constructive feedback and talk about learnings. Identify challenges and roadblocks so you can prevent them in the future.

“Accomplishments need to be celebrated, but they also need to be analyzed so that lessons can be learned and applied in the future. It’s also important to identify any dependencies or blockers so that they can be addressed.”

3. The future

Finally, don’t walk out of the meeting room without clear action items. You should be armed with a tangible idea of the changes you will implement in your project or product in your next step. Be explicit and don’t make assumptions–it’s important for every stakeholder to move forward with clarity.

“What still needs to be done is the next step in the process, and it’s essential to have a clear understanding of what needs to be done before anything can be declared finished. Moving forward is about setting everyone up for success and making sure that everyone has a common understanding of what they need to do next.”