PRINCE2 Agile Foundation Practice Questions

How should Brand-u-Like handle changes to the detailed brief?

1. Disallow any form of changes during delivery.

2. Allow changes but charge separately for them.

3. Insist that all changes require project board approval.

4. Implement changes without informing stakeholders.

The correct answer is: Allow changes but charge separately for them.

Allowing changes but charging separately for them is a practical approach in project management, particularly within the PRINCE2 Agile framework. This option recognizes the reality that projects often evolve as new information comes to light or as stakeholders’ needs change during the delivery process. By permitting changes, Brand-u-Like demonstrates flexibility and responsiveness, which are crucial in agile environments. Charging separately for these changes serves a dual purpose. First, it ensures that the project maintains its financial viability, as unplanned changes can strain resources and timelines. Second, it sets clear expectations with stakeholders about the implications of modifying the original brief. This transparency helps maintain trust and accountability, as stakeholders understand that changes come with potential costs and adjustments to timelines. In contrast, disallowing any form of changes during delivery inflexibly locks the project into its initial scope and can lead to dissatisfaction if stakeholder needs evolve. Requiring project board approval for every change might slow down responsiveness, hindering the agile principle of promoting adaptive planning. Lastly, implementing changes without informing stakeholders undermines communication and trust, which is counterproductive in any collaborative project environment.