Business Case Practice

The correct answer is 'Outputs'.

In PRINCE2 7, the term 'outputs' specifically refers to all artifacts that are produced during a project. These outputs are categorized into two main types:

1. Management products - documents and artifacts used to manage the project (such as plans, logs, registers, and reports)
2. Specialist products - the deliverables that meet the project's requirements and are handed over to the customer

This terminology is fundamental to PRINCE2's product-based planning approach.

Why the other answers are incorrect:

The second option describes deliverables but adds unnecessary qualifications about being 'tangible components of the project scope.' While this partially captures the concept, it doesn't encompass both management and specialist products, and the terminology isn't precise according to PRINCE2 7.

The third option, 'Work packages,' refers to a different concept in PRINCE2. Work packages are sets of information about required products and associated work that are agreed upon between the Project Manager and Team Manager. They are not the artifacts themselves but rather the instructions for creating them.

The fourth option describes products that have undergone a specific approval process. While products may be baselined and approved, this doesn't define what the artifacts are called in general. It's describing a state or status of products rather than the term for all project artifacts.

In PRINCE2 7, the Executive role has clear accountability for the Business Case throughout the project lifecycle.

The Executive is the member of the Project Board who owns the Business Case. This ownership means the Executive is ultimately accountable for ensuring that the Business Case:
- Provides viable justification for the investment
- Remains valid throughout the project
- Is reviewed and updated at key decision points
- Reflects the expected return on investment and value for money

This ownership is a fundamental responsibility of the Executive role, as they represent the business perspective and are accountable to corporate or programme management for the project's success.

Why the other answers are incorrect:

The Project Manager does not own the Business Case - they are responsible for maintaining and updating it on behalf of the Executive, but ownership and accountability remain with the Executive. While the Project Manager does coordinate updates and ensure the document is kept current, they do not have ownership.

The Senior User does not own the Business Case. The Senior User's role is to ensure that user needs are specified correctly and that the solution will deliver the required benefits. While they contribute to benefits validation and may provide input to the Business Case, they do not own it.

While it is true that the Project Manager develops and maintains the Business Case on behalf of the Executive, this does not mean they own it. The distinction between development/maintenance and ownership is crucial in PRINCE2 - the Executive retains ownership and accountability even though the Project Manager performs much of the practical work in creating and updating the document.

The correct answer is Dis-benefits.

In PRINCE2 7, dis-benefits are specifically defined as the measurable decline in one or more benefit areas that result from a project outcome. They are negative outcomes that are intentionally documented and managed alongside the positive benefits in the benefits management documentation, particularly in the Business Case and Benefits Management Approach.

Dis-benefits are:
- Perceived or actual negative outcomes
- Measured and tracked throughout the project lifecycle
- Documented in benefits management documentation
- Considered when evaluating whether a project remains viable
- Part of the overall benefits realization assessment

Why the other answers are incorrect:

The option about negative risks materializing into issues is incorrect because this describes the risk management process, not benefits management. When risks become issues, they are managed through issue management procedures, not tracked as dis-benefits in benefits documentation.

The option about adverse impacts from risk responses is incorrect because it specifically relates to secondary risks or consequences of risk treatment actions. While these might eventually be captured as dis-benefits, this terminology refers to risk response side-effects rather than the formal PRINCE2 term for negative outcomes in benefits management.

The option about unfavorable consequences as trade-offs for strategic objectives, while conceptually related to dis-benefits, is not the specific PRINCE2 terminology. This describes a general project management concept about trade-offs, but PRINCE2 uses the precise term 'dis-benefits' to refer to these measurable negative outcomes in the benefits management framework.