The correct answer is B – A product backlog should be created to list the project requirements from all of the project stakeholders.
In Agile, the product backlog serves as a living document where requirements, user stories, and stakeholder feedback are continuously refined. It is the central mechanism for capturing and prioritizing stakeholder needs and ensuring that business value is delivered incrementally.
From the PMI Agile Practice Guide:
“The product backlog is a prioritized list of work for the development team that is derived from stakeholder input, user stories, and emerging needs. It evolves as the project progresses and stakeholder feedback is incorporated.”
(PMI Agile Practice Guide, Section 5.2 – Product Backlog)
Mike Griffiths writes:
“Product backlogs provide transparency into stakeholder priorities. They enable the team to continuously align work with customer expectations and business needs.”
(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)
Why the other options are incorrect:
A refers to the traditional project charter, which is not commonly updated throughout the agile life cycle.
C is a misunderstanding—the Agile Manifesto is a set of principles, not a project-specific document.
D misuses user stories; stories are used for functional requirements, not stakeholder profiles.
Answer: B
══════════════════════════════════════════════════
