--- title: What Is a Stand-Up Meeting? Live vs. Async for Remote Teams description: A stand-up meeting is a 15-minute daily check-in to re-plan toward the sprint goal. See what to say, and when distributed teams should go live or async. image: https://www.catapultlabs.com/hubfs/distributed-agile-team-standup-slack-jira.png --- [![logo](https://www.catapultlabs.com/hubfs/Site/Clients/Colors=True%2c%20Format=Horizontal.svg)](https://www.catapultlabs.com) Menu - ###### Products ![](https://www.catapultlabs.com/hubfs/Site/Navbar/Vector%20(Stroke).svg) Team productivity![](https://www.catapultlabs.com/hubfs/Site/Navbar/arrow-right-2.svg) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Retros-2.svg)Agile Retros](https://www.catapultlabs.com/retrospectives) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Scrumpoker.svg)Scrum Poker](https://marketplace.atlassian.com/apps/1218960/scrumpoker-estimates-for-jira?hosting=cloud&tab=overview) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/TeamPulse-1.svg)TeamPulse](https://marketplace.atlassian.com/apps/1227873/teampulse-health-check-ins-for-jira?tab=overview&hosting=cloud) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/bot-1.svg)StandBot](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) Customer support![](https://www.catapultlabs.com/hubfs/Site/Navbar/arrow-right-2.svg) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Sync-Jan-24-2023-05-14-14-9110-PM.svg)Freshdesk + Trello](https://www.freshworks.com/apps/freshdesk/trello) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Sync-Jan-24-2023-05-09-14-4164-PM.svg)Freshservice + Trello](https://www.freshworks.com/apps/freshservice/trello) - ###### Solutions New![](https://www.catapultlabs.com/hubfs/Site/Navbar/Vector%20(Stroke).svg) Team productivity![](https://www.catapultlabs.com/hubfs/Site/Navbar/arrow-right-2.svg) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/devex-icon.svg)DevEx New](https://www.catapultlabs.com/solutions/devex) - ###### Platforms![](https://www.catapultlabs.com/hubfs/Site/Navbar/Vector%20(Stroke).svg) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/atlassian%20logo.svg)Atlassian - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Retros-2.svg)Agile Retros](https://www.catapultlabs.com/agile-retrospectives-for-jira-and-confluence) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Scrumpoker.svg)Scrum Poker](https://marketplace.atlassian.com/apps/1218960/scrumpoker-estimates-for-jira?hosting=cloud&tab=overview) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/TeamPulse-1.svg)TeamPulse](https://marketplace.atlassian.com/apps/1227873/teampulse-health-check-ins-for-jira?tab=overview&hosting=cloud) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/bot-1.svg)StandBot](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/Trello.svg)Trello - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Retros-1.svg)Agile Retros](https://trello.com/power-ups/61f7eba5e29fd13c6884a214/agile-retrospectives) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/Monday.svg)monday.com - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Retros-2.svg)Agile Retros](https://monday.com/marketplace/124) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/Slack.svg)Slack - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/bot-1.svg)StandBot](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/Freshworks.svg)Freshworks - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Sync-2.svg)Freshdesk + Trello](https://www.freshworks.com/apps/freshdesk/trello) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Sync-3.svg)Freshservice + Trello](https://www.freshworks.com/apps/freshservice/trello) - ###### Resources![](https://www.catapultlabs.com/hubfs/Site/Navbar/Vector%20(Stroke).svg) - [![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Navbar/Book.png?width=24&height=24&name=Book.png)Help center](https://help.catapultlabs.com/) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Opened-Book.svg)Blog](https://www.catapultlabs.com/blog) - [![](https://www.catapultlabs.com/hubfs/Site/Navbar/devex-icon.svg)Jira DevEx Guide](https://www.catapultlabs.com/guide/developer-experience-jira) - [![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Navbar/phone-calling.webp?width=24&height=24&name=phone-calling.webp)Contact Us](https://www.catapultlabs.com/contact) - [Atlassian Marketplace](https://marketplace.atlassian.com/vendors/1213059/catapult-labs-llc) - ![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Navbar/Menu-Mobile.png?width=622&height=312&name=Menu-Mobile.png) StandBot for Slack Stop worrying about your stand-up logistics! [Get it here](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) [Atlassian Marketplace](https://marketplace.atlassian.com/vendors/1213059/catapult-labs-llc) Team productivity![](https://www.catapultlabs.com/hubfs/Site/Navbar/arrow-right-Apr-12-2023-05-19-56-2589-AM.svg) Customer support![](https://www.catapultlabs.com/hubfs/Site/Navbar/arrow-right-Apr-12-2023-05-19-56-2589-AM.svg) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Retros-3.svg) Agile Retros Run engaging retrospectives inside Jira, Confluence, monday.com & Trello](https://www.catapultlabs.com/retrospectives) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/TeamPulse-1.svg) TeamPulse Build trust among your team by running health check-ins in Jira](https://marketplace.atlassian.com/apps/1227873/teampulse-health-check-ins-for-jira?tab=overview&hosting=cloud) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/bot-1.svg) StandBot Keep your team in sync with asynchronous stand-ups in Slack](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Scrumpoker.svg) Scrum Poker Estimate development tasks playing Planning Poker in Jira or Confluence](https://marketplace.atlassian.com/apps/1218960/scrumpoker-estimates-for-jira?hosting=cloud&tab=overview) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Sync-Jan-24-2023-05-14-14-9110-PM.svg) Freshdesk + Trello Keep your support teams in sync by linking Freshdesk tickets to Trello cards](https://www.freshworks.com/apps/freshdesk/trello) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Sync-Jan-24-2023-05-09-14-4164-PM.svg) Freshservice + Trello Empower your IT teams to collaborate by linking Freshservice tickets to Trello cards](https://www.freshworks.com/apps/freshservice/trello) ![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Navbar/robot%20logo.png?width=481&height=271&name=robot%20logo.png) StandBot for Slack Stop worrying about your stand-up logistics! [Get it here![](https://www.catapultlabs.com/hubfs/Site/Navbar/arrow-right-Apr-12-2023-05-19-56-2589-AM.svg)](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/atlassian%20logo.svg)Atlassian [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Retros-3.svg) Agile Retros Run engaging retrospective sessions inside Jira or Confluence](https://www.catapultlabs.com/agile-retrospectives-for-jira-and-confluence) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/TeamPulse-1.svg) TeamPulse Build trust among your team by running health check-ins in Jira](https://marketplace.atlassian.com/apps/1227873/teampulse-health-check-ins-for-jira?tab=overview&hosting=cloud) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Scrumpoker.svg) Scrum Poker Estimate development tasks playing Planning Poker in Jira or Confluence](https://marketplace.atlassian.com/apps/1218960/scrumpoker-estimates-for-jira?hosting=cloud&tab=overview) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/bot-1.svg) StandBot Keep your team in sync with asynchronous stand-ups in Slack](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) StandBot for Slack Stop worrying about your stand-up logistics! - ![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Standbot%20LP/checkmark-1.png?width=24&height=24&name=checkmark-1.png)Products Updates - ![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Standbot%20LP/checkmark-1.png?width=24&height=24&name=checkmark-1.png)Get immediate notifications on blockers - ![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Standbot%20LP/checkmark-1.png?width=24&height=24&name=checkmark-1.png)Export your stand-up data as CSV [Get it here![](https://www.catapultlabs.com/hubfs/Site/Navbar/arrow-right-Apr-12-2023-05-19-56-2589-AM.svg)](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) ![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Navbar/robot%20logo.png?width=481&height=271&name=robot%20logo.png) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/Trello.svg)Trello [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Sync-Jan-24-2023-05-09-14-4164-PM.svg) Agile Retros Run engaging retrospective sessions inside Trello](https://trello.com/power-ups/61f7eba5e29fd13c6884a214/agile-retrospectives) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/Monday.svg) monday.com [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Retros-3.svg) Agile Retros Run engaging retrospective sessions inside Jira or Confluence](https://monday.com/marketplace/124) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/Slack.svg) Slack [![](https://www.catapultlabs.com/hubfs/Site/Navbar/bot-1.svg) StandBot Keep your team in sync with asynchronous stand-ups in Slack](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) ![](https://www.catapultlabs.com/hubfs/Site/Navbar/Freshworks.svg)Freshworks [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Sync-Jan-24-2023-05-14-14-9110-PM.svg) Freshdesk + Trello Tips & tricks on everything Agile related, remote teams, and all their possibilities](https://www.freshworks.com/apps/freshdesk/trello) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Sync-Jan-24-2023-05-09-14-4164-PM.svg) Freshservice + Trello Empower your IT teams to collaborate by linking Freshservice tickets to Trello cards](https://www.freshworks.com/apps/freshservice/trello) [![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Navbar/Book.png?width=24&height=24&name=Book.png) Help center Learn how to install, set up, and use our different products](https://help.catapultlabs.com/) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/Opened-Book.svg) Blog Tips & tricks on everything Agile related, remote teams, and all their possibilities](https://www.catapultlabs.com/blog) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/devex-icon.svg) Jira DevEx Guide The ultimate DevEx guide for Agile teams](https://www.catapultlabs.com/guide/developer-experience-jira) [![](https://www.catapultlabs.com/hs-fs/hubfs/Site/Navbar/phone-calling.webp?width=24&height=24&name=phone-calling.webp) Contact Us](https://www.catapultlabs.com/contact) Team productivity![](https://www.catapultlabs.com/hubfs/Site/Navbar/arrow-right-Apr-12-2023-05-19-56-2589-AM.svg) [![](https://www.catapultlabs.com/hubfs/Site/Navbar/devex-icon.svg) DevEx New A suite of apps designed to revive scattered, disengaged Agile rituals](https://www.catapultlabs.com/solutions/devex) [![](https://www.catapultlabs.com/hubfs/Site/arrow-left.svg) Return to Blog](https://www.catapultlabs.com/blog) Remote Work # What Is a Stand-Up Meeting? A Practical Guide for Distributed Agile Teams 12 min read 19 October, 2026 ![Luis Ortiz](https://www.catapultlabs.com/hubfs/Luis%20Ortiz%20headshot.png) [Luis Ortiz](https://www.catapultlabs.com/blog/author/luis-ortiz) Table of Content [Remote Work](https://www.catapultlabs.com/blog/tag/remote-work) [jira](https://www.catapultlabs.com/blog/tag/jira) [Agile Ceremonies](https://www.catapultlabs.com/blog/tag/agile-ceremonies) [Scrum](https://www.catapultlabs.com/blog/tag/scrum) [Distributed Teams](https://www.catapultlabs.com/blog/tag/distributed-teams) [StandBot](https://www.catapultlabs.com/blog/tag/standbot) [Async Work](https://www.catapultlabs.com/blog/tag/async-work) [Slack](https://www.catapultlabs.com/blog/tag/slack) [Stand-Up Meeting](https://www.catapultlabs.com/blog/tag/stand-up-meeting) [Daily Scrum](https://www.catapultlabs.com/blog/tag/daily-scrum) Share this [![Share on linkedin](https://www.catapultlabs.com/hubfs/Site/Blogs/linkedin-default.svg)](http://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fwww.catapultlabs.com%2Fblog%2Fstand-up-meeting-guide%3Futm_medium%3Dsocial%26utm_source%3Dlinkedin) [![Share on twitter](https://www.catapultlabs.com/hubfs/Site/Blogs/twitter-default.svg)](https://twitter.com/intent/tweet?original_referer=https%3A%2F%2Fwww.catapultlabs.com%2Fblog%2Fstand-up-meeting-guide%3Futm_medium%3Dsocial%26utm_source%3Dtwitter&url=https%3A%2F%2Fwww.catapultlabs.com%2Fblog%2Fstand-up-meeting-guide%3Futm_medium%3Dsocial%26utm_source%3Dtwitter&source=tweetbutton&text=) [![Share on facebook](https://www.catapultlabs.com/hubfs/Site/Blogs/facebook-default.svg)](http://www.facebook.com/share.php?u=https%3A%2F%2Fwww.catapultlabs.com%2Fblog%2Fstand-up-meeting-guide%3Futm_medium%3Dsocial%26utm_source%3Dfacebook) [![Share on youtube](https://www.catapultlabs.com/hubfs/Site/Blogs/youtube-default.svg)](http://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fwww.catapultlabs.com%2Fblog%2Fstand-up-meeting-guide%3Futm_medium%3Dsocial%26utm_source%3Dyoutube) ### Join our newsletter The best collaborative work insights. ![Newsletter](https://www.encora.com/hubfs/Catapult-Labs-site/Newsletter.png) [Remote Work](https://www.catapultlabs.com/blog/tag/remote-work) [jira](https://www.catapultlabs.com/blog/tag/jira) [Agile Ceremonies](https://www.catapultlabs.com/blog/tag/agile-ceremonies) [Scrum](https://www.catapultlabs.com/blog/tag/scrum) [Distributed Teams](https://www.catapultlabs.com/blog/tag/distributed-teams) [StandBot](https://www.catapultlabs.com/blog/tag/standbot) [Async Work](https://www.catapultlabs.com/blog/tag/async-work) [Slack](https://www.catapultlabs.com/blog/tag/slack) [Stand-Up Meeting](https://www.catapultlabs.com/blog/tag/stand-up-meeting) [Daily Scrum](https://www.catapultlabs.com/blog/tag/daily-scrum) ⚡ Quick Answer What is a stand-up meeting? A stand-up meeting is a short daily check-in, 15 minutes at most, in which the people doing the work inspect progress toward the sprint goal, raise blockers, and adjust the plan for the next day. Scrum's name for it is the Daily Scrum. Distributed teams can run it live, async in Slack, or mix both. - The updates are for the team, so they can re-plan together. Status for managers can come from the Jira board. - Run it live when the team shares working hours and the plan is changing fast. Go async when time zones or routine updates make a daily call expensive. Almost every Agile team has a stand-up meeting on the calendar. Fewer could say what it's for. Somewhere between the Scrum Guide and a recurring invite, many stand-ups turned into half-hour status rounds for whoever asked for the update. Distributed teams pay for that twice: once in the meeting, and again in finding a time when everyone is awake. This guide goes back to the definition, covers how long a stand-up should run, who should be there and what to say, and then answers the question distributed teams face every sprint: should you run it live, async, or both? ## **What Is a Stand-Up Meeting?** A stand-up meeting is the team's daily planning check. The people doing the work look at progress against the goal, flag what's blocking them, and agree on the plan for the next day. Teams traditionally hold it on their feet, which keeps it short: nobody wants a long meeting standing up. In Scrum, the stand-up is the Daily Scrum. The [2020 Scrum Guide](https://scrumguides.org/scrum-guide.html) defines it in one sentence: "The Daily Scrum is a 15-minute event for the Developers of the Scrum Team." Its purpose is to inspect progress toward the sprint goal and adjust the sprint backlog, so the team leaves with a plan for the next working day. That definition sets the audience. The updates are for the other people doing the work, so they can re-plan the next 24 hours together. Anything that needs a longer conversation moves to a follow-up with only the people involved, which is how a good stand-up stays inside 15 minutes. ## **Is a Stand-Up Meeting the Same as a Daily Scrum?** **A stand-up** is any short, recurring team check-in on progress and blockers, used by Scrum, Kanban and non-Agile teams alike. The Daily Scrum is the Scrum Guide version: a 15-minute event, every working day, for the developers, whose purpose is to inspect progress toward the sprint goal and adapt the sprint backlog. Every Daily Scrum is a stand-up; not every stand-up is a Daily Scrum. The difference matters most for teams that don't run Scrum. A Kanban team has no sprint, so its Agile stand-up meeting follows the board instead: the team walks the columns from right to left, starting with the work closest to done, and asks what's stopping each item from moving. Support and operations teams use the same format around their queue. Teams that mix Scrum and Kanban often swap the classic questions for questions about flow; see [how stand-ups work in Scrumban](https://www.catapultlabs.com/blog/scrumban-can-improve-syncing-between-remote-and-hybrid-teams). The Scrum Guide also leaves the format to the team. The 2020 version doesn't require the three classic questions. The developers can use any structure, as long as the meeting focuses on progress toward the sprint goal and ends with a plan for the next day. Scrum.org describes the [Daily Scrum](https://www.scrum.org/resources/what-is-a-daily-scrum) as an internal meeting for the team: other people can attend, and the Scrum Master makes sure they don't disrupt it. ## **How Long Should a Stand-Up Meeting Be, and Who Should Attend?** Fifteen minutes is the upper limit, not the target. James Shore and Shane Warden put it plainly in [The Art of Agile Development](https://www.jamesshore.com/v2/books/aoad1/stand_up_meetings): "Thirty seconds per person is usually enough." For a team of eight, that's about four minutes of updates, with time left to agree on the plan. Who attends, and who talks: - **The people doing the sprint work.** Engineers, QA, designers: everyone with work items on the board. They do the talking. - **The Scrum Master.** Makes sure the stand-up happens and stays inside its timebox. Gives an update only if they're working on sprint items themselves. - **The Product Owner.** Same rule. Useful to have there, because a scope question can often be answered in one sentence. - **Managers and stakeholders.** Welcome to listen. The updates aren't addressed to them. When a stand-up meeting runs over, the cause is usually a discussion that should have been a follow-up. Keep a parking lot: when a topic needs more than a minute, write it down, finish the round, and let the two or three people involved stay on afterwards. Everyone else gets their time back. The same limit applies to an async stand-up. If writing an update takes more than a couple of minutes, the format is asking for too much. ## **What Do You Say in a Stand-Up Meeting?** Most teams start with three stand-up meeting questions: 1. What did I finish since the last stand-up? 2. What will I work on next? 3. What's blocking me? They're easy to remember, which is why they last. Their weakness is that they invite a list of activity ("I worked on the API") instead of progress against the goal. Two other formats fix that. **Sprint goal first.** Put the sprint goal on screen and ask one question: what's in the way of it? Updates that don't touch the goal can go in writing. **Walk the board.** Open the Jira board and go column by column from right to left, starting with the work items closest to done. The conversation follows the work instead of going person by person, and anything that hasn't moved in days shows up on its own. Our guide to [walking the board in a stand-up](https://www.catapultlabs.com/blog/walking-the-board-alongside-stand-bot) covers when the format works best. Whatever the format, a useful update names the work item and the next step. Compare these two: - **Weak:** "Still on the payments stuff, should be done soon." - **Strong:** "PAY-482 is in code review. Once it's merged I'm picking up PAY-490. I'm blocked on the sandbox credentials, and I need ten minutes with Ana after this." The second one tells the team what moved, what's next and who needs to talk, and anyone who wants the detail can open PAY-482. ## **Should Distributed Teams Run Stand-Ups Live, Async, or Both?** For a team in one office, the stand-up is cheap: everyone is already there. For a distributed team, a daily call takes a slot from the hours everyone shares, and that window gets smaller with every time zone you add. These questions decide which format fits: | Question | Lean live | Lean async | | --- | --- | --- | | How many working hours does the whole team share? | Most of the day | An hour or less | | What are most updates about? | Decisions, trade-offs, priorities that change day to day | Routine progress on work everyone already understands | | Where are you in the sprint? | Sprint start, release week, an incident | Mid-sprint, steady work | | How big is the team? | Small enough that a round fits in 15 minutes | Large enough that a round never does | Many distributed teams end up with both: a written check-in each day, and a 15-minute call on the days the plan needs a conversation, such as sprint start or the day before a release. Some teams go further and [replace some daily stand-ups with a weekly scrum](https://www.catapultlabs.com/blog/weekly-scrums-can-boost-productivity-while-saving-time). Async stand-ups work when the updates stay connected to the work. Atlassian's [State of Teams 2025](https://www.atlassian.com/blog/state-of-teams-2025) survey of 12,000 knowledge workers and 200 executives found that "leaders and teams waste 25% of their time just searching for answers." An update posted in a chat channel and never tied to a work item adds to that search. For teams that plan in Jira and talk in Slack, [StandBot, a Slack stand-up bot for Jira](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=cloud&tab=overview&utm_source=catapult-blog&utm_medium=referral&utm_campaign=2026-q4-stand-up-meeting-guide&utm_content=h2-intl-link-live-async), runs the check-in in your Slack channel at the time you set. Each person sees a quick view of their assigned Jira tickets while they write their update, which means every update can name its work item without anyone switching to Jira. The Scrum Master is notified as soon as someone reports a blocker, so it can get an owner before the next stand-up. The stand-up history stays in Jira, where you can download it as CSV or PDF. ![StandBot asking about blockers in Slack, with a team member’s answer and a Jira card showing the work item’s status, priority and assignee](https://www.catapultlabs.com/hs-fs/hubfs/standbot-blocker-screenshot.png?width=2352&height=1552&name=standbot-blocker-screenshot.png) For formats, templates and the habits that keep an async round from going quiet, read our guide on [how to run async standups for a distributed Jira team](https://www.catapultlabs.com/blog/async-standups-2026-guide-distributed-teams). ## **Stand-Up Meeting Best Practices: Keep It a Planning Check, Not a Status Report** When a stand-up stops working, it's usually for one of a handful of reasons, and each one has a small fix. **Updates go to the manager.** People look at whoever runs the meeting and report to them. Rotate the facilitator, or have the manager speak last, and ask people to talk to the team. If the manager needs status, the Jira board already has it. We've written about [how stand-ups drift into status meetings](https://www.catapultlabs.com/blog/behind-the-stand-up-spiral-why-daily-syncs-fail-and-how-to-fix-them), especially on distributed teams. **Problem-solving starts in the room.** Two people debug while everyone else waits. Use the parking lot: name the topic, name who needs to stay, and move on. **"Same as yesterday."** Shore and Warden list this as an anti-pattern, and for good reason: it tells the team nothing. Name the work item and what changed. If nothing changed, say why, because that's often the blocker. **It starts late.** Waiting five minutes for the last person teaches everyone to arrive five minutes late. Start on time with whoever is there. **The same blocker comes back every day.** The stand-up is where a blocker gets raised and gets an owner. When the same one shows up three days running, the cause is somewhere else in your process, so [bring recurring blockers to a retrospective inside Jira](https://www.catapultlabs.com/retrospectives) and fix it there. ## **Frequently Asked Questions** What is a stand-up meeting? A stand-up meeting is a daily team check-in of 15 minutes at most. The people doing the work look at progress toward the goal, flag blockers, and agree on the next day's plan. Scrum's name for it is the Daily Scrum, and teams hold it standing so it stays short. Is a stand-up meeting the same as a Daily Scrum? Not exactly. A stand-up is any short team check-in on progress and blockers, used by Scrum, Kanban and other teams. The Daily Scrum is the Scrum version: a 15-minute event, every working day, where the developers inspect progress toward the sprint goal and adapt their plan. Every Daily Scrum is a stand-up, but not every stand-up is a Daily Scrum. How long should a stand-up meeting be, and who should attend? Fifteen minutes at most, and often less: about 30 seconds per person is usually enough. The people doing the sprint work attend and give updates. The Scrum Master and Product Owner take part as contributors only if they work on sprint items. Managers and stakeholders can listen, but the updates are for the team. What do you say in a stand-up meeting? Many teams answer three questions: what I finished, what I'll work on next, and what's blocking me. Two alternatives keep the focus on the goal: start from the sprint goal and ask what's in the way of it, or walk the Jira board from right to left. A useful update names the work item and the next step. Should distributed teams run stand-ups live, async, or both? It depends on shared working hours, what the updates are about, and where you are in the sprint. Teams with little overlap and routine updates do well async, for example in Slack. Live works better when priorities change daily or during sprint starts and incidents. Many distributed teams post written updates every day and meet live only on the days the plan needs a conversation. A stand-up meeting exists for the people doing the work. Keep it to 15 minutes, tie every update to a real work item, and choose the format your whole team can join without anyone dialing in at midnight. For many distributed teams that means async most days and live when the plan needs a conversation. Since 2017, Catapult Labs' Jira apps have been trusted by 1,000+ enterprise clients and more than 3 million users. If your team plans in Jira and talks in Slack, try StandBot for your next stand-up. [Try StandBot Free on Jira](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=cloud&tab=overview&utm_source=catapult-blog&utm_medium=referral&utm_campaign=2026-q4-stand-up-meeting-guide&utm_content=bottom-cta) ![Luis Ortiz](https://www.catapultlabs.com/hubfs/Luis%20Ortiz%20headshot.png) Luis Ortiz Luis is the Co-Founder and leads Growth at Catapult Labs. He writes about practical Agile workflows across Jira, Confluence, and Slack, helping teams run better stand-ups, retrospectives, and improve productivity without meeting overload. [![](https://www.catapultlabs.com/hubfs/Site/Footer/linkedin.png)](https://www.linkedin.com/in/luis-ortiz-23a4a482/) #### You might also like [![logo](https://www.catapultlabs.com/hs-fs/hubfs/Site/Footer/Colors=True%2c%20Format=Horizontal%20(1).png?width=200&height=48&name=Colors=True%2c%20Format=Horizontal%20(1).png)](https://www.catapultlabs.com) [![balloon-1](https://www.catapultlabs.com/hubfs/Site/Footer/balloon-1.svg)](https://www.catapultlabs.com/contact) Products [Agile Retros](https://marketplace.atlassian.com/apps/1218860/agile-retrospectives-for-jira?hosting=datacenter&tab=overview) [Scrum Poker](https://marketplace.atlassian.com/apps/1218960/scrumpoker-estimates-for-jira?hosting=cloud&tab=overview) [TeamPulse](https://marketplace.atlassian.com/apps/1227873/teampulse-health-check-ins-for-jira?tab=overview&hosting=cloud) [StandBot](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) [Freshdesk + Trello](https://www.freshworks.com/apps/freshdesk/trello) [Freshservice + Trello](https://www.freshworks.com/apps/freshservice/trello) [Blog](https://www.catapultlabs.com/blog) [Help center](https://help.catapultlabs.com/) [![twitter](https://www.catapultlabs.com/hs-fs/hubfs/Site/Footer/twitter.png?width=24&height=24&name=twitter.png)](https://twitter.com/CatapultLabs_) [![linkedin](https://www.catapultlabs.com/hs-fs/hubfs/Site/Footer/linkedin.png?width=24&height=24&name=linkedin.png)](https://www.linkedin.com/company/25009688/) [![youtube](https://www.catapultlabs.com/hubfs/Site/Footer/YouTube_full-color_icon.svg)](https://www.youtube.com/@catapultlabs) Products Atlassian [Agile Retros](https://marketplace.atlassian.com/apps/1218860/agile-retrospectives-for-jira?hosting=datacenter&tab=overview) [Scrum Poker](https://marketplace.atlassian.com/apps/1218960/scrumpoker-estimates-for-jira?hosting=cloud&tab=overview) [TeamPulse](https://marketplace.atlassian.com/apps/1227873/teampulse-health-check-ins-for-jira?tab=overview&hosting=cloud) [StandBot](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) Trello [Agile Retros](https://trello.com/power-ups/61f7eba5e29fd13c6884a214/agile-retrospectives) Monday [Agile Retros](https://monday.com/marketplace/124) Slack [StandBot](https://marketplace.atlassian.com/apps/1217825/standbot-slack-stand-up-bot-for-jira?hosting=server&tab=overview) Freshworks [Freshdesk + Trello](https://www.freshworks.com/apps/freshdesk/trello) [Freshservice + Trello](https://www.freshworks.com/apps/freshservice/trello) [Blog](https://www.catapultlabs.com/blog) [Help center](https://help.catapultlabs.com/) [![twitter](https://www.catapultlabs.com/hs-fs/hubfs/Site/Footer/twitter.png?width=24&height=24&name=twitter.png)](https://twitter.com/CatapultLabs_) [![linkedin](https://www.catapultlabs.com/hs-fs/hubfs/Site/Footer/linkedin.png?width=24&height=24&name=linkedin.png)](https://www.linkedin.com/company/25009688/) [![youtube](https://www.catapultlabs.com/hubfs/Site/Footer/YouTube_full-color_icon.svg)](https://www.youtube.com/@catapultlabs) © 2026 Catapult Labs. All Rights Reserved [Terms](https://www.catapultlabs.com/legal?section=term_service) [EULA](https://www.catapultlabs.com/legal?section=eula) [Privacy Notice](https://www.catapultlabs.com/legal?section=global-privacy) [SLA](https://www.catapultlabs.com/legal?section=service-level) [Cookies Disclousure Policy](https://www.catapultlabs.com/legal?section=cookie-disclosure) Cookie Settings ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Luis Ortiz", "url" : "https://www.catapultlabs.com/blog/author/luis-ortiz" }, "dateModified" : "2026-10-19T23:59:14.842Z", "datePublished" : "2026-10-19T23:59:14.000Z", "headline" : "What Is a Stand-Up Meeting? Live vs. Async for Remote Teams", "image" : [ "https://www.catapultlabs.com/hubfs/distributed-agile-team-standup-slack-jira.png" ], "mainEntityOfPage" : { "@id" : "https://www.catapultlabs.com/blog/stand-up-meeting-guide", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.catapultlabs.com/hubfs/Site/Footer/Colors=True%2c%20Format=Horizontal%20(1).png" } } } ``` ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Luis Ortiz" }, "dateModified" : "2026-10-19T23:59:14+0000", "datePublished" : "2026-10-19T23:59:14+0000", "description" : "A stand-up meeting is a 15-minute daily check-in to re-plan toward the sprint goal. See what to say, and when distributed teams should go live or async.", "headline" : "What Is a Stand-Up Meeting? A Practical Guide for Distributed Agile Teams", "image" : "https://www.catapultlabs.com/hubfs/distributed-agile-team-standup-slack-jira.png", "mainEntityOfPage" : { "@id" : "https://www.catapultlabs.com/blog/stand-up-meeting-guide", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.catapultlabs.com/hubfs/Site/Clients/Colors=True%2c%20Format=Horizontal.svg" }, "name" : "Catapult Labs" } } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "A stand-up meeting is a daily team check-in of 15 minutes at most. The people doing the work look at progress toward the goal, flag blockers, and agree on the next day's plan. Scrum's name for it is the Daily Scrum, and teams hold it standing so it stays short." }, "name" : "What is a stand-up meeting?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Not exactly. A stand-up is any short team check-in on progress and blockers, used by Scrum, Kanban and other teams. The Daily Scrum is the Scrum version: a 15-minute event, every working day, where the developers inspect progress toward the sprint goal and adapt their plan. Every Daily Scrum is a stand-up, but not every stand-up is a Daily Scrum." }, "name" : "Is a stand-up meeting the same as a Daily Scrum?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Fifteen minutes at most, and often less: about 30 seconds per person is usually enough. The people doing the sprint work attend and give updates. The Scrum Master and Product Owner take part as contributors only if they work on sprint items. Managers and stakeholders can listen, but the updates are for the team." }, "name" : "How long should a stand-up meeting be, and who should attend?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Many teams answer three questions: what I finished, what I'll work on next, and what's blocking me. Two alternatives keep the focus on the goal: start from the sprint goal and ask what's in the way of it, or walk the Jira board from right to left. A useful update names the work item and the next step." }, "name" : "What do you say in a stand-up meeting?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "It depends on shared working hours, what the updates are about, and where you are in the sprint. Teams with little overlap and routine updates do well async, for example in Slack. Live works better when priorities change daily or during sprint starts and incidents. Many distributed teams post written updates every day and meet live only on the days the plan needs a conversation." }, "name" : "Should distributed teams run stand-ups live, async, or both?" } ] } ```