Daily Standup Best Practices for PMP: Run Effective Daily Scrums

What Is the Daily Standup?

The Daily Standup (or Daily Scrum in Scrum terminology) is a short, time-boxed event where the Development Team synchronizes their work and plans the next 24 hours. It is perhaps the most visible agile practice and one of the most frequently tested on the PMP exam — not for its mechanics, but for the principles behind it.

The Basics

Duration: 15 minutes maximum. It's called a "standup" because standing (physically or mentally) discourages lengthy discussions.
Frequency: Every working day, at the same time and place.
Participants: The Development Team. The Scrum Master ensures the event happens and coaches the team to keep it within the time-box. The Product Owner may attend but does not run the meeting.
Format: Each team member addresses three questions: What did I complete yesterday? What will I work on today? What impediments are blocking me?

Purpose: Synchronization, Not Status Reporting

This distinction is critical for the PMP exam. The Daily Standup is a team synchronization event, not a status report to the project manager. Team members are talking to each other, not to a manager. The goal is to ensure the team is aligned, identify impediments early, and adjust the day's plan as needed.

If a question describes a project manager using the standup to collect progress updates and report them to stakeholders, that's an anti-pattern. The correct approach is to let the team self-organize and use the standup for peer-to-peer coordination.

Common Anti-Patterns the PMP Tests

The Status Meeting

The standup becomes a report to the Scrum Master or project manager. Team members direct their updates upward rather than to each other. Fix: The Scrum Master should step back and let the team own the conversation.

The Problem-Solving Session

When someone raises an impediment, the team dives into solving it right there. The 15 minutes evaporate and half the team zones out. Fix: Note the problem, identify who needs to discuss it, and schedule a separate conversation immediately after the standup (often called a "parking lot" or "after-party").

The Monologue

One team member gives a detailed account of everything they did, consuming most of the time-box. Fix: Coach team members to keep updates concise — 30-60 seconds each. Details go to follow-up conversations.

The Attendance Nightmare

People consistently miss the standup, undermining synchronization. Fix: Ensure the time works for the whole team (especially important for distributed teams across time zones) and reinforce the value the event provides.

Standups for Distributed Teams

With remote and hybrid work now standard, many teams run virtual standups via video call. Some teams use asynchronous standups — posting updates in a shared channel (like Slack) instead of meeting synchronously. The PMP exam may present scenarios involving distributed teams and ask you to choose the most effective communication approach.

The agile principle of face-to-face conversation remains the ideal, but adaptations are appropriate. A synchronous video standup is closer to the ideal than asynchronous text updates. The key is maintaining the synchronization purpose regardless of format.

What Happens After the Standup

The standup itself doesn't solve problems — it surfaces them. After the standup:

Impediments are addressed by the Scrum Master or the team collectively
Team members who need to collaborate on a task connect and work together
The Sprint Backlog or task board is updated to reflect reality

Key Takeaways for Exam Day

The Daily Standup is for the team, by the team. It's 15 minutes, focused on synchronization. Problems are identified but solved elsewhere. The project manager (or Scrum Master) facilitates without controlling. If an exam question presents a dysfunctional standup, the answer usually involves returning to these fundamentals.

Strengthen your understanding of agile events and practices with PMPprep's practice questions.