The building-inspections Product Owner starts running Daily Scrum as a personal status meeting, asking each Developer to report to them. What should change?
Select an answer to reveal the explanation.
Short Explanation
Daily Scrum is the crew checking the day’s route, not a stand-up for the Product Owner’s notebook. If inspectors are reporting to the PO, the event has flipped into status theater. Let Developers inspect the Sprint Goal and adjust their own plan.
Full Explanation
Daily Scrum is an event for Developers to inspect progress toward the Sprint Goal and adapt the day's plan. It is not a status meeting owned by the Product Owner. When a building-inspections Product Owner starts running Daily Scrum as personal reporting, that must change: restore Developer ownership so self-management and focus on the Sprint Goal return, even if the Product Owner may attend without disrupting.
Keeping the status format because the Product Owner needs Daily Scrum as an executive briefing misuses the event for PO information needs. Replacing Daily Scrum with a Gantt checkpoint the Product Owner facilitates for the city manager further subordinates the team to hierarchy. Inviting every inspection supervisor to Daily Scrum to assign next-day tasks turns the daily plan into an external dispatch board.
Inspection supervisors and Product Owners can get updates without turning the Developers' daily plan into a status parade.
Exam caveat: PSPO II is clear that Daily Scrum belongs to Developers; Product Owner attendance is optional and must not convert the event into status reporting.
Operational check: stop facilitating Daily Scrum as PO Q&A, let Developers run the fifteen minutes against the Sprint Goal, and take inspection questions to a separate conversation if needed.