10.3 Business Analysis Tools and Techniques Summary
Key Takeaways
- SWOT analysis maps internal Strengths and Weaknesses against external Opportunities and Threats to justify projects and inform strategy.
- Cost-benefit analysis uses NPV, ROI, IRR, payback period, and benefit-cost ratio to judge whether an investment is worthwhile.
- The business case documents the problem, options analyzed, recommended solution, financial analysis, risks, and strategic alignment.
- Feasibility studies test whether a solution is technically, economically, organizationally, operationally, legally, and schedule-wise achievable.
- Stakeholder analysis, root-cause analysis, and decision analysis are cross-cutting techniques used across every BA task.
How These Tools Are Tested
Domain 4 questions rarely ask you to perform a calculation by hand; they ask you to recognize the right tool for the situation and interpret a result. Learn each tool's purpose, the one number or output it produces, and the rule for a "good" result.
A second pattern is the elicitation-versus-analysis distinction (covered earlier in Domain 4) reappearing as answer choices here: elicitation tools gather raw input from people, while analysis and modeling tools organize what was gathered into structure. Keep that boundary sharp and many distractor options fall away.
Needs-Assessment Tools
SWOT analysis
SWOT examines four dimensions; the trap is mixing internal with external.
| Dimension | Internal/External | Positive/Negative |
|---|---|---|
| Strengths | Internal | Positive |
| Weaknesses | Internal | Negative |
| Opportunities | External | Positive |
| Threats | External | Negative |
Cost-benefit analysis (CBA)
The exam expects you to know the "good" direction of each financial metric.
| Metric | What it is | "Good" rule |
|---|---|---|
| Net Present Value (NPV) | Today's value of all future cash flows minus cost | Positive NPV is favorable; higher is better |
| Return on Investment (ROI) | (Benefits − Costs) / Costs x 100% | Higher percent is better |
| Internal Rate of Return (IRR) | Discount rate where NPV = 0 | Above the cost of capital is good |
| Payback Period | Time to recover the initial outlay | Shorter is better (less risk) |
| Benefit-Cost Ratio (BCR) | Total benefits / total costs | Greater than 1.0 means benefits exceed costs |
Worked example: Project A has NPV +50,000 dollars, ROI 25%, BCR 1.4. Every signal is favorable (positive NPV, positive ROI, BCR over 1.0), so it is a sound investment. If two projects compete and only their NPVs differ, choose the higher NPV, not the shorter payback — NPV is the most complete measure because it accounts for the time value of money across the full life of the investment, whereas payback period ignores any cash flow after the break-even point. A classic trap offers a project with a tempting short payback but a lower NPV; the higher-NPV option still wins unless the question explicitly weights liquidity or risk.
The business case
The business case is the formal justification for the project.
- Problem or opportunity being addressed.
- Options analyzed (including the do-nothing baseline).
- Recommended solution and rationale.
- Financial analysis (NPV, ROI, IRR, payback).
- Risk assessment and mitigation.
- Strategic alignment and success criteria.
The business case is created before the project is authorized and is owned by the sponsor, not the project manager. It is revisited at key gates to confirm the investment still makes sense; if the business case no longer holds, the correct action may be to terminate the project rather than continue spending. On the exam, the business case is the document a question points to when it asks "why was this project approved?" or "what justifies continued funding?"
Analysis and Decision Tools
Feasibility study (the TELOS/POEMS dimensions)
| Type | Question it answers |
|---|---|
| Technical | Can we build it with available technology? |
| Economic | Will the benefits justify the cost? |
| Organizational | Will the organization adopt and support it? |
| Operational | Will it work in the real operating environment? |
| Schedule | Can it be done in the required timeframe? |
| Legal | Does it comply with applicable laws and regulations? |
Decision analysis
| Technique | Use it when |
|---|---|
| Decision matrix (weighted scoring) | Comparing several options on weighted criteria |
| Decision tree | Sequential decisions with probabilities/uncertainty |
| Force-field analysis | Weighing driving vs. restraining forces of a change |
| Multi-criteria decision analysis | Complex choices with many weighted factors |
Modeling and Visualization Tools
| Tool | What it shows | Use when |
|---|---|---|
| Process flow diagram | Steps, decisions, sequence | Documenting current or future process |
| Data flow diagram (DFD) | How data moves through a system | Capturing data requirements |
| Entity relationship diagram (ERD) | Relationships among data entities | Data/database modeling |
| Context diagram | System boundary and external actors | Defining solution scope |
| State transition diagram | How an object changes state | Modeling object lifecycles |
| Wireframe / prototype | Low-fidelity UI layout or interactive model | Validating UI requirements with users |
Cross-Cutting Techniques
These appear across every BA task, predictive or agile:
- Stakeholder analysis — identify and prioritize stakeholders (power/interest grid, salience model).
- Root-cause analysis — find the real problem, not the symptom (5 Whys, fishbone/Ishikawa diagram).
- Benchmarking — compare against industry standards or competitors.
- Estimation and prioritization — size work and rank by value, risk, and dependency (e.g., MoSCoW: Must, Should, Could, Won't).
Master Reference: Tool-to-Task Map
| BA task | Go-to tools |
|---|---|
| Needs assessment | SWOT, CBA, business case, feasibility study, root-cause analysis |
| Stakeholder identification | Stakeholder analysis, RACI, power/interest grid |
| Requirements elicitation | Interviews, facilitated workshops, observation, prototyping |
| Requirements analysis | Process/data models, gap analysis, decision analysis |
| Requirements documentation | SRS, use cases, user stories, RTM |
| Requirements validation | Acceptance criteria, UAT, reviews, demonstrations |
| Solution evaluation | Metrics/KPI analysis, surveys, post-project CBA |
Trap to watch: elicitation gathers requirements (interviews, workshops); analysis organizes and models them (process/data diagrams, gap analysis). The exam often offers an elicitation tool when the scenario actually calls for analysis, or vice versa — match the verb in the question to the column above.
Study Strategy for the Tools Questions
Because Domain 4 is 27% of the exam, expect several tool-selection items. Build a one-page recall sheet keyed to the verb in the prompt: justify points to business case and CBA; decide between options points to a decision matrix or decision tree; find the real problem points to root-cause analysis; understand who matters points to stakeholder analysis; confirm we can build it points to a feasibility study; show the process or data points to the modeling tools.
When two options both seem plausible, prefer the one that produces the specific output the question describes — a weighted score implies a decision matrix, a probability-weighted outcome implies a decision tree, and a positive-or-negative dollar figure implies NPV. Reading for the output, not just the tool name, is the discipline that separates a pass from a near miss on this domain.
A project shows an NPV of +50,000 dollars, an ROI of 25%, and a benefit-cost ratio of 1.4. What do these metrics indicate?
Which feasibility type evaluates whether the organization has the culture, leadership support, and willingness to adopt the proposed solution?
In a SWOT analysis, Opportunities and Threats are best described as:
A team needs to find the true underlying cause of a recurring business problem rather than treat its symptoms. Which technique fits best?
You've completed this section
Continue exploring other exams