Skip to content
PMPCAPM

Daily Standup (Daily Scrum)

The Daily Scrum (also called Daily Standup) is a 15-minute timeboxed event held each day of the Sprint where Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.

Share:

Know it well enough for the exam? Questions on Daily Standup (Daily Scrum) are scenario-based, not definitional.

Practice it free

Explanation

The Daily Scrum is for the Developers. While the Scrum Master ensures it takes place and teaches the team to keep it within 15 minutes, the Developers are responsible for conducting it. The event improves communication, identifies impediments, promotes quick decision-making, and eliminates the need for other meetings.

Traditionally, each participant answers three questions: What did I do yesterday? What will I do today? Do I have any impediments? However, the Scrum Guide allows the Developers to choose whatever structure they want, as long as the focus is on progress toward the Sprint Goal. Some teams use walking the board, where they review each in-progress item on the Kanban board.

The Daily Scrum is not a status meeting for management. It is a planning event for the Developers. If detailed discussions arise, they are taken offline after the standup. Consistency in time and place reduces complexity and helps establish a team rhythm.

Key Points

  • •Strictly timeboxed to 15 minutes
  • •Held at the same time and place each day for consistency
  • •Focused on progress toward the Sprint Goal, not individual status reporting
  • •Only Developers are required to participate; others may attend but do not disrupt

Exam Tip

The Daily Scrum is for Developers, not for the Scrum Master or stakeholders to collect status. If a question describes it as a status meeting, that answer is likely wrong.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Part of

Agile & Hybrid

Study full domain →

Practice Daily Standup (Daily Scrum)

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.