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.
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
Sprint
A Sprint is a fixed-length timebox of one month or less in Scrum during which the team creates a usable, potentially releasable product Increment.
Scrum Master
The Scrum Master is the accountability within Scrum responsible for establishing Scrum as defined in the Scrum Guide, helping the team and organization understand Scrum theory and practice, and removing impediments.
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.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
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 in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Part of
Agile & Hybrid
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.