:

:

Reference: https://prince2.wiki/principles/defined-roles-andresponsibilities/#:~:text=PRINCE2%20states%20that%20a%20project,Business%20sponsors%2C%20

Users%20and%20Suppliers

In PRINCE2 Agile, a Backlog is the prioritized list of requirements, features, or user stories that define

what needs to be delivered for a product. It is a dynamic and evolving list that is continually refined

and re-prioritized to ensure the most valuable work is done first. The backlog acts as a single source

of truth for what the team needs to deliver and provides transparency to stakeholders regarding

progress and priorities. It aligns with agile principles and practices such as Scrum, where the Product

Backlog contains all desired work for the product.

The Project Canvas is a high-level tool used for defining project scope and objectives, the Release

Map plans releases and iterations, and the Project Log tracks issues, risks, and actions but does not

list prioritized requirements.

Reference: PRINCE2 Agile Foundation Version 2, Section 5.3 "Agile Concepts," and PRINCE2 Agile

Study Guide, Chapter 5, "Products and Backlogs."

Reference:

https://publications.axelos.com/prince2agile2016/content.aspx?showNav=true&expandNav=true&p

age=PRA_41

Reference:

https://publications.axelos.com/prince2agile2016/content.aspx?page=pra_206&showNav=true&exp

andNav=true

The Release Planning Workshop is the forum where planning for the next stage occurs in PRINCE2

Agile. This workshop brings together the project management team and delivery teams to plan the

scope, schedule, and resources for the upcoming release or stage. It helps align business priorities

with delivery capacity and supports incremental and iterative delivery approaches.

The Team Planning Workshop focuses on more detailed planning at the team level within the

release, the Team Retrospective Workshop is dedicated to reflecting on performance and improving

processes, and the Progress Review Workshop is for reviewing progress against the plan rather than

planning future work.

Reference: PRINCE2 Agile Foundation Version 2, Section 6.4 "Planning Workshops," and PRINCE2

Agile Study Guide, Chapter 7, "Planning."

:

The Risk practice is specifically aimed at controlling uncertainties that could impact the achievement

of the project’s objectives. In PRINCE2 Agile, risk management involves identifying, assessing, and

controlling threats and opportunities to reduce negative impacts and maximize positive outcomes.

Effective risk management is a core theme and practice in PRINCE2 Agile and is crucial for agile

environments where change and uncertainty are inherent. The practice ensures that risks are

continuously monitored and appropriate responses are planned and implemented. This proactive

management helps keep the project viable and aligned with business justification.

While plans support managing scope and resources, issues deal with current problems rather than

potential future events, and quality ensures that products meet requirements, risk management

uniquely focuses on uncertainty.

The PRINCE2 Agile guidance emphasizes integrating agile techniques such as frequent reviews and

retrospectives to improve risk awareness and control.

Reference: PRINCE2 Agile Foundation Version 2, Section 8.3 "Risk Management Practice," and

PRINCE2 Agile Study Guide, Chapter 8.

: