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

In Scrum, the Product Backlog serves as the plan, and the Product Owner updates it as soon as new information or insight emerges. There is no separate project plan with fixed update points.

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

A traditional project plan tries to fix scope and schedule up front and then tracks deviations. Scrum handles complex work differently. The Product Backlog is ordered, emergent and always open to change, so it plays the role of the plan. The Product Owner is accountable for keeping it transparent, visible and understood. When a Sprint Review, a stakeholder conversation or new market data reveals something, the backlog changes right away. Waiting for a fixed checkpoint would let the plan describe a world that no longer exists, which undermines inspection and adaptation.

Why the Other Options Are Wrong

B. Before Sprint Planning to know how much work fits in the Sprint. Sprint capacity is the Developers’ call during Sprint Planning. A separate plan is not used to set it.

C. After the Daily Scrum for daily progress tracking. The Daily Scrum adapts the Sprint Backlog, which the Developers own. Daily project plan updates are not part of Scrum.

D. Before the Sprint Retrospective. The Retrospective looks at how the team works. It has nothing to do with updating a project plan.

Exam Tip

For PSPO II, expect familiar PSPO I ideas tested in new words. When “project plan” appears, translate it to Product Backlog.

Key Takeaways

• The Product Backlog takes the place of a project plan.
• Updates happen when learning happens, not on a schedule.
• A stale plan undermines inspection and adaptation.