2. Project Strategy, Selection and Business Case

Introduction and Context

Projects are not isolated technical exercises. They are instruments through which an organization implements strategy, changes its operating capability, responds to competition, complies with regulation, or creates new value for customers and other stakeholders. In production management, a project may involve introducing an automated assembly line, expanding capacity, redesigning a plant layout, implementing an enterprise resource planning system, developing a new product, or reducing energy consumption. Each proposal competes for scarce capital, managerial attention, skilled employees, production time, and organizational capacity. The central managerial question is therefore not simply whether a project can be completed, but whether it should be undertaken.

Project selection connects organizational intention with disciplined investment decision-making. It requires managers to translate broad strategic priorities into clear project objectives, compare alternative proposals, assess feasibility, quantify economic consequences, recognize uncertainty, and recommend a course of action. A well-prepared business case provides the evidence and logic for that recommendation. It also establishes a reference point against which benefits, costs, risks, and strategic contribution can later be evaluated.

The quality of selection decisions is particularly important in production environments. A technically attractive project may interrupt operations, create dependence on a single supplier, require unavailable skills, or generate benefits that are difficult to realize. Conversely, a project with a modest immediate financial return may protect regulatory compliance, preserve a strategic customer, or build an important capability. Project selection must therefore combine financial analysis with strategic, operational, risk, sustainability, and stakeholder considerations.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain the relationship between organizational strategy, production strategy, portfolios, programmes, and projects.

2. Translate strategic priorities into measurable project objectives and success criteria.

3. Distinguish project ideas, feasibility studies, business cases, and project charters.

4. Develop a structured feasibility study and business case.

5. Apply weighted scoring, cost–benefit analysis, NPV, IRR, payback, and sensitivity analysis.

6. Evaluate projects using strategic alignment, risk, capability, sustainability, and operational criteria.

7. Identify bias, uncertainty, ethical concerns, and governance risks in project selection.

8. Make and communicate a defensible project recommendation.

From Organizational Strategy to Project Objectives

Organizational strategy defines how an enterprise intends to create and sustain value. It may emphasize low cost, dependable delivery, quality leadership, flexibility, innovation, resilience, sustainability, or customer intimacy. Production strategy converts these priorities into decisions about process design, capacity, technology, facilities, sourcing, workforce, quality systems, inventory, and improvement methods. Projects provide temporary structures for making significant changes in these areas.

The relationship can be expressed as a hierarchy:

Organizational strategy → production strategy → strategic themes → portfolio priorities → programme or project objectives → deliverables and benefits.

For example, an organization may adopt the strategic theme of improving responsiveness to customers. The production strategy may require shorter lead times and greater product variety. A project may then implement flexible manufacturing cells and a digital production-planning system. The deliverables could include redesigned workstations, software configuration, employee training, and revised procedures. The intended benefits might be a 20 per cent reduction in average lead time, improved schedule adherence, and the ability to produce smaller batches economically.

A project objective should state the result to be achieved, not merely the activity to be performed. “Install a new production planning system” is primarily a deliverable statement. “Improve schedule adherence from 82 per cent to 95 per cent within six months of system stabilization” is a benefits-oriented objective. Strong objectives are specific, measurable, achievable within the organization’s influence, relevant to strategy, and time-bound. They should also identify the baseline, target, measurement method, owner, and period over which the benefit is expected.

A useful distinction is made between outputs, outcomes, and benefits. Outputs are the products or capabilities delivered by the project. Outcomes are the changes resulting from use of those outputs. Benefits are measurable improvements valued by the organization or its stakeholders. A new inspection system is an output; faster detection of defects is an outcome; lower scrap cost and improved customer acceptance are benefits. The project team may control outputs, but benefit realization usually depends on operational managers, users, suppliers, and customers after implementation.

Strategic alignment should not be treated as a slogan. It can be tested by asking:

• Which stated strategic priority does the project support?
• What problem or opportunity does it address?
• What happens if the project is not undertaken?
• Does it strengthen a distinctive capability or merely duplicate existing activity?
• Is the timing consistent with other strategic initiatives?
• Are the required resources available without damaging more important operations?

