{"id":48918,"date":"2021-04-06T13:20:46","date_gmt":"2021-04-06T13:20:46","guid":{"rendered":"https:\/\/staging-mondaycomblog.kinsta.cloud\/?post_type=pm&#038;p=48918"},"modified":"2026-08-30T04:45:09","modified_gmt":"2026-08-30T09:45:09","slug":"scrum-ceremonies","status":"publish","type":"post","link":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/","title":{"rendered":"5 Types of Scrum Ceremonies &#038; How to Run Them Effectively in 2026"},"content":{"rendered":"<div class=\"text-block\" id=\"text-block-1\">\n<p>Most delivery teams don&#8217;t struggle because they meet too little. They struggle because their meetings turn into status theater, where people take turns reading updates that could&#8217;ve been a message, and the real blockers never surface. Scrum ceremonies are meant to fix exactly that, but only when you run them with intent.<\/p>\n<p>Scrum ceremonies are structured events that create alignment, clarity, and continuous improvement for teams working in sprints. By establishing a predictable cadence, these events help teams deliver value faster while keeping focus on business goals and preventing wasted effort.<\/p>\n<p>In this guide, you&#8217;ll learn what each one is for, who should attend, how long each one should run, and practical tips to make them more effective. You&#8217;ll also see how the monday AI Workspace can automate routine updates and visualize progress, so your team spends its time on collaboration instead of admin.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-2\">\n<h2 class=\"h2 text-block__title\">Key takeaways<\/h2>\n<ul>\n<li><strong>A clear cadence drives delivery<\/strong>: sprint planning, daily scrums, sprint reviews, retrospectives, and backlog refinement work together to plan, coordinate, and improve<\/li>\n<li><strong>Timebox every ceremony<\/strong>: 15 minutes for daily scrums, and about two hours per week of sprint for planning, review, and retrospective<\/li>\n<li><strong>Prioritize problem-solving over status<\/strong>: ask &#8220;what help do you need?&#8221; and push routine updates to async channels<\/li>\n<li><strong>Invite the right people<\/strong>: product owner for priorities, scrum master for facilitation, developers for daily coordination, and stakeholders for the sprint review only<\/li>\n<li><strong>Use the monday AI Workspace to reduce admin<\/strong>: automate routine updates, summarize meetings into action items, and visualize capacity so teams focus on collaboration<\/li>\n<\/ul>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"1\">Get started with monday.com<\/a><\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-3\">\n<h2 class=\"h2 text-block__title\">What are scrum ceremonies?<\/h2>\n<p>Scrum ceremonies are recurring events that give teams a consistent rhythm for planning work, coordinating progress, reviewing outcomes, and improving how they work. In the official Scrum framework, the Sprint acts as the container for four formal events: Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective.<\/p>\n<p>Backlog refinement isn&#8217;t a formal Scrum event, but most Scrum teams treat it as an essential recurring activity because it keeps upcoming work clear, prioritized, and ready for future sprints. For that reason, it&#8217;s commonly discussed alongside the four Scrum ceremonies \u2014 and we&#8217;ll cover all five activities in this guide.<\/p>\n<p>Compared with a typical project status meeting, the difference is intent. A status meeting usually exists to report upward, while scrum ceremonies exist to move work forward for the team itself. Each ceremony has a fixed purpose and a firm timebox, so people know exactly why they&#8217;re there and when they&#8217;ll be done. In a two-week Sprint, for example, the team plans at the beginning, coordinates daily, reviews the completed work with stakeholders near the end, and reflects on how to improve before the next Sprint begins.<\/p>\n<p>Here&#8217;s how the five events fit together. Each one has a distinct purpose, so read the short label first and the explanation second.<\/p>\n<ul>\n<li><strong>Sprint planning:<\/strong> set the <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-sprint\/\">scrum sprint<\/a> goal and commit to a realistic <a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-backlog\/\">sprint backlog<\/a><\/li>\n<li><strong>Daily scrum:<\/strong> a 15-minute sync to align, surface blockers, and adjust the day&#8217;s plan<\/li>\n<li><strong>Sprint review:<\/strong> demo working software and gather stakeholder feedback to inform the backlog<\/li>\n<li><strong>Sprint retrospective:<\/strong> reflect on the process and agree on a few concrete improvements<\/li>\n<li><strong>Backlog refinement:<\/strong> continuously clarify, size, and prioritize upcoming work so planning runs smoothly<\/li>\n<\/ul>\n<p>Three terms show up across all of these meeting types, and it helps to define them plainly before you go further.<\/p>\n<ul>\n<li><strong>Sprint:<\/strong> a fixed period, typically one to four weeks, to deliver a defined slice of value<\/li>\n<li><strong>Product backlog:<\/strong> the prioritized list of features, enhancements, and fixes for the product<\/li>\n<li><strong>Sprint backlog:<\/strong> the subset the team commits to for the current sprint, aligned to the sprint goal<\/li>\n<\/ul>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-4\">\n<h2 class=\"h2 text-block__title\">The five Scrum ceremonies and activities teams use each sprint<\/h2>\n<p>Scrum gives each formal event a distinct purpose, set of participants, and timebox. Backlog refinement sits outside the official event structure, but it plays an important supporting role by preparing work for future sprints. Together, these activities create a repeatable cycle for deciding what to build, coordinating delivery, gathering feedback, and improving the team&#8217;s process.<\/p>\n<p>It also helps to remember that the sprint itself is the container event. It holds the other four meetings inside a fixed time-box, which is why scrum events always run in the same order within each cycle. Read the five that follow as one connected system: planning sets the goal, the daily scrum keeps it on track, the review tests it against real feedback, the retrospective improves how you got there, and refinement readies the next round.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-5\">\n<img width=\"1024\" height=\"576\" src=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-management-2.jpg\" class=\"attachment-large size-large\" alt=\"\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-management-2.jpg 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-management-2-300x169.jpg 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-management-2-768x432.jpg 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/>\n<\/div>\n<div class=\"text-block\" id=\"text-block-6\">\n<h3>1. Sprint planning<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-planning\/\">Sprint planning<\/a> sets the direction for the next sprint, which usually runs one to four weeks.<\/p>\n<ul>\n<li><strong data-start=\"3437\" data-end=\"3453\">Who attends:<\/strong> Developers; the Product Owner or Scrum Master participates when actively working on Sprint Backlog items<\/li>\n<li><strong data-start=\"3563\" data-end=\"3574\">Agenda:<\/strong> Inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed<\/li>\n<li><strong data-start=\"3658\" data-end=\"3671\">Duration:<\/strong> 15 minutes<\/li>\n<\/ul>\n<p>Teams can use the familiar yesterday\/today\/blockers format if it helps, but the goal isn&#8217;t to collect individual status reports. The Daily Scrum should help Developers decide how to adjust their plan and make progress toward the Sprint Goal.<\/p>\n<h3>2. Daily scrum standup<\/h3>\n<p>The daily scrum is a 15-minute sync that keeps the team aligned.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> the development team, with others free to observe<\/li>\n<li><strong>Agenda:<\/strong> each person answers what they completed yesterday, what they&#8217;ll work on today, and what&#8217;s blocking progress<\/li>\n<\/ul>\n<p>Keep the focus on coordination. Problem-solving happens afterward with only the people involved.<\/p>\n<h3>3. Sprint review<\/h3>\n<p>The <a href=\"https:\/\/monday.com\/blog\/rnd\/what-is-a-sprint-review-definition-goals-and-tips\/\">sprint review<\/a> closes the sprint by sharing completed work and gathering feedback.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> the <a href=\"https:\/\/monday.com\/blog\/rnd\/heres-how-you-build-a-successful-scrum-team\/\">scrum team<\/a> and stakeholders<\/li>\n<li><strong>Agenda:<\/strong> demonstrate working software, discuss what the team learned, and adjust the backlog<\/li>\n<li><strong>Duration:<\/strong> up to two hours for a two-week sprint<\/li>\n<\/ul>\n<p>Think of this as a collaborative session, not a presentation. The goal is meaningful dialogue about what to build next.<\/p>\n<h3>4. Sprint retrospective<\/h3>\n<p>This <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-retrospective-what-it-is-and-how-it-works\/\">agile retrospective<\/a> is your team&#8217;s chance to reflect on how you work together.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> the entire scrum team<\/li>\n<li><strong>Agenda:<\/strong> what went well, what needs improvement, and what you&#8217;ll try next sprint<\/li>\n<li><strong>Duration:<\/strong> about 1.5 hours for a two-week sprint<\/li>\n<\/ul>\n<p>The scrum master facilitates and keeps the conversation open. With the monday AI Workspace, teams can track retrospective action items across <a href=\"https:\/\/monday.com\/blog\/rnd\/how-to-get-the-most-out-of-your-scrum-artifacts\/\">scrum sprints<\/a> and measure which changes actually stick.<\/p>\n<h3>5. Backlog refinement<\/h3>\n<p>Backlog refinement, also called <a href=\"https:\/\/monday.com\/blog\/rnd\/backlog-grooming\/\">backlog grooming<\/a>, keeps upcoming work clear and ready.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> the product owner and development team<\/li>\n<li><strong>Agenda:<\/strong> clarify requirements, size effort, and break down large items<\/li>\n<li><strong>Duration:<\/strong> one to two hours per week<\/li>\n<\/ul>\n<p>A well-refined backlog makes sprint planning faster and commitments more reliable.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-7\">\n<h2 class=\"h2 text-block__title\">Who participates in scrum ceremonies?<\/h2>\n<p>Each scrum role brings specific value to the events. Having the right people in the room keeps agile scrum ceremonies purposeful and outcomes clear, so it&#8217;s worth being deliberate about who joins each one.<\/p>\n<ul>\n<li><strong>Product owner:<\/strong> owns the product vision and backlog. They <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-guide\/\">guide priorities<\/a> during sprint planning, adjust the backlog after sprint reviews, and prepare upcoming work during refinement<\/li>\n<li><strong>Scrum master:<\/strong> facilitates meetings, removes blockers, and keeps the team aligned with Scrum principles. Their job is to keep meetings on track and create a safe space for open contribution<\/li>\n<li><strong>Development team:<\/strong> builds the product. They run daily scrums, estimate and commit during planning, demo completed work in reviews, and suggest improvements in retrospectives<\/li>\n<li><strong>Stakeholders:<\/strong> join sprint reviews to give feedback and align direction with business goals. They step back from other meetings to keep the team focused<\/li>\n<\/ul>\n<p>A useful rule of thumb: if someone isn&#8217;t contributing to or acting on the outcome of a ceremony, they probably don&#8217;t need to be in it. Guarding attendance this way keeps sessions short and focused, and it respects everyone&#8217;s time.<\/p>\n<p>For larger organizations, a <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-of-scrums\/\">scrum of scrums<\/a> coordinates work across multiple teams to keep everyone aligned at scale. With the monday AI Workspace, leaders get portfolio-level visibility across those teams without disrupting daily execution.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"2\">Get started with monday.com<\/a><\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-8\">\n<h2 class=\"h2 text-block__title\">How to structure each scrum meeting<\/h2>\n<p>Even well-intentioned <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-ceremonies\/\">agile meetings<\/a> can drift off course without clear guardrails. Setting expectations for time, agenda, and format helps teams get the most out of every session, and it gives you a repeatable scrum meeting structure to reuse each sprint.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-9\">\n<img width=\"1024\" height=\"576\" src=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-retrospective-2.png\" class=\"attachment-large size-large\" alt=\"\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-retrospective-2.png 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-retrospective-2-300x169.png 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-retrospective-2-768x432.png 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/>\n<\/div>\n<div class=\"text-block\" id=\"text-block-10\">\n<h3>Duration and timeboxing<\/h3>\n<p>Each ceremony has a recommended length, and sticking to those limits keeps energy high and focus sharp. How long should sprint planning take? Sprint planning is timeboxed to about two hours per week of sprint, so a two-week sprint runs around four hours, and the meeting ends as soon as the team agrees on a goal and backlog. For a two-week sprint, plan on about:<\/p>\n<ul>\n<li><strong>Sprint planning:<\/strong> four hours<\/li>\n<li><strong>Daily scrum:<\/strong> 15 minutes<\/li>\n<li><strong>Sprint review:<\/strong> two hours<\/li>\n<li><strong>Sprint retrospective:<\/strong> 1.5 hours<\/li>\n<\/ul>\n<p>Teams working in longer or shorter sprints can adjust, but the principle holds: use timeboxes to respect people&#8217;s attention.<\/p>\n<h3>Agenda and format<\/h3>\n<p>A predictable agenda for scrum ceremonies makes it easier for participants to contribute meaningfully. Here&#8217;s the format each ceremony tends to follow.<\/p>\n<ul>\n<li><strong>Sprint planning:<\/strong> starts with the goal, then moves to backlog selection, task breakdown, and commitment<\/li>\n<li><strong data-start=\"4142\" data-end=\"4159\">fDaily Scrums:<\/strong> inspect progress toward the Sprint Goal, surface anything affecting the plan, and adjust the Sprint Backlog for the next day of work<\/li>\n<li><strong>Sprint reviews:<\/strong> begin with working software and end with stakeholder discussion<\/li>\n<li><strong>Retrospectives:<\/strong> often use &#8220;start, stop, continue&#8221; or a similar technique to surface insights<\/li>\n<\/ul>\n<h3>Supporting remote or hybrid teams<\/h3>\n<p>Distributed work doesn&#8217;t change the meetings; it changes how you run them. Reliable video, clear audio, and collaborative boards make remote participation seamless.<\/p>\n<p>Scheduling with time zones in mind matters, and engagement tools like polls or breakout rooms help keep energy up. For distributed teams, lean on async where you can: a written standup update posted before the sync lets the live time go to blockers and decisions instead of round-robin reporting. The monday AI Workspace provides shared sprint boards, asynchronous updates, and real-time visibility, so distributed teams stay aligned without losing momentum.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-11\">\n<h2 class=\"h2 text-block__title\">Seven tips for running effective scrum ceremonies<\/h2>\n<p>Scrum meetings work best when teams apply a few practical habits. These tips help each session feel valuable rather than routine.<\/p>\n<h3>1. Set expectations early<\/h3>\n<p>Share the purpose and prep work before each ceremony. When people know what to bring and what a good outcome looks like, they arrive ready, and the discussion moves faster. A one-line agenda pinned to the invite is often enough.<\/p>\n<h3>2. Respect the clock<\/h3>\n<p>Stay within the timebox. If a topic needs more time than the ceremony allows, capture it in a parking lot and schedule a focused follow-up with only the people involved, instead of letting it derail the session for everyone.<\/p>\n<h3>3. Encourage team ownership<\/h3>\n<p>Daily scrums belong to developers, not managers, and retrospectives only work if everyone feels safe to contribute. This helps bridge <a href=\"https:\/\/monday.com\/lp\/world-of-work-report\">a common perception gap<\/a> where leaders often overestimate the sense of ownership their teams feel.<\/p>\n<h3>4. Shift from status to support<\/h3>\n<p>Replace &#8220;what&#8217;s your status?&#8221; with &#8220;what do you need help with?&#8221; to spark collaboration instead of reporting.<\/p>\n<h3>5. Resolve blockers with urgency<\/h3>\n<p>When an impediment comes up, assign responsibility and track it visibly until it&#8217;s closed. The scrum master should work on removing obstacles between meetings, not just collect them during meetings.<\/p>\n<h3>6. Use tools that lighten the load<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-tools\/\">Scrum tools<\/a> support teams that use the Scrum framework, and the right one cuts the administrative weight of running meetings. The monday AI Workspace uses automation to reduce manual updates, surface trends, and flag risks before they stall progress. Tools can also reduce the coordination work surrounding each ceremony. In monday AI Workspace, teams can automate recurring reminders and status updates, keep sprint information visible between meetings, and use AI capabilities to summarize discussions and turn meeting notes into trackable action items. That matters because <a href=\"https:\/\/www.microsoft.com\/en-us\/worklab\/work-trend-index\/breaking-down-infinite-workday\">Microsoft&#8217;s 2025 Work Trend Index found employees are interrupted every two minutes by a meeting, email, or notification<\/a>, so anything that removes routine status updates gives that time back to delivery.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-12\">\n<img width=\"1024\" height=\"663\" src=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-kanban-board-2.jpg\" class=\"attachment-large size-large\" alt=\"\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-kanban-board-2.jpg 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-kanban-board-2-300x194.jpg 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-kanban-board-2-768x497.jpg 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/>\n<\/div>\n<div class=\"text-block\" id=\"text-block-13\">\n<h3>7. Keep experimenting<\/h3>\n<p>Teams evolve, so adjust formats, timing, and facilitation styles based on what delivers the most value. A rotating standup facilitator, a themed retro, or a shorter review can all keep sessions fresh. Retrospectives are a good place to check whether your meetings still work, and to retire the habits that no longer do.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"3\">Get started with monday.com<\/a><\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-14\">\n<h2 class=\"h2 text-block__title\">Scrum meeting metrics to track<\/h2>\n<p>A handful of scrum metrics tell you whether your meetings are actually improving delivery. Scrum metrics can help teams understand whether their planning and delivery are becoming more predictable over time. They work best as signals for discussion rather than individual performance measures: a change in velocity, cycle time, or sprint goal success should prompt the team to investigate what changed and why.<\/p>\n<ul>\n<li><strong>Velocity:<\/strong> the amount of work completed per sprint, useful for forecasting realistic commitments<\/li>\n<li><strong>Burndown and burnup:<\/strong> remaining or completed work against time, which shows whether a sprint is on pace<\/li>\n<li><strong>Sprint goal success rate:<\/strong> how often the team meets its sprint goal, a signal of planning accuracy<\/li>\n<li><strong>Cycle and lead time:<\/strong> how long an item takes to move from start to done, or from backlog to completion<\/li>\n<li><strong>Defect rate:<\/strong> the number of bugs or reopened items, a check on quality alongside speed<\/li>\n<\/ul>\n<p>The point isn&#8217;t to chase numbers. Track a few <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-metrics\/\">scrum metrics<\/a> consistently, review them in retrospectives, and adjust. Say velocity dips two sprints in a row: that&#8217;s a prompt to ask why in the retro, not a reason to push the team harder. With the monday AI Workspace, dashboards surface velocity and burndown automatically, so the data is ready when you need it rather than compiled by hand the night before a review.<\/p>\n\n<img width=\"1024\" height=\"576\" src=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/06\/monday-dev-scrumban-performance-1024x576.png\" class=\"attachment-large size-large\" alt=\"Create custom dashboards and reports to get an overview of your Scrumban process, including sprint progress, team velocity, and bottlenecks.\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/06\/monday-dev-scrumban-performance-1024x576.png 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/06\/monday-dev-scrumban-performance-300x169.png 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/06\/monday-dev-scrumban-performance-768x432.png 768w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/06\/monday-dev-scrumban-performance-1536x864.png 1536w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2024\/06\/monday-dev-scrumban-performance-2048x1152.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/>\n<\/div>\n<div class=\"text-block\" id=\"text-block-15\">\n<h2 class=\"h2 text-block__title\">How monday AI Workspace supports scrum ceremonies<\/h2>\n<p class=\"PDq2pG_selectionAnchorContainer\" data-start=\"6399\" data-end=\"6671\">Scrum ceremonies depend on accurate, current information. Sprint priorities need to be visible during planning, blockers need to remain visible after the Daily Scrum, and retrospective actions need to carry into the next sprint rather than disappearing into meeting notes.<\/p>\n<p data-start=\"6676\" data-end=\"6945\"><strong data-start=\"6676\" data-end=\"6767\">monday AI Workspace brings that information and the workflows around it into one place.<\/strong> Teams can manage sprint boards and backlogs, automate recurring coordination, track capacity and risks, and use AI to summarize updates and turn discussions into follow-up work.<\/p>\n<p>The idea isn&#8217;t to add another tool on top of your meetings. It&#8217;s to remove the manual steps around them, so the meetings themselves get shorter and sharper. Here&#8217;s how the platform maps to each ceremony, framed as the outcome you get.<\/p>\n<ul>\n<li><strong>Planning with clarity:<\/strong> <a href=\"https:\/\/monday.com\/blog\/project-management\/task-boards\/\">sprint boards<\/a> with more than 15 views, including Kanban and Gantt, show capacity, backlog priorities, and sprint goals in one place<\/li>\n<li><strong>Daily updates that run themselves:<\/strong> automations and templates handle recurring ceremony reminders and status roll-ups, so progress is tracked as people work<\/li>\n<li><strong>Reviews with real evidence:<\/strong> integrations with Jira, Slack, and Microsoft Teams let you demo working features and route feedback straight into the backlog<\/li>\n<li><strong>Retrospectives that drive change:<\/strong> monday workdocs capture retro notes, and the Meeting Summarizer turns them into tracked action items you can carry across sprints<\/li>\n<li><strong>Risk and capacity visibility:<\/strong> the Workload view surfaces who&#8217;s overcommitted, and dashboards with 10-plus widgets flag risks before they stall a sprint<\/li>\n<\/ul>\n<p>AI is most useful around Scrum ceremonies when it reduces the work required to prepare for meetings, capture decisions, and follow up afterward.<\/p>\n<ul>\n<li><strong>Meetings that run themselves:<\/strong> the Research Assistant Digital Worker automates agile meetings, so recurring prep and follow-up happen without a person chasing them<\/li>\n<li><strong>Faster backlog triage:<\/strong> AI Blocks summarize and categorize backlog items, which cuts the time it takes to sort and prioritize incoming work before refinement<\/li>\n<li><strong>Custom tools in minutes:<\/strong> monday vibe lets you describe a sprint or OKR-monitoring app in plain language and build it, so you&#8217;re not stuck fitting your process into someone else&#8217;s template<\/li>\n<li><strong>Sprint status where you already work:<\/strong> monday MCP connects your workspace to AI tools like Claude and Cursor, so you can pull sprint status directly from the assistant your team already uses<\/li>\n<\/ul>\n<p>Because these capabilities sit on one connected platform, the context carries across meetings. A blocker raised in a standup, a decision captured in a review, and an action item from a retro all live in the same place, so nothing gets lost between meetings and your team keeps its momentum from one sprint to the next.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-16\">\n<img width=\"1024\" height=\"576\" src=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-integration-center-2.png\" class=\"attachment-large size-large\" alt=\"\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-integration-center-2.png 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-integration-center-2-300x169.png 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-integration-center-2-768x432.png 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/>\n<\/div>\n<div class=\"text-block\" id=\"text-block-17\">\n<p>To see the difference in practice, compare running meetings by hand with running them on the platform.<\/p>\n\n<table id=\"tablepress-3813\" class=\"tablepress tablepress-id-3813\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Scrum work<\/th><th class=\"column-2\">Manual scrum ceremonies<\/th><th class=\"column-3\">Scrum meetings on monday AI Workspace<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Sprint planning and backlog<\/td><td class=\"column-2\">Priorities live in spreadsheets and docs that fall out of date between sprints.<\/td><td class=\"column-3\">Sprint boards and Kanban or Gantt views keep capacity, priorities, and the sprint goal in one live place.<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Daily status<\/td><td class=\"column-2\">Each person reads a verbal update while the rest of the team waits.<\/td><td class=\"column-3\">Automations roll up status as work progresses, so standups focus on blockers.<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Sprint review evidence<\/td><td class=\"column-2\">Someone assembles screenshots and notes ahead of the demo.<\/td><td class=\"column-3\">Integrations pull completed work directly, and feedback flows back to the backlog.<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Retrospective follow-through<\/td><td class=\"column-2\">Action items sit in meeting notes and get forgotten by the next sprint.<\/td><td class=\"column-3\">The Meeting Summarizer turns retro notes into tracked action items across sprints.<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Risk and capacity visibility<\/td><td class=\"column-2\">Overload and slippage surface only when a deadline is already at risk.<\/td><td class=\"column-3\">Workload view and dashboards flag capacity issues and risks early.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-3813 from cache -->\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-18\">\n<h2 class=\"h2 text-block__title\">Make Scrum ceremonies useful, not routine<\/h2>\n<p class=\"PDq2pG_selectionAnchorContainer\" data-start=\"9739\" data-end=\"9950\">Scrum ceremonies earn their place on the calendar when each one produces something the team can use: a realistic Sprint Goal, an updated plan, stakeholder feedback, or a concrete improvement for the next Sprint.<\/p>\n<p data-start=\"9955\" data-end=\"10253\">The meeting itself is only part of that process. Teams also need a reliable way to keep priorities, blockers, decisions, and follow-up work visible between ceremonies. monday AI Workspace connects that information in one place while automations and AI reduce the manual coordination surrounding it.<\/p>\n<p data-start=\"10258\" data-end=\"10370\">The result is a Scrum cadence built around decisions and delivery rather than another recurring set of meetings.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"4\">Get started with monday.com<\/a><\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-19\">\n<div class=\"accordion faq\" id=\"faq-faqs\">\n  <h2 class=\"accordion__heading section-title text-left\">FAQs<\/h2>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-faqs\" href=\"#q-faqs-1\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What are the five scrum values?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-faqs-1\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-faqs\">\n      <p>The <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-values\/\">five values that guide Scrum teams<\/a> are commitment, focus, openness, respect, and courage. These principles shape how teams collaborate, make decisions, and hold each other accountable throughout the sprint cycle.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-faqs\" href=\"#q-faqs-2\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What is the difference between agile and scrum ceremonies?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-faqs-2\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-faqs\">\n      <p>Agile is a broad philosophy that you can apply through several frameworks, such as <a href=\"https:\/\/monday.com\/blog\/project-management\/kanban-methodology\/\">Kanban<\/a> or Extreme Programming. Scrum ceremonies are specific to the Scrum framework and follow defined roles, timeboxes, and structures.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-faqs\" href=\"#q-faqs-3\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">Who should attend sprint retrospective meetings?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-faqs-3\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-faqs\">\n      <p>Sprint retrospective meetings should include the entire scrum team: the product owner, scrum master, and all development team members. Stakeholders generally sit this one out so the team feels comfortable discussing what to improve.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-faqs\" href=\"#q-faqs-4\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">How does monday AI Workspace help teams run scrum ceremonies?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-faqs-4\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-faqs\">\n      <p>The monday AI Workspace gives teams sprint boards, automations for ceremony reminders and status roll-ups, and dashboards that surface velocity and burndown automatically. Its agents automate agile meetings and summarize standups and retros into action items, so teams spend less time on admin and more on delivery.<\/p>\n    <\/div>\n  <\/div>\n  {\n    \"@context\": \"https:\\\/\\\/schema.org\",\n    \"@type\": \"FAQPage\",\n    \"mainEntity\": [\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What are the five scrum values?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The <a href=\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/scrum-values\\\/\">five values that guide Scrum teams are commitment, focus, openness, respect, and courage. These principles shape how teams collaborate, make decisions, and hold each other accountable throughout the sprint cycle.\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What is the difference between agile and scrum ceremonies?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Agile is a broad philosophy that you can apply through several frameworks, such as <a href=\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/kanban-methodology\\\/\">Kanban or Extreme Programming. Scrum ceremonies are specific to the Scrum framework and follow defined roles, timeboxes, and structures.\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"Who should attend sprint retrospective meetings?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Sprint retrospective meetings should include the entire scrum team: the product owner, scrum master, and all development team members. Stakeholders generally sit this one out so the team feels comfortable discussing what to improve.\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"How does monday AI Workspace help teams run scrum ceremonies?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The monday AI Workspace gives teams sprint boards, automations for ceremony reminders and status roll-ups, and dashboards that surface velocity and burndown automatically. Its agents automate agile meetings and summarize standups and retros into action items, so teams spend less time on admin and more on delivery.\\n\"\n            }\n        }\n    ]\n}<\/div>\n\n\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Sadly, a Scrum ceremony isn\u2019t an ornate presentation that happens after a particularly effective headlock in the British sport of rugby. More\u2019s the pity. In all honesty, I think the word ceremony is over-egging slightly, whichever way you cut it. But, inflated titles aside, these \u2018ceremonies\u2019 are important for bringing &#8230;<\/p>\n","protected":false},"author":5,"featured_media":359965,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"pages\/cornerstone-primary.php","format":"standard","meta":{"_acf_changed":false,"monday_item_id":18009256321,"monday_board_id":0,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[13904],"tags":[14019],"class_list":["post-48918","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-project-management","tag-scrum-methodology"],"acf":{"lobby_image":false,"post_thumbnail_title":"","hide_post_info":false,"hide_bottom_cta":false,"hide_from_blog":false,"cluster":"","banner_url":"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_blank","main_text_banner":"One platform for a better product","sub_title_banner":"with monday dev","sub_title_banner_second":"","banner_button_text":"Try monday dev","below_banner_line":"","landing_page_layout":false,"display_dates":"default","use_customized_cta":false,"display_subscribe_widget":false,"custom_schema_code":"<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"DefinedTermSet\", \"name\": \"Scrum Ceremonies\", \"description\": \"Scrum ceremonies are recurring events that give teams a consistent rhythm for planning work, coordinating progress, reviewing outcomes, and improving how they work.\", \"hasDefinedTerm\": [{\"@type\": \"DefinedTerm\", \"name\": \"Sprint planning\", \"description\": \"Sprint planning sets the direction for the next sprint, which usually runs one to four weeks.\"}, {\"@type\": \"DefinedTerm\", \"name\": \"Daily scrum\", \"description\": \"The daily scrum is a 15-minute sync that keeps the team aligned.\"}, {\"@type\": \"DefinedTerm\", \"name\": \"Sprint review\", \"description\": \"The sprint review closes the sprint by sharing completed work and gathering feedback.\"}, {\"@type\": \"DefinedTerm\", \"name\": \"Sprint retrospective\", \"description\": \"This agile retrospective is your team\u2019s chance to reflect on how you work together.\"}, {\"@type\": \"DefinedTerm\", \"name\": \"Backlog refinement\", \"description\": \"Backlog refinement, also called backlog grooming, keeps upcoming work clear and ready.\"}]}<\/script>","sidebar_color_banner":"","custom_tags":[14019],"featured_image_link":"","faqs":[{"faq_title":"FAQs","faq_shortcode":"faqs","faq":[{"question":"What are the five scrum values?","answer":"<p>The <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-values\/\">five values that guide Scrum teams<\/a> are commitment, focus, openness, respect, and courage. These principles shape how teams collaborate, make decisions, and hold each other accountable throughout the sprint cycle.<\/p>\n"},{"question":"What is the difference between agile and scrum ceremonies?","answer":"<p>Agile is a broad philosophy that you can apply through several frameworks, such as <a href=\"https:\/\/monday.com\/blog\/project-management\/kanban-methodology\/\">Kanban<\/a> or Extreme Programming. Scrum ceremonies are specific to the Scrum framework and follow defined roles, timeboxes, and structures.<\/p>\n"},{"question":"Who should attend sprint retrospective meetings?","answer":"<p>Sprint retrospective meetings should include the entire scrum team: the product owner, scrum master, and all development team members. Stakeholders generally sit this one out so the team feels comfortable discussing what to improve.<\/p>\n"},{"question":"How does monday AI Workspace help teams run scrum ceremonies?","answer":"<p>The monday AI Workspace gives teams sprint boards, automations for ceremony reminders and status roll-ups, and dashboards that surface velocity and burndown automatically. Its agents automate agile meetings and summarize standups and retros into action items, so teams spend less time on admin and more on delivery.<\/p>\n"}]}],"activate_cta_banner":false,"hide_time_to_read":false,"cornerstone_hero_cta_override":{"label":"Try monday dev","url":"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_blank\u201d"},"sections":[{"acf_fc_layout":"content_1","blocks":[{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<p>Most delivery teams don&#8217;t struggle because they meet too little. They struggle because their meetings turn into status theater, where people take turns reading updates that could&#8217;ve been a message, and the real blockers never surface. Scrum ceremonies are meant to fix exactly that, but only when you run them with intent.<\/p>\n<p>Scrum ceremonies are structured events that create alignment, clarity, and continuous improvement for teams working in sprints. By establishing a predictable cadence, these events help teams deliver value faster while keeping focus on business goals and preventing wasted effort.<\/p>\n<p>In this guide, you&#8217;ll learn what each one is for, who should attend, how long each one should run, and practical tips to make them more effective. You&#8217;ll also see how the monday AI Workspace can automate routine updates and visualize progress, so your team spends its time on collaboration instead of admin.<\/p>\n"}]},{"main_heading":"Key takeaways","content_block":[{"acf_fc_layout":"text","content":"<ul>\n<li><strong>A clear cadence drives delivery<\/strong>: sprint planning, daily scrums, sprint reviews, retrospectives, and backlog refinement work together to plan, coordinate, and improve<\/li>\n<li><strong>Timebox every ceremony<\/strong>: 15 minutes for daily scrums, and about two hours per week of sprint for planning, review, and retrospective<\/li>\n<li><strong>Prioritize problem-solving over status<\/strong>: ask &#8220;what help do you need?&#8221; and push routine updates to async channels<\/li>\n<li><strong>Invite the right people<\/strong>: product owner for priorities, scrum master for facilitation, developers for daily coordination, and stakeholders for the sprint review only<\/li>\n<li><strong>Use the monday AI Workspace to reduce admin<\/strong>: automate routine updates, summarize meetings into action items, and visualize capacity so teams focus on collaboration<\/li>\n<\/ul>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"1\">Get started with monday.com<\/a><\/p>\n"}]},{"main_heading":"What are scrum ceremonies?","content_block":[{"acf_fc_layout":"text","content":"<p>Scrum ceremonies are recurring events that give teams a consistent rhythm for planning work, coordinating progress, reviewing outcomes, and improving how they work. In the official Scrum framework, the Sprint acts as the container for four formal events: Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective.<\/p>\n<p>Backlog refinement isn&#8217;t a formal Scrum event, but most Scrum teams treat it as an essential recurring activity because it keeps upcoming work clear, prioritized, and ready for future sprints. For that reason, it&#8217;s commonly discussed alongside the four Scrum ceremonies \u2014 and we&#8217;ll cover all five activities in this guide.<\/p>\n<p>Compared with a typical project status meeting, the difference is intent. A status meeting usually exists to report upward, while scrum ceremonies exist to move work forward for the team itself. Each ceremony has a fixed purpose and a firm timebox, so people know exactly why they&#8217;re there and when they&#8217;ll be done. In a two-week Sprint, for example, the team plans at the beginning, coordinates daily, reviews the completed work with stakeholders near the end, and reflects on how to improve before the next Sprint begins.<\/p>\n<p>Here&#8217;s how the five events fit together. Each one has a distinct purpose, so read the short label first and the explanation second.<\/p>\n<ul>\n<li><strong>Sprint planning:<\/strong> set the <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-sprint\/\">scrum sprint<\/a> goal and commit to a realistic <a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-backlog\/\">sprint backlog<\/a><\/li>\n<li><strong>Daily scrum:<\/strong> a 15-minute sync to align, surface blockers, and adjust the day&#8217;s plan<\/li>\n<li><strong>Sprint review:<\/strong> demo working software and gather stakeholder feedback to inform the backlog<\/li>\n<li><strong>Sprint retrospective:<\/strong> reflect on the process and agree on a few concrete improvements<\/li>\n<li><strong>Backlog refinement:<\/strong> continuously clarify, size, and prioritize upcoming work so planning runs smoothly<\/li>\n<\/ul>\n<p>Three terms show up across all of these meeting types, and it helps to define them plainly before you go further.<\/p>\n<ul>\n<li><strong>Sprint:<\/strong> a fixed period, typically one to four weeks, to deliver a defined slice of value<\/li>\n<li><strong>Product backlog:<\/strong> the prioritized list of features, enhancements, and fixes for the product<\/li>\n<li><strong>Sprint backlog:<\/strong> the subset the team commits to for the current sprint, aligned to the sprint goal<\/li>\n<\/ul>\n"}]},{"main_heading":"The five Scrum ceremonies and activities teams use each sprint","content_block":[{"acf_fc_layout":"text","content":"<p>Scrum gives each formal event a distinct purpose, set of participants, and timebox. Backlog refinement sits outside the official event structure, but it plays an important supporting role by preparing work for future sprints. Together, these activities create a repeatable cycle for deciding what to build, coordinating delivery, gathering feedback, and improving the team&#8217;s process.<\/p>\n<p>It also helps to remember that the sprint itself is the container event. It holds the other four meetings inside a fixed time-box, which is why scrum events always run in the same order within each cycle. Read the five that follow as one connected system: planning sets the goal, the daily scrum keeps it on track, the review tests it against real feedback, the retrospective improves how you got there, and refinement readies the next round.<\/p>\n"}]},{"main_heading":"","content_block":[{"acf_fc_layout":"image","image_type":"normal","image":358105,"image_link":""}]},{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<h3>1. Sprint planning<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-planning\/\">Sprint planning<\/a> sets the direction for the next sprint, which usually runs one to four weeks.<\/p>\n<ul>\n<li><strong data-start=\"3437\" data-end=\"3453\">Who attends:<\/strong> Developers; the Product Owner or Scrum Master participates when actively working on Sprint Backlog items<\/li>\n<li><strong data-start=\"3563\" data-end=\"3574\">Agenda:<\/strong> Inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed<\/li>\n<li><strong data-start=\"3658\" data-end=\"3671\">Duration:<\/strong> 15 minutes<\/li>\n<\/ul>\n<p>Teams can use the familiar yesterday\/today\/blockers format if it helps, but the goal isn&#8217;t to collect individual status reports. The Daily Scrum should help Developers decide how to adjust their plan and make progress toward the Sprint Goal.<\/p>\n<h3>2. Daily scrum standup<\/h3>\n<p>The daily scrum is a 15-minute sync that keeps the team aligned.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> the development team, with others free to observe<\/li>\n<li><strong>Agenda:<\/strong> each person answers what they completed yesterday, what they&#8217;ll work on today, and what&#8217;s blocking progress<\/li>\n<\/ul>\n<p>Keep the focus on coordination. Problem-solving happens afterward with only the people involved.<\/p>\n<h3>3. Sprint review<\/h3>\n<p>The <a href=\"https:\/\/monday.com\/blog\/rnd\/what-is-a-sprint-review-definition-goals-and-tips\/\">sprint review<\/a> closes the sprint by sharing completed work and gathering feedback.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> the <a href=\"https:\/\/monday.com\/blog\/rnd\/heres-how-you-build-a-successful-scrum-team\/\">scrum team<\/a> and stakeholders<\/li>\n<li><strong>Agenda:<\/strong> demonstrate working software, discuss what the team learned, and adjust the backlog<\/li>\n<li><strong>Duration:<\/strong> up to two hours for a two-week sprint<\/li>\n<\/ul>\n<p>Think of this as a collaborative session, not a presentation. The goal is meaningful dialogue about what to build next.<\/p>\n<h3>4. Sprint retrospective<\/h3>\n<p>This <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-retrospective-what-it-is-and-how-it-works\/\">agile retrospective<\/a> is your team&#8217;s chance to reflect on how you work together.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> the entire scrum team<\/li>\n<li><strong>Agenda:<\/strong> what went well, what needs improvement, and what you&#8217;ll try next sprint<\/li>\n<li><strong>Duration:<\/strong> about 1.5 hours for a two-week sprint<\/li>\n<\/ul>\n<p>The scrum master facilitates and keeps the conversation open. With the monday AI Workspace, teams can track retrospective action items across <a href=\"https:\/\/monday.com\/blog\/rnd\/how-to-get-the-most-out-of-your-scrum-artifacts\/\">scrum sprints<\/a> and measure which changes actually stick.<\/p>\n<h3>5. Backlog refinement<\/h3>\n<p>Backlog refinement, also called <a href=\"https:\/\/monday.com\/blog\/rnd\/backlog-grooming\/\">backlog grooming<\/a>, keeps upcoming work clear and ready.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> the product owner and development team<\/li>\n<li><strong>Agenda:<\/strong> clarify requirements, size effort, and break down large items<\/li>\n<li><strong>Duration:<\/strong> one to two hours per week<\/li>\n<\/ul>\n<p>A well-refined backlog makes sprint planning faster and commitments more reliable.<\/p>\n"}]},{"main_heading":"Who participates in scrum ceremonies?","content_block":[{"acf_fc_layout":"text","content":"<p>Each scrum role brings specific value to the events. Having the right people in the room keeps agile scrum ceremonies purposeful and outcomes clear, so it&#8217;s worth being deliberate about who joins each one.<\/p>\n<ul>\n<li><strong>Product owner:<\/strong> owns the product vision and backlog. They <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-guide\/\">guide priorities<\/a> during sprint planning, adjust the backlog after sprint reviews, and prepare upcoming work during refinement<\/li>\n<li><strong>Scrum master:<\/strong> facilitates meetings, removes blockers, and keeps the team aligned with Scrum principles. Their job is to keep meetings on track and create a safe space for open contribution<\/li>\n<li><strong>Development team:<\/strong> builds the product. They run daily scrums, estimate and commit during planning, demo completed work in reviews, and suggest improvements in retrospectives<\/li>\n<li><strong>Stakeholders:<\/strong> join sprint reviews to give feedback and align direction with business goals. They step back from other meetings to keep the team focused<\/li>\n<\/ul>\n<p>A useful rule of thumb: if someone isn&#8217;t contributing to or acting on the outcome of a ceremony, they probably don&#8217;t need to be in it. Guarding attendance this way keeps sessions short and focused, and it respects everyone&#8217;s time.<\/p>\n<p>For larger organizations, a <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-of-scrums\/\">scrum of scrums<\/a> coordinates work across multiple teams to keep everyone aligned at scale. With the monday AI Workspace, leaders get portfolio-level visibility across those teams without disrupting daily execution.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"2\">Get started with monday.com<\/a><\/p>\n"}]},{"main_heading":"How to structure each scrum meeting","content_block":[{"acf_fc_layout":"text","content":"<p>Even well-intentioned <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-ceremonies\/\">agile meetings<\/a> can drift off course without clear guardrails. Setting expectations for time, agenda, and format helps teams get the most out of every session, and it gives you a repeatable scrum meeting structure to reuse each sprint.<\/p>\n"}]},{"main_heading":"","content_block":[{"acf_fc_layout":"image","image_type":"normal","image":358113,"image_link":""}]},{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<h3>Duration and timeboxing<\/h3>\n<p>Each ceremony has a recommended length, and sticking to those limits keeps energy high and focus sharp. How long should sprint planning take? Sprint planning is timeboxed to about two hours per week of sprint, so a two-week sprint runs around four hours, and the meeting ends as soon as the team agrees on a goal and backlog. For a two-week sprint, plan on about:<\/p>\n<ul>\n<li><strong>Sprint planning:<\/strong> four hours<\/li>\n<li><strong>Daily scrum:<\/strong> 15 minutes<\/li>\n<li><strong>Sprint review:<\/strong> two hours<\/li>\n<li><strong>Sprint retrospective:<\/strong> 1.5 hours<\/li>\n<\/ul>\n<p>Teams working in longer or shorter sprints can adjust, but the principle holds: use timeboxes to respect people&#8217;s attention.<\/p>\n<h3>Agenda and format<\/h3>\n<p>A predictable agenda for scrum ceremonies makes it easier for participants to contribute meaningfully. Here&#8217;s the format each ceremony tends to follow.<\/p>\n<ul>\n<li><strong>Sprint planning:<\/strong> starts with the goal, then moves to backlog selection, task breakdown, and commitment<\/li>\n<li><strong data-start=\"4142\" data-end=\"4159\">fDaily Scrums:<\/strong> inspect progress toward the Sprint Goal, surface anything affecting the plan, and adjust the Sprint Backlog for the next day of work<\/li>\n<li><strong>Sprint reviews:<\/strong> begin with working software and end with stakeholder discussion<\/li>\n<li><strong>Retrospectives:<\/strong> often use &#8220;start, stop, continue&#8221; or a similar technique to surface insights<\/li>\n<\/ul>\n<h3>Supporting remote or hybrid teams<\/h3>\n<p>Distributed work doesn&#8217;t change the meetings; it changes how you run them. Reliable video, clear audio, and collaborative boards make remote participation seamless.<\/p>\n<p>Scheduling with time zones in mind matters, and engagement tools like polls or breakout rooms help keep energy up. For distributed teams, lean on async where you can: a written standup update posted before the sync lets the live time go to blockers and decisions instead of round-robin reporting. The monday AI Workspace provides shared sprint boards, asynchronous updates, and real-time visibility, so distributed teams stay aligned without losing momentum.<\/p>\n"}]},{"main_heading":"Seven tips for running effective scrum ceremonies","content_block":[{"acf_fc_layout":"text","content":"<p>Scrum meetings work best when teams apply a few practical habits. These tips help each session feel valuable rather than routine.<\/p>\n<h3>1. Set expectations early<\/h3>\n<p>Share the purpose and prep work before each ceremony. When people know what to bring and what a good outcome looks like, they arrive ready, and the discussion moves faster. A one-line agenda pinned to the invite is often enough.<\/p>\n<h3>2. Respect the clock<\/h3>\n<p>Stay within the timebox. If a topic needs more time than the ceremony allows, capture it in a parking lot and schedule a focused follow-up with only the people involved, instead of letting it derail the session for everyone.<\/p>\n<h3>3. Encourage team ownership<\/h3>\n<p>Daily scrums belong to developers, not managers, and retrospectives only work if everyone feels safe to contribute. This helps bridge <a href=\"https:\/\/monday.com\/lp\/world-of-work-report\">a common perception gap<\/a> where leaders often overestimate the sense of ownership their teams feel.<\/p>\n<h3>4. Shift from status to support<\/h3>\n<p>Replace &#8220;what&#8217;s your status?&#8221; with &#8220;what do you need help with?&#8221; to spark collaboration instead of reporting.<\/p>\n<h3>5. Resolve blockers with urgency<\/h3>\n<p>When an impediment comes up, assign responsibility and track it visibly until it&#8217;s closed. The scrum master should work on removing obstacles between meetings, not just collect them during meetings.<\/p>\n<h3>6. Use tools that lighten the load<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-tools\/\">Scrum tools<\/a> support teams that use the Scrum framework, and the right one cuts the administrative weight of running meetings. The monday AI Workspace uses automation to reduce manual updates, surface trends, and flag risks before they stall progress. Tools can also reduce the coordination work surrounding each ceremony. In monday AI Workspace, teams can automate recurring reminders and status updates, keep sprint information visible between meetings, and use AI capabilities to summarize discussions and turn meeting notes into trackable action items. That matters because <a href=\"https:\/\/www.microsoft.com\/en-us\/worklab\/work-trend-index\/breaking-down-infinite-workday\">Microsoft&#8217;s 2025 Work Trend Index found employees are interrupted every two minutes by a meeting, email, or notification<\/a>, so anything that removes routine status updates gives that time back to delivery.<\/p>\n"}]},{"main_heading":"","content_block":[{"acf_fc_layout":"image","image_type":"normal","image":358121,"image_link":""}]},{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<h3>7. Keep experimenting<\/h3>\n<p>Teams evolve, so adjust formats, timing, and facilitation styles based on what delivers the most value. A rotating standup facilitator, a themed retro, or a shorter review can all keep sessions fresh. Retrospectives are a good place to check whether your meetings still work, and to retire the habits that no longer do.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"3\">Get started with monday.com<\/a><\/p>\n"}]},{"main_heading":"Scrum meeting metrics to track","content_block":[{"acf_fc_layout":"text","content":"<p>A handful of scrum metrics tell you whether your meetings are actually improving delivery. Scrum metrics can help teams understand whether their planning and delivery are becoming more predictable over time. They work best as signals for discussion rather than individual performance measures: a change in velocity, cycle time, or sprint goal success should prompt the team to investigate what changed and why.<\/p>\n<ul>\n<li><strong>Velocity:<\/strong> the amount of work completed per sprint, useful for forecasting realistic commitments<\/li>\n<li><strong>Burndown and burnup:<\/strong> remaining or completed work against time, which shows whether a sprint is on pace<\/li>\n<li><strong>Sprint goal success rate:<\/strong> how often the team meets its sprint goal, a signal of planning accuracy<\/li>\n<li><strong>Cycle and lead time:<\/strong> how long an item takes to move from start to done, or from backlog to completion<\/li>\n<li><strong>Defect rate:<\/strong> the number of bugs or reopened items, a check on quality alongside speed<\/li>\n<\/ul>\n<p>The point isn&#8217;t to chase numbers. Track a few <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-metrics\/\">scrum metrics<\/a> consistently, review them in retrospectives, and adjust. Say velocity dips two sprints in a row: that&#8217;s a prompt to ask why in the retro, not a reason to push the team harder. With the monday AI Workspace, dashboards surface velocity and burndown automatically, so the data is ready when you need it rather than compiled by hand the night before a review.<\/p>\n"},{"acf_fc_layout":"image","image_type":"normal","image":158635,"image_link":""}]},{"main_heading":"How monday AI Workspace supports scrum ceremonies","content_block":[{"acf_fc_layout":"text","content":"<p class=\"PDq2pG_selectionAnchorContainer\" data-start=\"6399\" data-end=\"6671\">Scrum ceremonies depend on accurate, current information. Sprint priorities need to be visible during planning, blockers need to remain visible after the Daily Scrum, and retrospective actions need to carry into the next sprint rather than disappearing into meeting notes.<\/p>\n<p data-start=\"6676\" data-end=\"6945\"><strong data-start=\"6676\" data-end=\"6767\">monday AI Workspace brings that information and the workflows around it into one place.<\/strong> Teams can manage sprint boards and backlogs, automate recurring coordination, track capacity and risks, and use AI to summarize updates and turn discussions into follow-up work.<\/p>\n<p>The idea isn&#8217;t to add another tool on top of your meetings. It&#8217;s to remove the manual steps around them, so the meetings themselves get shorter and sharper. Here&#8217;s how the platform maps to each ceremony, framed as the outcome you get.<\/p>\n<ul>\n<li><strong>Planning with clarity:<\/strong> <a href=\"https:\/\/monday.com\/blog\/project-management\/task-boards\/\">sprint boards<\/a> with more than 15 views, including Kanban and Gantt, show capacity, backlog priorities, and sprint goals in one place<\/li>\n<li><strong>Daily updates that run themselves:<\/strong> automations and templates handle recurring ceremony reminders and status roll-ups, so progress is tracked as people work<\/li>\n<li><strong>Reviews with real evidence:<\/strong> integrations with Jira, Slack, and Microsoft Teams let you demo working features and route feedback straight into the backlog<\/li>\n<li><strong>Retrospectives that drive change:<\/strong> monday workdocs capture retro notes, and the Meeting Summarizer turns them into tracked action items you can carry across sprints<\/li>\n<li><strong>Risk and capacity visibility:<\/strong> the Workload view surfaces who&#8217;s overcommitted, and dashboards with 10-plus widgets flag risks before they stall a sprint<\/li>\n<\/ul>\n<p>AI is most useful around Scrum ceremonies when it reduces the work required to prepare for meetings, capture decisions, and follow up afterward.<\/p>\n<ul>\n<li><strong>Meetings that run themselves:<\/strong> the Research Assistant Digital Worker automates agile meetings, so recurring prep and follow-up happen without a person chasing them<\/li>\n<li><strong>Faster backlog triage:<\/strong> AI Blocks summarize and categorize backlog items, which cuts the time it takes to sort and prioritize incoming work before refinement<\/li>\n<li><strong>Custom tools in minutes:<\/strong> monday vibe lets you describe a sprint or OKR-monitoring app in plain language and build it, so you&#8217;re not stuck fitting your process into someone else&#8217;s template<\/li>\n<li><strong>Sprint status where you already work:<\/strong> monday MCP connects your workspace to AI tools like Claude and Cursor, so you can pull sprint status directly from the assistant your team already uses<\/li>\n<\/ul>\n<p>Because these capabilities sit on one connected platform, the context carries across meetings. A blocker raised in a standup, a decision captured in a review, and an action item from a retro all live in the same place, so nothing gets lost between meetings and your team keeps its momentum from one sprint to the next.<\/p>\n"}]},{"main_heading":"","content_block":[{"acf_fc_layout":"image","image_type":"normal","image":358129,"image_link":""}]},{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<p>To see the difference in practice, compare running meetings by hand with running them on the platform.<\/p>\n\n<table id=\"tablepress-3813\" class=\"tablepress tablepress-id-3813\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Scrum work<\/th><th class=\"column-2\">Manual scrum ceremonies<\/th><th class=\"column-3\">Scrum meetings on monday AI Workspace<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Sprint planning and backlog<\/td><td class=\"column-2\">Priorities live in spreadsheets and docs that fall out of date between sprints.<\/td><td class=\"column-3\">Sprint boards and Kanban or Gantt views keep capacity, priorities, and the sprint goal in one live place.<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Daily status<\/td><td class=\"column-2\">Each person reads a verbal update while the rest of the team waits.<\/td><td class=\"column-3\">Automations roll up status as work progresses, so standups focus on blockers.<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Sprint review evidence<\/td><td class=\"column-2\">Someone assembles screenshots and notes ahead of the demo.<\/td><td class=\"column-3\">Integrations pull completed work directly, and feedback flows back to the backlog.<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Retrospective follow-through<\/td><td class=\"column-2\">Action items sit in meeting notes and get forgotten by the next sprint.<\/td><td class=\"column-3\">The Meeting Summarizer turns retro notes into tracked action items across sprints.<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Risk and capacity visibility<\/td><td class=\"column-2\">Overload and slippage surface only when a deadline is already at risk.<\/td><td class=\"column-3\">Workload view and dashboards flag capacity issues and risks early.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-3813 from cache -->\n"}]},{"main_heading":"Make Scrum ceremonies useful, not routine","content_block":[{"acf_fc_layout":"text","content":"<p class=\"PDq2pG_selectionAnchorContainer\" data-start=\"9739\" data-end=\"9950\">Scrum ceremonies earn their place on the calendar when each one produces something the team can use: a realistic Sprint Goal, an updated plan, stakeholder feedback, or a concrete improvement for the next Sprint.<\/p>\n<p data-start=\"9955\" data-end=\"10253\">The meeting itself is only part of that process. Teams also need a reliable way to keep priorities, blockers, decisions, and follow-up work visible between ceremonies. monday AI Workspace connects that information in one place while automations and AI reduce the manual coordination surrounding it.<\/p>\n<p data-start=\"10258\" data-end=\"10370\">The result is a Scrum cadence built around decisions and delivery rather than another recurring set of meetings.<\/p>\n<p><a class=\"cta-button blue-button\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\" rel=\"noopener\" aria-label=\"Get started with monday.com\" data-index=\"4\">Get started with monday.com<\/a><\/p>\n"}]},{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<div class=\"accordion faq\" id=\"faq-faqs\">\n  <h2 class=\"accordion__heading section-title text-left\">FAQs<\/h2>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-faqs\" href=\"#q-faqs-1\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What are the five scrum values?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-faqs-1\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-faqs\">\n      <p>The <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-values\/\">five values that guide Scrum teams<\/a> are commitment, focus, openness, respect, and courage. These principles shape how teams collaborate, make decisions, and hold each other accountable throughout the sprint cycle.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-faqs\" href=\"#q-faqs-2\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What is the difference between agile and scrum ceremonies?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-faqs-2\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-faqs\">\n      <p>Agile is a broad philosophy that you can apply through several frameworks, such as <a href=\"https:\/\/monday.com\/blog\/project-management\/kanban-methodology\/\">Kanban<\/a> or Extreme Programming. Scrum ceremonies are specific to the Scrum framework and follow defined roles, timeboxes, and structures.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-faqs\" href=\"#q-faqs-3\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">Who should attend sprint retrospective meetings?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-faqs-3\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-faqs\">\n      <p>Sprint retrospective meetings should include the entire scrum team: the product owner, scrum master, and all development team members. Stakeholders generally sit this one out so the team feels comfortable discussing what to improve.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-faqs\" href=\"#q-faqs-4\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">How does monday AI Workspace help teams run scrum ceremonies?        <svg class=\"angle-arrow angle-arrow--down\" width=\"32\" height=\"32\" viewBox=\"0 0 32 32\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n          <path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M16.5303 20.8839C16.2374 21.1768 15.7626 21.1768 15.4697 20.8839L7.82318 13.2374C7.53029 12.9445 7.53029 12.4697 7.82318 12.1768L8.17674 11.8232C8.46963 11.5303 8.9445 11.5303 9.2374 11.8232L16 18.5858L22.7626 11.8232C23.0555 11.5303 23.5303 11.5303 23.8232 11.8232L24.1768 12.1768C24.4697 12.4697 24.4697 12.9445 24.1768 13.2374L16.5303 20.8839Z\" fill=\"black\"\/>\n        <\/svg>\n      <\/h3>\n    <\/a>\n    <div id=\"q-faqs-4\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-faqs\">\n      <p>The monday AI Workspace gives teams sprint boards, automations for ceremony reminders and status roll-ups, and dashboards that surface velocity and burndown automatically. Its agents automate agile meetings and summarize standups and retros into action items, so teams spend less time on admin and more on delivery.<\/p>\n    <\/div>\n  <\/div>\n  <script type='application\/ld+json'>{\n    \"@context\": \"https:\\\/\\\/schema.org\",\n    \"@type\": \"FAQPage\",\n    \"mainEntity\": [\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What are the five scrum values?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The <a href=\\\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/scrum-values\\\/\\\">five values that guide Scrum teams<\\\/a> are commitment, focus, openness, respect, and courage. These principles shape how teams collaborate, make decisions, and hold each other accountable throughout the sprint cycle.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What is the difference between agile and scrum ceremonies?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Agile is a broad philosophy that you can apply through several frameworks, such as <a href=\\\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/kanban-methodology\\\/\\\">Kanban<\\\/a> or Extreme Programming. Scrum ceremonies are specific to the Scrum framework and follow defined roles, timeboxes, and structures.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"Who should attend sprint retrospective meetings?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Sprint retrospective meetings should include the entire scrum team: the product owner, scrum master, and all development team members. Stakeholders generally sit this one out so the team feels comfortable discussing what to improve.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"How does monday AI Workspace help teams run scrum ceremonies?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The monday AI Workspace gives teams sprint boards, automations for ceremony reminders and status roll-ups, and dashboards that surface velocity and burndown automatically. Its agents automate agile meetings and summarize standups and retros into action items, so teams spend less time on admin and more on delivery.<\\\/p>\\n\"\n            }\n        }\n    ]\n}<\/script><\/div>\n\n"}]}]}],"parse_from_google_doc":false,"show_sidebar_sticky_banner":false,"disclaimer":"","menu_cta_override":{"label":"","url":""},"show_contact_sales_button":"default","override_contact_sales_label":"","override_contact_sales_url":"","custom_header_banner":false},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.6 (Yoast SEO v28.0) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Scrum ceremonies: 5 types, tips, and examples [2026]<\/title>\n<meta name=\"description\" content=\"Learn how to run effective Scrum ceremonies, from sprint planning and daily Scrums to reviews and retrospectives, with practical tips for every meeting.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"5 Types of Scrum Ceremonies &amp; How to Run Them Effectively in 2026\" \/>\n<meta property=\"og:description\" content=\"Learn how to run effective Scrum ceremonies, from sprint planning and daily Scrums to reviews and retrospectives, with practical tips for every meeting.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/\" \/>\n<meta property=\"og:site_name\" content=\"monday.com Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-04-06T13:20:46+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-30T09:45:09+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting_s2_2026-08-02T13-00-22.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1344\" \/>\n\t<meta property=\"og:image:height\" content=\"768\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"monday.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"monday.com\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/\"},\"author\":{\"name\":\"monday.com\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/person\\\/002eeffbafc08d763cb24e64dd45cae4\"},\"headline\":\"5 Types of Scrum Ceremonies &#038; How to Run Them Effectively in 2026\",\"datePublished\":\"2021-04-06T13:20:46+00:00\",\"dateModified\":\"2026-08-30T09:45:09+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/\"},\"wordCount\":1882,\"publisher\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/scrum-meeting_s2_2026-08-02T13-00-22.png\",\"keywords\":[\"Scrum methodology\"],\"articleSection\":[\"Project management\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/\",\"name\":\"Scrum ceremonies: 5 types, tips, and examples [2026]\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/scrum-meeting_s2_2026-08-02T13-00-22.png\",\"datePublished\":\"2021-04-06T13:20:46+00:00\",\"dateModified\":\"2026-08-30T09:45:09+00:00\",\"description\":\"Learn how to run effective Scrum ceremonies, from sprint planning and daily Scrums to reviews and retrospectives, with practical tips for every meeting.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/#primaryimage\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/scrum-meeting_s2_2026-08-02T13-00-22.png\",\"contentUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/scrum-meeting_s2_2026-08-02T13-00-22.png\",\"width\":1344,\"height\":768,\"caption\":\"5 Types of Scrum Ceremonies 038 How to Run Them Effectively in 2026\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-ceremonies\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/monday.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Project management\",\"item\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"5 Types of Scrum Ceremonies &#038; How to Run Them Effectively in 2026\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/\",\"name\":\"monday.com Blog\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/monday.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#organization\",\"name\":\"monday.com Blog\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/res.cloudinary.com\\\/monday-blogs\\\/fl_lossy,f_auto,q_auto\\\/wp-blog\\\/2020\\\/12\\\/monday.com-logo-1.png\",\"contentUrl\":\"https:\\\/\\\/res.cloudinary.com\\\/monday-blogs\\\/fl_lossy,f_auto,q_auto\\\/wp-blog\\\/2020\\\/12\\\/monday.com-logo-1.png\",\"width\":200,\"height\":200,\"caption\":\"monday.com Blog\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/person\\\/002eeffbafc08d763cb24e64dd45cae4\",\"name\":\"monday.com\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/monday.com-logo-1-150x150.png\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/monday.com-logo-1-150x150.png\",\"contentUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/monday.com-logo-1-150x150.png\",\"caption\":\"monday.com\"},\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/author\\\/the-monday-com-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Scrum ceremonies: 5 types, tips, and examples [2026]","description":"Learn how to run effective Scrum ceremonies, from sprint planning and daily Scrums to reviews and retrospectives, with practical tips for every meeting.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/","og_locale":"en_US","og_type":"article","og_title":"5 Types of Scrum Ceremonies & How to Run Them Effectively in 2026","og_description":"Learn how to run effective Scrum ceremonies, from sprint planning and daily Scrums to reviews and retrospectives, with practical tips for every meeting.","og_url":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/","og_site_name":"monday.com Blog","article_published_time":"2021-04-06T13:20:46+00:00","article_modified_time":"2026-08-30T09:45:09+00:00","og_image":[{"width":1344,"height":768,"url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting_s2_2026-08-02T13-00-22.png","type":"image\/png"}],"author":"monday.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"monday.com","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/#article","isPartOf":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/"},"author":{"name":"monday.com","@id":"https:\/\/monday.com\/blog\/#\/schema\/person\/002eeffbafc08d763cb24e64dd45cae4"},"headline":"5 Types of Scrum Ceremonies &#038; How to Run Them Effectively in 2026","datePublished":"2021-04-06T13:20:46+00:00","dateModified":"2026-08-30T09:45:09+00:00","mainEntityOfPage":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/"},"wordCount":1882,"publisher":{"@id":"https:\/\/monday.com\/blog\/#organization"},"image":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting_s2_2026-08-02T13-00-22.png","keywords":["Scrum methodology"],"articleSection":["Project management"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/","url":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/","name":"Scrum ceremonies: 5 types, tips, and examples [2026]","isPartOf":{"@id":"https:\/\/monday.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/#primaryimage"},"image":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting_s2_2026-08-02T13-00-22.png","datePublished":"2021-04-06T13:20:46+00:00","dateModified":"2026-08-30T09:45:09+00:00","description":"Learn how to run effective Scrum ceremonies, from sprint planning and daily Scrums to reviews and retrospectives, with practical tips for every meeting.","breadcrumb":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/#primaryimage","url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting_s2_2026-08-02T13-00-22.png","contentUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting_s2_2026-08-02T13-00-22.png","width":1344,"height":768,"caption":"5 Types of Scrum Ceremonies 038 How to Run Them Effectively in 2026"},{"@type":"BreadcrumbList","@id":"https:\/\/monday.com\/blog\/project-management\/scrum-ceremonies\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/monday.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Project management","item":"https:\/\/monday.com\/blog\/project-management\/"},{"@type":"ListItem","position":3,"name":"5 Types of Scrum Ceremonies &#038; How to Run Them Effectively in 2026"}]},{"@type":"WebSite","@id":"https:\/\/monday.com\/blog\/#website","url":"https:\/\/monday.com\/blog\/","name":"monday.com Blog","description":"","publisher":{"@id":"https:\/\/monday.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/monday.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/monday.com\/blog\/#organization","name":"monday.com Blog","url":"https:\/\/monday.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/res.cloudinary.com\/monday-blogs\/fl_lossy,f_auto,q_auto\/wp-blog\/2020\/12\/monday.com-logo-1.png","contentUrl":"https:\/\/res.cloudinary.com\/monday-blogs\/fl_lossy,f_auto,q_auto\/wp-blog\/2020\/12\/monday.com-logo-1.png","width":200,"height":200,"caption":"monday.com Blog"},"image":{"@id":"https:\/\/monday.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/monday.com\/blog\/#\/schema\/person\/002eeffbafc08d763cb24e64dd45cae4","name":"monday.com","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2020\/12\/monday.com-logo-1-150x150.png","url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2020\/12\/monday.com-logo-1-150x150.png","contentUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2020\/12\/monday.com-logo-1-150x150.png","caption":"monday.com"},"url":"https:\/\/monday.com\/blog\/author\/the-monday-com-team\/"}]}},"auth_debug":{"user_exists":false,"user_id":0,"user_login":null,"roles":[],"authenticated":false,"get_current_user_id":0},"_links":{"self":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/48918","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/comments?post=48918"}],"version-history":[{"count":22,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/48918\/revisions"}],"predecessor-version":[{"id":359977,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/48918\/revisions\/359977"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media\/359965"}],"wp:attachment":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media?parent=48918"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/categories?post=48918"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/tags?post=48918"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}