Study PRINCE2 Agile Practitioner v2 Prioritization, Feedback, and Collaboration: key concepts, common traps, and exam decision cues.
Prioritization and feedback help PRINCE2 Agile protect value. Practitioner scenarios may show too much work, unclear stakeholder expectations, delayed decisions, or conflict over what matters most.
Prioritization should make tradeoffs visible. Techniques such as MoSCoW can help distinguish must-have outcomes from lower-priority wants, but the technique must be used responsibly. A must-have should not simply mean “someone important wants it.” It should reflect the minimum needed for a viable and justified outcome.
Feedback is valuable only when it changes understanding. If feedback reveals a risk, quality issue, or change to business value, the project should respond through the appropriate control route.
Good collaboration reduces handoff delay, unclear requirements, and late surprises. It does not mean everyone has equal authority over every decision. Practitioner answers should keep collaboration and accountability together.
A product owner labels every requested feature as must-have, making the timebox impossible. What is the best Practitioner response?
A. Accept all must-have labels without challenge.
B. Facilitate prioritization against minimum viable outcome, business value, and project constraints.
C. Remove all stakeholder involvement.
D. Extend the timebox without checking tolerance.
Best answer: B
Why: Prioritization must support a feasible, value-focused outcome. Labels should be tested against business need and project constraints.