{"id":603,"date":"2024-04-13T19:22:57","date_gmt":"2024-04-13T19:22:57","guid":{"rendered":"https:\/\/nextagile.ai\/blogs\/?p=603"},"modified":"2025-12-19T08:33:05","modified_gmt":"2025-12-19T08:33:05","slug":"daily-stand-up-meeting","status":"publish","type":"post","link":"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/","title":{"rendered":"Daily Stand-Up: How to Run and Best Practices with Expert Tips"},"content":{"rendered":"<p><i><span style=\"font-weight: 400;\">Thomas Sowell once said, &#8216;People who enjoy meetings should not be in charge of anything\u2019. <\/span><\/i><span style=\"font-weight: 400;\">????<\/span><\/p>\n<p><span style=\"font-weight: 400;\">By the way, <\/span><b>Daily Stand-up aka Daily Scrum is not called out as a meeting, as the makers are smart and they quote it as an \u2018event\u2019 which will lead to minimizing the meetings not mentioned in the Scrum Guide<\/b><span style=\"font-weight: 400;\">. We have still used the daily stand-up \u2018meeting\u2019 terminology to align with the popular parlance and to make it easier for people to discover this blog.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Firstly, let us clarify that there is no mention of the keyword Daily Stand-up in the Scrum Guide 2020 version. We would be very surprised if somebody gets into so much aesthetics as it will take the focus away from the value proposition and distract us towards some practice which has just one benefit -&gt; \u2018Stand, otherwise, you won\u2019t be attentive and talk for long\u2019.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Over time, <\/span><b>Daily Scrum is synonymous with Daily Standup<\/b><span style=\"font-weight: 400;\">. Henceforth, while you read the blog below, please be assured that both are the same for us and we also do not endorse you to stand mandatorily in your scrum event. ????<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In the software development context, Agile and many of the agile frameworks focus on delivering working software frequently. Not just some software but also software with business and value-driven functionalities sprint after sprint. Certain practices become very important for this to happen in a complex and uncertain environment. Not from a perspective of being religiously followed but due to the great benefit that comes with the discipline and rigor of following these practices.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Every practice has a purpose, outcome, and intention. One such practice of Agile methodology and Scrum framework, in particular, is Daily Stand Up or DSM. The Daily Stand-up meeting is not a traditional status meeting, especially the one used by project managers to get updates on project status. A daily stand-up meeting is held to communicate the status of the sprint by the development team.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The intent is to synchronize, inspect, adapt, and plan daily to help the development team do their work better. This blog aims to showcase everything about A daily Standup meeting. This event is also called Team Huddle, Daily Checkpoint Meeting, Daily Status Update, etc. These terms are coined by organizations to tailor to their language or needs.\u00a0\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We have attempted to answer the below questions, which are regularly asked from us in our consulting and coaching engagements.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What are daily stand-up meetings?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What should be the ideal duration of a daily stand-up call?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">How to finalize the daily stand-up agenda?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">How should this daily meeting or DSM be conducted?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What is the relevance of daily stand-up in Agile?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Do we have a standard daily stand-up format?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What are some of the daily stand-up best practices?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Is there a daily stand-up meeting template I can use?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Is there something called daily stand-up agile?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We will attempt to answer these and a few other queries about DSM in this blog, let\u2019s dive in.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_is_a_stand-up_meeting_in_Agile\"><\/span><b>What is a stand-up meeting in Agile?<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2><div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 ez-toc-wrap-left ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 eztoc-toggle-hide-by-default' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/#What_is_a_stand-up_meeting_in_Agile\" >What is a stand-up meeting in Agile?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/#Why_is_Stand-up_Important\" >Why is Stand-up Important?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/#Types_of_Agile_stand-up_meetings\" >Types of Agile stand-up meetings.<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/#How_to_run_a_daily_standup\" >How to run a daily standup?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/#Common_mistakes_and_best_practices_for_daily_standup_meetings\" >Common mistakes and best practices for daily standup meetings.<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/#Stand-up_meetings_for_distributed_teams\" >Stand-up meetings for distributed teams<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/#Better_meetings_create_better_projects\" >Better meetings create better projects<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/#Conclusion\" >Conclusion<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-stand-up-meeting\/#Frequently_Asked_Questions\" >Frequently Asked Questions<\/a><\/li><\/ul><\/nav><\/div>\n\n<p><span style=\"font-weight: 400;\">Agile focuses on close collaboration, periodic inspection of the work committed, and adaptation to changes.\u00a0 For such inspection, the team periodically checks the progress of their work, focusing collectively on how they can complete the work items planned for that sprint and if needed course correct to accomplish the sprint goal.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It is recommended that the team meet every day at the same place and time throughout the sprint, sprint after sprint to enable this collaboration, engagement, inspection, and adaptation. This event or meeting is simply called a Daily Stand-Up meeting.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Have you ever wondered why it is termed as a Daily standup call? The \u2018stand-up\u2019 is to remind you to stand up and not to settle down in your seats and get comfortable. The daily stand-up meeting should be time-bound and the focus should be on getting done with the meeting, making it focussed and effective.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A Daily stand-up meeting is a time-boxed ceremony or event that is part of the Scrum framework. Scrum is based on values of honesty, openness, trust, collaboration, etc. These values are ingrained in all the Scrum events and one of the events is the Daily Stand-up meeting. Scrum, as a term, is derived from the sport Rugby. It means working closely and tightly together with heads down, completely focussed on the completion of the goal.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Let&#8217;s see below how the Scrum team conducts a DSM and what happens in a Daily stand-up meeting. These are the daily stand-up best practices that should be followed.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What do the Scrum development team members do during this Stand-up call?<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Development team members ( Developers and QA) talk about the status of their user story\/work item\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The team members focus on how much of the work is remaining and the expected time of completion of their work item\/user story. In case the team members forecast completion of the work on the same day then the next work item they plan to pick will be updated<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The team members during a Daily Scrum call also highlight any risks or issues they have identified while working on their work items<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The focus of this Daily standup meeting for every team member is to let everyone know<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">where they stand wrt to their work item, ask for help if needed to take the work item to completion, and provide help or clarity to other team members to accomplish the sprint goal.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Daily Stand up call is a time-boxed event. The maximum daily standup meeting duration for an ideal team size of 10 is 15 minutes. The events and duration of an iteration in Scrum are all time-boxed. As Agile projects are uncertain in nature, the concept of timeboxing helps to bring some level of order and consistency in such a highly variable work environment. This is the significance of daily stand-up in Agile.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Daily Stand-up meetings offer daily opportunities to assess progress, gather feedback, and control the deviations from the committed sprint goal.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Why_is_Stand-up_Important\"><\/span><b>Why is Stand-up Important?<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Once the Sprint starts after the completion of the sprint planning and the work is underway during an iteration, the development team continues the planning process on a daily level by holding daily stand-up meetings or daily stand-up calls. Short, focused team huddles are in a way used as daily planning mechanisms.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-4060 size-full\" src=\"https:\/\/nextagile.ai\/blogs\/wp-content\/uploads\/2024\/04\/Why-is-stand-up-important.png\" alt=\"Why is stand-up important\" width=\"1200\" height=\"800\" title=\"\" srcset=\"https:\/\/nextagile.ai\/blogs\/wp-content\/uploads\/2024\/04\/Why-is-stand-up-important.png 1200w, https:\/\/nextagile.ai\/blogs\/wp-content\/uploads\/2024\/04\/Why-is-stand-up-important-300x200.png 300w, https:\/\/nextagile.ai\/blogs\/wp-content\/uploads\/2024\/04\/Why-is-stand-up-important-1024x683.png 1024w, https:\/\/nextagile.ai\/blogs\/wp-content\/uploads\/2024\/04\/Why-is-stand-up-important-768x512.png 768w, https:\/\/nextagile.ai\/blogs\/wp-content\/uploads\/2024\/04\/Why-is-stand-up-important-600x400.png 600w, https:\/\/nextagile.ai\/blogs\/wp-content\/uploads\/2024\/04\/Why-is-stand-up-important-150x100.png 150w\" sizes=\"auto, (max-width: 1200px) 100vw, 1200px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Here\u2019s why the daily stand-up calls are important:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Keep everyone <\/span><b>Focused<\/b><span style=\"font-weight: 400;\"> on the agreed-upon scope and sprint goal<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Daily meetings act as <\/span><b>Early warning indicators<\/b><span style=\"font-weight: 400;\"> for risks and issues allowing the development team to solve before they can derail the team\u2019s progress towards achieving the sprint goal.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bring <\/span><b>Alignment<\/b><span style=\"font-weight: 400;\"> towards one shared objective\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Promote <\/span><b>Focus <\/b><span style=\"font-weight: 400;\">as the meeting is short and structured in a way to discuss only work-in-progress items that are aligned with the sprint goal<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Brings <\/span><b>Transparency<\/b><span style=\"font-weight: 400;\"> as everyone knows what the others are working on as and when the team progresses. The ALM tools like JIRA, Rally, and Azure DevOps are used to showcase daily progress. This means the data is made available to everyone<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A sense of <\/span><b>Shared Accountability<\/b><span style=\"font-weight: 400;\"> in achieving the sprint goal is established<\/span><\/li>\n<\/ol>\n<h2><span class=\"ez-toc-section\" id=\"Types_of_Agile_stand-up_meetings\"><\/span><b>Types of Agile stand-up meetings.<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">In Agile ways of working, stand-up meetings have different nomenclature based on the chosen framework, needs of the project, etc. The Official Scrum guide refers to\u201d Daily Stand-up meetings\u201d as \u201cDaily Scrum\u201d event &amp; not meeting. Whether it is Scrum or Extreme programming or a routine agile project status call such meetings intend to figure out daily progress towards the committed goal, identify blockers, and resolve them ASAP &#8211; essentially a clear pathway for the teams. In essence, there isn&#8217;t more than one type of Agile stand-up meeting, though they might be termed differently in various contexts.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"How_to_run_a_daily_standup\"><\/span><b>How to run a daily standup?<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Here are some rules of engagement for running a daily stand-up or a basic daily meeting format:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The daily stand-up meeting agenda must be published well in advance<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ensure the daily stand-up participants &#8211; Product Owner, Scrum Master, and the Development team are present in every stand-up call<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ensure the call starts on time\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Start the Daily Scrum call, in alphabetical order, or use a Robin method or any other creative way to keep the fun element intact.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Every team member gives an update by answering these 3 questions using the below format.<\/span>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">What did I\u00a0 do yesterday that helped in meeting the sprint goal<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">What will I do today to meet the Sprint goal?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">Are there any impediments in your way that prevent me or the development team from meeting the Sprint goal?<\/span><\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Every team member talks about his \/ her user stories\/work items progress and also flags off blockers coming his\/her way<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The Product Owner can choose to check the progress made by the team toward the sprint goal once everyone completes talking about the progress made<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">If any course corrections have to be made or one needs technical or functional clarity on any elements, flag it during the daily stand-up meeting to take it up post-meeting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Make note of follow-up tasks that arise during the stand-up. <a href=\"https:\/\/en.wikipedia.org\/wiki\/Scrum_(software_development)\" target=\"_blank\" rel=\"noopener nofollow\">Scrum<\/a> Master must ensure these are assigned to the appropriate team member<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Daily Stand call ends when everyone completes talking about their work items\u00a0<\/span><\/li>\n<\/ol>\n<h2><span class=\"ez-toc-section\" id=\"Common_mistakes_and_best_practices_for_daily_standup_meetings\"><\/span><b>Common mistakes and best practices for daily standup meetings.<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Everyone following Agile and using the Scrum framework diligently runs the daily stand-up meeting. Unfortunately, these end up being long-drawn, boring, namesake meetings. The reason most of the time the Daily Stand-up meetings (DSM) don&#8217;t give the expected outcome is because the intent of the Daily Stand-up is not set in the first place. Teams use DSM to tick off boxes and to collect information about what everyone is doing.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When teams call this event a team status update meeting the essence of the DSM is lost. It must be made very clear that the <\/span><b>Daily Stand-up Meetings are events<\/b> <b>where teams get an opportunity every single day for a fixed short duration to hear out how other team members are progressing with their work items and offer help wherever needed<\/b><span style=\"font-weight: 400;\">. Everyone must be aware that during this event team members have the opportunity to check the progress made by them towards the sprint goal. This is an opportunity to check if a lesser-priority work item has to be parked and if something else of more priority is to be picked as part of course correction.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Here are a few common mistakes that must be avoided to reap the benefits of a Daily Stand meeting:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Not starting and closing the daily stand-up call on time<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Waiting for all the participants to join thereby delaying the meeting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Focusing only on the 3 questions and missing out on understanding how much work is remaining to meet the sprint goal<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Getting into lengthy technical discussions even before everyone completes their updates thereby digressing from the intent, not following the daily stand-up agenda, and losing interest<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Other stakeholders who are there to understand the progress provide their status when it is irrelevant to the development team<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Allowing stakeholders other than the Product Owner or Scrum Master to intrude into the status updates even before the completion of updates by the entire team thereby prolonging the daily stand-up meeting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Interrupting the team on questions or issues not pertinent to the planned <a href=\"https:\/\/nextagile.ai\/blogs\/agile\/product-backlog-vs-sprint-backlog\/\">sprint backlog<\/a><\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resolving issues that were identified during the daily stand-up call instead of taking them after the meeting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Keeping the updates succinct<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">Avoiding these aforementioned mistakes can make the Daily Standup meeting more purposeful and eventful. They are the top anti-patterns we encounter while we implement agile in organizations as an <\/span><a href=\"https:\/\/nextagile.ai\/agile-consulting-services\/\"><span style=\"font-weight: 400;\">agile consulting company<\/span><\/a><span style=\"font-weight: 400;\"> providing <\/span><a href=\"https:\/\/nextagile.ai\/agile-transformation-consulting\/\"><span style=\"font-weight: 400;\">agile transformation services<\/span><\/a><span style=\"font-weight: 400;\">. Having seen the pitfalls to avoid, let&#8217;s look at some best practices that have to be borne in mind:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">At any point of time if there is awkward silence just before the meeting start with an icebreaker.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Drive the status updates randomly or use round Robin method or take the alphabet route to bring randomness<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Keep the ALM tool like JIRA updated with pertinent status before the meeting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Announce if there is a planned leave the following day to everyone to plan any work in your absence\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use the Burndown chart during the Daily standup meeting to focus on how much work is remaining<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">In case of scope creep, raise it with the Product Owner to check the repercussions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Team members upon completion of their updates should stay on in the meeting pay close attention to other&#8217;s updates and offer help if it needed and they can help.<\/span><\/li>\n<\/ol>\n<h2><span class=\"ez-toc-section\" id=\"Stand-up_meetings_for_distributed_teams\"><\/span><b>Stand-up meetings for distributed teams<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Daily stand-up for co-located teams must be conducted at the same place and time.\u00a0 In the case of distributed teams coming together in one meeting room isn&#8217;t possible. In such cases where the team members are geographically distributed, virtual daily standup calls are the only option. Below are some pointers for effective virtual daily stand-up meetings:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Decide the most convenient time for all the team members<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ensure the video is turned on for the entire daily meeting\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">As the team member gives the update open the team scrum board in the ALM to stay focussed<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">In case of audio issues instead of stretching the meeting, update the status in the chat window to keep everyone informed<\/span><\/li>\n<\/ol>\n<h2><span class=\"ez-toc-section\" id=\"Better_meetings_create_better_projects\"><\/span><b>Better meetings create better projects<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Meetings are booked for a certain amount of time for a reason. When you attend a meeting or an event just because it is part of your calendar and have no input, the meeting loses its meaning. The time spent by the other attendees and the host is simply wasted as the planned outcome wasn\u2019t achieved.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Most of the time team members use meetings as a reason to clarify everything that&#8217;s been pending, as a social event, a place to discuss everything apart from the objective.\u00a0\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If the meetings are planned well the outcomes will be far superior. Below are a few pointers to make meetings effective thereby leading to better projects by fostering collaboration, communication, and alignment among the participants:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Set the expectations of the meeting, and the agenda well in advance so that everyone understands the purpose of the meeting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Keep the content short and crisp. Regular check-ins help everyone to be on the same page about the project&#8217;s progress<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Discuss issues openly if it is part of the agenda<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Respect everyone\u2019s time, start and end the meetings on time<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">If the agenda is to discuss ideas or solve a problem, brainstorm using various techniques to ensure everyone is involved and heard<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hold team members accountable for their commitments and progress<\/span><\/li>\n<\/ol>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span><b>Conclusion<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Conducting a daily stand-up meeting is an art. A little randomness to make it interesting and keeping the conversations succinct and to the point is the key to an outcome-oriented and focused daily stand-up meeting. Inspect and adapt, one of the core agile tenets applies to Daily Stand Up meetings. The outcome of this event is an updated sprint backlog.\u00a0 Daily stand-up meetings are not the only time when team members meet up to discuss the updates but also to adjust the plan toward achieving their sprint goal. They can meet as often as required for more detailed discussions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Hope you liked this blog. Reach out to us at <a href=\"mailto:consult@nextagile.ai\">consult@nextagile.ai<\/a><\/span><span style=\"font-weight: 400;\">\u00a0for any support in designing and implementing your <a style=\"color: blue; text-decoration: none;\" href=\"https:\/\/nextagile.ai\/agile-transformation-consulting\/\">agile transformation journey<\/a>.Agile Transformations are not rocket science, they should be simple, easily scalable, and an existing fun journey with a positive impact on the business value. As an <\/span><a style=\"color: blue; text-decoration: none;\" href=\"https:\/\/nextagile.ai\/agile-consulting-services\/\"><span style=\"font-weight: 400;\">agile consulting firm<\/span><\/a><span style=\"font-weight: 400;\">,we endeavor to simplify this journey for you so that you can focus on your core work area.\u00a0<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Frequently_Asked_Questions\"><\/span><strong>Frequently Asked Questions<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><b>1. What is not expected during daily stand-up meetings in Agile?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Many times Project managers or tech leads participate in Daily standup just to understand the progress but also intervene and ask questions during the meeting thus prolonging the meeting. This is not expected during such meetings as the questions may not be relevant to other team members. Daily stand-up meetings are not meant for lengthy discussions around user stories or technicalities.<\/span><\/p>\n<h3><b>2. What are the three questions in an Agile daily standup meeting?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">During a Daily stand up meeting every team member excluding the scrum master and the Product Owner is expected to the below 3 questions:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What did you do yesterday?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What will you do today?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Are there any impediments in your way?<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">The above-stated questions are considered as a format for the daily stand-up agenda. The idea of a DSM should be to understand everyone\u2019s progress, and check if the interdependencies on the user stories are causing any delay, any unplanned leave which may affect progress and thus delay the achievement of the sprint goal. What else needs to be done to achieve the Sprint goal, and how much work is remaining to get to the goal should be the focus areas. The questions listed above help in staying focussed. We have also included a sample daily stand-up meeting template or a daily stand-up format in this blog, which will help you prepare for the daily meeting.<\/span><\/p>\n<h3><b>3. What is the best duration of daily standup meetings?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Maximum of 15 mins is the best duration for a daily stand-up meeting. This duration is best for team size from 3-10 people. As the team size becomes bigger the scope for collaboration and focus becomes lesser. In a DSM big group means more confusion and less attention to detail. This is the best practice to maintain that duration. If the meetup ends in clarity for everyone and if it finishes early it is alright to end the DSM before the 15-minute duration. The other way also holds good. If the team members need more clarifications they can continue to stay on and extend the DSM provided they announce the updates have been completed and relevant participants who need clarification stay on while the rest leave the meeting.<\/span><\/p>\n<h3><b>4. What is a daily scrum vs stand-up meeting?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\"><a href=\"https:\/\/nextagile.ai\/blogs\/agile\/daily-scrum-meeting\/\">Daily Scrum Meeting<\/a> is the term used by the Scrum Guide. This is one of the five events\/ceremonies followed in Scrum Framework which focuses on checking every day if the sprint goal that was committed during the Sprint planning meeting can be achieved. This meeting is \u201cfor the Development Team\u201d and \u201c by the Development Team. Daily Stand-up meeting or daily meeting is simply another name for the daily scrum meeting.<\/span><span style=\"font-weight: 400;\">\u00a0 \u00a0 \u00a0 \u00a0<\/span><\/p>\n<h3><b>5. How do I prepare for a daily standup?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Following are a few prerequisites for running a Daily Standup meeting:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Find a time slot for the DSM by obtaining consensus from the entire team<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ensure the Daily stand-up is not at the end of the day for one team and early in morning for another distributed team. Find a mid path by discussing with all the team members<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">In the case of co-located team members avoid the DSM as soon as the day starts at work.\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The ideal slot would be after all the team members arrive comfortably and settle down. The idea is not to miss out on any latecomers in a DSM.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Roll out the calendar invites and mark everyone except the team members as optional.\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">In case you require some stakeholders on specific days send out a request for attendance separately<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">\u00a0User stories, tasks, and work items on the ALM tool must reflect the right status.\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">\u00a0Arrive a minute or two earlier than the scheduled time<\/span><\/li>\n<\/ol>\n<blockquote><p><em>Elevate your business with our <a href=\"https:\/\/nextagile.ai\/agile-transformation-consulting\/\">Agile Transformation Service<\/a>. Improve team performance, accelerate delivery, and adapt faster in a dynamic market.<\/em><\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>Thomas Sowell once said, &#8216;People who enjoy meetings should not be in charge of anything\u2019. ???? By the way, Daily Stand-up aka Daily Scrum is not called out as a meeting, as the makers are smart and they quote it as an \u2018event\u2019 which will lead to minimizing the meetings not mentioned in the Scrum&#8230;<\/p>\n","protected":false},"author":5,"featured_media":4059,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[2],"tags":[],"class_list":["post-603","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile"],"_links":{"self":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/comments?post=603"}],"version-history":[{"count":16,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/603\/revisions"}],"predecessor-version":[{"id":5079,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/603\/revisions\/5079"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media\/4059"}],"wp:attachment":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media?parent=603"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/categories?post=603"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/tags?post=603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}