Projects should also be assessed for strategic disalignment. A project may produce a positive financial return while increasing dependence on a technology that conflicts with the organization’s architecture, reducing workforce flexibility, or undermining environmental commitments. Alignment is therefore a matter of coherence, not just financial attractiveness.

Project Ideas, Feasibility Studies, and Business Cases

A project idea is an initial proposition, often expressed as a problem, opportunity, customer request, regulatory requirement, or proposed improvement. Ideas should be recorded and screened rather than accepted informally. Early screening prevents organizational energy being consumed by proposals that are clearly inconsistent with strategy or impossible under current constraints.

A feasibility study investigates whether a proposed project is practicable and sufficiently attractive to justify further commitment. It normally examines technical, operational, commercial, financial, legal, environmental, organizational, and schedule feasibility. Feasibility is not the same as certainty. It establishes the quality of available evidence, identifies assumptions, and determines whether remaining uncertainty is acceptable for the next decision gate.

A business case is a structured argument for investing in a project. It explains the need, options, expected value, costs, risks, dependencies, implementation approach, and governance arrangements. It is both an investment proposal and a management instrument. The business case should enable decision-makers to compare alternatives and understand the consequences of approval, postponement, modification, or rejection.

A project charter is normally prepared after authorization. It formally establishes the project, appoints the project manager, states high-level objectives, identifies key stakeholders, and grants authority to use organizational resources. The business case supports the decision to authorize; the charter initiates and frames the authorized project. Confusing these documents can lead to premature commitment before the investment logic has been adequately examined.

Building a Feasibility Study

A practical feasibility study begins with a clearly defined problem or opportunity. The problem statement should distinguish symptoms from causes. For instance, “late deliveries” may result from poor scheduling, inadequate capacity, unreliable suppliers, excessive changeover time, or inaccurate demand information. A project selected without diagnosing the underlying cause may deliver an impressive technical solution to the wrong problem.

The study should identify a baseline. Relevant baseline measures may include throughput, cycle time, capacity utilization, defect rate, changeover time, energy consumption, labour hours, maintenance cost, service level, or working capital. Without a baseline, projected improvement cannot be tested credibly.

The next step is to define alternatives. The comparison should include a “do nothing” or “status quo” option, although doing nothing may involve consequences and costs. Other alternatives may include improving the existing process, purchasing an off-the-shelf solution, developing a customized solution, outsourcing, leasing equipment, or implementing the change in stages. Considering alternatives guards against evaluating only the sponsor’s preferred solution.

Technical feasibility examines whether the proposed technology, process, materials, infrastructure, and skills are available and compatible. In a production setting, questions include whether equipment can integrate with existing machines, whether utilities and floor space are adequate, whether data standards are compatible, and whether the process can meet required tolerances and volumes.

Operational feasibility considers whether the organization can absorb and sustain the change. It includes workforce competence, maintenance arrangements, operating procedures, shift patterns, supplier readiness, training, disruption during installation, and acceptance by users. A solution that works in a demonstration but cannot be maintained on the shop floor is not operationally feasible.

Commercial feasibility addresses customers, competitors, suppliers, contractual commitments, market demand, pricing, and supply-chain implications. Financial feasibility estimates investment, operating effects, financing, cash flows, and returns. Legal and regulatory feasibility considers permits, safety requirements, labour law, data protection, intellectual property, environmental obligations, and contractual restrictions. Schedule feasibility examines whether the project can be completed in time to capture the proposed benefit.

The study should distinguish assumptions from evidence. An assumption might be that demand will grow by 8 per cent annually; evidence might be a contracted order or validated market forecast. A risk register should record uncertain events, their causes, consequences, probability, impact, response, and owner. At the feasibility stage, estimates should generally be expressed as ranges or scenarios rather than as unjustifiably precise single values.

Designing the Business Case

A robust business case commonly contains the following logic, presented in a form appropriate to the organization:

1. Executive recommendation: the decision requested and the principal reasons for it.

2. Strategic context: the organizational priority supported and the consequences of inaction.

3. Problem or opportunity: evidence of the current condition and its significance.

4. Objectives and benefits: measurable outcomes, benefit owners, and realization measures.

5. Options appraisal: status quo and alternative solutions, including key trade-offs.

6. Scope and deliverables: what is included, excluded, and required for implementation.

7. Financial case: investment, operating costs, benefits, cash flows, funding, and appraisal results.

8. Risk and uncertainty: principal risks, assumptions, scenarios, and mitigations.

9. Implementation and resources: schedule, capability, procurement, governance, and dependencies.

10. Impact assessment: effects on employees, customers, suppliers, safety, environment, and communities.

11. Recommendation and decision gates: proposed approval, conditions, review points, and authorities.

Benefits should be assigned to owners who can influence their realization. For example, the project manager may be responsible for delivering an automated line, while the production manager owns the benefits associated with throughput and labour productivity. A benefits register can record each benefit, baseline, target, measurement date, owner, dependencies, and current status.

A business case should show the full life-cycle cost rather than only the purchase price. Relevant costs may include design, procurement, installation, commissioning, training, downtime, software licences, maintenance, spare parts, energy, upgrades, disposal, and decommissioning. Benefits may include additional contribution margin, avoided cost, reduced waste, lower inventory, improved capacity, reduced penalties, risk avoidance, and residual asset value. Double counting must be avoided. For example, a claimed revenue increase should not also be counted as a separate equivalent productivity benefit unless the two are demonstrably distinct.

Investment Appraisal for Project Selection

Cost–Benefit Analysis

Cost–benefit analysis compares the expected value of benefits with the costs required to achieve them. Benefits can be financial or, where appropriate, converted into monetary values. A simple benefit–cost ratio is:

Benefit–cost ratio = Present value of benefits ÷ Present value of costs.

A ratio greater than one indicates that quantified benefits exceed quantified costs, subject to the assumptions and decision rules used. Cost–benefit analysis is useful for comparing options, but it becomes weak when important outcomes cannot be valued reliably. Safety, reputation, employee well-being, resilience, and strategic capability may need to be presented separately rather than forced into questionable monetary estimates.

Payback Period

The payback period is the time required for cumulative cash inflows to recover the initial investment. If annual cash inflows are constant:

Payback period = Initial investment ÷ Annual cash inflow.

For uneven cash flows, cumulative cash flow is traced year by year, and the fraction of the recovery year is calculated. Payback is easy to communicate and emphasizes liquidity and exposure. However, it ignores cash flows after payback and, in its simple form, ignores the time value of money. A project with a short payback may therefore be less valuable than a project with a longer payback but much greater total return.

Net Present Value

Net present value recognizes that money received in the future is worth less than money received today. It discounts expected net cash flows at a rate reflecting the organization’s required return and risk:

NPV = Σ [CFt ÷ (1 + r)t] − I0

where CFt is the net cash flow in period t, r is the discount rate, and I0 is the initial investment. A positive NPV indicates that the project is expected to create value above the required return, assuming the forecast and discount rate are appropriate. Among mutually exclusive projects with comparable risk, NPV is usually the strongest financial criterion because it measures absolute value creation.

The discount rate should be selected transparently. It may reflect the organization’s cost of capital, project risk, financing structure, or an approved corporate hurdle rate. Applying a low rate to a highly uncertain project can overstate value; applying an excessively high rate to a strategic or risk-reducing project can understate it. Cash flows should be consistent: nominal cash flows should use a nominal rate, and real cash flows should use a real rate.

Internal Rate of Return

The internal rate of return is the discount rate that makes NPV equal to zero. It expresses expected return as a percentage and is often attractive to managers because it can be compared with a hurdle rate. A project may be considered financially acceptable when its IRR exceeds the required return.

IRR has limitations. Projects with unconventional cash flows can have more than one IRR or no meaningful IRR. It can also rank mutually exclusive projects differently from NPV, especially when project sizes, timing, or reinvestment assumptions differ. When NPV and IRR conflict, managers should investigate the source of the conflict rather than rely automatically on the percentage measure. NPV normally provides the better basis for choosing between mutually exclusive investments.

Worked Illustration

Suppose a production project requires an initial investment of £500,000. It is expected to generate net cash inflows of £180,000 in each of the next four years. At a discount rate of 10 per cent, the present value factor for a four-year annuity is approximately 3.170. The present value of inflows is therefore approximately £570,600, producing an NPV of £70,600. The simple payback period is 500,000 ÷ 180,000, or approximately 2.78 years. The project appears financially attractive, but the conclusion should still be tested against installation disruption, demand uncertainty, technical compatibility, and the value of alternative uses of the funds.

Sensitivity and Scenario Analysis

Sensitivity analysis examines how a decision changes when one assumption changes while other assumptions remain constant. A project may be particularly sensitive to selling price, production volume, energy cost, implementation delay, labour savings, scrap reduction, or capital cost. If a small change in an assumption turns a positive NPV into a negative one, that assumption deserves careful validation and active monitoring.

Scenario analysis changes several related assumptions together. A downside scenario might combine lower demand, higher installation cost, and a six-month delay. An upside scenario might combine faster adoption, higher utilization, and lower maintenance cost. Scenario analysis is more realistic than changing variables independently when assumptions are correlated.

Decision-makers should also distinguish sensitivity from probability. Sensitivity shows the effect of change; it does not state how likely the change is. Where sufficient data exist, expected monetary value, simulation, decision trees, or probabilistic forecasting may be used. These methods should illuminate uncertainty, not create a false impression of mathematical certainty.

Multi-Criteria Selection and Strategic Alignment

Financial appraisal alone is inadequate when projects differ in strategic importance, risk, compliance status, or capability-building potential. A weighted scoring model makes non-financial criteria explicit. The organization first defines criteria, assigns weights whose total equals 100 per cent, rates each project, and calculates a weighted score:

Weighted score = Σ (criterion weight × project rating).

Possible criteria include strategic alignment, financial value, customer impact, operational improvement, technical feasibility, implementation risk, regulatory necessity, sustainability, organizational capability, and time to benefit. Rating scales must be defined clearly. For example, a rating of 1 may mean very weak and 5 very strong, with evidence required for each score.

Weights should reflect actual priorities rather than being manipulated to justify a preferred project. A governance group may conduct a calibration exercise in which several decision-makers independently score proposals and then discuss differences. Scores should be accompanied by rationale and confidence levels. A high score based on weak evidence should not be treated as equivalent to a high score based on validated data.

Portfolio selection adds another dimension. Projects should be considered together because they may share resources, technologies, suppliers, benefits, or risks. A portfolio may need a balance of mandatory compliance projects, efficiency projects, innovation projects, customer projects, and capability investments. Selecting every individually attractive project can create overload, delay, and diluted accountability. Portfolio managers therefore consider capacity constraints, interdependencies, sequencing, concentration risk, and strategic balance.

Governance, Ethics, and Professional Judgement

Project selection involves power as well as analysis. Sponsors may overstate benefits to secure approval, underestimate costs to pass a funding threshold, or define scope narrowly so that risks appear smaller. Common cognitive biases include optimism bias, confirmation bias, anchoring on an early estimate, sunk-cost bias, and the tendency to imitate fashionable technologies. Independent challenge, documented assumptions, reference-class information, and staged approvals can reduce these risks.

Ethical business cases present inconvenient information as well as attractive outcomes. They disclose uncertainty, distributional effects, safety concerns, workforce consequences, environmental impacts, and conflicts of interest. A project should not be approved merely because its financial benefits are strong if it creates unacceptable safety risks, violates legal requirements, misuses personal data, or shifts significant harm to vulnerable stakeholders.

Governance should specify who proposes, evaluates, approves, funds, reviews, and terminates projects. Approval limits, segregation of duties, procurement controls, audit trails, and stage gates improve accountability. A project that no longer supports strategy should be capable of being stopped, even after substantial expenditure. Past expenditure is a sunk cost and should not determine future investment; the relevant question is whether the remaining costs and benefits justify continuation.

