Skip to main content
CBE NEXUS · GLOBAL HIGHER EDUCATION

Chapter 2: Project Strategy, Business Cases and Feasibility

Undergraduate Bachelor of Project Management · Year 1 · Full study notes, applied methods and assessment guide

Chapter overview

This chapter develops undergraduate-level understanding of project strategy, business cases and feasibility. It combines conceptual explanations, practical methods, decision frameworks, worked examples and applied cases. Students should connect each method to project context, governance, people, evidence and measurable outcomes rather than treating tools as isolated templates.

Learning outcomes: explain the chapter's key terminology; apply relevant methods to a realistic project; interpret evidence and assumptions; evaluate limitations and risks; communicate a defensible recommendation; and connect project outputs with stakeholder needs and intended benefits.

Concept map: Project Strategy, Business Cases and Feasibility

Project contextNeed and objectivesAnalysisEvidence and optionsDecisionAuthority and actionControlMeasure and learn

This diagram is a learning aid. Apply the sequence to the chapter topics and identify the feedback loops needed when assumptions or conditions change.

Chapter contents

1. Strategic alignment2. Problem definition and opportunity framing3. Objectives and measurable outcomes4. Options appraisal and the do-nothing case5. Feasibility dimensions6. Technical and operational feasibility7. Financial appraisal and affordability8. Economic appraisal and wider value9. Cost-benefit analysis10. Worked NPV example11. Payback, ROI and benefit-cost ratio12. Risk-adjusted business cases13. Market analysis and demand forecasting14. Environmental and social appraisal15. Procurement and delivery feasibility16. Business case structure and assurance17. Decision-making and investment governance18. Case study: digital student servicesAssessment questions

1. Strategic alignment

A project should exist because it contributes to a stated organisational or public objective. Strategic alignment connects the proposed change to priorities such as service access, productivity, resilience, compliance, customer experience or infrastructure capacity. The link must be explicit: a broad claim that a project supports development is not enough. Translate strategy into a problem or opportunity, define the people affected, identify the desired change and specify how progress will be measured. Strategic alignment should be revisited when external conditions change, because an initiative that was valuable at approval may become less relevant after a policy shift, technology change or funding reduction.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

2. Problem definition and opportunity framing

A business case begins with a well-evidenced problem or opportunity, not a predetermined solution. Define the current condition, who experiences it, the scale and consequences, the underlying causes and the evidence supporting the diagnosis. Separate symptoms from causes: long waiting times may arise from insufficient capacity, poor scheduling, data errors or a process bottleneck. Each cause suggests different interventions. Use baseline data, interviews, observation, service records and independent research where appropriate. State uncertainties and avoid overstating evidence. A clear problem statement allows decision-makers to compare options rather than simply approve the first proposed technology or construction solution.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

3. Objectives and measurable outcomes

Objectives describe what the project intends to achieve. They should be specific enough to guide design and measurable enough to support evaluation. A useful objective identifies the target population or system, the desired change, a measure and a timeframe. For example, rather than saying 'improve service', specify a target reduction in average waiting time while maintaining safety and satisfaction. Distinguish outputs from outcomes: installing a digital booking platform is an output; increased appointment access may be an outcome. Benefits are the measurable value arising from outcomes, such as reduced missed appointments or better use of staff capacity.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

4. Options appraisal and the do-nothing case

Options appraisal compares credible ways to address the need. Include a do-nothing or business-as-usual baseline, a do-minimum option and one or more substantive alternatives. The do-nothing case reveals the consequences of allowing current conditions to continue; it is not automatically cost-free. The do-minimum option tests whether targeted maintenance or process changes could address the problem. More ambitious options may involve new assets, technology, partnerships or operating models. Compare options against strategic fit, service quality, affordability, deliverability, risk, environmental impact and stakeholder effects. Record why rejected options were not preferred so that the decision remains transparent.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

5. Feasibility dimensions

