When should the Product Owner update the project plan? (choose the best answer)

Scrum does not use a traditional, static "project plan." Instead, the plan is emergent and is represented by the Product Backlog. The Product Backlog is a living artifact that contains all known requirements, features, and work for the product. The Product Owner is accountable for managing this backlog. It is continuously updated and refined throughout the product's lifecycle as the Scrum Team and stakeholders learn more about the product and the market. This adaptive planning approach is a core tenet of Scrum's empiricism, allowing for flexibility and responsiveness to change.

A. The Daily Scrum is a planning event for the Developers to inspect progress toward the Sprint Goal, not a status meeting for the Product Owner to update a plan.

B. The Sprint Retrospective is an event focused on inspecting and improving the Scrum Team's processes, interactions, and tools, not for updating the product or project plan.

D. While the Product Backlog should be refined before Sprint Planning, updating it is a continuous activity, not a singular event. Developers, not the PO, select the work for the Sprint.

1. The Scrum Guide (2020):

"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." (Schwaber

K.

& Sutherland

J.

2020

p. 11). This establishes the Product Backlog as the plan.

"Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details

estimates

and order to them." (Schwaber

K.

& Sutherland

J.

2020

p. 12). This confirms the continuous nature of updates.

2. Peer-reviewed Academic Publication:

Hohl

P.

et al. (2018). Backlog Refinement in Large-Scale Agile System Development. In Agile Processes in Software Engineering and Extreme Programming - Workshops. "The PBL [Product Backlog] is a living artifact that is continuously updated based on the changing reality of the project." (p. 1

Section 1). DOI: https://doi.org/10.1007/978-3-319-98339-71

3. University Courseware:

University of Virginia

Darden School of Business: In the course "Agile Development in Practice

" the Product Backlog is described as the "dynamic

ordered list of work to be done

" which serves as the project's plan and is expected to evolve over time. (Course materials on Agile artifacts).