During a Sprint, the Product Owner's primary focus is on maximizing the value of the product resulting from the work of the Developers. This involves several ongoing activities. The Product Owner is responsible for the Product Backlog, which is a living artifact; they continuously refine and reorder it as new information emerges from stakeholders or the market (A). They collaborate closely with the Developers, clarifying requirements and answering questions about the Sprint Backlog items to ensure a shared understanding (B). Furthermore, a crucial part of the role is continuous engagement with stakeholders to gather feedback, manage expectations, and validate the product direction, which informs future backlog ordering (E).

C. Update the Sprint burndown chart.

The Sprint Backlog and its progress visualizations are owned and managed by the Developers. The Product Owner does not update these artifacts.

D. Prioritize the Developer's tasks.

The Product Owner orders the Product Backlog. The self-managing Developers determine how to accomplish the work within the Sprint, including the order of their tasks.

F. Run the Daily Scrum.

The Daily Scrum is an event for the Developers to inspect progress and adapt their plan. The Product Owner does not run or facilitate this meeting.

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Scrum.org.

For A & E: Page 6

"The Product Owner is also accountable for effective Product Backlog management

which includes: ... Ordering Product Backlog items... The Product Backlog is an emergent

ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team." This management is a continuous activity. The PO represents stakeholders

which requires ongoing communication.

For B: Page 7

"For Product Owners to succeed

the entire organization must respect their decisions... The Product Owner is one person

not a committee. The Product Owner may represent the needs of many stakeholders in the Product Backlog." This implies they are the point of clarification for the Developers.

For C & D: Page 9

"The Sprint Backlog is a plan by and for the Developers. It is a highly visible

real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal."

For F: Page 10

"The Daily Scrum is a 15-minute event for the Developers of the Scrum Team... If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog

they participate as Developers." This clarifies they do not run the event in their PO capacity.

2. Hohl

P.

Klünder

J.

van der Veen

A.

& Gorschek

T. (2018). A large-scale study on the motivations for using agile practices. In Proceedings of the 22nd International Conference on Evaluation and Assessment in Software Engineering 2018 (pp. 173-183). https://doi.org/10.1145/3210459.3210478

This study reinforces the PO's role in continuous communication with both the team (clarifying requirements) and stakeholders (gathering feedback) as a core practice for achieving product value. (Section 4.1

Table 2).