Prepare for the PRINCE2 Agile Test with focused questions. Engage with interactive quizzes that offer hints and explanations, helping you ace your exam with confidence!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


How should the work package for the Story of Cheese be authorized?

  1. Through a written proposal submitted to stakeholders

  2. During the project board meeting

  3. At a timebox planning meeting with team agreement

  4. By the project manager in isolation

The correct answer is: At a timebox planning meeting with team agreement

The work package for the Story of Cheese should be authorized at a timebox planning meeting with team agreement because this approach promotes collaboration and ensures that all team members have a shared understanding of the work to be completed. This method aligns with the agile principles of PRINCE2 Agile, which emphasize the importance of team involvement and communication in the planning process. In agile environments, the emphasis is on flexibility, responsiveness to change, and active participation from the development team. By discussing and agreeing on the work during a timebox planning meeting, the team can collectively determine how to tackle the story, clarify roles, establish priorities, and address any potential challenges upfront. This collaborative decision-making also fosters ownership and accountability among team members, increasing the likelihood of successful delivery. The other options do not encompass the same level of collaboration and engagement with the team. A written proposal submitted to stakeholders may not include the input of the entire team, potentially leading to misalignment on expectations. Authorizing during a project board meeting places the decision in a more formal context that may not be as conducive to agile methodologies. Authorizing by the project manager in isolation further removes the collaboration aspect, which is crucial in agile development, as it may lead to decisions made without the team's insights or agreement