CACS407 Software Project Management

Software Project ManagementUnit 88 min read

Software Evaluation & Cost-Benefit Analysis

Unit 8 of Software Project Management: Explores how to justify software projects using financial metrics, ROI, and strategic alignment, comparing evaluation techniques like cost-benefit analysis, payback period, and NPV with real-world examples from Nepal’s e-commerce and banking sectors.

TAKEAWAYS:

  • Cost-benefit analysis (CBA) quantifies project value by comparing tangible costs (e.g., development time) with intangible benefits (e.g., customer satisfaction).
  • ROI (Return on Investment) and NPV (Net Present Value) are key financial metrics to decide if a project is viable, with NPV accounting for time-value of money.
  • Strategic assessment aligns software projects with organizational goals (e.g., Daraz’s supply chain automation supporting Nepal’s e-commerce growth).
  • Qualitative vs. quantitative methods: Surveys (qualitative) and financial models (quantitative) both inform evaluation, but CBA relies heavily on the latter.
  • Payback period tells how long it takes to recover initial costs, while discounted cash flow (DCF) adjusts for inflation and risk.
  • Stakeholder analysis ensures project benefits (e.g., Pathao’s ride-sharing efficiency) outweigh costs for all parties involved.

1. Introduction to Software Evaluation

Software evaluation determines whether a project is worth pursuing by comparing its costs (development, maintenance) against its benefits (revenue, efficiency gains). Unlike other units (e.g., risk management or scheduling), evaluation focuses on justification—proving the project aligns with business goals and delivers measurable value.

Why Evaluate?

  • Resource allocation: Limited budgets require prioritizing projects (e.g., NTC’s fiber expansion vs. mobile app upgrades).
  • Risk mitigation: Identifies projects with high costs but low returns (e.g., a custom ERP system for a small business).
  • Stakeholder buy-in: Convincing investors or executives (e.g., NEPSE’s stock trading platform upgrades).

2. Key Evaluation Techniques

A. Cost-Benefit Analysis (CBA)

CBA systematically compares costs (direct/indirect) and benefits (monetary/non-monetary) of a project.

Formula:

Example: Ncell’s 5G Rollout

  • Costs: Infrastructure ($50M), spectrum licenses ($20M), training ($5M).
  • Benefits: Higher revenue ($80M/year), brand loyalty, government subsidies ($10M).
  • Net Benefit: $80M – ($50M + $20M + $5M) + $10M = $15M.

Visual:

flowchart TD
    A["Cost-Benefit Analysis"] --> B["Costs: $50M (Infrastructure) + $20M (Spectrum Licenses) + $5M (Training)"]
    A --> C["Benefits: $80M (Revenue) + $10M (Subsidies)"]
    B --> D["Tangible Costs"]
    C --> E["Tangible Benefits"]
    C --> F["Intangible: Brand Loyalty, Efficiency Gains"]

B. Financial Metrics

Metric Formula When to Use Example (Nepal)
ROI (Net Profit / Cost) × 100% Quick viability check Khalti’s payment gateway: ROI = 300%
NPV Long-term projects (e.g., Daraz’s warehouse automation) NPV = $12M (positive → proceed)
Payback Period Time to recover initial cost Short-term projects (e.g., Pathao’s driver app) 2 years to break even
IRR Discounted rate where NPV=0 Comparing projects with unequal lifespans IRR = 15% (accept if > bank interest)

Worked Example: Bank Loan Interest Calculation A bank offers a loan for a software project with:

  • Initial Cost: $200,000
  • Annual Benefits: $50,000 (Years 1–5)
  • Discount Rate (r): 10%

Calculate NPV: Decision: Proceed (NPV > 0).


3. Strategic Assessment

Aligns projects with organizational goals (e.g., Nepal’s digital transformation strategy).

Key Factors:

  1. Market Fit: Does the project solve a real problem? (e.g., eSewa’s mobile payments reducing cash dependency).
  2. Competitive Advantage: Does it differentiate the company? (e.g., Daraz’s same-day delivery vs. local shops).
  3. Regulatory Compliance: Meets legal requirements (e.g., NEPSE’s data security standards).
  4. Scalability: Can the project grow with the business? (e.g., NTC’s cloud infrastructure).

Visual:

Problem-Solution Fit (eSewa)Market FitDifferentiation (Pathao)Competitive EdgeNepal’s Data Protection ActComplianceCloud (NTC) vs. On-PremiseScalabilityStrategic Assessment

4. Qualitative vs. Quantitative Methods

Method Description Example
Quantitative Uses hard data (financial models) NPV calculation for Ncell’s 5G
Qualitative Uses surveys, expert opinions Customer satisfaction surveys for eSewa
Hybrid Combines both (e.g., CBA + stakeholder feedback) Daraz’s warehouse automation project
QuantitativeNumbers, MetricsQualitativeFeedback, Surveys
How each method contributes to software evaluation

Example: Khalti’s Payment Gateway

  • Quantitative: ROI = 400% (transaction fees vs. development cost).
  • Qualitative: User surveys show 90% satisfaction with speed.

5. Stakeholder Analysis

Identifies who benefits and who bears costs.

Example: NEPSE’s Trading Platform Upgrade

  • Stakeholders:
    • Investors: Want higher returns (benefit).
    • Traders: Need faster execution (benefit).
    • IT Team: Bears maintenance costs (cost).
  • Impact Matrix:

    | Stakeholder | Benefit Level | Cost Level | | Investors | High | Low | | Traders | High | Medium | | IT Team | Low | High |


6. Real-World Applications

In the Real World

  1. eSewa’s Mobile Payments

    • Idea Used: Cost-Benefit Analysis to justify development costs against merchant adoption and transaction fees.
    • How: eSewa calculated that every $1 spent on development saved $5 in cash-handling costs for businesses, leading to a 3:1 ROI.
  2. Daraz’s Supply Chain Automation

    • Idea Used: Strategic Assessment + NPV to decide between manual warehouses and robotic sorting.
    • How: Daraz’s NPV analysis showed robotic sorting would reduce order fulfillment time by 40% and cut labor costs by 25%, justifying the $1.2M investment.
  3. Ncell’s 4G to 5G Transition

    • Idea Used: Payback Period + IRR to compare 5G’s higher upfront costs against long-term revenue from faster speeds.
    • How: Ncell’s IRR of 18% (vs. bank interest of 12%) confirmed 5G was financially viable despite a 3-year payback period.

7. Common Pitfalls in Evaluation

  • Ignoring Intangible Benefits: Overlooking customer loyalty (e.g., Pathao’s app ratings).
  • Overestimating Costs: Underestimating maintenance (e.g., banks’ cybersecurity updates).
  • Short-Term Focus: Choosing projects with quick paybacks but no long-term value (e.g., a flashy app with no scalability).

8. Exam Tip

  • For CBA/NPV/ROI:
    • Always show calculations (even if simplified) in exams. Use the NPV formula and payback period tables.
    • Link to real examples (e.g., "Like Ncell’s 5G, this project has a 3-year payback").
  • For Strategic Assessment:
    • Use mindmaps (like above) to structure answers. Highlight market fit and scalability.
  • For Stakeholder Analysis:
    • Draw a table (like the NEPSE example) to compare benefits/costs per stakeholder.
  • Compare Techniques:
    • If asked to compare top-down vs. bottom-up estimation (from Unit 4), note that CBA uses bottom-up (detailed cost breakdown) while strategic assessment is top-down (big-picture goals).

Based on the TU BCA syllabus for Software Project Management (CACS407), unit 8.

Discussion

Loading…