What it means
A small product team works on several connected tasks; one person waits on a design decision while another is about to build the affected screen. A brief daily conversation can expose the dependency before work is wasted.
The meeting helps the team coordinate and adapt its plan, and it should not become a performance report to a manager. The Scrum Guide defines the Daily Scrum as a 15-minute event for the developers of a Scrum Team, focused on progress toward the Sprint Goal and an actionable plan for the next day.
Scrum does not require each person to answer the familiar three questions about yesterday, today and blockers; those can be useful, but they are one format, not the official rule. A non-Scrum team may still hold a stand-up, but it should describe its own goal and not claim to be following Scrum just because it meets daily.
Keep the group relevant, since people doing interdependent work benefit most and a large audience waiting through unrelated updates will lose attention. Choose a predictable time, using asynchronous notes or rotating times for a global team, and include remote colleagues fairly with shared audio and a visible board.
Standing is optional, because the name suggests brevity rather than an accessibility requirement. Use a visible work list so the meeting can focus on goals and blocked items rather than reading every ticket aloud.
Bring real impediments by saying what is blocked, who can help and when a decision is needed, because vague statements such as still working on it do not change the plan. Keep updates concise, move deep problem-solving to a follow-up with only the people who need to stay, and coordinate handoffs, such as a designer telling the engineer when a decision will land.
Avoid individual interrogation, because if a manager uses the meeting to ask each person to justify their hours, people may hide problems, and performance conversations belong elsewhere. If the same blocker appears every day, assign an owner and a resolution path, and record who owns any problem two people agree to solve later.
A daily meeting is also not the only planning tool, since longer-term priorities, workload and strategy need separate discussions. An illustrative meeting cost is attendees times meeting minutes, so eight people in a 15-minute stand-up spend 120 person-minutes, or two person-hours, which is a scheduling measure rather than a judgement that the meeting was wasteful.
Measure usefulness by whether blockers surfaced earlier and whether people left knowing the immediate plan, as attendance rate alone is weak evidence. For owners, a daily stand-up is inexpensive only when it changes coordination, so keep it short, let the team adjust the format and make it safe to name problems.
In practice
Real-world examples.
Example
An engineer flags a pending design decision before beginning a dependent task. The designer commits to deliver it by noon, and the engineer starts a different ticket first. No work is built on an assumption that later changes.
Example
A service team identifies an urgent handoff and assigns a follow-up after the call. Only the two people involved stay behind to settle details. Everyone else returns to work within the 15 minutes.
Example
A remote team uses a shared board so all attendees see the same work. Each person names blocked items and requests help rather than reading tickets aloud. Colleagues on video have the same visibility as those in the room.
Formula
Calculation
Illustrative meeting time = attendees x minutes. 8 x 15 = 120 person-minutes, or two person-hours; value depends on changed coordination.
Worked example. A team of eight holds the stand-up on 20 working days in a month, so monthly time is 8 x 15 x 20 = 2,400 person-minutes, or 40 person-hours. Assuming, for illustration, a loaded cost of $50 per person-hour, the time is worth 40 x $50 = $2,000 a month. The cost is justified only if the meeting surfaces blockers or handoffs that save at least that much wasted work, which is why usefulness, not attendance, should be measured.Case study
Seen in the real world.
This entirely fictional example follows Pine Digital. Its daily meeting became a 40-minute ticket recital, and a recurring access problem stayed unresolved. The team moved detailed discussion afterward and assigned an owner for access. The case shows a format correction, not a guarantee that every daily meeting is valuable.
After the change, the 15-minute meeting covered only goals, blockers and handoffs, and the access owner resolved the recurring problem within two days. The team still reviews the format each month and skips the meeting on days when the board shows nothing is blocked. The case is illustrative and shows a format correction rather than a universal recipe.
Watch out
Common mistakes.
- Treating the meeting as individual performance reporting.
- Spending the whole group time solving a problem only two people own.
- Repeating a blocker without assigning a follow-up.
Questions
People also ask.
What is a daily stand-up?
A short daily check-in to coordinate work and surface obstacles.
How long should it last?
The Daily Scrum is 15 minutes; other teams should choose a brief duration that fits their work.
What is covered?
Current progress toward a shared goal, next steps, dependencies and impediments.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related