Feasibility asks whether an option can be delivered and sustained. Technical feasibility considers whether the technology, design, skills and interfaces are workable. Operational feasibility asks whether the organisation can run and maintain the result. Financial feasibility tests affordability and funding. Economic feasibility compares wider costs and benefits. Legal and regulatory feasibility examines permissions, standards, rights and obligations. Environmental and social feasibility considers impacts and acceptability. Schedule feasibility tests whether the required outcome can be achieved in the available time. A proposal can be technically possible but operationally unrealistic if the organisation cannot recruit or train the people needed to use it.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

6. Technical and operational feasibility

Technical assessment examines maturity, compatibility, reliability, capacity, cybersecurity, maintainability, integration and supplier capability. It should identify assumptions that require prototypes, pilots, surveys or specialist review. Operational assessment maps the future process and asks who will own, staff, maintain and support the outcome. Consider training, user support, data migration, service continuity, spare parts, maintenance budgets and handover. A technology pilot should test real operating conditions and representative users, not only a demonstration prepared by the supplier. Technical claims should be independently validated when failure could affect safety, essential services or major public expenditure.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

7. Financial appraisal and affordability

Financial appraisal examines cash flows from the perspective of the organisation funding the project. Include capital expenditure, operating expenditure, staffing, training, licences, maintenance, replacement, financing and decommissioning where relevant. Distinguish one-off costs from recurring costs and identify the timing of payments. Affordability asks whether the organisation can meet those commitments within realistic budget limits, not merely whether the project has a positive theoretical return. Include contingency for uncertainty and test the effect of inflation, exchange rates, interest rates and supplier price changes. Financial models should state their assumptions and avoid false precision.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

8. Economic appraisal and wider value

Economic appraisal considers costs and benefits to society or the wider system, including effects that may not appear in the sponsor's accounts. Examples include travel-time savings, reduced pollution, improved access, public health outcomes, local employment and resilience. Avoid double counting: if a benefit is already reflected in another measure, adding both can exaggerate value. Identify who receives benefits and who bears costs, because aggregate net benefit can conceal unequal distribution. Use recognised appraisal guidance applicable to the jurisdiction and sector, and document how non-market impacts were valued or described qualitatively.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

9. Cost-benefit analysis

Cost-benefit analysis compares monetised benefits and costs over a defined appraisal period. Net present value discounts future net cash flows to reflect time value and opportunity cost. The general expression is NPV = Σ[(B_t − C_t)/(1+r)^t], where B_t is benefit in period t, C_t is cost, r is the discount rate and t is the period index. A positive NPV indicates that discounted benefits exceed discounted costs under the model assumptions. It does not prove that the project is equitable, affordable or risk-free. Results should be tested with sensitivity analysis and interpreted alongside non-monetised impacts.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

10. Worked NPV example

Suppose an initiative costs 100,000 at time zero and is expected to produce net benefits of 40,000 at the end of each of three years. At a discount rate of 10%, NPV = −100,000 + 40,000/1.10 + 40,000/1.10² + 40,000/1.10³. The discounted benefits are approximately 36,364, 33,058 and 30,053. Their sum is 99,475, giving NPV of approximately −525. Under these assumptions the project is close to break-even but slightly negative. A small change in benefits, cost or discount rate could change the decision, so the estimate should not be reported as a precise certainty.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

11. Payback, ROI and benefit-cost ratio

Payback period estimates how long it takes for cumulative cash inflows to recover the initial investment. It is easy to communicate but ignores benefits after payback and, in its simple form, the time value of money. Return on investment compares net gain with investment cost, but definitions differ and must be stated. Benefit-cost ratio divides discounted benefits by discounted costs; a ratio above one indicates benefits exceed costs under the appraisal assumptions. These indicators answer different questions and should not be used alone. A project with a longer payback may still be essential for safety, legal compliance or public service obligations.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

12. Risk-adjusted business cases

A business case should show how uncertainty affects the recommendation. Identify major assumptions, estimate plausible ranges and model scenarios such as optimistic, central and pessimistic cases. Sensitivity analysis changes one or more variables to reveal which assumptions drive the result. Scenario analysis examines coherent combinations, such as delayed approvals together with inflation and reduced demand. Where appropriate, expected monetary value can be estimated by multiplying outcome values by their probabilities, but probability estimates may be weak for novel projects. Use ranges and explain confidence rather than presenting uncertain forecasts as guaranteed outcomes.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

