How long should a stand-up be?

Fifteen minutes is the upper limit, not the target. Most healthy teams finish in 8–12 minutes. If yours runs over consistently, look at team size, format (try walking the board), or whether you're solving problems instead of surfacing them.

Should the project manager run the stand-up?

No. The stand-up is for the team. A PM running the meeting turns it into a status read-out, which destroys its coordination value. The team should self-organise; the PM attends as a peer.

Three questions or walk the board?

For new teams, the three-question format gives structure. For mature teams, walking the board right-to-left is faster and focuses the team on finishing work rather than reporting on it.

What should I do with topics that need more discussion?

Park them. Capture the topic, the people who need to discuss it, and move on. A five-minute follow-up after stand-up is far more productive than a 30-minute hijacked daily meeting.

Can stand-ups be remote?

Yes, but with discipline: cameras on, shared board visible, strict time-box, and a single facilitator. Remote stand-ups without those guardrails are the fastest path to silent disengagement.

What's the construction equivalent?

The morning toolbox talk or Last Planner huddle. Foremen review the day's activities, confirm crews and materials, and flag constraints. The cadence, length, and discipline are nearly identical.

How do I tell if my stand-up is broken?

Three smells: it runs long, no impediments are ever raised, and the team treats it as a tax. Any one of those means the format needs to change or the meeting needs to be retired.

Should stakeholders attend?

Stakeholders may observe but should not participate. The stand-up is the team's meeting; outside questions belong in dedicated stakeholder check-ins, not in the team's coordination time.

Which calculators on PMMilestone.org apply to Daily Stand-up?

For Daily Stand-up, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Daily Stand-up?

That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.

Which related encyclopedia entries should I read alongside Daily Stand-up?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Daily Stand-up?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Daily Stand-up is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Daily Stand-up defined on PMMilestone Research & Insights?

A short, focused, time-boxed daily meeting where the delivery team aligns on progress, plans the next 24 hours of work, and surfaces blockers. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Agile · Letter D

Daily Stand-up

A short, focused, time-boxed daily meeting where the delivery team aligns on progress, plans the next 24 hours of work, and surfaces blockers.

By Dr. Hassan Eliwa, PhD · Founder of PMMilestone.org and PMMilestone.com · Updated 2026-06-22

Definition

The Daily Stand-up (also called the daily scrum or huddle) is a 15-minute-or-less team meeting where the delivery team synchronises on the work in flight. Done well, it is the team's heartbeat: it surfaces impediments early, exposes coupling between work items, and keeps everyone honest about commitment. Done badly, it becomes a status read-out for the project manager and the team's least productive 15 minutes of the day.

History

Daily synchronisation is older than agile. Toyota's asaichi ("morning market") meetings predate Scrum by decades, and construction crews have run morning toolbox talks since the 1950s. Scrum codified the practice in 1995 around three questions; Kanban communities later moved towards "walk the board" rather than person-by-person updates. Both styles share the same goal: short, daily, action-oriented alignment.

Principles

For the team, by the team: the stand-up is a coordination meeting, not a status meeting.
Time-boxed: 15 minutes is the limit, not the target.
Standing: the discomfort keeps the meeting short.
Same time, same place: predictability cuts overhead.
Surface, don't solve: impediments are captured; resolution happens after.

Two Formats

Three-question format: what I did yesterday, what I plan today, what is blocking me. Suits new teams and individual accountability.
Walk the board: work the items right to left across the board, focusing on flow and blockers. Suits mature teams and Kanban systems.

Real-World IT / Agile Example

A platform team I coached had drifted into status-meeting territory — 25 minutes, the PM asking each person what they were doing, no impediments raised. We switched to walking the board right-to-left, capped at 12 minutes, and added a "park lot" board for follow-up topics. Within two weeks, blockers were being raised on the day they occurred (vs. an average of 2.3 days previously) and the team's lead time dropped 18%.

Real-World Construction Example

