Benefits Realization practice questions

Determine the technical infrastructure requirements.

Why wrong: Technical requirements are part of the project execution plan, not the benefits plan.

The technical specifications of the new infrastructure.

Why wrong: Technical specifications are not relevant to board-level benefits realization.

Assign technical staff to the project.

Why wrong: Staffing is an operational activity, not part of the benefits plan creation.

Detailed list of all software bugs encountered during development.

Why wrong: This is technical detail, not strategic value reporting.

A complete breakdown of the project team members' hours.

Why wrong: Resource tracking is a project management metric, not a governance metric.

Identify the project stakeholders.

Why wrong: Stakeholder identification is a precursor to planning, not the core task.

As a single aggregate number for the entire organization.

Why wrong: Aggregate numbers often mask specific failures or successes.

Only by the IT department, as they manage the system.

Why wrong: IT usually provides the tool; the business realizes the benefit.

Draft the user manual.

Why wrong: User manuals are documentation.

In a narrative format that focuses on technical project milestones.

Why wrong: Benefits need to be measurable, not narrative.

Design the technical architecture.

Why wrong: Architecture is a project execution phase.

Procure the hardware.

Why wrong: Procurement follows after the business case is established.

Immediately terminate the project to prevent further cost overruns.

Why wrong: Arbitrary termination ignores the benefits being realized, which might still outweigh the cost.

Ignore the cost overrun as long as the project delivery schedule remains on track.

Why wrong: Cost overruns directly degrade the net benefit realization.

Request an additional budget from the steering committee without analysis.

Why wrong: Budget requests must be supported by revised business value analysis.

The depreciation schedule of existing legacy assets.

Why wrong: Depreciation is an accounting adjustment, not a direct cash investment cost.

The projected increase in annual sales revenue.

Why wrong: This is a benefit, not a cost.

The market value of competitor technology.

Why wrong: Market value of external technology is irrelevant to internal project ROI.

An output is a strategic goal; an outcome is a project milestone.

Why wrong: Strategic goals are higher-level objectives, not outputs.

An output is the increased sales revenue; an outcome is the new CRM software.

Why wrong: The roles are reversed; software is the output, revenue is the outcome.

An output and an outcome are essentially the same and can be used interchangeably.

Why wrong: Outputs and outcomes serve very different functions in benefits planning.

To manage the technical development life cycle of the software.

Why wrong: This is the role of the technical lead or project manager.

To authorize the release of funds from the enterprise budget.

Why wrong: This is the role of the finance department or steering committee.

To audit the project documentation for compliance with PMBOK standards.

Why wrong: Auditing is a governance or audit function, not a benefits realization role.

The number of vendors involved in the project.

Why wrong: Vendor count is a procurement detail, not a value driver.

The total volume of code written.

Why wrong: Code volume is not a value metric.

To ensure the system meets all security standards.

Why wrong: Security compliance is usually part of the Go-Live process, not a PIR.

To finalize the payment for external contractors.

Why wrong: Contract payment is a procurement function.

To evaluate the performance of the project manager.

Why wrong: PIR is about the investment outcomes, not just the project performance.

To ensure software development complies with vendor licensing requirements.

Why wrong: Licensing is a compliance issue, not a benefits realization requirement.

To automate the generation of project status reports for stakeholders.

Why wrong: Status reporting is a project management activity, not a benefits realization core function.

To allocate budget for ongoing maintenance and support costs.

Why wrong: Budget allocation is a function of financial planning, not benefits tracking.

The high cost of cloud hosting services.

Why wrong: Cloud costs are an expense, not a benefit tracking challenge.

The requirement to have a steering committee.

Why wrong: Steering committees are a requirement, not a challenge to tracking.

The lack of software tools to track project milestones.

Why wrong: Project tools are generally available; the issue is benefit measurement.

A cost that was not included in the original budget.

Why wrong: This is a cost overrun.

A benefit that was planned but not achieved.

Why wrong: That is an 'unrealized benefit' or a failed metric.

The depreciation of hardware assets over time.

Why wrong: Depreciation is an accounting cost.

The vendor contract.

Why wrong: The contract governs the legal relationship, not the business success.

The technical design document.

Why wrong: This defines how the system is built, not why it is successful.

The project charter.

Why wrong: The charter provides authorization, but the business case details the value/success criteria.

The list of technical software vulnerabilities.

Why wrong: Vulnerabilities belong in a security plan.

The server hardware specifications.

Why wrong: Hardware specs are technical project details.

To minimize the IT budget.

Why wrong: The goal is value delivery, not just minimizing cost.

To manage the technical infrastructure components.

Why wrong: This is infrastructure management, not value management.

To automate the software development life cycle.

Why wrong: This is DevOps, not value management.

The steering committee met too frequently.

Why wrong: Governance meeting frequency does not directly impact user adoption.

The project lacked sufficient technical documentation.

Why wrong: Lack of docs rarely prevents system usage if the system is valuable.

The project was delivered under budget.

Why wrong: Being under budget is a positive project result.

The number of users trained on the new system.

Why wrong: Training metrics indicate adoption, not the resulting efficiency benefit.

The number of systems upgraded.

Why wrong: This is an output, not a measure of the benefit.

The total budget spent on software licenses.

Why wrong: This is a cost, not a benefit.

To conduct daily meetings with the development team.

Why wrong: Daily meetings are an operational activity.

To write the detailed technical specification for the project.

Why wrong: This is the role of architects and engineers.

To manage the daily vendor relationship.

Why wrong: This is the role of the vendor manager.

Increased revenue from new digital sales channels.

Why wrong: This is a direct, measurable financial benefit.

Decrease in server hardware acquisition costs.

Why wrong: This is a direct cost saving.

Reduction in annual software maintenance costs.

Why wrong: This is a direct, measurable financial benefit.

To secure the budget before the project is approved.

Why wrong: Budgeting is part of the financial planning process.

To identify technical risks in the software architecture.

Why wrong: Risk assessment is a separate project management process.

To ensure that the project team is selected correctly.

Why wrong: Staffing is a project management task.

A network diagram of project team communication channels.

Why wrong: This is a communication management tool.

A list of all server interdependencies.

Why wrong: This is a technical infrastructure map.

A schedule of hardware maintenance updates.

Why wrong: This is a maintenance plan.