13. Market analysis and demand forecasting

Demand analysis estimates who will use the proposed output, how often, under what conditions and what alternatives they have. Methods include historical trend analysis, surveys, interviews, revealed behaviour, demographic analysis, service data and comparable projects. Forecasts should account for seasonality, capacity limits, substitution, affordability, adoption barriers and changes in policy or technology. Avoid assuming that stated interest equals actual use. Test forecasts against conservative scenarios and examine whether the project can scale up or down. For public services, consider unmet need among people who are not represented in existing usage data.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

14. Environmental and social appraisal

Environmental assessment identifies impacts on land, water, air, energy, biodiversity, climate, waste and resource use. Social appraisal examines access, inclusion, displacement, health, safety, livelihoods, cultural heritage and community cohesion. Identify affected groups early and plan meaningful consultation. Mitigation should follow a hierarchy: avoid impacts where possible, minimise those that cannot be avoided, restore affected conditions and compensate for residual impacts where appropriate and lawful. Do not treat consultation as a single meeting after the preferred option has already been fixed. Evidence from affected people may change the design or the decision itself.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

15. Procurement and delivery feasibility

A feasible option must be capable of being procured and delivered under the available market and governance conditions. Assess supplier capacity, competition, lead times, contract model, local skills, supply-chain concentration, logistics, land access and permit dependencies. A highly specialised solution may create long-term dependence on one supplier. Consider whether the organisation can act as an intelligent client: define requirements, evaluate proposals, manage contract performance and accept the output. Procurement feasibility also includes the time required for tendering, approvals, negotiations and mobilisation, which can be material to the schedule.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

16. Business case structure and assurance

A robust business case commonly explains strategic need, options, economic value, commercial approach, financial affordability, management arrangements, risks and recommendation. It should identify the decision requested, funding profile, accountable sponsor, benefit owners and conditions for proceeding. Independent assurance challenges evidence, assumptions, estimates and governance readiness. Assurance is not an attempt to make every proposal fail; it improves decision quality by exposing weaknesses while they can still be addressed cheaply. The business case should be updated when scope, costs, benefits, risks or context change materially.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

17. Decision-making and investment governance

Investment decisions should be made by an authorised body using transparent criteria and documented evidence. A decision record identifies options considered, key assumptions, dissenting views, conditions, delegated limits and reasons for approval or rejection. Conflicts of interest should be declared and managed. Decision-makers should distinguish sunk costs from future value: money already spent cannot be recovered and should not justify continuing an otherwise unsound project. Equally, a temporary forecast problem does not automatically justify cancellation if the underlying need and benefits remain strong and a credible recovery option exists.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

18. Case study: digital student services

A university proposes a student-services platform to reduce queues and improve access. The problem diagnosis reveals long in-person waits, duplicated records and unclear service ownership. Options include process redesign only, a limited booking system, or an integrated platform. Feasibility review tests data protection, integration with student records, accessibility, support staffing, vendor capability and recurring licence cost. The business case compares implementation and operating costs with expected time savings, improved service access and reduced error rates. A pilot with students and staff tests actual usage. The case demonstrates why strategic alignment, feasibility and measurable benefits must be considered together.

In application, the project manager should identify the decision being supported, the evidence available, the people affected and the authority required to act. Record assumptions explicitly and distinguish confirmed information from estimates. Where the method is applied to a live project, adapt the level of detail to complexity, uncertainty, safety, legal obligations and the cost of failure. Review the result with relevant specialists and update the project records when new evidence changes the conclusion.

A useful discipline is to test the approach at three levels: first, whether it is logically sound; second, whether the organisation has the capability and resources to implement it; and third, whether the intended users or beneficiaries experience the expected improvement. This prevents a technically correct document from being mistaken for a successful outcome. Teams should also consider inclusion, accessibility, environmental effects, lifecycle cost and operational ownership.

Additional applied study: Sensitivity analysis and scenario testing

