Agile and Scrum frameworks have provided us with a specific set of meetings to greatly improve how we work as a team. Sprints can look different between teams, but it should always start with a planning meeting. In this meeting you commit to the work you aim to finish within the agreed upon timeframe (usually a two week period). There can be a lot of ground to cover, which is why we recommend coming up with a list of potential work before the meeting even starts. This list can be added to the agenda for everyone to review ahead of time. Using this method, the meeting conversation can be focused on deciding what work is most important right now and who will complete which tasks.
When the conversation veers off track or goes too deep into a rabbit hole, you can bring it back to the agenda. If someone on your team isn’t certain about what was decided or why it was decided, they can refer back to the discussion notes.
By allowing them to plan ahead for the conversation, you give your team the opportunity to brainstorm, problem-solve, and share their insights deeper than they would by just showing up to the meeting.
When you’re planning your work, it’s easy to get wrapped up in the implementation without having covered the full context of the story. On another story you might go in-depth on the context but accidentally forget to discuss the red flags and move straight into the next story.