The Delivering level is responsible for the day-to-day management and decision-making within the constraints set by the project manager. Delivering teams carry out the actual work to create the project products and manage their activities under the project’s governance framework. The Project Manager manages the overall project, while directing sets the strategic direction and commissioning authorizes initiation.
This separation ensures clear responsibilities and empowers the delivery teams to self-manage within defined boundaries.
[Reference: PRINCE2 Agile Foundation Version 2, Section 3.4 "Project Management Structure," and PRINCE2 Agile Study Guide, Chapter 3., ]
Question # 47
What is a purpose of the 'team planning' workshop?
The Team Planning Workshop is primarily held to update the product backlog. This collaborative session allows the delivery team to break down, refine, and reprioritize user stories or tasks to prepare for the upcoming iteration or sprint. The team reviews the product backlog items, clarifies acceptance criteria, estimates effort, and commits to the planned work.
Updating the product backlog at this level ensures that detailed planning aligns with the overall project vision and release goals. It empowers the team to self-organize and manage their workload, supporting agile principles of autonomy and collaboration.
While the project dashboard (A) provides status reporting, the release map (C) focuses on higher-level release planning, and OKRs (D) relate to strategic objectives, these are not the central focus of the team planning workshop.
PRINCE2 Agile promotes team planning workshops as essential forums for translating business priorities into actionable, manageable work for delivery teams.
[Reference: PRINCE2 Agile Foundation Version 2, Section 6.3 "Team Planning," and PRINCE2 Agile Study Guide, Chapter 6., , ]
Question # 48
Which statement about the ‘initiating a project’ process is CORRECT?
Options:
A.
The initiation stage plan should form part of the project plan
B.
The impact of frequent releases on quality management should be assessed
C.
The process should take more time than usual for disruptive projects
D.
The project solution should be documented in detail in the project product description
Personas in PRINCE2 Agile serve as fictional, archetypal users representing the needs, behaviors, and goals of real users. In the business case practice, personas are used to identify and articulate specific user benefits. This ensures the project focuses on delivering value that meets the actual needs of different user groups.
By understanding personas, teams can tailor product features and prioritize requirements that provide meaningful benefits, thereby strengthening the business case and increasing stakeholder buy-in. Personas help clarify who will use the product, what problems they face, and how the solution delivers value.
Personas go beyond demographic grouping (A); they are detailed profiles including motivations and pain points. They do not relate directly to timelines (B) or product version differentiation (D).
Using personas aligns with agile principles of customer focus and continuous stakeholder engagement embedded in PRINCE2 Agile.
[Reference: PRINCE2 Agile Foundation Version 2, Section 7.1 "Using Personas in Business Case," and PRINCE2 Agile Study Guide, Chapter 7., ]
