Answering: “When should the Product Owner update the project plan?” (PSPO I)

The Product Backlog is the plan in Scrum, and the Product Owner updates it whenever new information or insights emerge. There is no separate project plan to maintain on a schedule.

Exam Question

When should the Product Owner update the project plan?
(choose the best answer)
A. The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.
B. Before the Sprint Planning to know how much work will have to be done in the Sprint.
C. After the Daily Scrum to ensure an accurate daily overview of project progress.
D. The project plan must be updated prior to the Sprint Retrospective.

Correct Answer

A. The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.

Why This Is the Correct Answer

The Scrum Guide calls the Product Backlog “an emergent, ordered list of what is needed to improve the product” and “the single source of work undertaken by the Scrum Team.” It shows what the team intends to build and in what order, which is what a plan is for. Because it is emergent, it changes whenever the Product Owner learns something from stakeholders, the market or the latest Increment. Tying updates to particular events, like the Daily Scrum or the Retrospective, would make the plan lag behind reality. In Scrum, planning is continuous rather than a separate document kept in sync.

Why the Other Options Are Wrong

B. Before Sprint Planning to know how much work fits in the Sprint. The Developers decide how much work fits in the Sprint. A separate plan is not needed for that.

C. After the Daily Scrum for a daily overview of progress. The Daily Scrum is for the Developers and the Sprint Backlog. The Product Owner does not maintain a daily project plan.

D. Prior to the Sprint Retrospective. The Retrospective is about how the team works. There is no rule linking it to plan updates.

Exam Tip

If an option names the Product Backlog as the plan, it is a strong candidate. Scrum replaces the classic project plan with an emergent backlog.

Key Takeaways

• The Product Backlog acts as the product plan.
• It changes whenever new insight appears.
• There is no separate project plan in Scrum.