PRINCE2 Agile in the Wider Context (PRINCE2 Agile) Questions

Question 1

A team is negotiating a supplier agreement for an agile project. The supplier prefers a fully fixed scope, but the delivery approach relies on adjusting features each sprint based on business feedback. How should the team structure the agreement to keep it agile-friendly?

Keep the scope, cost, and delivery dates all rigidly locked so the supplier commits to every requirement Fix the full feature set upfront and let the timeline and budget flex as the sprints progress Fix the time and cost while allowing the delivered features to vary within an agreed priority order Leave time, cost, and scope open so the supplier decides which features to build each sprint

Correct Answer: Fix the time and cost while allowing the delivered features to vary within an agreed priority order

The correct approach fixes time and cost while letting features flex within an agreed priority order, which is the classic PRINCE2 Agile method of fixing what is essential and flexing scope so business feedback can shape each sprint's delivery.

Fixing the full feature set and flexing time and budget contradicts agile because it locks scope, the least reliable variable, and lets deadlines slip. Locking scope, cost, and dates all rigidly leaves no room for adaptation and breaks the agile delivery model. Leaving everything open removes accountability and hands feature decisions to the supplier rather than the business.

Key concept tested: fixing time and cost while flexing scope in agile contracts.

Question 2

When assessing the integration of agile projects into a traditional programme context, what provides the strongest rationale for synchronizing the timeboxes and release cycles?

It enables coordinated benefits realization and proactive management of interdependencies across multiple initiatives. It guarantees that the corporate board maintains granular oversight over every individual team member's daily activities. It ensures that all specialized teams utilize identical frameworks and standardized reporting metrics across the entire overarching portfolio. It mandates that governance structures strictly approve all iterative adjustments before the development phase begins.

Correct Answer: It enables coordinated benefits realization and proactive management of interdependencies across multiple initiatives.

Synchronizing timeboxes and release cycles is essential because it allows interdependent projects to integrate their outputs simultaneously, thereby facilitating smoother benefits realization and effective risk management at the broader programme level.
Granular oversight of daily activities represents micromanagement rather than effective programme governance. Mandating identical frameworks restricts individual teams from selecting the most appropriate agile methodologies for their specific work context. Requiring strict governance approval for every iterative adjustment fundamentally contradicts the core agile principles of empowerment and adaptive delivery.
The key concept tested is the effective integration of agile project delivery within a traditional programme management environment.

Question 3

In PRINCE2 Agile, what is the primary purpose of a burn chart?

To record risks and issues encountered during a delivery timebox To assign specific team roles and formal responsibilities across a stage To visually track work remaining or completed over time To display the fixed budget allocation approved for the whole project

Correct Answer: To visually track work remaining or completed over time

A burn chart's primary purpose is to visually track work remaining or completed over time, giving the team a simple, transparent view of progress toward a goal such as a sprint or release. This supports the agile focus on transparency and empirical delivery.

Assigning roles and responsibilities is handled by the project's organization structure, not a burn chart. Recording risks and issues is the job of a risk register or issue log. Displaying fixed budget allocation relates to financial planning documents, not progress visualization.

The key concept tested is understanding burn charts as a progress tracking and transparency tool in agile delivery.

PRINCE2 Agile in the Wider Context

PRINCE2 Agile - PRINCE2 Agile in the Wider Context Example Questions

Question 1

Question 2

Question 3

Unlock Premium Access