Digital tools can improve selection by integrating financial models, portfolio dashboards, resource data, risk registers, and benefits tracking. Analytics can identify trends in historical estimates and actual performance, while scenario tools can test alternative assumptions. Artificial intelligence may assist with demand forecasting, option generation, document analysis, and anomaly detection. However, AI-generated recommendations require human validation because training data may be biased, assumptions may be opaque, and strategic or ethical judgements cannot be delegated automatically. Sensitive commercial and personal information also requires appropriate cybersecurity and access controls.

An Illustrative Case: Selecting an Automated Inspection Project

Background

A fictional manufacturer of precision components supplies several industrial customers. Its strategic priorities are dependable quality, shorter lead times, and reduction of avoidable production waste. Final inspection is currently manual. The organization is considering a machine-vision inspection project costing £420,000, including cameras, software, integration, training, and commissioning.

Situation and Problem

Inspection results vary between shifts, defects are sometimes detected late, and inspectors spend significant time on repetitive checks. Management estimates that the project could reduce scrap and rework by £120,000 per year, reduce overtime by £45,000 per year, and create additional usable capacity worth an estimated £70,000 per year. Annual software support and maintenance are expected to cost £35,000. The project would require a planned production interruption during installation and would change inspection roles.

The proposal is strategically relevant, but the financial estimate depends on whether the system can detect the full range of defects and whether released capacity will actually be used. There is also a risk that poor-quality training data will reduce accuracy when product mix changes.

Analysis of Options

The status quo avoids capital expenditure but retains current quality variation and limits capacity. A lower-cost option would improve manual inspection through standardized work, additional training, and sampling redesign. A full machine-vision solution offers greater long-term capability but requires integration with production equipment and the quality database. A staged pilot on one product family would cost £95,000 and would provide evidence before full deployment, although it would delay some benefits.

The financial case for the full project uses an estimated annual net benefit of £200,000: £120,000 scrap and rework reduction, £45,000 overtime reduction, and £70,000 capacity value, less £35,000 support cost. The simple payback is approximately 2.1 years before considering installation disruption and taxes. At a 10 per cent discount rate, the project may produce a positive NPV over its useful life, but the result is sensitive to the capacity benefit and defect-detection rate.

A weighted scoring model is also applied. Criteria are strategic alignment, financial value, quality impact, technical feasibility, implementation risk, workforce readiness, and sustainability. The full project scores strongly on alignment and quality but less strongly on technical risk. The pilot scores lower on immediate financial value but higher on evidence generation and risk control. The status quo scores well only on low immediate expenditure.

Recommended Approach

The evaluation team recommends the staged pilot, subject to defined success criteria. The pilot must demonstrate a specified detection rate, false-rejection rate, data integration, operator usability, and validated financial effect. A decision gate after the pilot will determine whether to proceed to full deployment. The business case assigns the quality manager responsibility for defect reduction benefits, the production manager responsibility for capacity utilization, and the project manager responsibility for the pilot deliverables and evidence.

Outcome and Learning Points

In this illustrative case, the most rational decision is not necessarily the largest or fastest investment. The staged approach purchases information and reduces exposure while preserving the option to scale. It also recognizes that a benefit estimate is not automatically a realized benefit. The case demonstrates five principles: strategic fit must be made explicit; alternatives matter; financial results depend on operational assumptions; uncertainty should shape the implementation path; and benefit ownership must continue after project delivery.

Challenges and Common Mistakes

Several errors recur in project selection. The first is beginning with a solution rather than a problem. The second is treating revenue forecasts as benefits without analyzing demand, price, capacity, and contribution margin. The third is omitting transition costs and operational disruption. The fourth is using a single optimistic estimate instead of ranges and scenarios. The fifth is double counting benefits or confusing outputs with outcomes. The sixth is ignoring opportunity cost: resources committed to one project cannot simultaneously support every other proposal.

Other mistakes include selecting a project because a competitor has adopted similar technology, assuming that a high IRR always means superior value, failing to include the status quo, assigning arbitrary scoring weights, and approving projects without named benefit owners. A technically sound project can fail through weak change management, inadequate training, poor data, or lack of post-implementation measurement.

