Study guide

8.3 Business Case and Needs Assessment

CAPM Certified Associate in Project Management Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CAPM Exam Overview

1.1 About the CAPM Exam 1.2 PMBOK 7th Edition Overview 1.3 Exam Content Outline (ECO) 1.4 CAPM vs. PMP: Understanding the Differences

2 Chapter 2: Project Life Cycles and Processes (Domain 1, Tasks 1-2)

2.1 Projects, Programs, and Portfolios 2.2 Project Life Cycle Phases 2.3 The Five Process Groups 2.4 The Ten Knowledge Areas

3 Chapter 3: Project Management Planning (Domain 1, Task 2)

3.1 The Project Management Plan 3.2 Scope Management and the WBS 3.3 Schedule Management 3.4 Cost Management and Earned Value 3.5 Quality Management

4 Chapter 4: Project Roles, Responsibilities, and Ethics (Domain 1, Tasks 3-4)

4.1 Project Roles and Responsibilities 4.2 Leadership and Emotional Intelligence 4.3 Risk Management Fundamentals 4.4 PMI Code of Ethics and Professional Conduct 4.5 Problem-Solving Tools and Techniques

5 Chapter 5: Resource, Communication, and Stakeholder Management (Domain 1, Tasks 2-3)

5.1 Resource Management 5.2 Communications Management 5.3 Stakeholder Management 5.4 Procurement Management 5.5 Issues, Risks, Assumptions, and Constraints

6 Chapter 6: Predictive, Plan-Based Methodologies (Domain 2)

6.1 When to Use a Predictive Approach 6.2 WBS, Work Packages, and Activity Definition 6.3 Predictive Project Controls and Artifacts 6.4 Critical Path and Schedule Calculations

7 Chapter 7: Agile Frameworks and Methodologies (Domain 3, Tasks 1-3)

7.1 When to Use an Adaptive (Agile) Approach 7.2 The Scrum Framework 7.3 Kanban, XP, and SAFe 7.4 Agile Planning, Estimation, and Metrics 7.5 Agile Project Controls and Artifacts

8 Chapter 8: Business Analysis Roles and Stakeholder Communication (Domain 4, Tasks 1-2)

8.1 Business Analysis Roles and Responsibilities 8.2 Stakeholder Communication in Business Analysis 8.3 Business Case and Needs Assessment

9 Chapter 9: Requirements Gathering and Product Roadmaps (Domain 4, Tasks 3-4)

9.1 Requirements Gathering Approaches 9.2 Requirements Traceability Matrix 9.3 Product Roadmaps

10 Chapter 10: BA Methodologies and Requirements Validation (Domain 4, Tasks 5-6)

10.1 Business Analysis in Predictive and Agile Approaches 10.2 Acceptance Criteria and Requirements Validation 10.3 Business Analysis Tools and Techniques Summary

8.3 Business Case and Needs Assessment

Key Takeaways Explain This Topic AI

A needs assessment maps the current state (as-is), defines the desired future state (to-be), and quantifies the gap the project must close

A situation statement names the problem, who it affects, the measurable impact, and the desired outcome — keep it specific and number-driven

The business case justifies the investment: problem, options (always including 'do nothing'), recommendation, financials, risk, strategic fit, and success metrics

Know the financial decision rules: NPV positive = pursue, BCR greater than 1.0 = pursue, IRR above the hurdle rate = pursue, shorter payback is better

The business case is a living document — revisit it at phase gates to confirm the investment is still justified before spending more

Last updated: June 2026

Pre-Project BA Work

Before a charter is signed, business analysis identifies the need, evaluates options, and builds the justification. This is the front end of value delivery and a heavily tested slice of Domain 4. The deliverable that authorizes spending is the business case , built on a needs assessment .

Needs Assessment

A needs assessment is a systematic look at the current situation to determine what must change. The six steps:

Identify the problem or opportunity — what is happening, or failing to happen, that demands attention?

Assess the current state (as-is) — how does work happen today; where are the pain points?

Define the desired future state (to-be) — what should it look like after the project?

Identify the gap — the measurable difference between as-is and to-be

Evaluate options — what alternatives could close that gap?

Recommend a solution — which option fits within the constraints?

The gap is the heart of the assessment: it defines what the project must accomplish . If you cannot quantify the gap, you cannot justify the spend.

Situation Statement

A situation statement frames the problem in a repeatable structure so stakeholders agree on what is being solved before solutions are debated.

  • Component Content
  • The problem/opportunity of [describe the issue]
  • Affects [who is impacted]
  • The impact of which is [measurable consequence]
  • A successful solution would [desired outcome]

Worked example: "The problem of manual data entry into three separate systems affects the operations team of 45 people. The impact is roughly 15 hours of wasted effort per week and a 12% error rate. A successful solution would integrate the three systems into one platform, eliminating redundant entry and reducing the error rate below 2%."

Notice the numbers — 45 people, 15 hours, 12% to under 2%. A vague statement ("data entry is annoying") cannot anchor a business case; a quantified one feeds straight into the financial analysis.

The Business Case

The business case documents why the organization should invest. It answers "Why this, why now, and what do we get back?"

  • Section Content
  • Executive summary The recommendation in brief
  • Problem / opportunity statement The business need being addressed
  • Analysis of options Alternatives considered, including 'do nothing'
  • Recommended solution The chosen option and rationale
  • Financial analysis Costs, benefits, ROI, NPV, payback
  • Risk assessment Key risks and mitigations
  • Strategic alignment Link to organizational goals
  • Implementation approach High-level execution plan
  • Success metrics How outcomes will be measured
  • Financial Decision Rules — memorize the cutoffs
  • Metric What it is Decision rule
  • Payback period Time to recover the initial investment Shorter is better

Net Present Value (NPV) Present value of future cash flows minus the investment Positive = pursue; negative = reject

  • Return on Investment (ROI) (Benefits − Costs) / Costs × 100% Higher is better
  • Internal Rate of Return (IRR) Discount rate where NPV = 0 Above the hurdle rate = pursue
  • Benefit-Cost Ratio (BCR) Total benefits / total costs Greater than 1.0 = pursue

Reading the numbers: An NPV of −$30,000 means the discounted benefits fall $30,000 short of the cost — the project destroys value and should be rejected on financials alone. A BCR of 0.85 (below 1.0) likewise fails. When comparing two positive-NPV projects, prefer the higher NPV; payback alone ignores cash flows after recovery, so it is a tiebreaker, not a primary rule.

Evaluating Options

The BA weighs each option across several dimensions:

Factor Question

Value Which option delivers the most stakeholder value?

Cost What is each option's total cost of ownership?

Risk What risks does each carry?

Feasibility Is it technically and organizationally achievable?

Timeline How long to implement?

Strategic fit Which best supports strategy?

Dependencies What external factors must hold true?

Most business cases evaluate at least three options:

  • Do nothing — keep the current state as the comparison baseline
  • Minimum solution — address only the critical needs at low cost
  • Full solution — comprehensive, addresses all identified needs

Exam tip: Always include do nothing . It quantifies the cost of inaction, prevents "solution bias," and gives decision-makers a true baseline. A CAPM question that omits it from the options list is usually flagging the mistake.

Feasibility and the Living Business Case

Feasibility analysis checks whether the recommended option is technically , economically , operationally , and legally viable before resources are committed. Finally, the business case is a living document : it is revisited at phase gates and major milestones to confirm the assumptions still hold and the benefits are still worth the spend. If the business case no longer justifies the work, the right call may be to terminate the project — protecting the organization from sunk-cost thinking.