September 7, 2026 · 8 min read
TL;DR: Across this question bank, an option that sends something to the daily standup appears 28 times and is the correct answer 4 times. The keyed cases are all the same shape: work already in flight has hit a blocker and the team needs to know now. Everything else the distractors try to do there, whether that is diagnosing poor performance, settling a design argument, showing progress to a stakeholder or reporting status upward, belongs to the retrospective, a spike, or the sprint review. Learn which event owns which job and a whole family of questions collapses into one decision.
The daily standup is the agile event candidates are surest about, which is exactly why the exam uses it as bait. It sounds like the responsible thing to do. Something has gone wrong, the team meets every day anyway, so raise it there. The question writers know that instinct is sitting in your head, and they put it in the option list.
Almost nothing. The daily standup is a short coordination meeting for the people doing the work: what moved, what is stuck, what we are picking up next. It is not where the team diagnoses its own dysfunction, not where a design question gets settled, and not where anyone outside the team gets a progress report.
Every keyed use of the standup in this bank fits inside that description. One question has a story card blocked by an external contact who is out of the office. The keyed answer raises it as a blocker at the next standup so the whole team can swarm on it. That is coordination: work is in flight, it has stopped, and the people who could unstick it are in the room tomorrow morning.
The distractors are the interesting part. They are not absurd. Each one takes a real problem and sends it to the standup instead of to the event that owns it.
Most standup questions are really testing this table, one row at a time.
| The situation | Where it goes | Why not the standup |
|---|---|---|
| Work in flight has hit a blocker | Daily standup | This is what it is for |
| Performance is dropping and nobody knows why | Retrospective | The standup coordinates work, it does not inspect how the team works |
| The team and the product owner disagree about how a feature should behave | A spike, or refinement | An unknown needs evidence, not a fifteen-minute conversation |
| A stakeholder wants to see delivered scope | Sprint review | The review exists to show the increment and take feedback |
| New scope has arrived and needs ordering against everything else | Backlog refinement | Ordering is the product owner's work, done against the whole backlog |
| A new team has no agreed roles or ways of working | Team charter | A daily meeting does not create an agreement nobody has made |
Work through a real one. A programme manager complains that one project is performing worse than the others in the portfolio, and asks what that project's manager can do over the next couple of sprints. The options include raising it with the product owner at the sprint review, opening the conversation at the daily standup, running team-building activities, and finding the root cause at the retrospective. Three of those four are meetings that already exist. Only one of them exists to inspect how the team is working, and that is the retrospective. The standup option is not wrong because standups are bad. It is wrong because a fifteen-minute coordination slot is not where a team gets to the bottom of why it is slow.
Common trap: the belief that the daily standup is where the team reports status. That framing is what most of these distractors are built on, and this bank keys against it repeatedly. When a new cross-functional team is producing miscommunication and rework, setting up a standup so they report what they have finished is offered, and the keyed answer is a team charter. When the question asks what the development team contributes to backlog refinement, turning up to standups to report on their work is offered, and the keyed answer is estimating the cards so the product owner can order them by value and effort. Any option that describes the standup as reporting is a signal that the writer is testing this exact misconception.
Only the team. Every option in this bank that brings an outsider into the daily standup is a distractor, which makes this the most mechanical rule in the slice.
A board member who wants to see how delivery is progressing gets invited to the next sprint review. A compliance officer with regulatory changes gets encouraged to detail them for the product backlog rather than announce them at the daily scrum. Stakeholders from supporting departments do not get required to attend and report progress; the keyed fix there is a product owner the team can approach with questions as they arise.
None of those keyed answers are exotic. They are just the event that was designed for the job. That pattern only shows up when you have the wrong answers in front of you as data rather than as one-off mistakes, which is why the explanations here name the distractor and say what it would have cost, instead of only marking it wrong.
When is the daily standup the correct answer on the PMP exam? When something is blocking work that is already in progress and the team needs to know about it now. The clearest keyed case in this bank is a story card that depends on an external contact who is out of the office, and the keyed answer raises it as a blocker at the next standup so the team can swarm on it. Four of the 28 standup options are keyed, and they share that shape.
Why is raising something at the daily standup usually wrong? Because the thing being raised usually needs a different event. Diagnosing poor performance belongs in the retrospective. Settling an argument about how a feature should behave belongs in a spike. Showing progress to a stakeholder belongs in the sprint review. The standup coordinates rather than decides, so a distractor that puts a decision there has put the right topic in the wrong room.
Should stakeholders or managers attend the daily standup? Not on this bank's evidence. Options bringing a board member, a compliance officer or supporting stakeholders into the standup appear repeatedly and are keyed zero times. When a board member wants to see delivery progress, the keyed answer is the sprint review.
Is the standup a status meeting? The exam treats it as coordination, not reporting. Two separate questions offer the standup framed as reporting, one for a new team's miscommunication and one for the development team's role in refinement, and both keyed answers are something else entirely.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 exam content outline, and every wrong answer is explained rather than just marked wrong, including the ones that look responsible. Start the free 20-question sample with no card and no signup.
Related: Agile Metrics: Velocity, Throughput, and Which One the Scenario Wants and Continuous Improvement: Retrospectives, Lessons Learned, and What the Exam Actually Rewards. Study the domain: Process.
Sources: PMI, PMP Exam Content Outline (2026) · The Scrum Guide
When is the daily standup the correct answer on the PMP exam?
When something is blocking work that is already in progress and the team needs to know about it now. In this bank the clearest keyed case is a story card that depends on an external contact who is out of the office: the keyed answer raises it as a blocker at the next standup so the team can swarm on it. That is the standup working as designed, a fast coordination point for work in flight. Four of the 28 options mentioning the standup are keyed, and they all share that shape.
Why is raising something at the daily standup usually wrong?
Because the thing being raised usually needs a different event. Diagnosing why performance is poor belongs in the retrospective. Settling an argument about how a feature should behave belongs in a spike or a refinement conversation. Showing progress to a stakeholder belongs in the sprint review. The standup is short, it is for the people doing the work, and it coordinates rather than decides. When a distractor puts a decision or a diagnosis there, it is putting the right topic in the wrong room.
Should stakeholders or managers attend the daily standup?
Not on this bank's evidence. Options that bring a board member, a compliance officer or a group of supporting-department stakeholders into the standup appear repeatedly and are keyed zero times. When a board member wants to see delivery progress, the keyed answer is the sprint review, which exists for exactly that. The standup is the team's coordination meeting, and turning it into a reporting session for outsiders changes what it is for.
Is the standup a status meeting?
The exam treats it as coordination, not reporting. One question has a new team drawn from across the business with miscommunication and rework, and offers setting up a standup so they report what they have finished; the keyed answer is a team charter instead, because what is missing is agreement on roles and ways of working, not a daily report. Another offers turning up to standups to report on their work as the development team's role in backlog refinement; the keyed answer is estimating the cards. Both distractors describe the standup as reporting, and both are wrong.