Daily Scrum
PSM I PSM I · Scrum Events
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. It is a 15-minute event for the Developers of the Scrum Team, held at the same time and place every working day of the Sprint. That is the whole definition, and almost every exam question about the Daily Scrum tests one of its elements: the purpose (inspect and adapt, not report), the participants (the Developers), the length (15 minutes), or the regularity (same time and place daily). The Daily Scrum improves communication, identifies impediments, promotes quick decision-making, and consequently eliminates the need for other meetings. It is not a status meeting, not a reporting session, and not a briefing for the Product Owner or the Scrum Master.
The most common misunderstanding about the Daily Scrum is who it is for. It is for the Developers. The Product Owner and the Scrum Master participate only if they are actively working on items in the Sprint Backlog — and when they do, they participate as Developers, not in their own accountability. A Product Owner who attends every Daily Scrum to hear progress reports is misusing the event; a Scrum Master who runs it as a roll call is doing the same. The Developers run their own Daily Scrum. The Scrum Master ensures the event takes place and stays within its timebox, and coaches the Developers if the event is not working — but does not own it. The exam tests this with scenarios where managers or Product Owners want to attend: the correct answer is that they may attend only if actively working on Sprint Backlog items, and the event's purpose is the Developers' inspection and adaptation, not reporting upward.
Another tested detail is structure. The Developers can select whatever structure and techniques they want, as long as the Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. The famous three questions — what did I do yesterday, what will I do today, are there any impediments — are not prescribed by the Scrum Guide. They are a common technique, and many teams use them, but the Guide does not require them, and a question that claims the three questions are mandatory is wrong. What is mandatory is the focus and the output: progress toward the Sprint Goal, and an actionable plan for the next day. Teams that walk the board, focus on the Sprint Goal, or discuss impediments first are all fine, as long as those two conditions are met.
Why 15 minutes matters
The 15-minute timebox is not arbitrary. A short, focused, daily inspection keeps the feedback loop tight: problems surface within a day instead of festering for a week, and the plan adapts while there is still time to act. When the Daily Scrum stretches to 30 or 45 minutes, it usually means the team is solving problems in the event instead of identifying them and solving them afterwards, or that the event has drifted into status reporting. The fix is not a longer timebox — it is focus: inspect progress toward the Sprint Goal, adapt the Sprint Backlog, agree the next day's plan, and take detailed discussions offline. The Scrum Master coaches the team toward this discipline when the event runs long, but the responsibility for keeping it short belongs to the Developers themselves.
Worked scenario
A Scrum Team's Daily Scrum has become a 25-minute round of individual status updates, delivered to the Scrum Master, who takes notes for a manager. Progress toward the Sprint Goal is rarely discussed, and impediments are mentioned but never followed up. Three things are wrong. First, the event is for the Developers, not for reporting to the Scrum Master or a manager. Second, the focus should be progress toward the Sprint Goal and the next day's plan, not individual updates. Third, the timebox is 15 minutes, and the extra time suggests problem-solving is happening inside the event instead of after it. The Scrum Master should coach the Developers to restructure the event — perhaps by focusing on the Sprint Backlog and the Sprint Goal rather than going person by person — and help the team take detailed discussions offline. The manager's need for information should be met through the artifacts, which are transparent by design, not by turning the Daily Scrum into a reporting channel.
Common Daily Scrum problems
The Daily Scrum drifts off course in familiar ways. The most common is turning into a status meeting: each Developer reports what they did yesterday to the Scrum Master or Product Owner, instead of the Developers inspecting progress toward the Sprint Goal together. The fix is to focus the conversation on the goal and the plan, not on individual activity — walking the Sprint Backlog or discussing the Sprint Goal directly often works better than going person by person. Another common problem is problem-solving inside the event: two Developers start debugging a technical issue while the rest of the team waits. The fix is to identify the issue, agree to discuss it after the event, and move on. A third problem is the event running long because the team tries to cover too much: the fix is discipline about the 15-minute timebox and trust that detailed discussions can happen afterwards. A fourth is skipping the event when the team feels busy — which is exactly when the inspection matters most, because pressure is when plans drift furthest from reality.
The Daily Scrum also serves transparency. Because the Developers inspect the Sprint Backlog daily and adapt it as they learn, the backlog stays an accurate, real-time picture of the Sprint — anyone who looks at it can see the true state of the work. That transparency is what lets the Product Owner trust the team's progress without attending the event, and what lets stakeholders see reality instead of a report. When the Daily Scrum is skipped or turned into a reporting ritual, the Sprint Backlog goes stale, transparency drops, and decisions start being made on outdated information. The 15 minutes a day is a small price for a plan that is always current.
Exam traps to watch for
- Treating the Daily Scrum as a status report to the Product Owner, Scrum Master, or a manager. It is the Developers' event for inspecting progress toward the Sprint Goal.
- Believing the three questions are mandatory. The Guide does not prescribe them; the Developers choose their own structure as long as the event focuses on the Sprint Goal and produces an actionable plan.
- Letting the Daily Scrum run long. It is 15 minutes; detailed problem-solving happens after the event, not inside it.
- Thinking the Scrum Master runs the Daily Scrum. The Scrum Master ensures it happens and stays in timebox; the Developers own it.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.What is the purpose of the Daily Scrum?
Explanation: The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. It is not a reporting session for the Product Owner or stakeholders. Tasks are not assigned — the team is self-managing. And re-ordering the Product Backlog is the Product Owner's work, not the Daily Scrum's purpose.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q2.How long is the Daily Scrum?
Explanation: The Daily Scrum is a 15-minute event. Thirty minutes and one hour are both too long. And it is not open-ended — the 15-minute timebox is fixed, and detailed discussions are taken offline rather than extending the event.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q3.Who participates in the Daily Scrum?
Explanation: The Daily Scrum is an event for the Developers. The Product Owner or Scrum Master participate only if they are actively working on items in the Sprint Backlog, and then they participate as Developers. Stakeholders do not attend. And all Developers participate — it is a team inspection, not a voluntary reporting session.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q4.A manager asks to attend the Daily Scrum every day to stay informed about progress. What is the BEST response?
Explanation: The Daily Scrum is the Developers' event, not a reporting channel for managers. Transparency in Scrum comes through the artifacts — the Sprint Backlog shows progress toward the Sprint Goal to anyone who looks. Turning the event into a manager briefing breaks its purpose. Letting the manager silently observe still changes the dynamic and misses the point. And cancelling the event removes a key inspection opportunity.
Exam objective: PSM I Focus Area: Developing People and Teams — Self-Managing Teams
Q5.Which statement about the structure of the Daily Scrum is TRUE?
Explanation: The Developers can select whatever structure and techniques they want, as long as the Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day. The three questions are a common technique but are not prescribed by the Guide. The Scrum Master does not set the agenda. And no particular order is mandated.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q6.During the Daily Scrum, two Developers discover a complex technical problem that needs an hour of discussion. What should they do?
Explanation: The Daily Scrum is timeboxed to 15 minutes; detailed problem-solving happens after the event. Extending the event breaks the timebox. Skipping the rest of the event means the team loses its daily inspection. Waiting until the Retrospective leaves the problem unsolved for days — the Retrospective is for inspecting the team's way of working, not for solving technical problems.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q7.When is the Daily Scrum held?
Explanation: The Daily Scrum is held at the same time and place every working day of the Sprint — the regularity is what keeps the feedback loop tight. Once a week is far too infrequent. It is not conditional on having impediments. And it is not a start-and-end event.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q8.What is the Scrum Master's role in the Daily Scrum?
Explanation: The Scrum Master ensures that all Scrum events take place and are positive, productive, and kept within the timebox — for the Daily Scrum that means coaching the Developers when the event is not working, not running it. Assigning tasks contradicts self-management. Reporting to stakeholders is not the Scrum Master's job after this event. Deciding which impediments to work on is the Developers' call as they adapt their plan.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q9.Which of the following is a benefit of the Daily Scrum, according to the Scrum Guide?
Explanation: The Daily Scrum improves communication, identifies impediments, promotes quick decision-making, and consequently eliminates the need for other meetings. It does not replace the Sprint Backlog — it adapts it. The Sprint Goal is not changed daily. And stakeholders do not use it to add requirements; new work goes through the Product Owner and the Product Backlog.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events