← Portal CONCEPT 02 Project Failure & CBA
01 / 05 • 00:00
2.1 Standish CHAOS & Project Failure

When Does a Software Project Fail?

CHAOS OUTCOME 1IDEAL
Successful
All Constraints Satisfied
  • Delivered on time, within budget, with all originally specified features and functions.
  • Delivers positive business value exceeding development + operational costs.
Requires realistic baseline planning and disciplined change control.
CHAOS OUTCOME 2PARTIAL
Challenged
Operational, But Compromised
  • Completed and deployed into use, but over budget, past deadline, and/or missing specified features.
  • Caused by scope creep, optimistic estimates, or gold-plating.
SCS 2214 Overlap: Failure along Spec, Time, or Money (Moore's Law makes slow projects obsolete).
CHAOS OUTCOME 3FAILED
Impaired
Cancelled or Never Used
  • Cancelled prior to completion, or built and rejected by end users.
  • Root Causes: Lack of user involvement, poor WBS, zero risk register, wrong technology stack.
A technically running program that solves the wrong business problem is still a failed project.
2.2 Economic Feasibility Framework

CBA: Costs vs. Benefits Taxonomy

3 PROJECT COST CATEGORIES

1. Development / Direct Costs

Outlays directly incurred to engineer the software: developer salaries, workstations, IDE/software licenses.

2. Setup & Conversion Costs

One-time transition costs: legacy database migration, parallel running periods, initial staff training.

3. Operational & Maintenance Costs

Recurring annual expenses over system lifetime: cloud/server hosting, helpdesk support, patches, renewals.

3 PROJECT BENEFIT CATEGORIES

1. Direct Benefits

Immediate, measurable cash savings or new revenue (e.g., saving $15,000/yr in paper stationery and clerical overtime).

2. Assessable Indirect Benefits

Secondary efficiency gains reasonably estimated in money (e.g., 40% fewer data-entry errors saving 10 hrs/wk rework).

3. Intangible Benefits

Positive strategic impacts hard to express in exact dollars (corporate reputation, student satisfaction, staff morale).

2.3 Quantitative Evaluation Formulas

Five CBA Financial Metrics

Metric Formula Decision Rule Key Limitation (Exam Favorite)
Net Profit Total Benefits − Total Costs Accept if > 0; higher looks better Ignores initial investment scale AND timing of cash flows (time value of money).
Payback Period Year before recovery + (Unrecovered / Recovery Yr Inflow) Prefer shortest payback (lower risk) Ignores all cash flows AFTER breakeven date and ignores time value of money.
ROI / ARR (Avg Annual Profit / Total Investment) × 100% Accept if ROI > target / bank rate Uses simple accounting averages; ignores exact cash timing & compounding.
Net Present Value (NPV) Σ [Net Cash Flow_t / (1 + r)^t] − Initial Cost_0 Accept if NPV > 0; pick highest NPV Sensitive to discount rate r; absolute dollar figure ignores capital scale.
IRR Discount rate r where NPV = 0 Accept if IRR > cost of capital Assumes inflows reinvested at IRR; multiple roots if cash signs flip.

Why NPV Wins Over Net Profit & Payback

NPV accounts for both the Time Value of Money ($1 today > $1 in 3 years) and all lifecycle cash flows from Year 0 to the final year.

15–20 MARK EXAM STAPLE
2.4 Guaranteed NUST Exam Calculation

Worked Case: Project Alpha vs. Beta

CASH FLOWS (10% DISCOUNT RATE)
YearDF (10%)AlphaBeta
Yr 01.0000-$100,000-$100,000
Yr 10.9091+$50,000+$10,000
Yr 20.8264+$50,000+$30,000
Yr 30.7513+$30,000+$100,000
Alpha PV: 45,455 + 41,320 + 22,539 = $109,314
Beta PV: 9,091 + 24,792 + 75,130 = $109,013
METRIC COMPARISON & DECISION
MetricAlphaBeta
Net Profit$30,000$40,000
Payback2.0 years2 + 60/100 = 2.6 yrs
ROI10.00%13.33%
NPV (10%)+$9,314+$9,013

Recommendation: Select Project Alpha

Even though Beta shows higher raw Net Profit ($40k vs $30k), Alpha delivers a higher NPV (+$9,314 vs +$9,013) and faster 2.0-year payback because its inflows arrive earlier.

2.5 Exam Traps & PM Role in Feasibility

CBA Exam Traps & PM Stewardship

4 COSTLY EXAM TRAPSDON'T LOSE MARKS
  • Year 0 Discounting: Year 0 happens TODAY! Its factor is always 1.0000, never 1/(1+r)^1.
  • Picking by Net Profit Alone: Early-inflow projects often beat late-inflow projects on NPV—always rank by NPV.
  • Implicit ROI Denominator: Always state ROI = (Avg Annual Profit / Total Investment) × 100% explicitly (Hughes & Cotterell).
  • Ignoring Strategic Fit: Regulatory compliance or cybersecurity may justify a lower-NPV project in essays.
PM ROLE IN ECONOMIC SUCCESS5 FUNCTIONS
  • Business Case Stewardship: Verify technical + CBA feasibility before heavy spend.
  • Stepwise Planning: Realistic WBS & effort estimation (no SWAG budgets).
  • Monitoring & EVM: Catch cost/schedule variances early.
  • Change Control Board (CCB): Block unapproved gold-plating & scope creep.
  • Stakeholder Alignment: Bridge non-technical sponsors and engineers.

Completed Concept 2: Project Failure & CBA

Next up: Step-Wise Project Planning, DISCO Objectives, WBS, Process Models, and CASE tools.

Next: Concept 3 (WBS & SDLC) →