What are Scrum meetings, and how to run them effectively in 2025

Scrum meetings are structured ceremonies that create alignment, clarity, and continuous improvement for development teams working in sprints. By establishing a predictable cadence, these five key meetings help teams deliver value faster while maintaining focus on business goals and preventing wasted effort.

In this article, you’ll learn about each scrum ceremony, who should participate in each, and practical tips to make them more effective. We’ll also show how platforms like monday dev can automate routine updates and visualize progress, letting your team focus on collaboration rather than administration.

Whether you’re new to Scrum or looking to optimize your existing process, mastering these fundamentals creates a system that supports clear communication, removes blockers, and gives everyone visibility into progress.

Key takeaways

• A clear cadence drives delivery: Sprint planning, daily scrums, sprint reviews, retrospectives, and backlog refinement work together to plan, coordinate, and improve
• Timebox every ceremony: Keep daily scrums to 15 minutes and set appropriate limits for planning, reviews, and retrospectives
• Prioritize problem-solving over status: Ask “What help do you need?” and move routine status updates outside the meeting
• Use monday dev to reduce admin: Automate routine updates and visualize capacity so teams can spend meeting time on collaboration
• Invite the right people: Match product owners, Scrum masters, developers, and stakeholders to the ceremonies where their input is needed

Scrum meetings at a glance

Scrum defines 5 events in each sprint. Together, they create the cadence for planning, daily coordination, feedback, and improvement.

• Sprint planning: Set the scrum sprint goal and commit to a realistic sprint backlog.
• Daily scrum (standup): 15-minute sync to align, surface blockers, and adjust the day’s plan.
• Sprint review: Demo working software and gather stakeholder feedback to inform the backlog.
• Sprint retrospective: Reflect on the process and agree on a few concrete improvements.
• Backlog refinement: Continuously clarify, size, and prioritize upcoming work so planning runs smoothly.

• Sprint: A fixed period (typically 1–4 weeks) to deliver a defined slice of value.
• Product backlog: The prioritized list of features, enhancements, and fixes for the product.
• Sprint backlog: The subset the team commits to for the current sprint, aligned to the sprint goal.

The 5 Scrum ceremonies

Each Scrum ceremony has a distinct purpose, participants, and timebox. Together, they provide structure without slowing execution.

1. Sprint planning

Sprint planning sets the direction for the next sprint (1–4 weeks).

• Who attends: Product owner, scrum master, and the full development team.
• Agenda: Review priorities, discuss how to deliver them, and agree on a realistic sprint backlog.
• Duration: About 2 hours per week of sprint (4 hours for a 2-week sprint).

By the end, the team should leave with a shared sprint goal and clear commitments.

2. Daily scrum standup

The daily scrum is a 15-minute sync to keep the team aligned.

• Who attends: Development team (others may observe).
• Agenda: Each person answers:
  • What did I complete yesterday?
  • What will I work on today?
  • What’s blocking progress?

Keep the focus on coordination. Problem-solving happens after with only those involved.

3. Sprint review

Sprint review closes the sprint by sharing completed work and gathering feedback.

• Who attends: Scrum team and stakeholders.
• Agenda: Demonstrate working software, discuss what was learned, and adjust the backlog.
• Duration: Up to 2 hours for a 2-week sprint.

Think of this as a collaborative session, not a presentation. The goal is meaningful dialogue about what to build next.

4. Sprint retrospective

This agile retrospective is your team’s chance to reflect on how you work together.

• Who attends: Entire Scrum team.
• Agenda:
  • What went well?
  • What needs improvement?
  • What will we try next sprint?
• Duration: About 1.5 hours for a 2-week sprint.

The scrum master facilitates, ensuring open conversation. With monday dev, teams can track retrospective action items across scrum sprints and measure which changes stick.

5. Backlog refinement

Backlog refinement (also called backlog grooming) keeps upcoming work clear and ready.

• Who attends: Product owner and development team.
• Agenda: Clarify requirements, size effort, and break down large items.
• Duration: 1–2 hours per week.

A well-refined backlog makes sprint planning faster and commitments more reliable.

Who participates and why it matters

Each Scrum role brings specific value to the ceremonies. Having the right people in the room keeps meetings purposeful and outcomes clear.

• Product owner: Owns the product vision and backlog. They guide priorities during sprint planning, adjust the backlog after sprint reviews, and prepare upcoming work during backlog refinement.
• Scrum master: Facilitates ceremonies, removes blockers, and ensures the team follows Scrum principles. Their role is to keep meetings on track and create a safe environment for open contribution.
• Development team: Builds the product. They run daily scrums, estimate and commit during planning, demo completed work in reviews, and suggest improvements in retrospectives.
• Stakeholders: Join sprint reviews to provide feedback and align direction with business goals. They step back from other ceremonies to keep the team focused.

