{"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,"raw":"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.\r\n\r\nIn all honesty, I think the word ceremony is over-egging slightly, whichever way you cut it.\r\n\r\nBut, inflated titles aside, these \u2018ceremonies\u2019 are important for bringing structure, continuous improvement, and opportunities for learning to Scrum projects.\r\n\r\nThis article will explain what they are and why 4 is the magic number in this case (sorry, Schoolhouse Rock).\r\n<h2>A quick reminder about Scrum<\/h2>\r\nScrum is a framework within the Agile methodology. Originally used in software development, it has since been adapted for many other types of <a href=\"https:\/\/monday.com\/blog\/rnd\/product-development\/\">product development<\/a>.\u00a0 <span style=\"font-weight: 200;\">Read more about these frameworks in our piece all about <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-vs-scrum\/\">agile and scrum.<\/a><\/span>\r\n\r\n<a href=\"https:\/\/assets.kpmg\/content\/dam\/kpmg\/be\/pdf\/2019\/11\/agile-transformation.pdf\" target=\"_blank\" rel=\"nofollow noopener\">88%<\/a> of organizations are moving towards Agile as a way to deliver their projects, with increased flexibility a key reason for the change.\r\n<blockquote>One of the main characteristics of Agile projects is that the deliverable isn\u2019t fully defined. Work is produced over short periods of time (known as sprints) and refined after each sprint to get closer to the desired outcome.<\/blockquote>\r\nCollaboration is crucial for successfully developing a product using Agile as the project team needs to work closely with business stakeholders to refine the end deliverable.\r\n\r\nRegular meetings, or ceremonies, are an important part of tracking progress and continually improving the outcome to meet business requirements.\r\n\r\nScrum is a simple concept, but can be tricky to implement. There are 3 components to the Scrum framework that act as a structure for delivering the work.\r\n<p class=\"p1\">[cta-button url=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_blank\u201d]Try monday dev[\/cta-button]<\/p>\r\n\r\n<h3>Roles<\/h3>\r\nLike any project, defining roles and responsibilities between members of the project team and the business is important, so everyone is clear on who\u2019s doing what.\r\n\r\nIn the Scrum framework, there are 3 key roles:\r\n<ol>\r\n \t<li>The <strong>product owner<\/strong> represents the business and helps translate customer requirements into work packages for the <a href=\"https:\/\/monday.com\/blog\/rnd\/development-team\/\">development team<\/a>.<\/li>\r\n \t<li>The <strong>Scrum master<\/strong> oversees the development process and facilitates improvements to it. They make sure team members have everything they need to get the job done.<\/li>\r\n \t<li><strong><strong>Team members<\/strong>\u00a0<\/strong>Scrum is all about individuals working autonomously to contribute to the outcome.<\/li>\r\n<\/ol>\r\nFor more information on the 7 key roles within the Agile methodology, check out our <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-roles\/\" target=\"_blank\" rel=\"noopener\">article<\/a>.\r\n<h3>Artifacts<\/h3>\r\nAs what the Scrum team is delivering regularly changes, it\u2019s important to track what\u2019s been done and what needs to happen next.\r\n\r\nThe <strong>product backlog<\/strong> lists all the changes requested by a business and is updated after each iteration.\r\n\r\nThe <strong>sprint backlog<\/strong> contains the changes from the <a href=\"https:\/\/monday.com\/blog\/project-management\/product-backlog\/\">product backlog<\/a> that are still to be made during the sprint that\u2019s in progress.\r\n\r\n<img class=\"aligncenter wp-image-48926 size-full\" title=\"Product backlog template from monday.com\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/03\/Product-backlog-template-from-monday.com_.png\" alt=\"Screenshot showing monday.com product backlog template\" width=\"1269\" height=\"556\" \/>\r\n\r\nFinally, the <strong>product increment<\/strong> is a list of all the changes made in the current sprint cycle and the new functionality they provide.\r\n<h3>Ceremonies<\/h3>\r\nCeremonies are used to plan and organize the work that\u2019s happening in the current sprint and also at the end of each sprint to review what went well and what might need to be changed for the next iteration.\r\n<h2>The 4 Scrum ceremonies in detail<\/h2>\r\nFirstly, let\u2019s look at how the 4 ceremonies fit together to help organize and manage both single and multiple sprints. The below timeline shows a 4-week period during which 2 x 2-week sprints are held.\r\n\r\n<img class=\"aligncenter wp-image-48931 size-full\" title=\"Timeline showing scrum ceremonies and their organization\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/03\/Timeline-showing-scrum-ceremonies-and-their-organization.png\" alt=\"4 week timeline showing when scrum ceremonies are held\" width=\"906\" height=\"417\" \/>\r\n\r\n(<a href=\"https:\/\/usefyi.com\/scrum-ceremonies\/#:~:text=%20The%204%20Scrum%20ceremonies:%20A%20timeline%20,holds%20sprint%20review.%20The%20entire%20team...%20More\" target=\"_blank\" rel=\"nofollow noopener\">Image Source<\/a>)\r\n<h3>1. Sprint planning<\/h3>\r\nAs you can see from the above, each 2-week sprint starts with a <a class=\"wpil_keyword_link \" title=\"sprint planning\" href=\"https:\/\/monday.com\/templates\/template\/80440\/sprint-planning\" data-wpil-keyword-link=\"linked\">sprint planning<\/a> ceremony.\r\n\r\nDuring this meeting, 2 main things are decided.\r\n<ul>\r\n \t<li>What to bring forward from the product backlog to the <a href=\"https:\/\/monday.com\/blog\/project-management\/sprint-backlog\/\">sprint backlog<\/a>.<\/li>\r\n \t<li>How those things are going to be delivered.<\/li>\r\n<\/ul>\r\nDeciding what to bring forward can be tricky. It requires matching an estimate of how long tasks on the product backlog are going to take to complete with the capacity of the development team.\r\n\r\nmonday.com\u2019s customizable <a href=\"https:\/\/monday.com\/go-templates\/sprint-planning\" target=\"_blank\" rel=\"noopener\">sprint planning template<\/a> makes things easy to manage with columns showing item status, owner, priority, and estimated duration.\r\n\r\n<img class=\"aligncenter wp-image-48936 size-full\" title=\"Sprint planning template from monday.com\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/03\/Sprint-planning-template-from-monday.com_.png\" alt=\"screenshot showing sprint planning template from monday.com with columns for status, assignee, priority and estimated duration\" width=\"1045\" height=\"472\" \/>\r\n\r\nUnlike other tools, such as Kanban boards, you can also show dependencies, which is great if you have tasks that affect others.\r\n\r\n<strong>How long should a sprint planning ceremony be?<\/strong>\r\n\r\nThe Scrum master is responsible for the logistics around the sprint planning meeting. It\u2019s standard practice to allow 2 hours of planning for every week of the sprint. So, a 2-week sprint would have a 4-hour planning meeting scheduled.\r\n\r\n<strong>Who attends?<\/strong>\r\n\r\nThe Scrum master, development team, and product owner should all be in attendance.\r\n\r\n<strong>What gets done?<\/strong>\r\n\r\nDuring the meeting, the team should work together to form a <strong>sprint goal<\/strong>. This is important as it brings clarity to the team and stakeholders about what should be delivered by the end of the upcoming sprint. It also provides something to review against at the end.\r\n\r\nThis is also an important opportunity for the development team to check in with the product owner. They need to agree on the acceptance criteria for tasks and check any assumptions they\u2019re working on.\r\n\r\nTo end the meeting, the Scrum master should confirm that there\u2019s consensus on what\u2019s being delivered and that there\u2019s a plan in place. This plan will be relatively high-level as the Scrum framework emphasizes self-management by individuals, giving them the space to complete their work how they want.\r\n<h3>2. Daily Scrum<\/h3>\r\nOtherwise known as a daily standup meeting, this is a chance for the team to come together to communicate progress. But, the intention isn\u2019t a status update meeting. The purpose is to identify any obstacles that might stop or slow work being done.\r\n\r\nAnything that\u2019s identified falls to the Scrum master to manage \u2014 their key purpose is to facilitate work getting done as easily as possible.\r\n\r\n<strong>How long is a daily Scrum meeting?<\/strong>\r\n\r\nThese are meant to be short! Standard practice is around 15 minutes. If there are topics you think will take longer, encourage that conversation to happen outside the daily <a href=\"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/\">Scrum meetin<\/a>g.\r\n\r\n<strong>Who attends?<\/strong>\r\n\r\nThis one\u2019s mainly for the development team and the Scrum master. The product owner is an optional attendee.\r\n\r\n<strong>What gets done?<\/strong>\r\n\r\nThe point of the daily standup is for each team member to share 4 things:\r\n<ul>\r\n \t<li>What I did yesterday<\/li>\r\n \t<li>What I\u2019m working on today<\/li>\r\n \t<li>What I plan to do tomorrow<\/li>\r\n \t<li>What\u2019s in my way<\/li>\r\n<\/ul>\r\nUsing this structure gives the rest of the team a quick overview on progress and identifies any obstacles that need resolving by the Scrum master.\r\n\r\nIdeally, this meeting is conducted face-to-face, but it can be done virtually if teams are distributed.\r\n\r\n[twitter]Running the daily Scrum virtually is a piece of cake with monday.com. Our Work OS integrates with all the usual collaboration tools, which means that\u2019s one less thing you have to worry about.[\/twitter]\r\n<p class=\"p1\">[cta-button url=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_blank\u201d]Try monday dev[\/cta-button]<\/p>\r\n\r\n<h3>3. Sprint review<\/h3>\r\nThe <a href=\"https:\/\/monday.com\/blog\/rnd\/what-is-a-sprint-review-definition-goals-and-tips\/\">sprint review meeting<\/a> is a chance for the development team to share the work that\u2019s been completed during the sprint with business stakeholders.\r\n\r\nIt\u2019s an opportunity to gather feedback from them about the work that\u2019s been done and discuss how that informs what needs to be prioritized on \u2014 or added to \u2014 the backlog.\r\n\r\n<strong>How long is a sprint review?<\/strong>\r\n\r\nAs this is about product demonstrations, it\u2019s sensible to allow a couple of hours for this meeting. Rule of thumb is around 1 hour per week of sprint completed. So, a 2-week sprint would result in a 2-hour meeting.\r\n\r\n<strong>Who attends?<\/strong>\r\n\r\nThe development team, product owner, and Scrum master should attend, plus business stakeholders. The product owner and Scrum master should work together to determine suitable business representation in advance.\r\n\r\n<strong>What gets done?<\/strong>\r\n\r\nThe development team showcases the work that\u2019s been completed during the sprint. The focus should be less on proving things work and more about explaining the value of each element and how it fits into the project overall.\r\n\r\nThe development team might reference high-level documents such as the project roadmap or <a href=\"https:\/\/monday.com\/templates\/software-requirements-specification\" target=\"_blank\" rel=\"noopener\">software requirements specification<\/a> to help stakeholders connect with the overall progress.\r\n\r\nmonday.com\u2019s <a href=\"https:\/\/monday.com\/templates\/project-roadmap\" target=\"_blank\" rel=\"noopener\">project roadmap<\/a> provides a snapshot of the key deliverables and is ideal for helping stakeholders understand how work completed in the current sprint contributes to the bigger picture.\r\n\r\n<img class=\"aligncenter wp-image-48946 size-full\" title=\"Project roadmap template from monday.com\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/03\/Project-roadmap-template-from-monday.com_.png\" alt=\"screenshot of project roadmap template from monday.com\" width=\"1450\" height=\"568\" \/>\r\n<blockquote>The product owner should lead a discussion with stakeholders about their thoughts. Actionable feedback is captured and added to the backlog. This discussion helps to refine and prioritize the backlog in preparation for the next round of sprint planning.<\/blockquote>\r\nIt\u2019s also an opportunity for the development team to be praised for work completed to date. This should be about building a trusting and productive relationship between the project and the business.\r\n<h3>4. Sprint Retrospective<\/h3>\r\nThis is the second meeting that happens at the end of each sprint. The <a class=\"wpil_keyword_link \" title=\"sprint retrospective\" href=\"https:\/\/monday.com\/templates\/template\/80436\/sprint-retrospective\" data-wpil-keyword-link=\"linked\">sprint retrospective<\/a> meeting differs from the sprint review as this one isn\u2019t about the work that\u2019s been completed.\r\n\r\nIt\u2019s much more about continuous improvement and learning from how things went in the previous sprint. This desire to always try to do things better is a key part of <a class=\"wpil_keyword_link \" title=\"Agile project management\" href=\"https:\/\/monday.com\/blog\/rnd\/agile-project-management\/\" data-wpil-keyword-link=\"linked\">Agile project management<\/a>.\r\n\r\n<strong>How long is a sprint retrospective?<\/strong>\r\n\r\nThere\u2019s no set time for a <a href=\"https:\/\/monday.com\/blog\/project-management\/agile-retrospective-what-it-is-and-how-it-works\/\">sprint retrospective<\/a>. How long they take will depend on how long the team has been working together, their experience, and their maturity. Allowing around 1.5 hours for a 2-week sprint is a good place to start.\r\n\r\n<strong>Who attends?<\/strong>\r\n\r\nThis is for the Scrum master and the development team to look at their internal processes. The product owner is an optional attendee, and there shouldn\u2019t be business stakeholders.\r\n\r\n<strong>What gets done?<\/strong>\r\n\r\nThis is an opportunity for the entire team to offer an honest review of the sprint. Questions could include:\r\n<ul>\r\n \t<li>What worked well during the last sprint?<\/li>\r\n \t<li>What didn\u2019t work so well during the last sprint?<\/li>\r\n \t<li>What could we change to help us improve?<\/li>\r\n<\/ul>\r\nOnce all the feedback has been shared, the team should decide on the actions to be taken for the coming sprint. These should be recorded and assigned an owner to make sure that they\u2019re followed through.\r\n\r\nmonday.com\u2019s <a href=\"https:\/\/monday.com\/templates\/sprint-retrospective\" target=\"_blank\" rel=\"noopener\">sprint retrospective<\/a> template helps you capture all this information easily. It also allows you to track progress from sprint to sprint through color-coded labels monitoring what\u2019s been implemented and what the team is still working on.\r\n\r\n<img class=\"aligncenter wp-image-48951 size-full\" title=\"Sprint Retrospective template from monday.com\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/03\/Sprint-Retrospective-template-from-monday.com_.png\" alt=\"screenshot showing feedback gathered during the sprint retrospective\" width=\"1419\" height=\"559\" \/>\r\n\r\nLike anything new, it can take a couple of iterations for change to occur, but the intention for improvement should be strong.\r\n<h2>Scrum ceremonies enable collaboration<\/h2>\r\nIn this article, we\u2019ve taken a look at the 4 Scrum ceremonies and why they\u2019re important for your project.\r\n\r\nScrum ceremonies ensure there\u2019s visibility of the work being done and allow collaboration between the project team and business stakeholders. This means work can be progressed iteratively, and there\u2019s a shared responsibility for the output.\r\n\r\nWe can help you get started. At monday.com, our sprint planning template helps you prioritize work for your next sprint and keeps everyone on the same page.\r\n<p class=\"p1\">[cta-button url=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_blank\u201d]Try monday dev[\/cta-button]<\/p>"},"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.4) - 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}]}}