Sensitivity analysis identifies the variables that most influence the appraisal result. Change one assumption at a time, such as construction cost, demand, adoption rate, operating expense or discount rate, and observe the effect on NPV or affordability. Scenario analysis changes several related assumptions together to represent a coherent future, for example delayed approvals, inflation and lower-than-forecast demand occurring at the same time. A switching value identifies the point at which a preferred option would no longer be preferred. These techniques help decision-makers understand exposure and establish monitoring triggers. They do not remove uncertainty; they show where evidence is most valuable and where contingency or staged commitment may be justified.

For assessment, support your analysis with a clear project example, state the assumptions used and explain how the team would record, communicate and review the decision. Strong answers distinguish a method's intended benefit from its limitations and show how it connects to the approved project objectives.

Additional applied study: Benefits realisation planning

Benefits realisation planning identifies the changes expected after project outputs are introduced, the measures that will demonstrate those changes and the people accountable for achieving them. A benefits map links outputs to capabilities, behaviour changes, outcomes and strategic value. Each benefit should have a baseline, target, measurement method, owner and expected realisation date. Some benefits appear only after adoption and operational adjustment, so responsibility often continues beyond project closure. Disbenefits should also be recorded, such as staff workload during transition or reduced access for people who cannot use a digital channel. A business case is stronger when it explains how benefits will be realised, not merely how outputs will be delivered.

For assessment, support your analysis with a clear project example, state the assumptions used and explain how the team would record, communicate and review the decision. Strong answers distinguish a method's intended benefit from its limitations and show how it connects to the approved project objectives.

Additional applied study: Staged investment and option value

Where uncertainty is high, a project may be divided into stages with decision points before major commitments. A pilot, prototype, feasibility study or limited rollout can generate evidence that improves later decisions. Staging may preserve the option to expand, redesign or stop, although it can also create duplicated mobilisation costs or delay economies of scale. The business case should compare the value of learning with the cost of staging. Define what evidence will be collected, what thresholds will trigger expansion and who has authority to make the next investment decision. Staged commitment is especially useful when technology, demand or operating conditions are uncertain.

For assessment, support your analysis with a clear project example, state the assumptions used and explain how the team would record, communicate and review the decision. Strong answers distinguish a method's intended benefit from its limitations and show how it connects to the approved project objectives.

University examination and revision questions

Attempt each question using definitions, explanation, evidence, examples and evaluation. Where a question asks for application, state your assumptions and show how the method would be used in a real project.

Question 1: Define the central concept in this chapter and explain why it matters.

Model answer: A strong answer defines the concept precisely, identifies its purpose, explains its relationship with other project controls and gives a practical example. It should distinguish the concept from related terms and state the consequences of applying it poorly.

Question 2: Explain how the chapter's methods support project decision-making.

Model answer: The methods organise evidence, clarify assumptions, expose dependencies and make trade-offs visible. They support decisions when their inputs are reliable, their limitations are understood and the decision is made by an authorised person.

Question 3: Discuss three common implementation challenges and suitable responses.

Model answer: Typical challenges include incomplete information, competing stakeholder priorities and limited resources. Responses include early engagement, transparent prioritisation, realistic estimates, explicit ownership, risk review and controlled change.

Question 4: Apply the chapter to a public-sector or organisational project.

Model answer: Begin with the need and intended beneficiaries. Define the deliverables, constraints and stakeholders; select relevant tools; identify risks and controls; explain how progress will be measured; and state how the output will be accepted and sustained.

Question 5: Evaluate why professional judgement remains necessary when using project tools.

Model answer: Tools simplify complex conditions and depend on assumptions. Professional judgement is required to interpret evidence, identify bias, assess context, understand ethical consequences and decide when specialist advice or escalation is necessary.

Chapter summary

This chapter develops undergraduate-level understanding of project strategy, business cases and feasibility. It combines conceptual explanations, practical methods, decision frameworks, worked examples and applied cases. Students should connect each method to project context, governance, people, evidence and measurable outcomes rather than treating tools as isolated templates. The central lesson is to use project management methods as connected decision aids. Maintain clear ownership, test assumptions, communicate honestly, involve affected stakeholders and review evidence as the project evolves. A sound method is only valuable when it improves decisions and contributes to a result that can be accepted, operated and sustained.

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.