For larger organizations, a scrum of scrums can coordinate across multiple teams, ensuring alignment at scale. With a platform like monday dev, leaders get portfolio-level visibility without disrupting daily execution.

How to structure each scrum meeting

Even well-intentioned Agile ceremonies can drift off course without clear guardrails. Setting expectations for time, agenda, and format helps teams get the most out of every session.

Duration and timeboxing

Each ceremony has a recommended length, and sticking to those limits keeps energy high and focus sharp. For a 2-week sprint, plan on about:

• Sprint planning: 4 hours
• Daily scrum: 15 minutes
• Sprint review: 2 hours
• Sprint retrospective: 1.5 hours

Teams working in longer or shorter sprints can adjust, but the principle remains — use timeboxes to respect people’s attention.

Agenda and format

A predictable structure makes it easier for participants to contribute meaningfully.

• Sprint planning starts with the goal, then backlog selection, task breakdown, and commitment.
• Daily scrums follow the three-question format, so updates are consistent.
• Sprint reviews begin with working software and end with stakeholder discussion.
• Retrospectives often use “Start, Stop, Continue” or similar techniques to surface insights.

Get it now: Meeting agenda template

Supporting remote or hybrid teams

Distributed work doesn’t change the ceremonies — it changes how you run them. Reliable video, clear audio, and collaborative boards make remote participation seamless.

Scheduling with time zones in mind matters, and engagement tools like polls or breakout rooms help keep energy up. monday dev provides shared sprint boards, asynchronous updates, and real-time visibility, making it easier for distributed teams to stay aligned without losing momentum.

What development teams say about monday dev

These practices become easier to maintain when planning, progress, and follow-up actions stay visible between meetings. Teams using monday dev have applied that approach across their development workflows, as these examples show.

"monday dev empowered us to optimize our GTM approach, resulting in faster, more dependable deliveries"

Steven Hamrell | Director of Product Management

"monday dev empowers us to manage the entire development process on one platform so we can speed up product delivery and improve customer satisfaction"

Mitchel Hudson | Head of Technology

"We're operating in an open, deep trusting, transparent environment with no silos of information. It's about completely opening access to everyone who needs it."

Alan Schmoll | Executive Vice President, Vistra Platform

7 tips for effective agile development meetings

Scrum meetings work best when teams apply a few practical habits. These tips help meetings feel valuable rather than routine.

1. Set expectations early

Share the purpose and prep work before each ceremony so people arrive ready to contribute. Keeping sprint goals, backlog priorities, and ownership visible in monday dev also gives participants the context they need before the meeting starts.

2. Respect the clock

Stay within the timebox. Capture off-topic items in a parking lot instead of derailing the session.

3. Encourage team ownership

Daily scrums belong to developers, not managers. Retrospectives work only if everyone feels safe to contribute. This helps bridge a common perception gap where leaders often overestimate the sense of ownership felt by their teams.

4. Shift from status to support

Move routine status reporting outside the meeting so the team can use the time to discuss dependencies, blockers, and where support is needed. When progress is already visible on a shared monday dev sprint board, the Daily Scrum doesn’t need to become a round-robin status report.

5. Resolve blockers with urgency

When an impediment comes up, assign responsibility and track it visibly until it’s closed. Teams can also flag blocked work in monday dev, assign ownership, and keep the issue visible after the meeting until it’s resolved.

6. Use tools that lighten the load

Scrum tools support teams that use the Scrum framework. A platform like monday dev uses automation to reduce manual updates, surface trends, and highlight potential risks before they stall progress.

7. Keep experimenting

Teams evolve. Adjust formats, timing, and facilitation styles based on what delivers the most value. Retrospectives are a good place to check whether your ceremonies still work.

Run smarter, faster ceremonies with monday dev

monday dev brings sprint planning, backlog priorities, capacity, progress, and retrospective actions into the same workflow, giving teams a shared view of what’s planned, what’s moving, and what needs attention.

Plan sprints with capacity in view

Visual boards bring team capacity, backlog priorities, and sprint goals together so teams can make more realistic commitments during sprint planning.

Keep daily progress visible

As work moves through the sprint, monday dev tracks progress in the same workflow, while automations can handle routine notifications and follow-ups.

Bring evidence into sprint reviews

Teams can connect development tools and work data so completed work, progress, and stakeholder feedback are available when reviewing the sprint.

Track retrospective actions between sprints

Improvement ideas don’t need to disappear when the retrospective ends. Teams can assign action items, track them across sprints, and see whether agreed changes were actually implemented.

Keep the backlog ready

Teams can organize, prioritize, and refine upcoming work so backlog items are clearer before they reach the next sprint planning session.

By keeping sprint goals, backlog items, capacity, blockers, and improvement actions visible in monday dev, teams can use their Scrum meetings to make decisions and resolve issues rather than reconstructing information that already exists elsewhere.