Best practice is to use a proportionate, evidence-based process. Small low-risk projects should not face the same documentation burden as major capital investments, but every proposal should state its purpose, alternatives, assumptions, costs, benefits, risks, and decision authority. Independent review should be used for material investments. Stage gates should permit continuation, revision, postponement, or termination. After implementation, actual results should be compared with the business case so that the organization learns how to improve future estimates and decisions.

Current Developments

Project selection is increasingly influenced by resilience, decarbonization, cyber risk, supply-chain transparency, and the economics of digital operations. Organizations are evaluating not only direct financial return but also exposure to disruption, energy intensity, data governance, and the ability to adapt production systems. Digital twins, advanced analytics, and integrated portfolio platforms can improve option modelling and benefit monitoring, although their value depends on data quality and managerial capability.

There is also growing interest in real-options thinking. A project may have value because it creates the right, but not the obligation, to expand, defer, abandon, or switch technology as information improves. Pilot projects, modular investments, and staged commitments can therefore be viewed as ways of preserving strategic flexibility. This perspective is especially useful where uncertainty is high and irreversible expenditure should be delayed until critical assumptions are tested.

Chapter Summary

Project selection is the process of deciding which proposed investments best support organizational strategy and can be delivered within available constraints. Production strategy translates broad priorities into operational capabilities, while projects create the temporary interventions needed to develop those capabilities. Effective objectives distinguish outputs, outcomes, and benefits and include measurable targets, baselines, owners, and time frames.

Feasibility studies test whether a proposal is technically, operationally, commercially, financially, legally, environmentally, and organizationally practicable. A business case presents the problem, alternatives, strategic contribution, costs, benefits, risks, implementation plan, and governance required for an informed decision. Financial tools include cost–benefit analysis, payback, NPV, IRR, sensitivity analysis, and scenario analysis. These tools must be supplemented by weighted scoring and portfolio analysis when strategic, operational, regulatory, sustainability, or capability factors are important.

Sound decisions depend on transparent assumptions, independent challenge, ethical disclosure, benefit ownership, stage-gated governance, and recognition of uncertainty. Digital analytics and AI can support analysis but do not replace professional judgement. The strongest selection process does not merely identify attractive projects; it chooses a balanced set of initiatives that the organization can absorb and convert into realized benefits.

Key Terms

Business case: A structured justification for investing in a project, including options, costs, benefits, risks, and implementation arrangements.

Feasibility study: An investigation into whether a proposed project is practicable and sufficiently attractive to proceed.

Strategic alignment: The degree to which a project supports organizational strategy and production priorities.

Portfolio: A collection of projects, programmes, and other work managed together to achieve strategic objectives.

Programme: A coordinated group of related projects managed to obtain benefits that would not arise from managing them separately.

Project objective: A specific result the project is intended to achieve.

Output: A product, service, or capability delivered by a project.

Outcome: A change produced through the use or adoption of project outputs.

Benefit: A measurable improvement valued by the organization or its stakeholders.

Benefit owner: The person accountable for realizing and measuring a specified benefit.

Baseline: The formally established current performance or reference condition against which change is assessed.

Payback period: The time required for cumulative cash inflows to recover the initial investment.

Net present value (NPV): The present value of future net cash flows less the initial investment.

Internal rate of return (IRR): The discount rate at which a project’s NPV equals zero.

Discount rate: The rate used to convert future cash flows into present values.

Sensitivity analysis: Examination of how a result changes when one assumption is varied.

Scenario analysis: Evaluation of outcomes under internally consistent combinations of assumptions.

Weighted scoring model: A multi-criteria method that combines ratings with assigned criterion weights.

Stage gate: A formal decision point at which a project is reviewed and continued, changed, deferred, or stopped.

Opportunity cost: The value of the best alternative use of resources committed to a project.

Review Questions

Short Answer Questions

1. What is the difference between a project output, outcome, and benefit?

2. Why should the status quo be included as an option in a feasibility study?

3. State the principal purpose of a business case.

4. What does a positive NPV indicate, subject to the reliability of the assumptions?

5. Why is a benefit owner required after a project has delivered its outputs?

Long Answer Questions

1. Explain how organizational strategy is translated into production projects, using an appropriate manufacturing example.

