The Project Backlog is the artifact used to describe the project’s major products in the form of epic user stories. Epic stories are large, high-level user stories that capture significant features or product components that may later be decomposed into smaller, more detailed user stories in the product backlog.
The Project Backlog provides a strategic view of what the project intends to deliver and supports planning at the project level, including releases and stages. It bridges the gap between business requirements and team-level delivery.
The Product Backlog (C) contains detailed user stories ready for development but is typically more granular. The Release Map (B) plans releases and iterations but does not list epic stories. The Project Dashboard (A) is a reporting tool, not a repository of requirements.
The use of epic user stories in the project backlog aligns with agile practices for managing scope and enables incremental delivery aligned with business priorities.
[Reference: PRINCE2 Agile Foundation Version 2, Section 5.4 "Backlogs and Epics," and PRINCE2 Agile Study Guide, Chapter 5., , ]
Submit