How to Conduct Scrum Meetings | Fellow.app

Scrum meetings work best when they stay tightly structured, actively inclusive, and relentlessly action-oriented—so teams can turn short check-ins into real momentum. The core idea is simple: these are time-boxed Agile gatherings where teams align on progress and next steps, then leave with clear commitments. When time limits, agendas, and follow-through are treated as non-negotiable, the meetings stop becoming status theater and start functioning as a practical planning and feedback loop.

Scrum meetings typically include three recurring formats. The Daily Scrum (often called the daily standup) is capped at 15 minutes, with each person sharing what they completed, what they’re working on, and any roadblocks. Sprint planning happens at the start of a Sprint to set goals, prioritize tasks, and distribute work. Sprint review and retrospective occur at the end of the Sprint, combining feedback on what was delivered with a discussion of what should improve next cycle. The emphasis on time boxing is meant to protect efficiency and keep attention on the work that matters.

Conducting these meetings effectively comes down to disciplined mechanics and shared participation. First, time boxing keeps discussions focused and prevents overruns—especially for standups, which should remain concise. Second, relevance requires a clear agenda tied to the meeting’s purpose: daily standups center on progress and obstacles, while planning and reviews focus on goals, outcomes, and learning. Third, collaboration means everyone gets a chance to contribute, which can be supported by structured agendas that assign talking points or sections.

Equally important is documentation and follow-through. Action items should be recorded during the meeting, and commitments must be tracked afterward so decisions don’t evaporate. A practical workflow improvement mentioned is integrating meeting management tools with project management systems—specifically connecting Fellow with tools like Jira, Linear, Monday, and Asana—so action items land in the right place and remain visible.

Active participation is framed as a set of behaviors: come prepared with updates and known blockers, listen closely to others, offer help when needed, and keep updates concise to respect everyone’s time. The transcript also highlights using Fellow’s AI features—recording, transcription, and summarization—to reduce the burden of note-taking while still staying engaged. Finally, confidence is treated as preparation plus communication: know the work, speak up with thoughts or concerns, and ask questions to clarify or improve progress. Done well, scrum meetings become a reliable system for alignment, learning, and execution rather than a recurring time sink.