Retros in PRINCE2 Agile Flashcards
How is PRINCE2 Agile not compatible with traditional contracts?
Traditional contracts show a list of requirements that need to be met in order for the product to be signed off. This is not in line with Agile as the details of the product may change or may not be known.
How can a contract portray the PRINCE2 Agile method?
A traditional contract covering the broad requirements would still suffice, but a different method is needed to define the detail (SOW, iterative scoping).
Guidance for creating a PRINCE2 Agile contract
Outline the broad requirements (i.e. a user should be able to).
Outline the need for trust, partnership, and collaboration.
Outline the level of risk. It should be proportional to the strength of the existing relationship between the parties (longer partnership means more trust).
The cost could be flexed as the requirements are unknown.
Focus on outcomes (benefits) as opposed to outputs (product).
Good to outline the amount of customer involvement that is needed in the contract.
Give some tangible milestones throughout the project.
Allow a method for the project to the stopped by the project board at any time.
Prioritise requirements
Incentivise timely delivery
