PRINCE2 Agile - Change theme Flashcards
How is change treated in PRINCE2 Agile?
Agile embraces change. It comes with an understanding that change is inevitable and helps to build a more suitable product. PRINCE2 is more change-averse and acts to “control” change.
In PRINCE2 Agile, a change is something that impacts the product, whereas in PRINCE2 it can be anything that impacts the project.
Combining the two approaches allows for innovation and pivots in the details and overall control of the change in the project.
What degree of change is welcomed in PRINCE2 Agile?
Changes to the baseline need to be carefully managed and are generally seen in a negative light. These are called baseline changes. Changes to the details of the product are generally welcomed. These are called detailed changes.
In PRINCE2 Agile, changes that will impact the ability to build an MVP are taken very seriously.
Where is the focus of most change in PRINCE2 Agile?
The scope and deliverables are the most common points to be flexed, meaning most of the change occurs in this area. Time and cost are rarely flexed.
How can the project be set up to handle change?
The project baseline and requirements can be specified in an appropriate level of detail that matches the impact of deviation down the line. Furthermore, instead of a binary requirement (it is right or it is wrong), it could be a spectrum of requirements (must do X, should do Y, could do Z). The latter is particularly good when the project acts in an uncertain environment.
The product requirements can be general at first, then be specified later on in the project.
Good risk management can lessen the impact of change.
What is needed to respond effectively to change
- Proactively finding and handling change
- Having a consistent and good change control approach
- Logging the change and what type it is
- Configuration Management -
- Document config, test the product, and and record the test results for each iteration
- Good for the audit trial and for future learning. Good to version the iterations.
- When using versions, can return to a previous version if there are major issues.
How does escalating change work in PRINCE2 Agile?
The Agile team may be handle change so long as it falls within the tolerances set by the PM. If the tolerances are exceeded, the Agile team needs to escalate. Any changes that impact the baselines need to be escalated to the PM, PB, or CA.
What happens when a party wants control over changes to details of the spec in an Agile environment?
This should not happen. Teams should be able to self-organise and prioritise to hit deadlines and be on cost.
