Continued Business Justification in Agile
Continued Business Justification in Agile
Continued Business Justification is one of the seven core principles of PRINCE2, and it plays an equally vital role within PRINCE2 Agile. This principle states that a project must remain desirable, viable, and achievable throughout its entire lifecycle. If a project can no longer be justified, it should be stopped. In an Agile context, this principle takes on additional dimensions because of the flexible, iterative, and value-driven nature of Agile delivery.
Why It Is Important
Every project consumes resources, time, and money. Without ongoing justification, organizations risk pouring investment into initiatives that no longer deliver value. In Agile environments, where requirements evolve rapidly and priorities shift, the risk of drifting away from the original business need is even higher.
Continued Business Justification ensures that:
1. The project remains aligned with organizational goals.
2. Value is delivered early and frequently, allowing benefits to be realized sooner.
3. Poor investments can be identified and halted quickly, avoiding waste.
4. Decisions are based on evidence rather than assumptions or sunk costs.
What It Is
The principle is embodied primarily in the Business Case, which documents the reasons for the project, expected benefits, costs, risks, and timescales. In PRINCE2, the Business Case is reviewed at key decision points to confirm that the project remains justified.
In PRINCE2 Agile, this concept is enriched by Agile thinking. Agile emphasizes delivering value incrementally, so justification is not just checked at stage boundaries but is continuously validated through the delivery of working products. The focus shifts toward value and benefits realization as the project proceeds.
How It Works in Agile
Frequent delivery of value: Agile delivers products in increments, meaning benefits can start flowing early. This provides ongoing evidence that the business case is being met.
Prioritization techniques: Tools like MoSCoW (Must have, Should have, Could have, Won't have) help ensure that the highest-value items are delivered first, protecting the business justification even if scope is flexed.
Fixing time and cost, flexing scope: In PRINCE2 Agile, time and cost are often fixed while scope and quality are variable. This means the business case can still be satisfied by delivering the most valuable features within the constraints, rather than attempting to deliver everything.
Continuous feedback: Regular reviews, retrospectives, and stakeholder feedback allow the team to confirm the project is still worthwhile, adjusting direction as needed.
Empirical decision-making: Instead of relying on lengthy up-front planning, Agile uses actual delivered outcomes to reconfirm justification.
How to Answer Exam Questions
When facing questions on this topic, focus on demonstrating that you understand both the PRINCE2 principle and how Agile enhances it. Examiners want to see that you can connect the theory to Agile practice.
Key points to remember:
1. Justification must be maintained throughout the project, not just at the start.
2. Agile enables early and frequent value delivery, supporting continued justification.
3. Flexing scope (rather than time and cost) helps protect the business case.
4. The Business Case is the primary management product linked to this principle.
5. A project that loses its justification should be stopped.
Exam Tips: Answering Questions on Continued Business Justification in Agile
Tip 1: Read the question carefully to identify whether it asks about the PRINCE2 principle, the Agile enhancement, or both. Tailor your answer accordingly.
Tip 2: Use keywords such as value, benefits, viable, desirable, and achievable to signal your understanding.
Tip 3: Remember the link between this principle and flexing scope. Questions often test whether you know that scope and quality are flexed while time and cost remain fixed to preserve justification.
Tip 4: When given a scenario, look for signs that a project may no longer be justified (rising costs, lost benefits, changed priorities) and be prepared to state that it should be reviewed or stopped.
Tip 5: Connect the principle to Agile behaviors and techniques such as MoSCoW prioritization, incremental delivery, and frequent feedback loops.
Tip 6: Avoid the common trap of thinking justification is a one-time activity. Emphasize the word continued in your answers.
By understanding both the foundational PRINCE2 principle and how Agile approaches strengthen it, you will be well prepared to answer any exam question on Continued Business Justification with clarity and confidence.