The construction equivalent is the Last Planner morning huddle: foremen meet at the site office, review the day's committed activities, confirm crew assignments, and flag constraints. On a tunnelling project I worked on, the morning huddle was 10 minutes, attended by 14 foremen, and produced a daily constraint log that the project controls team chased through the day. Reasons for incomplete work dropped from 38% to 11% over six months.

Project Controls Perspective

Controls teams treat stand-up as a leading indicator. Two metrics matter: impediment lead time (raised → resolved) and raised-blocker count per week. A stand-up with zero blockers for weeks is not a healthy team — it is a silent team. A stand-up surfacing 3–6 blockers a week with short resolution times is a healthy one.

Common Mistakes

Drifting past 15 minutes — the meeting becomes a cost.
PM-led status round; the team learns to perform rather than coordinate.
Solving problems in the meeting — others tune out.
No follow-up on impediments — raising them stops feeling worth it.
Skipping when sprint pressure is high — exactly when alignment matters most.
Remote stand-ups without cameras or shared board — energy and signal both collapse.

Expert Tips

Walk the board right-to-left. Focus on getting work to done, not starting more.
Park topics that need depth. A 60-second decision: "Park lot."
Assign an impediment owner. If everyone owns it, no one does.
Time-box hard. Use a visible timer.
Skip the stand-up only when the team agrees — never because the PM is busy.

Key Takeaways

Stand-up is for the team, not for the PM.
15 minutes, standing, same time, same place.
Walking the board outperforms the three-question format for mature teams.
Surface, don't solve — park deeper topics.
The number and lead time of impediments is the diagnostic.

Related Concepts

Stand-ups complement Agile, Kanban, Sprint Retrospectives, Issue Management, and Look-Ahead Schedules. Playbooks at PMMilestone.org.

Frequently Asked Questions

How long should a stand-up be?
Fifteen minutes is the upper limit, not the target. Most healthy teams finish in 8–12 minutes. If yours runs over consistently, look at team size, format (try walking the board), or whether you're solving problems instead of surfacing them.
Should the project manager run the stand-up?
No. The stand-up is for the team. A PM running the meeting turns it into a status read-out, which destroys its coordination value. The team should self-organise; the PM attends as a peer.
Three questions or walk the board?
For new teams, the three-question format gives structure. For mature teams, walking the board right-to-left is faster and focuses the team on finishing work rather than reporting on it.
What should I do with topics that need more discussion?
Park them. Capture the topic, the people who need to discuss it, and move on. A five-minute follow-up after stand-up is far more productive than a 30-minute hijacked daily meeting.
Can stand-ups be remote?
Yes, but with discipline: cameras on, shared board visible, strict time-box, and a single facilitator. Remote stand-ups without those guardrails are the fastest path to silent disengagement.
What's the construction equivalent?
The morning toolbox talk or Last Planner huddle. Foremen review the day's activities, confirm crews and materials, and flag constraints. The cadence, length, and discipline are nearly identical.
How do I tell if my stand-up is broken?
Three smells: it runs long, no impediments are ever raised, and the team treats it as a tax. Any one of those means the format needs to change or the meeting needs to be retired.
Should stakeholders attend?
Stakeholders may observe but should not participate. The stand-up is the team's meeting; outside questions belong in dedicated stakeholder check-ins, not in the team's coordination time.
Which calculators on PMMilestone.org apply to Daily Stand-up?
For Daily Stand-up, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.
What is a common misconception about Daily Stand-up?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.
Which related encyclopedia entries should I read alongside Daily Stand-up?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
How does Dr. Hassan Eliwa's research treat Daily Stand-up?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Daily Stand-up is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
How is Daily Stand-up defined on PMMilestone Research & Insights?
A short, focused, time-boxed daily meeting where the delivery team aligns on progress, plans the next 24 hours of work, and surfaces blockers. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

View the full FAQ page for Daily Stand-up →