This keeps the conversation during the meeting focused on making decisions, rather than sharing context. ⚡️ Expert tip: Stop this agenda item from monopolizing the meeting by giving your team a place to share issues and add comments throughout the sprint, when they’re top of mind ( Hypercontext does that! ). This is a round robin discussion where everyone is encouraged to contribute to at least one of those three items (start, stop or edit).

What prevented you from doing your best work? What should we start, stop, edit, keep? (5-15 minutes) This is the time where scope changes and reiterations will be communicated, resulting in changes requested for the next Sprint. With any project, it’s important the Owners have buy-in and acceptance of the finished product. Product acceptance and change requests (10 minutes) There’s nothing worse than wasting 10 minutes messing around with dongles at the start of every meeting. This is an opportunity to knowledge share with the team as well as celebrate wins.Įxpert tip: Make sure you have the right tech in place to have everyone share their screen seamlessly. Demo (20-30 minutes)ĭuring this time, your team will show and tell what they’ve worked on in the sprint. Here are four items to include on your sprint retrospective agenda:Ĭlick here to jump to the Hypercontext sprint retrospective meeting agenda template! 1.

Meeting length: 60 minutes (up to 90 minutes for larger teams) Retro meetings are held at the end of the sprint and can take anywhere from one to two hours, depending on the size of your team. Sprint retrospectives are a type of agile meeting or scrum ceremony that allows the team and scrum master to reflect on process and collect feedback, and use that information to fuel improvements for the next sprint.

Retrospective meeting