{"id":249550,"date":"2025-09-17T10:23:23","date_gmt":"2025-09-17T10:23:23","guid":{"rendered":"https:\/\/monday.com\/blog\/?p=249550"},"modified":"2026-08-31T00:40:39","modified_gmt":"2026-08-31T05:40:39","slug":"the-different-types-of-scrum-meetings-for-beginners","status":"publish","type":"post","link":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/","title":{"rendered":"What are Scrum meetings, and how to run them effectively in 2025"},"content":{"rendered":"<div class=\"text-block\" id=\"text-block-1\">\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/\" target=\"_blank\" rel=\"noopener\">Scrum meetings<\/a> are structured ceremonies that create alignment, clarity, and continuous improvement for development teams working in sprints. By establishing a predictable cadence, these five key meetings help teams deliver value faster while maintaining focus on business goals and preventing wasted effort.<\/p>\n<p>In this article, you&#8217;ll learn about each scrum ceremony, who should participate in each, and practical tips to make them more effective. We&#8217;ll also show how platforms like monday dev can automate routine updates and visualize progress, letting your team focus on collaboration rather than administration.<\/p>\n<p>Whether you&#8217;re new to Scrum or looking to optimize your existing process, mastering these fundamentals creates a system that supports clear communication, removes blockers, and gives everyone visibility into progress.<\/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 data-section-id=\"wf0zwt\" data-start=\"6327\" data-end=\"6502\"><strong data-start=\"6329\" data-end=\"6365\">A clear cadence drives delivery:<\/strong> Sprint planning, <strong data-start=\"6383\" data-end=\"6455\">daily scrums, sprint reviews, retrospectives, and backlog refinement<\/strong> work together to plan, coordinate, and improve<\/li>\n<li data-section-id=\"1oask5k\" data-start=\"6503\" data-end=\"6637\"><strong data-start=\"6505\" data-end=\"6532\">Timebox every ceremony:<\/strong> Keep <strong data-start=\"6538\" data-end=\"6568\">daily scrums to 15 minutes<\/strong> and set appropriate limits for planning, reviews, and retrospectives<\/li>\n<li data-section-id=\"1kngezw\" data-start=\"6638\" data-end=\"6768\"><strong data-start=\"6640\" data-end=\"6683\">Prioritize problem-solving over status:<\/strong> Ask <strong data-start=\"6688\" data-end=\"6716\">\u201cWhat help do you need?\u201d<\/strong> and move routine status updates outside the meeting<\/li>\n<li data-section-id=\"68lhdt\" data-start=\"6769\" data-end=\"6911\"><strong data-start=\"6771\" data-end=\"6806\">Use monday dev to reduce admin:<\/strong> <strong data-start=\"6807\" data-end=\"6835\">Automate routine updates<\/strong> and <strong data-start=\"6840\" data-end=\"6862\">visualize capacity<\/strong> so teams can spend meeting time on collaboration<\/li>\n<li data-section-id=\"8812af\" data-start=\"6912\" data-end=\"7058\"><strong data-start=\"6914\" data-end=\"6942\">Invite the right people:<\/strong> Match <strong data-start=\"6949\" data-end=\"7012\">product owners, Scrum masters, developers, and stakeholders<\/strong> to the ceremonies where their input is needed<\/li>\n<\/ul>\n<p><\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-3\">\n<h2 class=\"h2 text-block__title\">Scrum meetings at a glance<\/h2>\n<p>Scrum defines 5 events in each sprint. Together, they create the cadence for planning, daily coordination, feedback, and improvement.<\/p>\n<ul>\n<li><strong>Sprint planning:<\/strong> Set the <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-sprint\/\" target=\"_blank\" rel=\"noopener\">scrum sprint<\/a> goal and commit to a realistic <a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-backlog\/\">sprint backlog<\/a>.<\/li>\n<li><strong>Daily scrum (standup):<\/strong> 15-minute sync to align, surface blockers, and adjust the day\u2019s plan.<\/li>\n<li><strong>Sprint review:<\/strong> Demo working software and gather stakeholder feedback to inform the backlog.<\/li>\n<li><strong>Sprint retrospective:<\/strong> Reflect on the process and agree on a few concrete improvements.<\/li>\n<li><strong>Backlog refinement:<\/strong> Continuously clarify, size, and prioritize upcoming work so planning runs smoothly.<\/li>\n<\/ul>\n<ul>\n<li><strong>Sprint:<\/strong> A fixed period (typically 1\u20134 weeks) to deliver a defined slice of value.<\/li>\n<li><strong>Product backlog:<\/strong> The prioritized list of features, enhancements, and fixes for the product.<\/li>\n<li><strong>Sprint backlog:<\/strong> The subset the team commits to for the current sprint, aligned to the sprint goal.<\/li>\n<\/ul>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-4\">\n<h2 class=\"h2 text-block__title\">The 5 Scrum ceremonies<\/h2>\n<p><img src=\"https:\/\/monday.monday.com\/protected_static\/5\/resources\/2316957220\/large-Blog%20image%20-%20sprint%20management.png\" \/><\/p>\n<p>Each Scrum ceremony has a distinct purpose, participants, and timebox. Together, they provide structure without slowing execution.<\/p>\n<h3>1. Sprint planning<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-planning\/\" target=\"_blank\" rel=\"noopener\">Sprint planning<\/a> sets the direction for the next sprint (1\u20134 weeks).<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> Product owner, scrum master, and the full development team.<\/li>\n<li><strong>Agenda:<\/strong> Review priorities, discuss how to deliver them, and agree on a realistic sprint backlog.<\/li>\n<li><strong>Duration:<\/strong> About 2 hours per week of sprint (4 hours for a 2-week sprint).<\/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 to keep the team aligned.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> Development team (others may observe).<\/li>\n<li><strong>Agenda:<\/strong> Each person answers:\n<ul>\n<li>What did I complete yesterday?<\/li>\n<li>What will I work on today?<\/li>\n<li>What\u2019s blocking progress?<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Keep the focus on coordination. Problem-solving happens after with only those involved.<\/p>\n<h3>3. Sprint review<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/what-is-a-sprint-review-definition-goals-and-tips\/\" target=\"_blank\" rel=\"noopener\">Sprint review<\/a> closes the sprint by sharing completed work and gathering feedback.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> <a href=\"https:\/\/monday.com\/blog\/rnd\/heres-how-you-build-a-successful-scrum-team\/\" target=\"_blank\" rel=\"noopener\">Scrum team<\/a> and stakeholders.<\/li>\n<li><strong>Agenda:<\/strong> Demonstrate working software, discuss what was learned, and adjust the backlog.<\/li>\n<li><strong>Duration:<\/strong> Up to 2 hours for a 2-week sprint.<\/li>\n<\/ul>\n<p>Think of this as a collaborative session, not a presentation. The goal is meaningful dialogue about what to build next.<\/p>\n<h3>4. Sprint retrospective<\/h3>\n<p><img src=\"https:\/\/monday.monday.com\/protected_static\/5\/resources\/2316955998\/large-Blog%20image%20-%20Retro.png\" \/><\/p>\n<p>This <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-retrospective-what-it-is-and-how-it-works\/\" target=\"_blank\" rel=\"noopener\">agile retrospective<\/a> is your team&#8217;s chance to reflect on how you work together.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> Entire Scrum team.<\/li>\n<li><strong>Agenda:<\/strong>\n<ul>\n<li>What went well?<\/li>\n<li>What needs improvement?<\/li>\n<li>What will we try next sprint?<\/li>\n<\/ul>\n<\/li>\n<li><strong>Duration:<\/strong> About 1.5 hours for a 2-week sprint.<\/li>\n<\/ul>\n<p>The scrum master facilitates, ensuring open conversation. With monday dev, 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\" rel=\"noopener\">scrum sprints<\/a> and measure which changes 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\" rel=\"noopener\">backlog grooming<\/a>) keeps upcoming work clear and ready.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> Product owner and development team.<\/li>\n<li><strong>Agenda:<\/strong> Clarify requirements, size effort, and break down large items.<\/li>\n<li><strong>Duration:<\/strong> 1\u20132 hours per week.<\/li>\n<\/ul>\n<p>A well-refined backlog makes sprint planning faster and commitments more reliable.<\/p>\n<a class=\"cta-button blue-button\" aria-label=\"Try monday dev\" href=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_blank\">Try monday dev<\/a>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-5\">\n<h2 class=\"h2 text-block__title\">Who participates and why it matters<\/h2>\n<p>Each Scrum role brings specific value to the ceremonies. Having the right people in the room keeps meetings purposeful and outcomes clear.<\/p>\n<ul>\n<li><strong>Product owner<\/strong>: Owns the product vision and backlog. They <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-guide\/\" target=\"_blank\" rel=\"noopener\">guide priorities<\/a> during sprint planning, adjust the backlog after sprint reviews, and prepare upcoming work during backlog refinement.<\/li>\n<li><strong>Scrum master<\/strong>: Facilitates ceremonies, removes blockers, and ensures the team follows Scrum principles. Their role is to keep meetings on track and create a safe environment for open contribution.<\/li>\n<li><strong>Development team<\/strong>: Builds the product. They run daily scrums, estimate and commit during planning, demo completed work in reviews, and suggest improvements in retrospectives.<\/li>\n<li><strong>Stakeholders<\/strong>: Join sprint reviews to provide feedback and align direction with business goals. They step back from other ceremonies to keep the team focused.<\/li>\n<\/ul>\n<p>For larger organizations, a <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-of-scrums\/\" target=\"_blank\" rel=\"noopener\">scrum of scrums<\/a> can coordinate across multiple teams, ensuring alignment at scale. With a platform like monday dev, leaders get portfolio-level visibility without disrupting daily execution.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-6\">\n<h2 class=\"h2 text-block__title\">How to structure each scrum meeting<\/h2>\n<p>Even well-intentioned <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-ceremonies\/\">Agile ceremonies<\/a> can drift off course without clear guardrails. Setting expectations for time, agenda, and format helps teams get the most out of every session.<\/p>\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. For a 2-week sprint, plan on about:<\/p>\n<ul>\n<li>Sprint planning: 4 hours<\/li>\n<li>Daily scrum: 15 minutes<\/li>\n<li>Sprint review: 2 hours<\/li>\n<li>Sprint retrospective: 1.5 hours<\/li>\n<\/ul>\n<p>Teams working in longer or shorter sprints can adjust, but the principle remains \u2014 use timeboxes to respect people\u2019s attention.<\/p>\n<h3>Agenda and format<\/h3>\n<p>A predictable structure makes it easier for participants to contribute meaningfully.<\/p>\n<ul>\n<li>Sprint planning starts with the goal, then backlog selection, task breakdown, and commitment.<\/li>\n<li>Daily scrums follow the three-question format, so updates are consistent.<\/li>\n<li>Sprint reviews begin with working software and end with stakeholder discussion.<\/li>\n<li>Retrospectives often use \u201cStart, Stop, Continue\u201d or similar techniques to surface insights.<\/li>\n<\/ul>\n<p><strong>Get it now: <\/strong><a href=\"https:\/\/monday.com\/blog\/project-management\/meeting-agenda-template\/\">Meeting agenda template<\/a><\/p>\n<h3>Supporting remote or hybrid teams<\/h3>\n<p>Distributed work doesn\u2019t change the ceremonies \u2014 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. monday dev provides shared sprint boards, asynchronous updates, and real-time visibility, making it easier for distributed teams to stay aligned without losing momentum.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-7\">\n<h2 class=\"h2 text-block__title\">What development teams say about monday dev<\/h2>\n<p class=\"PDq2pG_selectionAnchorContainer\" data-start=\"2549\" data-end=\"2778\">These practices become easier to maintain when planning, progress, and follow-up actions stay visible between meetings. Teams using monday dev have applied that approach across their development workflows, as these examples show.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-8\">\n<h2 class=\"h2 text-block__title\">7 tips for effective agile development meetings<\/h2>\n<p><img src=\"https:\/\/monday.monday.com\/protected_static\/5\/resources\/2316957614\/large-Blog%20image%20-%20Agile%20nisights.png\" \/><\/p>\n<p>Scrum meetings work best when teams apply a few practical habits. These tips help meetings feel valuable rather than routine.<\/p>\n<h3>1. Set expectations early<\/h3>\n<p class=\"PDq2pG_selectionAnchorContainer\" data-start=\"4546\" data-end=\"4787\">Share the purpose and prep work before each ceremony so people arrive ready to contribute. Keeping sprint goals, backlog priorities, and ownership visible in monday dev also gives participants the context they need before the meeting starts.<\/p>\n<h3>2. Respect the clock<\/h3>\n<p>Stay within the timebox. Capture off-topic items in a parking lot instead of derailing the session.<\/p>\n<h3>3. Encourage team ownership<\/h3>\n<p>Daily scrums belong to developers, not managers. Retrospectives work only if everyone feels safe to contribute. This helps bridge <a href=\"https:\/\/monday.com\/lp\/world-of-work-report\" target=\"_blank\" rel=\"noopener\">a common perception gap<\/a> where leaders often overestimate the sense of ownership felt by their teams.<\/p>\n<h3>4. Shift from status to support<\/h3>\n<p>Move routine status reporting outside the meeting so the team can use the time to discuss dependencies, blockers, and where support is needed. When progress is already visible on a shared monday dev sprint board, the Daily Scrum doesn&#8217;t need to become a round-robin status report.<\/p>\n<h3>5. Resolve blockers with urgency<\/h3>\n<p>When an impediment comes up, assign responsibility and track it visibly until it\u2019s closed. Teams can also flag blocked work in monday dev, assign ownership, and keep the issue visible after the meeting until it&#8217;s resolved.<\/p>\n<h3>6. Use tools that lighten the load<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-tools\/\" target=\"_blank\" rel=\"noopener\">Scrum tools<\/a> support teams that use the Scrum framework. A platform like monday dev uses automation to reduce manual updates, surface trends, and highlight potential risks before they stall progress.<\/p>\n<h3>7. Keep experimenting<\/h3>\n<p>Teams evolve. Adjust formats, timing, and facilitation styles based on what delivers the most value. Retrospectives are a good place to check whether your ceremonies still work.<\/p>\n\n<\/div>\n<div class=\"text-block\" id=\"text-block-9\">\n<h2 class=\"h2 text-block__title\">Run smarter, faster ceremonies with monday dev<\/h2>\n<p>monday dev brings sprint planning, backlog priorities, capacity, progress, and retrospective actions into the same workflow, giving teams a shared view of what\u2019s planned, what\u2019s moving, and what needs attention.<\/p>\n<h3 class=\"PDq2pG_selectionAnchorContainer\" data-section-id=\"177mb20\" data-start=\"7458\" data-end=\"7496\">Plan sprints with capacity in view<\/h3>\n<p data-start=\"7500\" data-end=\"7649\">Visual boards bring team capacity, backlog priorities, and sprint goals together so teams can make more realistic commitments during sprint planning.<\/p>\n<h3 data-section-id=\"1mx252v\" data-start=\"7651\" data-end=\"7682\">Keep daily progress visible<\/h3>\n<p data-start=\"7686\" data-end=\"7835\">As work moves through the sprint, monday dev tracks progress in the same workflow, while automations can handle routine notifications and follow-ups.<\/p>\n<h3 data-section-id=\"t8aefm\" data-start=\"7837\" data-end=\"7875\">Bring evidence into sprint reviews<\/h3>\n<p data-start=\"7879\" data-end=\"8023\">Teams can connect development tools and work data so completed work, progress, and stakeholder feedback are available when reviewing the sprint.<\/p>\n<h3 data-section-id=\"1199hze\" data-start=\"8025\" data-end=\"8072\">Track retrospective actions between sprints<\/h3>\n<p data-start=\"8076\" data-end=\"8262\">Improvement ideas don&#8217;t need to disappear when the retrospective ends. Teams can assign action items, track them across sprints, and see whether agreed changes were actually implemented.<\/p>\n<h3 data-section-id=\"umsyow\" data-start=\"8264\" data-end=\"8290\">Keep the backlog ready<\/h3>\n<p data-start=\"8294\" data-end=\"8431\">Teams can organize, prioritize, and refine upcoming work so backlog items are clearer before they reach the next sprint planning session.<\/p>\n<p>By keeping sprint goals, backlog items, capacity, blockers, and improvement actions visible in monday dev, teams can use their Scrum meetings to make decisions and resolve issues rather than reconstructing information that already exists elsewhere.<\/p>\n<a class=\"cta-button blue-button\" aria-label=\"Try monday dev\" href=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_blank\">Try monday dev<\/a>\n<div class=\"accordion faq\" id=\"faq-scrum-meetings\">\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-scrum-meetings\" href=\"#q-scrum-meetings-1\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What are the 5 scrum values?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-scrum-meetings-1\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>The <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-values\/\" target=\"_blank\">5 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-scrum-meetings\" href=\"#q-scrum-meetings-2\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What is a scrum meeting?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-scrum-meetings-2\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>A Scrum meeting is any of the recurring ceremonies in the Scrum framework. These meetings keep the team aligned on goals, progress, and improvements during each sprint.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-scrum-meetings\" href=\"#q-scrum-meetings-3\" 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-scrum-meetings-3\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>The difference between agile and Scrum meetings is that agile is a broad philosophy that can be applied through several frameworks, such as Kanban 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-scrum-meetings\" href=\"#q-scrum-meetings-4\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">How long should sprint planning take?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-scrum-meetings-4\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>Sprint planning is timeboxed to about 2 hours for each week of the sprint. A 2-week sprint typically requires around 4 hours. The meeting ends when the team agrees on a goal and the sprint backlog, even if that happens earlier.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-scrum-meetings\" href=\"#q-scrum-meetings-5\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">Who should attend sprint retrospective meetings?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-scrum-meetings-5\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>Sprint retrospective meetings should include the entire Scrum team \u2014 the product owner, scrum master, and all development team members. Stakeholders generally sit this one out to ensure 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-scrum-meetings\" href=\"#q-scrum-meetings-6\" aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What are common Scrum metrics?        \n          \n        \n      <\/h3>\n    <\/a>\n    <div id=\"q-scrum-meetings-6\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>Scrum teams often track metrics such as velocity (work completed per sprint), burndown charts (remaining work vs. time), lead time (how long it takes an item to move from backlog to completion), and defect rates. These <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-metrics\/\" target=\"_blank\">Scrum metrics<\/a> provide insight into delivery speed, predictability, and quality without turning Scrum into a performance scorecard.<\/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 5 scrum values?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The <a href=\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/scrum-values\\\/\" target=\"_blank\">5 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 a scrum meeting?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>A Scrum meeting is any of the recurring ceremonies in the Scrum framework. These meetings keep the team aligned on goals, progress, and improvements during each sprint.\\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>The difference between agile and Scrum meetings is that agile is a broad philosophy that can be applied through several frameworks, such as 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\": \"How long should sprint planning take?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Sprint planning is timeboxed to about 2 hours for each week of the sprint. A 2-week sprint typically requires around 4 hours. The meeting ends when the team agrees on a goal and the sprint backlog, even if that happens earlier.\\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 \\u2014 the product owner, scrum master, and all development team members. Stakeholders generally sit this one out to ensure the team feels comfortable discussing what to improve.\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What are common Scrum metrics?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Scrum teams often track metrics such as velocity (work completed per sprint), burndown charts (remaining work vs. time), lead time (how long it takes an item to move from backlog to completion), and defect rates. These <a href=\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/scrum-metrics\\\/\" target=\"_blank\">Scrum metrics provide insight into delivery speed, predictability, and quality without turning Scrum into a performance scorecard.\\n\"\n            }\n        }\n    ]\n}<\/div>\n\n\n<\/div>","protected":false},"excerpt":{"rendered":"","protected":false},"author":310,"featured_media":237002,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"pages\/cornerstone-primary.php","format":"standard","meta":{"_acf_changed":false,"monday_item_id":18008515875,"monday_board_id":0,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[13911],"tags":[],"class_list":["post-249550","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-rnd"],"acf":{"sections":[{"acf_fc_layout":"content_1","blocks":[{"main_heading":"","content_block":[{"acf_fc_layout":"text","content":"<p><a href=\"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/\" target=\"_blank\" rel=\"noopener\">Scrum meetings<\/a> are structured ceremonies that create alignment, clarity, and continuous improvement for development teams working in sprints. By establishing a predictable cadence, these five key meetings help teams deliver value faster while maintaining focus on business goals and preventing wasted effort.<\/p>\n<p>In this article, you&#8217;ll learn about each scrum ceremony, who should participate in each, and practical tips to make them more effective. We&#8217;ll also show how platforms like monday dev can automate routine updates and visualize progress, letting your team focus on collaboration rather than administration.<\/p>\n<p>Whether you&#8217;re new to Scrum or looking to optimize your existing process, mastering these fundamentals creates a system that supports clear communication, removes blockers, and gives everyone visibility into progress.<\/p>\n"}]},{"main_heading":"Key takeaways","content_block":[{"acf_fc_layout":"text","content":"<ul>\n<li data-section-id=\"wf0zwt\" data-start=\"6327\" data-end=\"6502\"><strong data-start=\"6329\" data-end=\"6365\">A clear cadence drives delivery:<\/strong> Sprint planning, <strong data-start=\"6383\" data-end=\"6455\">daily scrums, sprint reviews, retrospectives, and backlog refinement<\/strong> work together to plan, coordinate, and improve<\/li>\n<li data-section-id=\"1oask5k\" data-start=\"6503\" data-end=\"6637\"><strong data-start=\"6505\" data-end=\"6532\">Timebox every ceremony:<\/strong> Keep <strong data-start=\"6538\" data-end=\"6568\">daily scrums to 15 minutes<\/strong> and set appropriate limits for planning, reviews, and retrospectives<\/li>\n<li data-section-id=\"1kngezw\" data-start=\"6638\" data-end=\"6768\"><strong data-start=\"6640\" data-end=\"6683\">Prioritize problem-solving over status:<\/strong> Ask <strong data-start=\"6688\" data-end=\"6716\">\u201cWhat help do you need?\u201d<\/strong> and move routine status updates outside the meeting<\/li>\n<li data-section-id=\"68lhdt\" data-start=\"6769\" data-end=\"6911\"><strong data-start=\"6771\" data-end=\"6806\">Use monday dev to reduce admin:<\/strong> <strong data-start=\"6807\" data-end=\"6835\">Automate routine updates<\/strong> and <strong data-start=\"6840\" data-end=\"6862\">visualize capacity<\/strong> so teams can spend meeting time on collaboration<\/li>\n<li data-section-id=\"8812af\" data-start=\"6912\" data-end=\"7058\"><strong data-start=\"6914\" data-end=\"6942\">Invite the right people:<\/strong> Match <strong data-start=\"6949\" data-end=\"7012\">product owners, Scrum masters, developers, and stakeholders<\/strong> to the ceremonies where their input is needed<\/li>\n<\/ul>\n<p><iframe loading=\"lazy\" title=\"Scrum meetings: The complete guide [2025]\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube.com\/embed\/fZ_JYj_LaS4?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/p>\n"}]},{"main_heading":"Scrum meetings at a glance","content_block":[{"acf_fc_layout":"text","content":"<p>Scrum defines 5 events in each sprint. Together, they create the cadence for planning, daily coordination, feedback, and improvement.<\/p>\n<ul>\n<li><strong>Sprint planning:<\/strong> Set the <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-sprint\/\" target=\"_blank\" rel=\"noopener\">scrum sprint<\/a> goal and commit to a realistic <a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-backlog\/\">sprint backlog<\/a>.<\/li>\n<li><strong>Daily scrum (standup):<\/strong> 15-minute sync to align, surface blockers, and adjust the day\u2019s plan.<\/li>\n<li><strong>Sprint review:<\/strong> Demo working software and gather stakeholder feedback to inform the backlog.<\/li>\n<li><strong>Sprint retrospective:<\/strong> Reflect on the process and agree on a few concrete improvements.<\/li>\n<li><strong>Backlog refinement:<\/strong> Continuously clarify, size, and prioritize upcoming work so planning runs smoothly.<\/li>\n<\/ul>\n<ul>\n<li><strong>Sprint:<\/strong> A fixed period (typically 1\u20134 weeks) to deliver a defined slice of value.<\/li>\n<li><strong>Product backlog:<\/strong> The prioritized list of features, enhancements, and fixes for the product.<\/li>\n<li><strong>Sprint backlog:<\/strong> The subset the team commits to for the current sprint, aligned to the sprint goal.<\/li>\n<\/ul>\n"}]},{"main_heading":"The 5 Scrum ceremonies","content_block":[{"acf_fc_layout":"text","content":"<p><img decoding=\"async\" src=\"https:\/\/monday.monday.com\/protected_static\/5\/resources\/2316957220\/large-Blog%20image%20-%20sprint%20management.png\" \/><\/p>\n<p>Each Scrum ceremony has a distinct purpose, participants, and timebox. Together, they provide structure without slowing execution.<\/p>\n<h3>1. Sprint planning<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/sprint-planning\/\" target=\"_blank\" rel=\"noopener\">Sprint planning<\/a> sets the direction for the next sprint (1\u20134 weeks).<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> Product owner, scrum master, and the full development team.<\/li>\n<li><strong>Agenda:<\/strong> Review priorities, discuss how to deliver them, and agree on a realistic sprint backlog.<\/li>\n<li><strong>Duration:<\/strong> About 2 hours per week of sprint (4 hours for a 2-week sprint).<\/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 to keep the team aligned.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> Development team (others may observe).<\/li>\n<li><strong>Agenda:<\/strong> Each person answers:\n<ul>\n<li>What did I complete yesterday?<\/li>\n<li>What will I work on today?<\/li>\n<li>What\u2019s blocking progress?<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Keep the focus on coordination. Problem-solving happens after with only those involved.<\/p>\n<h3>3. Sprint review<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/what-is-a-sprint-review-definition-goals-and-tips\/\" target=\"_blank\" rel=\"noopener\">Sprint review<\/a> closes the sprint by sharing completed work and gathering feedback.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> <a href=\"https:\/\/monday.com\/blog\/rnd\/heres-how-you-build-a-successful-scrum-team\/\" target=\"_blank\" rel=\"noopener\">Scrum team<\/a> and stakeholders.<\/li>\n<li><strong>Agenda:<\/strong> Demonstrate working software, discuss what was learned, and adjust the backlog.<\/li>\n<li><strong>Duration:<\/strong> Up to 2 hours for a 2-week sprint.<\/li>\n<\/ul>\n<p>Think of this as a collaborative session, not a presentation. The goal is meaningful dialogue about what to build next.<\/p>\n<h3>4. Sprint retrospective<\/h3>\n<p><img decoding=\"async\" src=\"https:\/\/monday.monday.com\/protected_static\/5\/resources\/2316955998\/large-Blog%20image%20-%20Retro.png\" \/><\/p>\n<p>This <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-retrospective-what-it-is-and-how-it-works\/\" target=\"_blank\" rel=\"noopener\">agile retrospective<\/a> is your team&#8217;s chance to reflect on how you work together.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> Entire Scrum team.<\/li>\n<li><strong>Agenda:<\/strong>\n<ul>\n<li>What went well?<\/li>\n<li>What needs improvement?<\/li>\n<li>What will we try next sprint?<\/li>\n<\/ul>\n<\/li>\n<li><strong>Duration:<\/strong> About 1.5 hours for a 2-week sprint.<\/li>\n<\/ul>\n<p>The scrum master facilitates, ensuring open conversation. With monday dev, 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\" rel=\"noopener\">scrum sprints<\/a> and measure which changes 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\" rel=\"noopener\">backlog grooming<\/a>) keeps upcoming work clear and ready.<\/p>\n<ul>\n<li><strong>Who attends:<\/strong> Product owner and development team.<\/li>\n<li><strong>Agenda:<\/strong> Clarify requirements, size effort, and break down large items.<\/li>\n<li><strong>Duration:<\/strong> 1\u20132 hours per week.<\/li>\n<\/ul>\n<p>A well-refined backlog makes sprint planning faster and commitments more reliable.<\/p>\n<a class=\"cta-button blue-button\" aria-label=\"Try monday dev\" href=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_blank\">Try monday dev<\/a>\n"}]},{"main_heading":"Who participates and why it matters","content_block":[{"acf_fc_layout":"text","content":"<p>Each Scrum role brings specific value to the ceremonies. Having the right people in the room keeps meetings purposeful and outcomes clear.<\/p>\n<ul>\n<li><strong>Product owner<\/strong>: Owns the product vision and backlog. They <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-guide\/\" target=\"_blank\" rel=\"noopener\">guide priorities<\/a> during sprint planning, adjust the backlog after sprint reviews, and prepare upcoming work during backlog refinement.<\/li>\n<li><strong>Scrum master<\/strong>: Facilitates ceremonies, removes blockers, and ensures the team follows Scrum principles. Their role is to keep meetings on track and create a safe environment for open contribution.<\/li>\n<li><strong>Development team<\/strong>: Builds the product. They run daily scrums, estimate and commit during planning, demo completed work in reviews, and suggest improvements in retrospectives.<\/li>\n<li><strong>Stakeholders<\/strong>: Join sprint reviews to provide feedback and align direction with business goals. They step back from other ceremonies to keep the team focused.<\/li>\n<\/ul>\n<p>For larger organizations, a <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-of-scrums\/\" target=\"_blank\" rel=\"noopener\">scrum of scrums<\/a> can coordinate across multiple teams, ensuring alignment at scale. With a platform like monday dev, leaders get portfolio-level visibility without disrupting daily execution.<\/p>\n"}]},{"main_heading":"How to structure each scrum meeting","content_block":[{"acf_fc_layout":"text","content":"<p>Even well-intentioned <a href=\"https:\/\/monday.com\/blog\/rnd\/agile-ceremonies\/\">Agile ceremonies<\/a> can drift off course without clear guardrails. Setting expectations for time, agenda, and format helps teams get the most out of every session.<\/p>\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. For a 2-week sprint, plan on about:<\/p>\n<ul>\n<li>Sprint planning: 4 hours<\/li>\n<li>Daily scrum: 15 minutes<\/li>\n<li>Sprint review: 2 hours<\/li>\n<li>Sprint retrospective: 1.5 hours<\/li>\n<\/ul>\n<p>Teams working in longer or shorter sprints can adjust, but the principle remains \u2014 use timeboxes to respect people\u2019s attention.<\/p>\n<h3>Agenda and format<\/h3>\n<p>A predictable structure makes it easier for participants to contribute meaningfully.<\/p>\n<ul>\n<li>Sprint planning starts with the goal, then backlog selection, task breakdown, and commitment.<\/li>\n<li>Daily scrums follow the three-question format, so updates are consistent.<\/li>\n<li>Sprint reviews begin with working software and end with stakeholder discussion.<\/li>\n<li>Retrospectives often use \u201cStart, Stop, Continue\u201d or similar techniques to surface insights.<\/li>\n<\/ul>\n<p><strong>Get it now: <\/strong><a href=\"https:\/\/monday.com\/blog\/project-management\/meeting-agenda-template\/\">Meeting agenda template<\/a><\/p>\n<h3>Supporting remote or hybrid teams<\/h3>\n<p>Distributed work doesn\u2019t change the ceremonies \u2014 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. monday dev provides shared sprint boards, asynchronous updates, and real-time visibility, making it easier for distributed teams to stay aligned without losing momentum.<\/p>\n"}]},{"main_heading":"What development teams say about monday dev","content_block":[{"acf_fc_layout":"text","content":"<p class=\"PDq2pG_selectionAnchorContainer\" data-start=\"2549\" data-end=\"2778\">These practices become easier to maintain when planning, progress, and follow-up actions stay visible between meetings. Teams using monday dev have applied that approach across their development workflows, as these examples show.<\/p>\n"},{"acf_fc_layout":"testimonials_carousel","testimonial_collection_select":14085,"tc_slide_to_show":"2"}]},{"main_heading":"7 tips for effective agile development meetings","content_block":[{"acf_fc_layout":"text","content":"<p><img decoding=\"async\" src=\"https:\/\/monday.monday.com\/protected_static\/5\/resources\/2316957614\/large-Blog%20image%20-%20Agile%20nisights.png\" \/><\/p>\n<p>Scrum meetings work best when teams apply a few practical habits. These tips help meetings feel valuable rather than routine.<\/p>\n<h3>1. Set expectations early<\/h3>\n<p class=\"PDq2pG_selectionAnchorContainer\" data-start=\"4546\" data-end=\"4787\">Share the purpose and prep work before each ceremony so people arrive ready to contribute. Keeping sprint goals, backlog priorities, and ownership visible in monday dev also gives participants the context they need before the meeting starts.<\/p>\n<h3>2. Respect the clock<\/h3>\n<p>Stay within the timebox. Capture off-topic items in a parking lot instead of derailing the session.<\/p>\n<h3>3. Encourage team ownership<\/h3>\n<p>Daily scrums belong to developers, not managers. Retrospectives work only if everyone feels safe to contribute. This helps bridge <a href=\"https:\/\/monday.com\/lp\/world-of-work-report\" target=\"_blank\" rel=\"noopener\">a common perception gap<\/a> where leaders often overestimate the sense of ownership felt by their teams.<\/p>\n<h3>4. Shift from status to support<\/h3>\n<p>Move routine status reporting outside the meeting so the team can use the time to discuss dependencies, blockers, and where support is needed. When progress is already visible on a shared monday dev sprint board, the Daily Scrum doesn&#8217;t need to become a round-robin status report.<\/p>\n<h3>5. Resolve blockers with urgency<\/h3>\n<p>When an impediment comes up, assign responsibility and track it visibly until it\u2019s closed. Teams can also flag blocked work in monday dev, assign ownership, and keep the issue visible after the meeting until it&#8217;s resolved.<\/p>\n<h3>6. Use tools that lighten the load<\/h3>\n<p><a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-tools\/\" target=\"_blank\" rel=\"noopener\">Scrum tools<\/a> support teams that use the Scrum framework. A platform like monday dev uses automation to reduce manual updates, surface trends, and highlight potential risks before they stall progress.<\/p>\n<h3>7. Keep experimenting<\/h3>\n<p>Teams evolve. Adjust formats, timing, and facilitation styles based on what delivers the most value. Retrospectives are a good place to check whether your ceremonies still work.<\/p>\n"}]},{"main_heading":"Run smarter, faster ceremonies with monday dev","content_block":[{"acf_fc_layout":"text","content":"<p>monday dev brings sprint planning, backlog priorities, capacity, progress, and retrospective actions into the same workflow, giving teams a shared view of what\u2019s planned, what\u2019s moving, and what needs attention.<\/p>\n<h3 class=\"PDq2pG_selectionAnchorContainer\" data-section-id=\"177mb20\" data-start=\"7458\" data-end=\"7496\">Plan sprints with capacity in view<\/h3>\n<p data-start=\"7500\" data-end=\"7649\">Visual boards bring team capacity, backlog priorities, and sprint goals together so teams can make more realistic commitments during sprint planning.<\/p>\n<h3 data-section-id=\"1mx252v\" data-start=\"7651\" data-end=\"7682\">Keep daily progress visible<\/h3>\n<p data-start=\"7686\" data-end=\"7835\">As work moves through the sprint, monday dev tracks progress in the same workflow, while automations can handle routine notifications and follow-ups.<\/p>\n<h3 data-section-id=\"t8aefm\" data-start=\"7837\" data-end=\"7875\">Bring evidence into sprint reviews<\/h3>\n<p data-start=\"7879\" data-end=\"8023\">Teams can connect development tools and work data so completed work, progress, and stakeholder feedback are available when reviewing the sprint.<\/p>\n<h3 data-section-id=\"1199hze\" data-start=\"8025\" data-end=\"8072\">Track retrospective actions between sprints<\/h3>\n<p data-start=\"8076\" data-end=\"8262\">Improvement ideas don&#8217;t need to disappear when the retrospective ends. Teams can assign action items, track them across sprints, and see whether agreed changes were actually implemented.<\/p>\n<h3 data-section-id=\"umsyow\" data-start=\"8264\" data-end=\"8290\">Keep the backlog ready<\/h3>\n<p data-start=\"8294\" data-end=\"8431\">Teams can organize, prioritize, and refine upcoming work so backlog items are clearer before they reach the next sprint planning session.<\/p>\n<p>By keeping sprint goals, backlog items, capacity, blockers, and improvement actions visible in monday dev, teams can use their Scrum meetings to make decisions and resolve issues rather than reconstructing information that already exists elsewhere.<\/p>\n<a class=\"cta-button blue-button\" aria-label=\"Try monday dev\" href=\"https:\/\/auth.monday.com\/p\/software\/users\/sign_up_new?origin=hp_fullbg_page_header#soft_signup_from_step\" target=\"_blank\">Try monday dev<\/a>\n<div class=\"accordion faq\" id=\"faq-scrum-meetings\">\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-scrum-meetings\" href=\"#q-scrum-meetings-1\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What are the 5 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-scrum-meetings-1\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>The <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-values\/\" target=\"_blank\">5 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-scrum-meetings\" href=\"#q-scrum-meetings-2\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What is a scrum meeting?        <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-scrum-meetings-2\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>A Scrum meeting is any of the recurring ceremonies in the Scrum framework. These meetings keep the team aligned on goals, progress, and improvements during each sprint.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-scrum-meetings\" href=\"#q-scrum-meetings-3\"\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-scrum-meetings-3\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>The difference between agile and Scrum meetings is that agile is a broad philosophy that can be applied through several frameworks, such as Kanban 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-scrum-meetings\" href=\"#q-scrum-meetings-4\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">How long should sprint planning take?        <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-scrum-meetings-4\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>Sprint planning is timeboxed to about 2 hours for each week of the sprint. A 2-week sprint typically requires around 4 hours. The meeting ends when the team agrees on a goal and the sprint backlog, even if that happens earlier.<\/p>\n    <\/div>\n  <\/div>\n    <div class=\"accordion__item\">\n    <a class=\"accordion__button d-block\" data-toggle=\"collapse\" data-parent=\"#faq-scrum-meetings\" href=\"#q-scrum-meetings-5\"\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-scrum-meetings-5\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>Sprint retrospective meetings should include the entire Scrum team \u2014 the product owner, scrum master, and all development team members. Stakeholders generally sit this one out to ensure 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-scrum-meetings\" href=\"#q-scrum-meetings-6\"\n      aria-expanded=\"false\">\n      <h3 class=\"accordion__question\">What are common Scrum metrics?        <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-scrum-meetings-6\" class=\"accordion__answer collapse collapse--md\" data-parent=\"#faq-scrum-meetings\">\n      <p>Scrum teams often track metrics such as velocity (work completed per sprint), burndown charts (remaining work vs. time), lead time (how long it takes an item to move from backlog to completion), and defect rates. These <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-metrics\/\" target=\"_blank\">Scrum metrics<\/a> provide insight into delivery speed, predictability, and quality without turning Scrum into a performance scorecard.<\/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 5 scrum values?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>The <a href=\\\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/scrum-values\\\/\\\" target=\\\"_blank\\\">5 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 a scrum meeting?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>A Scrum meeting is any of the recurring ceremonies in the Scrum framework. These meetings keep the team aligned on goals, progress, and improvements during each sprint.<\\\/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>The difference between agile and Scrum meetings is that agile is a broad philosophy that can be applied through several frameworks, such as Kanban 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\": \"How long should sprint planning take?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Sprint planning is timeboxed to about 2 hours for each week of the sprint. A 2-week sprint typically requires around 4 hours. The meeting ends when the team agrees on a goal and the sprint backlog, even if that happens earlier.<\\\/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 \\u2014 the product owner, scrum master, and all development team members. Stakeholders generally sit this one out to ensure the team feels comfortable discussing what to improve.<\\\/p>\\n\"\n            }\n        },\n        {\n            \"@type\": \"Question\",\n            \"name\": \"What are common Scrum metrics?\",\n            \"acceptedAnswer\": {\n                \"@type\": \"Answer\",\n                \"text\": \"<p>Scrum teams often track metrics such as velocity (work completed per sprint), burndown charts (remaining work vs. time), lead time (how long it takes an item to move from backlog to completion), and defect rates. These <a href=\\\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/scrum-metrics\\\/\\\" target=\\\"_blank\\\">Scrum metrics<\\\/a> provide insight into delivery speed, predictability, and quality without turning Scrum into a performance scorecard.<\\\/p>\\n\"\n            }\n        }\n    ]\n}<\/script><\/div>\n\n"}]}]}],"faqs":[{"faq_title":"FAQs","faq_shortcode":"scrum-meetings","faq":[{"question":"What are the 5 scrum values?","answer":"<p>The <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-values\/\" target=\"_blank\">5 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 a scrum meeting?","answer":"<p>A Scrum meeting is any of the recurring ceremonies in the Scrum framework. These meetings keep the team aligned on goals, progress, and improvements during each sprint.<\/p>\n"},{"question":"What is the difference between agile and Scrum meetings?","answer":"<p>The difference between agile and Scrum meetings is that agile is a broad philosophy that can be applied through several frameworks, such as Kanban or Extreme Programming. Scrum meetings are specific to the Scrum framework and follow defined roles, timeboxes, and structures.<\/p>\n"},{"question":"How long should sprint planning take?","answer":"<p>Sprint planning is timeboxed to about 2 hours for each week of the sprint. A 2-week sprint typically requires around 4 hours. The meeting ends when the team agrees on a goal and the sprint backlog, even if that happens earlier.<\/p>\n"},{"question":"Who should attend sprint retrospective meetings?","answer":"<p>Sprint retrospective meetings should include the entire Scrum team \u2014 the product owner, scrum master, and all development team members. Stakeholders generally sit this one out to ensure the team feels comfortable discussing what to improve.<\/p>\n"},{"question":"What are common Scrum metrics?","answer":"<p>Scrum teams often track metrics such as velocity (work completed per sprint), burndown charts (remaining work vs. time), lead time (how long it takes an item to move from backlog to completion), and defect rates. These <a href=\"https:\/\/monday.com\/blog\/rnd\/scrum-metrics\/\" target=\"_blank\">Scrum metrics<\/a> provide insight into delivery speed, predictability, and quality without turning Scrum into a performance scorecard.<\/p>\n"}]}],"parse_from_google_doc":false,"lobby_image":false,"post_thumbnail_title":"","hide_post_info":false,"hide_bottom_cta":false,"hide_from_blog":false,"landing_page_layout":false,"hide_time_to_read":false,"sidebar_color_banner":"","custom_tags":false,"disclaimer":"","cornerstone_hero_cta_override":{"label":"","url":""},"show_contact_sales_button":"default","cluster":"","display_dates":"default","featured_image_link":"","custom_header_banner":false,"activate_cta_banner":false,"banner_url":"","main_text_banner":"","sub_title_banner":"","sub_title_banner_second":"","banner_button_text":"","below_banner_line":"","use_customized_cta":false,"custom_schema_code":"<script type=\"application\/ld+json\">\r\n{\r\n  \"@context\": \"https:\/\/schema.org\",\r\n  \"@type\": \"HowTo\",\r\n  \"name\": \"7 tips for effective agile development meetings\",\r\n  \"step\": [\r\n    {\r\n      \"@type\": \"HowToStep\",\r\n      \"position\": 1,\r\n      \"name\": \"Set expectations early\",\r\n      \"text\": \"Share the purpose and prep work before each ceremony. People arrive ready, and the discussion moves faster.\"\r\n    },\r\n    {\r\n      \"@type\": \"HowToStep\",\r\n      \"position\": 2,\r\n      \"name\": \"Respect the clock\",\r\n      \"text\": \"Stay within the timebox. Capture off-topic items in a parking lot instead of derailing the session.\"\r\n    },\r\n    {\r\n      \"@type\": \"HowToStep\",\r\n      \"position\": 3,\r\n      \"name\": \"Encourage team ownership\",\r\n      \"text\": \"Daily scrums belong to developers, not managers. Retrospectives work only if everyone feels safe to contribute.\"\r\n    },\r\n    {\r\n      \"@type\": \"HowToStep\",\r\n      \"position\": 4,\r\n      \"name\": \"Shift from status to support\",\r\n      \"text\": \"Replace \u201cWhat\u2019s your status?\u201d with \u201cWhat do you need help with?\u201d to spark collaboration instead of reporting.\"\r\n    },\r\n    {\r\n      \"@type\": \"HowToStep\",\r\n      \"position\": 5,\r\n      \"name\": \"Resolve blockers with urgency\",\r\n      \"text\": \"When an impediment comes up, assign responsibility and track it visibly until it\u2019s closed. The scrum master should work on removing obstacles between meetings, not just collect them during ceremonies.\"\r\n    },\r\n    {\r\n      \"@type\": \"HowToStep\",\r\n      \"position\": 6,\r\n      \"name\": \"Use tools that lighten the load\",\r\n      \"text\": \"A platform like monday dev uses automation to reduce manual updates, surface trends, and highlight potential risks before they stall progress.\"\r\n    },\r\n    {\r\n      \"@type\": \"HowToStep\",\r\n      \"position\": 7,\r\n      \"name\": \"Keep experimenting\",\r\n      \"text\": \"Teams evolve. Adjust formats, timing, and facilitation styles based on what delivers the most value. Retrospectives are a good place to check whether your ceremonies still work.\"\r\n    }\r\n  ]\r\n}\r\n<\/script>","show_sidebar_sticky_banner":false,"menu_cta_override":{"label":"","url":""},"override_contact_sales_label":"","override_contact_sales_url":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.6 (Yoast SEO v28.0) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Scrum Meetings Explained: The Complete Guide for 2025<\/title>\n<meta name=\"description\" content=\"Scrum meetings help agile teams plan, align, and improve through daily standups, sprint planning, reviews, retrospectives, and backlog refinement.\" \/>\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\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What are Scrum meetings, and how to run them effectively in 2025\" \/>\n<meta property=\"og:description\" content=\"Scrum meetings help agile teams plan, align, and improve through daily standups, sprint planning, reviews, retrospectives, and backlog refinement.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/\" \/>\n<meta property=\"og:site_name\" content=\"monday.com Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-09-17T10:23:23+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-31T05:40:39+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/monday.com\/blog\/wp-content\/uploads\/2025\/07\/Sprint-Scrum-sprint-cover1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"4800\" \/>\n\t<meta property=\"og:image:height\" content=\"2400\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Naama Oren\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Naama Oren\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"1 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/\"},\"author\":{\"name\":\"Naama Oren\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#\\\/schema\\\/person\\\/1e67abedbcb96f722953d7a1a49e6c4d\"},\"headline\":\"What are Scrum meetings, and how to run them effectively in 2025\",\"datePublished\":\"2025-09-17T10:23:23+00:00\",\"dateModified\":\"2026-08-31T05:40:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/\"},\"wordCount\":11,\"publisher\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/Sprint-Scrum-sprint-cover1.png\",\"articleSection\":[\"Product development life cycle\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/\",\"name\":\"Scrum Meetings Explained: The Complete Guide for 2025\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/Sprint-Scrum-sprint-cover1.png\",\"datePublished\":\"2025-09-17T10:23:23+00:00\",\"dateModified\":\"2026-08-31T05:40:39+00:00\",\"description\":\"Scrum meetings help agile teams plan, align, and improve through daily standups, sprint planning, reviews, retrospectives, and backlog refinement.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/#primaryimage\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/Sprint-Scrum-sprint-cover1.png\",\"contentUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/Sprint-Scrum-sprint-cover1.png\",\"width\":4800,\"height\":2400,\"caption\":\"What are Scrum meetings and how to run them effectively in 2025\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/the-different-types-of-scrum-meetings-for-beginners\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/monday.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Product development life cycle\",\"item\":\"https:\\\/\\\/monday.com\\\/blog\\\/rnd\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"What are Scrum meetings, and how to run them effectively in 2025\"}]},{\"@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\\\/1e67abedbcb96f722953d7a1a49e6c4d\",\"name\":\"Naama Oren\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/501450638_10162463772521335_3925171118141134561_n-150x150.jpg\",\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/501450638_10162463772521335_3925171118141134561_n-150x150.jpg\",\"contentUrl\":\"https:\\\/\\\/monday.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/501450638_10162463772521335_3925171118141134561_n-150x150.jpg\",\"caption\":\"Naama Oren\"},\"url\":\"https:\\\/\\\/monday.com\\\/blog\\\/author\\\/naama-oren\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Scrum Meetings Explained: The Complete Guide for 2025","description":"Scrum meetings help agile teams plan, align, and improve through daily standups, sprint planning, reviews, retrospectives, and backlog refinement.","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\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/","og_locale":"en_US","og_type":"article","og_title":"What are Scrum meetings, and how to run them effectively in 2025","og_description":"Scrum meetings help agile teams plan, align, and improve through daily standups, sprint planning, reviews, retrospectives, and backlog refinement.","og_url":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/","og_site_name":"monday.com Blog","article_published_time":"2025-09-17T10:23:23+00:00","article_modified_time":"2026-08-31T05:40:39+00:00","og_image":[{"width":4800,"height":2400,"url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2025\/07\/Sprint-Scrum-sprint-cover1.png","type":"image\/png"}],"author":"Naama Oren","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Naama Oren","Est. reading time":"1 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/#article","isPartOf":{"@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/"},"author":{"name":"Naama Oren","@id":"https:\/\/monday.com\/blog\/#\/schema\/person\/1e67abedbcb96f722953d7a1a49e6c4d"},"headline":"What are Scrum meetings, and how to run them effectively in 2025","datePublished":"2025-09-17T10:23:23+00:00","dateModified":"2026-08-31T05:40:39+00:00","mainEntityOfPage":{"@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/"},"wordCount":11,"publisher":{"@id":"https:\/\/monday.com\/blog\/#organization"},"image":{"@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2025\/07\/Sprint-Scrum-sprint-cover1.png","articleSection":["Product development life cycle"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/","url":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/","name":"Scrum Meetings Explained: The Complete Guide for 2025","isPartOf":{"@id":"https:\/\/monday.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/#primaryimage"},"image":{"@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/#primaryimage"},"thumbnailUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2025\/07\/Sprint-Scrum-sprint-cover1.png","datePublished":"2025-09-17T10:23:23+00:00","dateModified":"2026-08-31T05:40:39+00:00","description":"Scrum meetings help agile teams plan, align, and improve through daily standups, sprint planning, reviews, retrospectives, and backlog refinement.","breadcrumb":{"@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/#primaryimage","url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2025\/07\/Sprint-Scrum-sprint-cover1.png","contentUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2025\/07\/Sprint-Scrum-sprint-cover1.png","width":4800,"height":2400,"caption":"What are Scrum meetings and how to run them effectively in 2025"},{"@type":"BreadcrumbList","@id":"https:\/\/monday.com\/blog\/rnd\/the-different-types-of-scrum-meetings-for-beginners\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/monday.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Product development life cycle","item":"https:\/\/monday.com\/blog\/rnd\/"},{"@type":"ListItem","position":3,"name":"What are Scrum meetings, and how to run them effectively in 2025"}]},{"@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\/1e67abedbcb96f722953d7a1a49e6c4d","name":"Naama Oren","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/04\/501450638_10162463772521335_3925171118141134561_n-150x150.jpg","url":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/04\/501450638_10162463772521335_3925171118141134561_n-150x150.jpg","contentUrl":"https:\/\/monday.com\/blog\/wp-content\/uploads\/2026\/04\/501450638_10162463772521335_3925171118141134561_n-150x150.jpg","caption":"Naama Oren"},"url":"https:\/\/monday.com\/blog\/author\/naama-oren\/"}]}},"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\/249550","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\/310"}],"replies":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/comments?post=249550"}],"version-history":[{"count":8,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/249550\/revisions"}],"predecessor-version":[{"id":361033,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/posts\/249550\/revisions\/361033"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media\/237002"}],"wp:attachment":[{"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/media?parent=249550"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/categories?post=249550"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/monday.com\/blog\/wp-json\/wp\/v2\/tags?post=249550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}