{"id":59623,"date":"2021-04-27T11:03:10","date_gmt":"2021-04-27T11:03:10","guid":{"rendered":"https:\/\/staging-mondaycomblog.kinsta.cloud\/?post_type=pm&#038;p=59623"},"modified":"2026-08-30T04:49:13","modified_gmt":"2026-08-30T09:49:13","slug":"scrum-meeting","status":"publish","type":"post","link":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/","title":{"rendered":"Scrum meetings and 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 meetings are meant to fix exactly that, but only when you run them with intent.<\/p>\n<p>Scrum meetings 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>\n<p><strong>A clear cadence drives delivery<\/strong>: sprint planning, daily scrums, sprint reviews, retrospectives, and backlog refinement work together to plan, coordinate, and improve<\/p>\n<\/li>\n<li>\n<p><strong>Timebox every ceremony<\/strong>: 15 minutes for daily scrums, and about two hours per week of sprint for planning, review, and retrospective<\/p>\n<\/li>\n<li>\n<p><strong>Prioritize problem-solving over status<\/strong>: ask &#8220;what help do you need?&#8221; and push routine updates to async channels<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<\/ul>\n<p><a aria-label=\"Get started with monday.com\" class=\"cta-button blue-button\" data-index=\"1\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\">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 meetings?<\/h2>\n<p>A scrum meeting is any of the recurring events in the Scrum framework that keep a team aligned on goals, progress, and improvements throughout a sprint. Scrum defines five events inside each sprint, and together they create the cadence for planning, daily coordination, feedback, and improvement.<\/p>\n<p>Compared with a typical project status meeting, the difference is intent. A status meeting usually exists to report upward, while scrum meetings 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. Picture a two-week sprint: the team plans on day one, syncs for 15 minutes each morning, demos finished work at the end, and closes with a short reflection before the next cycle 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>\n<p><strong>Sprint planning:<\/strong> set the <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-sprint\/\" target=\"_blank\">scrum sprint<\/a> goal and commit to a realistic <a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-backlog\/\" target=\"_blank\">sprint backlog<\/a><\/p>\n<\/li>\n<li>\n<p><strong>Daily scrum:<\/strong> a 15-minute sync to align, surface blockers, and adjust the day&#8217;s plan<\/p>\n<\/li>\n<li>\n<p><strong>Sprint review:<\/strong> demo working software and gather stakeholder feedback to inform the backlog<\/p>\n<\/li>\n<li>\n<p><strong>Sprint retrospective:<\/strong> reflect on the process and agree on a few concrete improvements<\/p>\n<\/li>\n<li>\n<p><strong>Backlog refinement:<\/strong> continuously clarify, size, and prioritize upcoming work so planning runs smoothly<\/p>\n<\/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>\n<p><strong>Sprint:<\/strong> a fixed period, typically one to four weeks, to deliver a defined slice of value<\/p>\n<\/li>\n<li>\n<p><strong>Product backlog:<\/strong> the prioritized list of features, enhancements, and fixes for the product<\/p>\n<\/li>\n<li>\n<p><strong>Sprint backlog:<\/strong> the subset the team commits to for the current sprint, aligned to the sprint goal<\/p>\n<\/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 meeting types<\/h2>\n<p>Each scrum meeting has a distinct purpose, set of participants, and timebox. Together they provide structure without slowing execution. They aren&#8217;t strictly optional either: the framework treats them as a connected system, and skipping one tends to weaken the others, so most teams run all five and adjust the format rather than dropping events.<\/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-1.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-1.jpg 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-management-1-300x169.jpg 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-management-1-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\/\" target=\"_blank\">Sprint planning<\/a> sets the direction for the next sprint, which usually runs one to four weeks.<\/p>\n<ul>\n<li>\n<p><strong>Who attends:<\/strong> the product owner, scrum master, and the full development team<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> review priorities, discuss how to deliver them, and agree on a realistic sprint backlog<\/p>\n<\/li>\n<li>\n<p><strong>Duration:<\/strong> about two hours per week of sprint, so roughly four hours for a two-week sprint<\/p>\n<\/li>\n<\/ul>\n<p>By the end, the team should leave with a shared sprint goal and clear commitments.<\/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>\n<p><strong>Who attends:<\/strong> the development team, with others free to observe<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> each person answers what they completed yesterday, what they&#8217;ll work on today, and what&#8217;s blocking progress<\/p>\n<\/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\/\" target=\"_blank\">sprint review<\/a> closes the sprint by sharing completed work and gathering feedback.<\/p>\n<ul>\n<li>\n<p><strong>Who attends:<\/strong> the <a href=\"https:\/\/monday.com\/blog\/rnd\/heres-how-you-build-a-successful-scrum-team\/\" target=\"_blank\">scrum team<\/a> and stakeholders<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> demonstrate working software, discuss what the team learned, and adjust the backlog<\/p>\n<\/li>\n<li>\n<p><strong>Duration:<\/strong> up to two hours for a two-week sprint<\/p>\n<\/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\/\" target=\"_blank\">agile retrospective<\/a> is your team&#8217;s chance to reflect on how you work together.<\/p>\n<ul>\n<li>\n<p><strong>Who attends:<\/strong> the entire scrum team<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> what went well, what needs improvement, and what you&#8217;ll try next sprint<\/p>\n<\/li>\n<li>\n<p><strong>Duration:<\/strong> about 1.5 hours for a two-week sprint<\/p>\n<\/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\/\" target=\"_blank\">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\/\" target=\"_blank\">backlog grooming<\/a>, keeps upcoming work clear and ready.<\/p>\n<ul>\n<li>\n<p><strong>Who attends:<\/strong> the product owner and development team<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> clarify requirements, size effort, and break down large items<\/p>\n<\/li>\n<li>\n<p><strong>Duration:<\/strong> one to two hours per week<\/p>\n<\/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 meetings?<\/h2>\n<p>Each scrum role brings specific value to the events. Having the right people in the room keeps agile scrum meetings purposeful and outcomes clear, so it&#8217;s worth being deliberate about who joins each one.<\/p>\n<ul>\n<li>\n<p><strong>Product owner:<\/strong> owns the product vision and backlog. They <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-guide\/\" target=\"_blank\">guide priorities<\/a> during sprint planning, adjust the backlog after sprint reviews, and prepare upcoming work during refinement<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/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\/\" target=\"_blank\">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 aria-label=\"Get started with monday.com\" class=\"cta-button blue-button\" data-index=\"2\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\">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\/\" target=\"_blank\">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-1.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-1.png 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-retrospective-1-300x169.png 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-sprint-retrospective-1-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>\n<p><strong>Sprint planning:<\/strong> four hours<\/p>\n<\/li>\n<li>\n<p><strong>Daily scrum:<\/strong> 15 minutes<\/p>\n<\/li>\n<li>\n<p><strong>Sprint review:<\/strong> two hours<\/p>\n<\/li>\n<li>\n<p><strong>Sprint retrospective:<\/strong> 1.5 hours<\/p>\n<\/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 meetings makes it easier for participants to contribute meaningfully. Here&#8217;s the format each ceremony tends to follow.<\/p>\n<ul>\n<li>\n<p><strong>Sprint planning:<\/strong> starts with the goal, then moves to backlog selection, task breakdown, and commitment<\/p>\n<\/li>\n<li>\n<p><strong>Daily scrums:<\/strong> follow the three-question format, so updates stay consistent<\/p>\n<\/li>\n<li>\n<p><strong>Sprint reviews:<\/strong> begin with working software and end with stakeholder discussion<\/p>\n<\/li>\n<li>\n<p><strong>Retrospectives:<\/strong> often use &#8220;start, stop, continue&#8221; or a similar technique to surface insights<\/p>\n<\/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 meetings<\/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\" target=\"_blank\">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\/\" target=\"_blank\">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. Its agents go a step further: the Research Assistant automates agile meetings, and the Meeting Summarizer turns standup and retro notes into action items. That matters because <a href=\"https:\/\/www.microsoft.com\/en-us\/worklab\/work-trend-index\/breaking-down-infinite-workday\" target=\"_blank\">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-1.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-1.jpg 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-kanban-board-1-300x194.jpg 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-kanban-board-1-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 aria-label=\"Get started with monday.com\" class=\"cta-button blue-button\" data-index=\"3\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\">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. Think of them the way a coach reads a scoreboard mid-season: useful for spotting trends and starting better conversations, not for ranking individuals. Use them to inform your retrospectives, not to turn scrum into a performance scorecard. Read each metric alongside what it reveals.<\/p>\n<ul>\n<li>\n<p><strong>Velocity:<\/strong> the amount of work completed per sprint, useful for forecasting realistic commitments<\/p>\n<\/li>\n<li>\n<p><strong>Burndown and burnup:<\/strong> remaining or completed work against time, which shows whether a sprint is on pace<\/p>\n<\/li>\n<li>\n<p><strong>Sprint goal success rate:<\/strong> how often the team meets its sprint goal, a signal of planning accuracy<\/p>\n<\/li>\n<li>\n<p><strong>Cycle and lead time:<\/strong> how long an item takes to move from start to done, or from backlog to completion<\/p>\n<\/li>\n<li>\n<p><strong>Defect rate:<\/strong> the number of bugs or reopened items, a check on quality alongside speed<\/p>\n<\/li>\n<\/ul>\n<p><img alt=\"Sprint dashboard tracking scrum meeting metrics like velocity and burndown on the monday AI Workspace\" src=\"https:\/\/res.cloudinary.com\/monday-blogs\/w_1024,h_576,c_fit\/fl_lossy,f_auto,q_auto\/wp-blog\/2025\/02\/monday-dev-sprint-dashboard.png\" \/>The point isn&#8217;t to chase numbers. Track a few <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-metrics\/\" target=\"_blank\">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<\/div>\n<div class=\"text-block\" id=\"text-block-15\">\n<h2 class=\"h2 text-block__title\">How monday AI Workspace supports scrum meetings<\/h2>\n<p>The hardest part of scrum usually isn&#8217;t the framework; it&#8217;s the admin around it: chasing status updates, rebuilding the same reports, and losing retro action items between sprints. The monday AI Workspace closes that gap so meetings run smoother and teams spend more time on collaboration than on reporting. That shift is where most teams are heading: <a href=\"https:\/\/www.mckinsey.com\/capabilities\/tech-and-ai\/our-insights\/superagency-in-the-workplace-empowering-people-to-unlock-ais-full-potential-at-work\" target=\"_blank\">McKinsey&#8217;s research found 92% of companies plan to increase their AI investments over the next three years<\/a>, and automating ceremony admin is one of the clearest places to start.<\/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>\n<p><strong>Planning with clarity:<\/strong> <a href=\"https:\/\/monday.com\/blog\/project-management\/task-boards\/\" target=\"_blank\">sprint boards<\/a> with more than 15 views, including Kanban and Gantt, show capacity, backlog priorities, and sprint goals in one place<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<\/ul>\n<p>AI adds another layer, and it&#8217;s easiest to understand through the outcome each capability delivers rather than the feature itself.<\/p>\n<ul>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/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-1.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-1.png 1024w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-integration-center-1-300x169.png 300w, https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/08\/monday-dev-integration-center-1-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<table style=\"min-width: 75px\">\n<colgroup>\n<col style=\"min-width: 25px\" \/>\n<col style=\"min-width: 25px\" \/>\n<col style=\"min-width: 25px\" \/><\/colgroup>\n<tbody>\n<tr>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Scrum work<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Manual scrum meetings<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Scrum meetings on monday AI Workspace<\/p>\n<\/th>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Sprint planning and backlog<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Priorities live in spreadsheets and docs that fall out of date between sprints.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Sprint boards and Kanban or Gantt views keep capacity, priorities, and the sprint goal in one live place.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Daily status<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Each person reads a verbal update while the rest of the team waits.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Automations roll up status as work progresses, so standups focus on blockers.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Sprint review evidence<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Someone assembles screenshots and notes ahead of the demo.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Integrations pull completed work directly, and feedback flows back to the backlog.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Retrospective follow-through<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Action items sit in meeting notes and get forgotten by the next sprint.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>The Meeting Summarizer turns retro notes into tracked action items across sprints.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Risk and capacity visibility<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Overload and slippage surface only when a deadline is already at risk.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Workload view and dashboards flag capacity issues and risks early.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-18\">\n<h2 class=\"h2 text-block__title\">Turning scrum meetings into consistent delivery<\/h2>\n<p>Scrum meetings aren&#8217;t the goal in themselves. They&#8217;re the rhythm that turns good intentions into shipped work, sprint after sprint. When each ceremony has a clear purpose, the right people, and a firm timebox, your team plans with confidence, coordinates without friction, and improves a little every cycle.<\/p>\n<p>The shift worth making is from meetings that report on work to meetings that move it forward. That&#8217;s where people and AI running meetings together pays off: the monday AI Workspace handles the routine admin, so your team can spend its energy on the conversations that actually change outcomes. Get that balance right, and consistent delivery stops being a stretch goal and starts being your default.<\/p>\n<p><a aria-label=\"Get started with monday.com\" class=\"cta-button blue-button\" data-index=\"4\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\">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\/\" target=\"_blank\">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 meetings?        \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\/\" target=\"_blank\">Kanban<\/a> or Extreme Programming. Scrum meetings 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 meetings?        \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\\\/\" target=\"_blank\">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 meetings?\",\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\\\/\" target=\"_blank\">Kanban or Extreme Programming. Scrum meetings 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 meetings?\",\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":"A recent survey suggests that our favorite day for meetings is Tuesday, while nearly <a href=\"https:\/\/bettermeetings.expert\/meeting-statistics\/\" target=\"_blank\" rel=\"nofollow noopener\">50%<\/a> of us get grumpy about meetings held on a Monday.\r\n\r\nSo the prospect of a project management framework that insists on daily meetings might go down like a bit of a lead balloon.\r\n\r\nAdd to that the fact you need to shoe-horn in another 3 meetings over a 2-week period, and mutiny seems almost assured.\r\n\r\nSo why is the Scrum framework so beloved of a meeting? What\u2019s the point of them all? Any chance one of them is a runt meeting that could be quietly forgotten about?\r\n\r\nIn this article, we\u2019ll answer all those questions and more.\r\n\r\nWe\u2019ll cover the 4 different Scrum meetings, when each is used, and why they\u2019re important. Heads up: there\u2019s no runt one.\r\n\r\nPlus we\u2019ll give you some hints and tips on how to get the most out of them.\r\n<h2>What is a Scrum meeting?<\/h2>\r\nScrum is the <a href=\"https:\/\/stateofagile.com\/#ufh-i-615706098-14th-annual-state-of-agile-report\/7027494\" target=\"_blank\" rel=\"nofollow noopener\">most popular<\/a> project management framework within the Agile methodology. It\u2019s used for the incremental delivery of products or services, across many industries.\r\n\r\nIn Scrum, work is delivered in short time periods called \u2018sprints\u2019, and the project is constantly evolving based on client feedback and project progress.\r\n\r\n[twitter]The Scrum framework is given structure through its key artifacts, roles, and meetings.[\/twitter]\r\n\r\nThe <a href=\"https:\/\/monday.com\/blog\/rnd\/how-to-get-the-most-out-of-your-scrum-artifacts\/\" target=\"_blank\" rel=\"noopener\"><strong>artifacts<\/strong><\/a> include the product and sprint backlogs (lists of work to be accomplished) plus the product increment, which is the sum of the total work completed to date.\r\n\r\nThere are <a href=\"https:\/\/monday.com\/blog\/rnd\/understanding-the-basics-of-scrum-roles-and-agile-project-management\/\" target=\"_blank\" rel=\"noopener\"><strong>3 key roles<\/strong><\/a>: the Product Owner, the Scrum Master, and the development team.\r\n\r\n<img class=\"aligncenter wp-image-59635 size-full\" title=\"The 3 key Scrum roles\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/04\/The-3-key-Scrum-roles.png\" alt=\"image showing the 3 key Scrum roles and their responsibilities\" width=\"888\" height=\"769\" \/>\r\n\r\n(<a href=\"https:\/\/resources.scrumalliance.org\/Article\/how-scrum-scrum-teams-work\" target=\"_blank\" rel=\"nofollow noopener\">Image Source<\/a>)\r\n\r\nThere are <strong>4 Scrum meetings<\/strong> \u2014 also termed ceremonies \u2014 used throughout each sprint.\r\n\r\nThis is how the meetings would be arranged over a typical 2-week sprint:\r\n\r\n<img class=\"aligncenter wp-image-59640 size-full\" title=\"Scrum meetings conducted during each sprint\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/04\/Scrum-meetings-conducted-during-each-sprint.png\" alt=\"image showing the 4 Scrum meetings that are conducted during each sprint and where they appear during the sprint cycle\" 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\r\nLet\u2019s look at each Scrum meeting in more detail.\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>Sprint planning<\/h3>\r\nThe purpose of the <a class=\"wpil_keyword_link \" title=\"sprint planning\" href=\"https:\/\/monday.com\/go-templates\/sprint-planning\" data-wpil-keyword-link=\"linked\">sprint planning<\/a> meeting is to agree on what items are going to be delivered during the sprint, and how the team will deliver them.\r\n\r\nTo help the decision process, the product owner should prioritize the product backlog in advance.\r\n\r\nThe <strong>product backlog<\/strong> is a list of all the items that need to be completed to satisfy the business requirements of the project.\r\n\r\n<img class=\"aligncenter wp-image-59645 size-full\" title=\"Product backlog in monday.com\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/04\/Product-backlog-in-monday.com_.png\" alt=\"image showing an example product backlog in monday.com\" width=\"1269\" height=\"556\" \/>\r\n\r\nOnce the product owner and the project team have agreed on the items that will be delivered, those items are moved forward to create the <strong>sprint backlog<\/strong>.\r\n\r\nGiven its name, there are no prizes for guessing that this meeting comes right at the beginning of the sprint cycle.\r\n\r\nIt\u2019s common to allow around 2 hours of planning for every week of the sprint duration. So, a 2-week sprint would have a 4-hour sprint planning meeting.\r\n\r\nAs this meeting\u2019s highly collaborative, both the project development team and the product owner should attend. If the team\u2019s using a Scrum Master role, they plan the logistics of the\r\n\r\nmeeting.\r\n\r\nDuring the meeting, the attendees should work together to create a <strong>sprint goal<\/strong>. The sprint goal ensures a shared understanding of what\u2019s expected to be delivered and provides a metric to measure progress against.\r\n<h3>Daily standup<\/h3>\r\nThis is a short daily meeting attended by the project team. Ideally, the daily standup meeting is conducted face-to-face, though distributed teams may have to run it virtually.\r\n\r\nmonday.com makes running <a href=\"https:\/\/monday.com\/blog\/es\/sin-categorizar\/remote-communication-2\/\" target=\"_blank\" rel=\"noopener\">virtual meetings<\/a> a cinch, with in-platform communication and sharing options. It also integrates with all your favorite collaboration tools \u2014 which is one less thing to think about.\r\n\r\n<img class=\"aligncenter wp-image-59650 size-full\" title=\"Communication made easy with monday.com\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/04\/Communication-made-easy-with-monday.com_.png\" alt=\"image showing 4 team members communicating from their own workspaces using the monday.com platform\" width=\"1294\" height=\"607\" \/>\r\n\r\nThe daily standup is conducted \u2014 you guessed it \u2014 standing up to encourage efficient communication and decision-making.\r\n\r\nThe purpose of the meeting is to provide a quick update on progress, so everyone\u2019s clear who\u2019s doing what.\r\n\r\nEach team member focuses on 3 key things:\r\n<ul>\r\n \t<li>What they\u2019re working on today<\/li>\r\n \t<li>What they plan to tackle next<\/li>\r\n \t<li>Any obstacles that are in the way of them getting work done<\/li>\r\n<\/ul>\r\nThe main responsibility of the Scrum Master is to facilitate work moving forward. Any obstacles or distractions that are identified by the team fall to them to manage.\r\n\r\nThese meetings are meant to be brief, around 15\u201320 minutes in length. Any conversations that require extra time should be continued outside of the daily standup.\r\n<h3>Sprint review<\/h3>\r\nThe sprint review meeting is an opportunity for the project team to show business stakeholders what\u2019s been delivered during the sprint.\r\n\r\nIt\u2019s less about the detail of each individual item and more about how it fits into the overall project to deliver value. The product owner facilitates the meeting and seeks feedback from the business about the work that\u2019s been completed.\r\n\r\nFeedback from the business may result in new items being added to the product backlog and may inform which items are prioritized for the next sprint.\r\n\r\nUnsurprisingly, this meeting should be attended by all members of the project team, the product owner, and key business stakeholders.\r\n\r\nThe sprint review is the first of 2 meetings that occur at the end of every sprint. Best practice allows for at least an hour for every week of the sprint, so a 2-week sprint would have a 2-hour sprint review.\r\n<h3>Sprint retrospective<\/h3>\r\nThe <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> is the second meeting that happens at the end of the sprint.\r\n\r\nThe purpose of the sprint retrospective meeting is continuous improvement, which is a <a href=\"https:\/\/monday.com\/blog\/project-management\/agile-principles\/\" target=\"_blank\" rel=\"noopener\">key principle<\/a> of all Agile frameworks.\r\n\r\nIt\u2019s an opportunity for the project team to come together and review how well they worked as individuals, and as a team, during the last sprint.\r\n\r\nBoth things that are working well and areas for improvement should be identified.\r\n\r\nUsing this feedback, the team can agree on actions and approaches they are going to take to try and improve during the upcoming sprint. These should be written down and assigned to an owner to ensure they\u2019re followed up.\r\n\r\nmonday.com has an easy-to-use <a href=\"https:\/\/monday.com\/templates\/sprint-retrospective\" target=\"_blank\" rel=\"noopener\">sprint retrospective<\/a> template to ensure nothing gets lost. It\u2019s simple to assign an owner and add color-coded labels to help you track progress from sprint to sprint.\r\n\r\n<img class=\"aligncenter wp-image-59655 size-full\" title=\"Sprint Retrospective template from monday.com\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/04\/Sprint-Retrospective-template-from-monday.com_.png\" alt=\"screenshot showing feedback gathered during the sprint retrospective\" width=\"1419\" height=\"559\" \/>\r\n<p style=\"text-align: center\">[cta-button url=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\"]Get started[\/cta-button]<\/p>\r\n\r\n<h2>Challenges with Scrum meetings and how to manage them<\/h2>\r\nThere are a few key challenges you might face running Scrum meetings. Here\u2019s what they are and how to tackle them.\r\n<h3>Getting too detailed during daily standups<\/h3>\r\nIt\u2019s tempting to share everything you\u2019re doing with the rest of the team, especially if you\u2019re facing something tricky or if you want to celebrate something going well.\r\n\r\nBut, try and keep the purpose of the meeting in mind \u2014 shared understanding of progress and identification of obstacles. If what you want to say doesn't contribute to either of those things, set up a separate meeting outside the standup.\r\n<h3>Not having the right people in the room<\/h3>\r\nScrum meetings will only be successful if the right people are engaged in them.\r\n\r\nIf the product owner hasn\u2019t prioritized the product backlog before sprint planning starts, it\u2019s easy to see how the wrong things could be put forward for delivery. Which ends up being pretty frustrating for both the business and the development team.\r\n\r\nEqually, they\u2019ll be times that you <em>don\u2019t<\/em> want people to attend a meeting.\r\n\r\nBusiness stakeholders shouldn\u2019t be invited to the sprint retrospective as it might stifle honest feedback from the team. This can impact learning and improvement for the next sprint.\r\n<blockquote>Make sure the value of each meeting is clearly understood, and that attendees know why they are attending and how they can best contribute. Also, people tend to be busy \u2014 get smart with your scheduling and plan meetings well in advance.<\/blockquote>\r\nmonday.com makes planning regular meetings easy through automation.\r\n\r\nFor example, you can set up an automation recipe that reminds required attendees about the sprint review meeting as soon as the sprint planning meeting is finished.\r\n\r\n<img class=\"aligncenter wp-image-59660 size-full\" title=\"Setting automations using monday.com\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/04\/Setting-automations-using-monday.com_.png\" alt=\"image showing how to build custom automations in monday.com\" width=\"1099\" height=\"600\" \/>\r\n<h3>Not learning from the sprint retrospective<\/h3>\r\nSpeaking of the sprint retrospective, it\u2019s only valuable if it prompts action.\r\n\r\nIt\u2019s important to create an environment that allows team members to feel confident identifying both things that could have gone better and things they\u2019ve done well.\r\n\r\nBut it\u2019s not a pity party. And there\u2019s only a smidge of room for navel-gazing and\/or fist-pumping. Make sure thoughts are turned into actionable feedback, which is both captured and tracked.\r\n<h3>Getting side-tracked during sprint planning<\/h3>\r\nAssuming the product owner has done their job, you\u2019ll have a nicely prioritized list of work items to discuss during the sprint planning meeting.\r\n\r\n<img class=\"aligncenter wp-image-59665 size-full\" title=\"Sprint planning template from monday.com\" src=\"https:\/\/www.monday.com\/blog\/wp-content\/uploads\/2021\/04\/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\nThe focus should be on estimating the work required to deliver those items \u2014 and ensuring it matches team capacity \u2014 and figuring out how those items are going to be delivered.\r\n\r\nTempting though it is, don\u2019t get side-tracked by looking at other items on the product backlog.\r\n\r\nWhile it\u2019s normal to want to get cracking on an area of work you\u2019re really good at or enjoy, meeting the needs of the business has got to be the name of the game.\r\n<h2>Scrum meetings provide organization and structure to each sprint<\/h2>\r\nIn this article, we\u2019ve covered the 4 types of Scrum meetings, including the purpose of each and where it fits within the sprint cycle.\r\n\r\nWe\u2019ve also highlighted some of the challenges faced in running the meetings and how best to handle them.\r\n\r\nScrum meetings are critical to optimizing the Scrum framework and form the backbone of planning and delivering each iteration.\r\n\r\nWhy not tick the first off your list with our fully customizable <a href=\"https:\/\/monday.com\/templates\/sprint-planning\" target=\"_blank\" rel=\"noopener\">sprint planning<\/a> template?\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>A recent survey suggests that our favorite day for meetings is Tuesday, while nearly 50% of us get grumpy about meetings held on a Monday. So the prospect of a project management framework that insists on daily meetings might go down like a bit of a lead balloon. Add to &#8230;<\/p>\n","protected":false},"author":5,"featured_media":60485,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"pages\/cornerstone-primary.php","format":"standard","meta":{"_acf_changed":false,"monday_item_id":12070617158,"monday_board_id":0,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[13911,13904],"tags":[14019],"class_list":["post-59623","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-rnd","category-project-management","tag-scrum-methodology"],"acf":{"lobby_image":false,"post_thumbnail_title":"","hide_post_info":false,"hide_bottom_cta":false,"hide_from_blog":true,"cluster":"","banner_url":"","main_text_banner":"","sub_title_banner":"","sub_title_banner_second":"","banner_button_text":"","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\": \"DefinedTerm\", \"name\": \"Scrum meetings\", \"description\": \"Scrum meetings are structured ceremonies that create alignment, clarity, and continuous improvement for development teams working in sprints.\"}<\/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\/\" target=\"_blank\">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 meetings?","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\/\" target=\"_blank\">Kanban<\/a> or Extreme Programming. Scrum meetings 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 meetings?","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":true,"cta_banner_text":"<p><strong>Don\u2019t miss <\/strong> more quality content!<\/p>\n","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 meetings are meant to fix exactly that, but only when you run them with intent.<\/p>\n<p>Scrum meetings 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>\n<p><strong>A clear cadence drives delivery<\/strong>: sprint planning, daily scrums, sprint reviews, retrospectives, and backlog refinement work together to plan, coordinate, and improve<\/p>\n<\/li>\n<li>\n<p><strong>Timebox every ceremony<\/strong>: 15 minutes for daily scrums, and about two hours per week of sprint for planning, review, and retrospective<\/p>\n<\/li>\n<li>\n<p><strong>Prioritize problem-solving over status<\/strong>: ask &#8220;what help do you need?&#8221; and push routine updates to async channels<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<\/ul>\n<p><a aria-label=\"Get started with monday.com\" class=\"cta-button blue-button\" data-index=\"1\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\">Get started with monday.com<\/a><\/p>\n"}]},{"main_heading":"What are scrum meetings?","content_block":[{"acf_fc_layout":"text","content":"<p>A scrum meeting is any of the recurring events in the Scrum framework that keep a team aligned on goals, progress, and improvements throughout a sprint. Scrum defines five events inside each sprint, and together they create the cadence for planning, daily coordination, feedback, and improvement.<\/p>\n<p>Compared with a typical project status meeting, the difference is intent. A status meeting usually exists to report upward, while scrum meetings 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. Picture a two-week sprint: the team plans on day one, syncs for 15 minutes each morning, demos finished work at the end, and closes with a short reflection before the next cycle 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>\n<p><strong>Sprint planning:<\/strong> set the <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-sprint\/\" target=\"_blank\">scrum sprint<\/a> goal and commit to a realistic <a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-backlog\/\" target=\"_blank\">sprint backlog<\/a><\/p>\n<\/li>\n<li>\n<p><strong>Daily scrum:<\/strong> a 15-minute sync to align, surface blockers, and adjust the day&#8217;s plan<\/p>\n<\/li>\n<li>\n<p><strong>Sprint review:<\/strong> demo working software and gather stakeholder feedback to inform the backlog<\/p>\n<\/li>\n<li>\n<p><strong>Sprint retrospective:<\/strong> reflect on the process and agree on a few concrete improvements<\/p>\n<\/li>\n<li>\n<p><strong>Backlog refinement:<\/strong> continuously clarify, size, and prioritize upcoming work so planning runs smoothly<\/p>\n<\/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>\n<p><strong>Sprint:<\/strong> a fixed period, typically one to four weeks, to deliver a defined slice of value<\/p>\n<\/li>\n<li>\n<p><strong>Product backlog:<\/strong> the prioritized list of features, enhancements, and fixes for the product<\/p>\n<\/li>\n<li>\n<p><strong>Sprint backlog:<\/strong> the subset the team commits to for the current sprint, aligned to the sprint goal<\/p>\n<\/li>\n<\/ul>\n"}]},{"main_heading":"The five scrum meeting types","content_block":[{"acf_fc_layout":"text","content":"<p>Each scrum meeting has a distinct purpose, set of participants, and timebox. Together they provide structure without slowing execution. They aren&#8217;t strictly optional either: the framework treats them as a connected system, and skipping one tends to weaken the others, so most teams run all five and adjust the format rather than dropping events.<\/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":356323,"image_link":null}]},{"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\/\" target=\"_blank\">Sprint planning<\/a> sets the direction for the next sprint, which usually runs one to four weeks.<\/p>\n<ul>\n<li>\n<p><strong>Who attends:<\/strong> the product owner, scrum master, and the full development team<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> review priorities, discuss how to deliver them, and agree on a realistic sprint backlog<\/p>\n<\/li>\n<li>\n<p><strong>Duration:<\/strong> about two hours per week of sprint, so roughly four hours for a two-week sprint<\/p>\n<\/li>\n<\/ul>\n<p>By the end, the team should leave with a shared sprint goal and clear commitments.<\/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>\n<p><strong>Who attends:<\/strong> the development team, with others free to observe<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> each person answers what they completed yesterday, what they&#8217;ll work on today, and what&#8217;s blocking progress<\/p>\n<\/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\/\" target=\"_blank\">sprint review<\/a> closes the sprint by sharing completed work and gathering feedback.<\/p>\n<ul>\n<li>\n<p><strong>Who attends:<\/strong> the <a href=\"https:\/\/monday.com\/blog\/rnd\/heres-how-you-build-a-successful-scrum-team\/\" target=\"_blank\">scrum team<\/a> and stakeholders<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> demonstrate working software, discuss what the team learned, and adjust the backlog<\/p>\n<\/li>\n<li>\n<p><strong>Duration:<\/strong> up to two hours for a two-week sprint<\/p>\n<\/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\/\" target=\"_blank\">agile retrospective<\/a> is your team&#8217;s chance to reflect on how you work together.<\/p>\n<ul>\n<li>\n<p><strong>Who attends:<\/strong> the entire scrum team<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> what went well, what needs improvement, and what you&#8217;ll try next sprint<\/p>\n<\/li>\n<li>\n<p><strong>Duration:<\/strong> about 1.5 hours for a two-week sprint<\/p>\n<\/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\/\" target=\"_blank\">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\/\" target=\"_blank\">backlog grooming<\/a>, keeps upcoming work clear and ready.<\/p>\n<ul>\n<li>\n<p><strong>Who attends:<\/strong> the product owner and development team<\/p>\n<\/li>\n<li>\n<p><strong>Agenda:<\/strong> clarify requirements, size effort, and break down large items<\/p>\n<\/li>\n<li>\n<p><strong>Duration:<\/strong> one to two hours per week<\/p>\n<\/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 meetings?","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 meetings purposeful and outcomes clear, so it&#8217;s worth being deliberate about who joins each one.<\/p>\n<ul>\n<li>\n<p><strong>Product owner:<\/strong> owns the product vision and backlog. They <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-guide\/\" target=\"_blank\">guide priorities<\/a> during sprint planning, adjust the backlog after sprint reviews, and prepare upcoming work during refinement<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/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\/\" target=\"_blank\">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 aria-label=\"Get started with monday.com\" class=\"cta-button blue-button\" data-index=\"2\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\">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\/\" target=\"_blank\">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":356331,"image_link":null}]},{"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>\n<p><strong>Sprint planning:<\/strong> four hours<\/p>\n<\/li>\n<li>\n<p><strong>Daily scrum:<\/strong> 15 minutes<\/p>\n<\/li>\n<li>\n<p><strong>Sprint review:<\/strong> two hours<\/p>\n<\/li>\n<li>\n<p><strong>Sprint retrospective:<\/strong> 1.5 hours<\/p>\n<\/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 meetings makes it easier for participants to contribute meaningfully. Here&#8217;s the format each ceremony tends to follow.<\/p>\n<ul>\n<li>\n<p><strong>Sprint planning:<\/strong> starts with the goal, then moves to backlog selection, task breakdown, and commitment<\/p>\n<\/li>\n<li>\n<p><strong>Daily scrums:<\/strong> follow the three-question format, so updates stay consistent<\/p>\n<\/li>\n<li>\n<p><strong>Sprint reviews:<\/strong> begin with working software and end with stakeholder discussion<\/p>\n<\/li>\n<li>\n<p><strong>Retrospectives:<\/strong> often use &#8220;start, stop, continue&#8221; or a similar technique to surface insights<\/p>\n<\/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 meetings","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\" target=\"_blank\">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\/\" target=\"_blank\">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. Its agents go a step further: the Research Assistant automates agile meetings, and the Meeting Summarizer turns standup and retro notes into action items. That matters because <a href=\"https:\/\/www.microsoft.com\/en-us\/worklab\/work-trend-index\/breaking-down-infinite-workday\" target=\"_blank\">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":356339,"image_link":null}]},{"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 aria-label=\"Get started with monday.com\" class=\"cta-button blue-button\" data-index=\"3\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\">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. Think of them the way a coach reads a scoreboard mid-season: useful for spotting trends and starting better conversations, not for ranking individuals. Use them to inform your retrospectives, not to turn scrum into a performance scorecard. Read each metric alongside what it reveals.<\/p>\n<ul>\n<li>\n<p><strong>Velocity:<\/strong> the amount of work completed per sprint, useful for forecasting realistic commitments<\/p>\n<\/li>\n<li>\n<p><strong>Burndown and burnup:<\/strong> remaining or completed work against time, which shows whether a sprint is on pace<\/p>\n<\/li>\n<li>\n<p><strong>Sprint goal success rate:<\/strong> how often the team meets its sprint goal, a signal of planning accuracy<\/p>\n<\/li>\n<li>\n<p><strong>Cycle and lead time:<\/strong> how long an item takes to move from start to done, or from backlog to completion<\/p>\n<\/li>\n<li>\n<p><strong>Defect rate:<\/strong> the number of bugs or reopened items, a check on quality alongside speed<\/p>\n<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Sprint dashboard tracking scrum meeting metrics like velocity and burndown on the monday AI Workspace\" src=\"https:\/\/res.cloudinary.com\/monday-blogs\/w_1024,h_576,c_fit\/fl_lossy,f_auto,q_auto\/wp-blog\/2025\/02\/monday-dev-sprint-dashboard.png\"\/>The point isn&#8217;t to chase numbers. Track a few <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-metrics\/\" target=\"_blank\">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"}]},{"main_heading":"How monday AI Workspace supports scrum meetings","content_block":[{"acf_fc_layout":"text","content":"<p>The hardest part of scrum usually isn&#8217;t the framework; it&#8217;s the admin around it: chasing status updates, rebuilding the same reports, and losing retro action items between sprints. The monday AI Workspace closes that gap so meetings run smoother and teams spend more time on collaboration than on reporting. That shift is where most teams are heading: <a href=\"https:\/\/www.mckinsey.com\/capabilities\/tech-and-ai\/our-insights\/superagency-in-the-workplace-empowering-people-to-unlock-ais-full-potential-at-work\" target=\"_blank\">McKinsey&#8217;s research found 92% of companies plan to increase their AI investments over the next three years<\/a>, and automating ceremony admin is one of the clearest places to start.<\/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>\n<p><strong>Planning with clarity:<\/strong> <a href=\"https:\/\/monday.com\/blog\/project-management\/task-boards\/\" target=\"_blank\">sprint boards<\/a> with more than 15 views, including Kanban and Gantt, show capacity, backlog priorities, and sprint goals in one place<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<\/ul>\n<p>AI adds another layer, and it&#8217;s easiest to understand through the outcome each capability delivers rather than the feature itself.<\/p>\n<ul>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/li>\n<li>\n<p><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<\/p>\n<\/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":356347,"image_link":null}]},{"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<table style=\"min-width: 75px;\">\n<colgroup>\n<col style=\"min-width: 25px;\"\/>\n<col style=\"min-width: 25px;\"\/>\n<col style=\"min-width: 25px;\"\/><\/colgroup>\n<tbody>\n<tr>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Scrum work<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Manual scrum meetings<\/p>\n<\/th>\n<th colspan=\"1\" rowspan=\"1\">\n<p>Scrum meetings on monday AI Workspace<\/p>\n<\/th>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Sprint planning and backlog<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Priorities live in spreadsheets and docs that fall out of date between sprints.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Sprint boards and Kanban or Gantt views keep capacity, priorities, and the sprint goal in one live place.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Daily status<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Each person reads a verbal update while the rest of the team waits.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Automations roll up status as work progresses, so standups focus on blockers.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Sprint review evidence<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Someone assembles screenshots and notes ahead of the demo.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Integrations pull completed work directly, and feedback flows back to the backlog.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Retrospective follow-through<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Action items sit in meeting notes and get forgotten by the next sprint.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>The Meeting Summarizer turns retro notes into tracked action items across sprints.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Risk and capacity visibility<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Overload and slippage surface only when a deadline is already at risk.<\/p>\n<\/td>\n<td colspan=\"1\" rowspan=\"1\">\n<p>Workload view and dashboards flag capacity issues and risks early.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n"}]},{"main_heading":"Turning scrum meetings into consistent delivery","content_block":[{"acf_fc_layout":"text","content":"<p>Scrum meetings aren&#8217;t the goal in themselves. They&#8217;re the rhythm that turns good intentions into shipped work, sprint after sprint. When each ceremony has a clear purpose, the right people, and a firm timebox, your team plans with confidence, coordinates without friction, and improves a little every cycle.<\/p>\n<p>The shift worth making is from meetings that report on work to meetings that move it forward. That&#8217;s where people and AI running meetings together pays off: the monday AI Workspace handles the routine admin, so your team can spend its energy on the conversations that actually change outcomes. Get that balance right, and consistent delivery stops being a stretch goal and starts being your default.<\/p>\n<p><a aria-label=\"Get started with monday.com\" class=\"cta-button blue-button\" data-index=\"4\" href=\"https:\/\/auth.monday.com\/users\/sign_up_new\" target=\"_blank\">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\/\" target=\"_blank\">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 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-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\/\" target=\"_blank\">Kanban<\/a> or Extreme Programming. Scrum meetings 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 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-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\\\/\\\" target=\\\"_blank\\\">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 meetings?\",\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\\\/\\\" target=\\\"_blank\\\">Kanban<\\\/a> or Extreme Programming. Scrum meetings 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 meetings?\",\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"}]}]}]},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Scrum meetings and how to run them effectively in 2026 | monday.com Blog<\/title>\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-meeting\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scrum meetings and how to run them effectively in 2026 | monday.com Blog\" \/>\n<meta property=\"og:description\" content=\"A recent survey suggests that our favorite day for meetings is Tuesday, while nearly 50% of us get grumpy about meetings held on a Monday. So the prospect of a project management framework that insists on daily meetings might go down like a bit of a lead balloon. Add to ...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/\" \/>\n<meta property=\"og:site_name\" content=\"monday.com Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-04-27T11:03:10+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-30T09:49:13+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1200\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\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-meeting\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/\"},\"author\":{\"name\":\"monday.com\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/person\\\/002eeffbafc08d763cb24e64dd45cae4\"},\"headline\":\"Scrum meetings and how to run them effectively in 2026\",\"datePublished\":\"2021-04-27T11:03:10+00:00\",\"dateModified\":\"2026-08-30T09:49:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/\"},\"wordCount\":1651,\"publisher\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/scrum-meeting-1.jpg\",\"keywords\":[\"Scrum methodology\"],\"articleSection\":[\"Product development life cycle\",\"Project management\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/\",\"name\":\"Scrum meetings and how to run them effectively in 2026 | monday.com Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/scrum-meeting-1.jpg\",\"datePublished\":\"2021-04-27T11:03:10+00:00\",\"dateModified\":\"2026-08-30T09:49:13+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/#primaryimage\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/scrum-meeting-1.jpg\",\"contentUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/scrum-meeting-1.jpg\",\"width\":2400,\"height\":1200,\"caption\":\"Scrum meetings and how to run them effectively in 2026\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/project-management\\\/scrum-meeting\\\/#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\":\"Scrum meetings and 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 plugin. -->","yoast_head_json":{"title":"Scrum meetings and how to run them effectively in 2026 | monday.com Blog","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-meeting\/","og_locale":"en_US","og_type":"article","og_title":"Scrum meetings and how to run them effectively in 2026 | monday.com Blog","og_description":"A recent survey suggests that our favorite day for meetings is Tuesday, while nearly 50% of us get grumpy about meetings held on a Monday. So the prospect of a project management framework that insists on daily meetings might go down like a bit of a lead balloon. Add to ...","og_url":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/","og_site_name":"monday.com Blog","article_published_time":"2021-04-27T11:03:10+00:00","article_modified_time":"2026-08-30T09:49:13+00:00","og_image":[{"width":2400,"height":1200,"url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting-1.jpg","type":"image\/jpeg"}],"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-meeting\/#article","isPartOf":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/"},"author":{"name":"monday.com","@id":"https:\/\/monday.com\/blog\/#\/schema\/person\/002eeffbafc08d763cb24e64dd45cae4"},"headline":"Scrum meetings and how to run them effectively in 2026","datePublished":"2021-04-27T11:03:10+00:00","dateModified":"2026-08-30T09:49:13+00:00","mainEntityOfPage":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/"},"wordCount":1651,"publisher":{"@id":"https:\/\/monday.com\/blog\/#organization"},"image":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting-1.jpg","keywords":["Scrum methodology"],"articleSection":["Product development life cycle","Project management"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/","url":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/","name":"Scrum meetings and how to run them effectively in 2026 | monday.com Blog","isPartOf":{"@id":"https:\/\/monday.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/#primaryimage"},"image":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting-1.jpg","datePublished":"2021-04-27T11:03:10+00:00","dateModified":"2026-08-30T09:49:13+00:00","breadcrumb":{"@id":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/#primaryimage","url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting-1.jpg","contentUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2021\/04\/scrum-meeting-1.jpg","width":2400,"height":1200,"caption":"Scrum meetings and how to run them effectively in 2026"},{"@type":"BreadcrumbList","@id":"https:\/\/monday.com\/blog\/project-management\/scrum-meeting\/#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":"Scrum meetings and 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\/59623","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=59623"}],"version-history":[{"count":7,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/59623\/revisions"}],"predecessor-version":[{"id":355817,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/59623\/revisions\/355817"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media\/60485"}],"wp:attachment":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media?parent=59623"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/categories?post=59623"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/tags?post=59623"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}