Should the Product Owner Attend the Daily Scrum? Perspectives and Guidelines

Last Friday, the organizer launched a lunchtime discussion about a controversial FDCC certification question: "Who should attend the Daily Scrum meeting?" The main point of contention was whether the Product Owner (PO) should participate.

The question presented multiple choice options, with options D and E eliminated. The remaining debate focused on option A: "Should the PO should attend the Daily Scrum?"

Arguments for PO attendance:

PO must attend to understand goal progress and obstacles, track requirement completion, and ensure consistent understanding across roles.

PO participation helps avoid misalignment between development and requirements.

PO presence bridges gaps and builds trust, especially in teams newly adopting Agile.

Arguments against PO attendance:

Goals should be clarified during sprint planning; the PO can monitor progress via the board and review meetings without speaking in the stand‑up.

The Daily Scrum is not for explaining requirements; it focuses on short‑term planning.

The Scrum Primer explains that the Daily Scrum is a 15‑minute event for the development team to plan the next 24 hours, review work, and adjust the sprint. The Scrum Master ensures the meeting runs smoothly and prevents external participants from disrupting it.

From this description, the Scrum Master must attend and facilitate, while the PO’s attendance is optional and depends on the team’s needs. In practice, if the project is tight, the PO may proactively join.

The author strongly recommends PO participation, emphasizing the importance of ceremony.

Further discussion points include how to keep stand‑up meetings efficient, key questions about clarifying requirements, and best practices for concise, effective Daily Scrums, illustrated with several diagrams.

Overall, the article provides a balanced view on PO involvement in Daily Scrum meetings and offers guidance for improving stand‑up efficiency.