Do you record a summary of Sprint Meetings?

Creating a comprehensive summary and recording of your Sprint Meeting is a great way to communicate changes in a product to the community and stakeholders — especially for those unable to attend.

Learn more on what happens at Sprint Retrospective, Sprint Review, and Sprint Planning meetings.

Why record a summary of the Sprint Meeting?

• Clarity: Provides a clear, accessible update for all stakeholders, including those not present
• Documentation: Serves as a historical record of decisions and discussions, valuable for future Sprints and project continuity
• Engagement: Ensures that all stakeholders, regardless of their availability to attend, have access to the same information, promoting inclusiveness and alignment
• Community: Allows the community at large to see what is happening on a product and provide feedback

Prepare for the Sprint Meeting recording

Before you start recording, ensure you have the right people ready for key roles:

• Have someone ready to scribe: Designate someone to take detailed notes during the meeting. This person will capture key decisions, action items, and important discussion points that may not be fully covered in the video summary
• Have someone ready to YakShave: Designate someone to handle secondary recordings during the meeting. While the main presenter is recording the Sprint summary, this person can start separate recordings (YakShaves) to create tasks or work items as needed

Having these roles clearly defined beforehand ensures a smoother recording process and better documentation of your Sprint Meeting.

Avoid long pauses

During the meeting, don’t pause ask, “Does anyone have any questions?” — this often leads to awkward silence and slows down the meeting.

Instead, remind the team before to use the “Raise Hand” feature in Microsoft Teams if they have something to say. This keeps the meeting moving and ensures everyone gets a chance to contribute without unnecessary delays.

Record the Sprint Meeting summary

The Sprint Meeting summary should be what it is: a summary. So keep it concise by focusing on the main goals and decisions that were discussed during the Sprint Meeting.

Here's a suggested runsheet for what to cover in the video:

1. Before the recording, inform participants that the session is being recorded and ask them if there's nothing sensitive in the Sprint Retrospective
2. Start the recording by showing the Product website
3. Run through Sprint Review Email - which should include the Sprint Retrospective Tip: The summary should be focused on the Dones and any special highlights. In the email template, bold the most important points so they stand out. These highlighted items should be called out in the summary
4. Run through Sprint Planning Email
5. Finish the recording on the Product YouTube Channel, and mention that the current recording will be uploaded there

See useful tips on how to make great videos.

Note: Everyone should be free to speak candidly in a Sprint Retrospective, and you don’t want the fact that there will be a recorded summary to make people not speak up. The recorded retro should only include the main good and bad points... it gives some window into the team, but not everything.

Share the Sprint Meeting summary recording

If you've never uploaded a video to YouTube, you can follow this tutorial

Note: Don't forget to check that you're uploading to the right channel. Ideally have a channel for each product (e.g. SSW Website, SSW TimePro, etc.).

You will fill the title, description, and thumbnail fields with clear, helpful content to improve visibility and engagement.

Video title

It is important to have an accurate title that makes it clear what Scrum Sprint you are making a video for. The best way is to follow a consistent format across each video. At SSW, we follow this format:

Video description

You should also include a description about the contents for ease of navigation. E.g. YouTube allows you to add timecode chapter markers by adding it in the description.

Video thumbnail

The thumbnail should show the Sprint iteration, the Team's name and the date when the meeting occured. This often comes from the start screen of a Teams recording.

For a more visual appealing thumbnail, you can use a PowerPoint slide that are updated every Sprint. E.g.: SSW.Website Thumbnail.

Below is a good example of how a Sprint Summary video should look like on YouTube.

✅ Figure: Good example – The video contains a great title, description and thumbnail

✅ Good example of a Sprint Meeting recording

Here is an example of a Sprint Meeting recording from the Tina CMS Team.

By adopting these practices, teams can ensure that the outcomes of Sprint Meetings are effectively communicated and documented, supporting project success and stakeholder satisfaction.