2. Describe the main components of a feasibility study and explain why each is important.

3. Compare payback, NPV, and IRR as methods of project investment appraisal.

4. Explain how a weighted scoring model can complement financial appraisal in project selection.

5. Discuss the governance and ethical issues that can affect the credibility of a business case.

Analytical / Application Questions

1. A project requires an investment of £600,000 and generates annual net cash inflows of £175,000 for five years. Calculate the simple payback period and explain two reasons why payback alone is insufficient for selection.

2. A proposed automation project has a positive NPV only when demand growth exceeds 6 per cent. Identify the managerial implications of this sensitivity and recommend actions before approval.

3. Two projects have similar NPVs, but one supports regulatory compliance and the other creates optional capacity for future growth. Design a weighted selection approach that could help a portfolio committee make a defensible decision.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a project benefit from a project output?

A. An output is always financial, while a benefit is always technical

B. An output is delivered by the project, while a benefit is a measurable improvement resulting from its use

C. An output occurs after implementation, while a benefit occurs before authorization

D. An output is a risk estimate, while a benefit is a project constraint

Correct Answer: B. An output is delivered by the project, while a benefit is a measurable improvement resulting from its use

Question 2

A production project has a positive NPV but conflicts with the organization’s stated sustainability strategy. What is the most appropriate conclusion?

A. Approve it automatically because NPV is positive

B. Reject all financially positive projects with environmental effects

C. Evaluate the conflict explicitly and compare the project with strategically consistent alternatives

D. Ignore sustainability because it cannot be measured financially

Correct Answer: C. Evaluate the conflict explicitly and compare the project with strategically consistent alternatives

Question 3

Which item is most appropriately examined under operational feasibility?

A. Whether the organization can train operators and maintain the new equipment

B. Whether the discount rate is below the inflation rate

C. Whether the project has multiple IRRs

D. Whether a competitor has adopted the technology

Correct Answer: A. Whether the organization can train operators and maintain the new equipment

Question 4

An investment of £500,000 produces constant annual net cash inflows of £125,000. What is the simple payback period?

A. 2 years

B. 3 years

C. 4 years

D. 5 years

Correct Answer: C. 4 years

Question 5

Why is NPV generally preferred when choosing between mutually exclusive projects of different scale?

A. It ignores the timing of cash flows

B. It measures absolute value created after allowing for the time value of money

C. It always produces a higher percentage return

D. It excludes the initial investment

Correct Answer: B. It measures absolute value created after allowing for the time value of money

Question 6

What does sensitivity analysis primarily reveal?

A. The legally responsible project sponsor

B. The exact probability of every future event

C. How changes in assumptions affect the project’s result

D. The number of stakeholders in the project

Correct Answer: C. How changes in assumptions affect the project’s result

Question 7

A weighted scoring model gives a project a high overall score, but most ratings are based on unvalidated assumptions. What should decision-makers do?

A. Treat the score as conclusive because the mathematics is correct

B. Increase the project’s budget to compensate

C. Review the evidence and confidence behind the ratings before approval

D. Remove all non-financial criteria

Correct Answer: C. Review the evidence and confidence behind the ratings before approval

Question 8

Which practice best reduces optimism bias in a business case?

A. Using only the sponsor’s preferred estimate

B. Excluding the status quo option

C. Using independent challenge, ranges, scenarios, and evidence from comparable projects

D. Reporting benefits without assigning owners

Correct Answer: C. Using independent challenge, ranges, scenarios, and evidence from comparable projects

Question 9

In the illustrative inspection project, why was a pilot recommended rather than immediate full deployment?

A. The project had no strategic relevance

B. The pilot could test critical technical and benefit assumptions while limiting exposure

C. Pilots always have higher NPVs than full projects

D. The organization did not need quality improvement

Correct Answer: B. The pilot could test critical technical and benefit assumptions while limiting exposure

Question 10

Which statement about IRR is correct?

A. It is the discount rate that makes NPV equal to zero

B. It is always superior to NPV for ranking projects

C. It measures the project’s payback in months

D. It excludes all future cash flows

Correct Answer: A. It is the discount rate that makes NPV equal to zero