Fatskills
Practice. Master. Repeat.
Study Guide: Business Analysis 101: Strategy Analysis - Assessing Risks and Feasibility
Source: https://www.fatskills.com/business-analyst/chapter/business-analysis-strategy-analysis-assessing-risks-and-feasibility

Business Analysis 101: Strategy Analysis - Assessing Risks and Feasibility

By Fatskills Exam Guides Team — the exam nerds behind 28,500+ quizzes and 2.1M practice questions across 500+ global exams.

⏱️ ~5 min read

Assessing Risks and Feasibility – Study Guide
(Designed for ECBA, CCBA & CBAP candidates – also a handy on?the?job reference for PMs and new BAs)


What This Is

Assessing Risks and Feasibility is the analysis activity where the Business Analyst (BA) determines whether a proposed solution is realistic, affordable, and likely to deliver the expected value. It sits early in the Requirements Life Cycle (typically during the Strategy Analysis and Requirements Analysis & Design Definition knowledge areas) and feeds into the decision?making gate that either green?lights the initiative or sends it back for re?scoping.

Real?world example: A retail firm wants to replace its legacy CRM with a cloud?based platform. The BA evaluates the technical integration risk, the budget impact, regulatory compliance, and whether the organization has the skills to adopt the new system before any detailed requirements are written.


Key Terms & Techniques

  • Risk Register – A living artifact (Strategy Analysis) that logs identified risks, their probability, impact, and mitigation actions.
  • Risk Probability & Impact Matrix – A visual tool (Strategy Analysis) that plots risks on a 2?dimensional grid to prioritize mitigation effort.
  • Feasibility Study – A high?level analysis (Strategy Analysis) that answers “Can we do it?” and “Should we do it?”; deliverable: Feasibility Report.
  • Cost?Benefit Analysis (CBA) – Quantitative technique (Business Analysis Planning & Monitoring) that compares expected benefits against costs; output: CBA Spreadsheet.
  • SWOT Analysis – Structured brainstorming (Strategy Analysis) of Strengths, Weaknesses, Opportunities, Threats; often a SWOT Diagram in the business case.
  • Decision?Tree Analysis – Diagrammatic technique (Requirements Analysis & Design Definition) that maps alternative courses of action and their expected outcomes.
  • Monte Carlo Simulation – Probabilistic modeling (Requirements Analysis & Design Definition) used when risk impacts are highly variable; output: Simulation Report.
  • Stakeholder Risk Appetite Assessment – Interview/Survey (Elicitation & Collaboration) that captures how much risk each stakeholder is willing to accept; deliverable: Risk Appetite Matrix.
  • Technical Feasibility Assessment – Review of existing architecture, interfaces, and technology constraints (Solution Evaluation); output: Technical Feasibility Document.
  • Operational Feasibility Assessment – Evaluation of people, processes, and organizational readiness (Solution Evaluation); output: Operational Readiness Checklist.

Step?by?Step / Process Flow

  1. Identify & Document Risks – Conduct stakeholder interviews, workshops, and document analysis to populate the Risk Register.
  2. Determine Probability & Impact – Use the Probability?Impact Matrix (or Monte Carlo if data exists) to rank each risk.
  3. Analyze Feasibility – Run a Feasibility Study that includes Technical, Operational, Economic, Legal, and Schedule feasibility; produce a Feasibility Report.
  4. Quantify Benefits & Costs – Build a Cost?Benefit Analysis and, where appropriate, a Decision?Tree to compare alternatives.
  5. Validate Findings with Stakeholders – Hold a review session; capture sign?offs on the Risk Register, Feasibility Report, and CBA.
  6. Baseline & Communicate – Freeze the risk?baseline (add to the Business Case) and circulate the final artifacts to the governance board for go/no?go decision.

Common Mistakes

Mistake Correction
Mistake: Treating risk assessment as a one?time “check?list” activity. Correction: BABOK requires continuous risk monitoring; update the Risk Register after each major milestone (e.g., after a design iteration).
Mistake: Confusing “feasibility” with “requirements validation.” Correction: Feasibility answers whether a solution can be built; validation answers whether the built solution meets the documented requirements. Keep the two artifacts separate.
Mistake: Using only qualitative judgments (high/low) for cost?benefit analysis. Correction: Wherever possible, assign monetary values (NPV, ROI) – BABOK expects a quantitative CBA for high?impact projects.
Mistake: Ignoring stakeholder risk appetite and assuming a single “average” tolerance. Correction: Capture each stakeholder’s appetite; map it to the Risk Register to prioritize mitigation that aligns with governance expectations.
Mistake: Documenting risks but never linking them to requirements or design decisions. Correction: Trace each risk to the requirement(s) it may affect (e.g., using a traceability matrix) so that mitigation can be built into the solution design.

Certification Exam Tips

Exam Level Tip
ECBA Expect scenario questions that ask what the BA should produce first – the answer is usually the Risk Register or Feasibility Report (Strategy Analysis).
CCBA Look for “Which technique helps prioritize risks for mitigation?” – the correct answer is the Probability?Impact Matrix (Strategy Analysis).
CBAP Questions often combine knowledge areas: “After a feasibility study, the BA discovers the solution is technically viable but operationally risky. What is the next step?” – answer: Stakeholder Risk Appetite Assessment (Elicitation & Collaboration) followed by Update Risk Register (Strategy Analysis).
All Levels Trap: “The BA performs a Cost?Benefit Analysis after the solution is built.” – In BABOK, CBA is done before solution selection (Strategy Analysis).
All Levels Remember the input-output flow: Project Charter-Feasibility Study-Business Case. If a question flips the order, it’s wrong.

Quick Check Questions

  1. Scenario: After a risk workshop, the team has 12 identified risks with varying likelihoods. Which technique should the BA use to decide which risks need immediate mitigation?
    Answer: Probability?Impact Matrix. It ranks risks by combining likelihood and impact, highlighting the high?priority items.

  2. Scenario: The sponsor asks whether the new CRM can be delivered within the 12?month budget. Which deliverable gives the answer?
    Answer: Cost?Benefit Analysis (CBA) Report. It quantifies expected costs versus benefits and shows whether the budget is realistic.

  3. Scenario: Stakeholders are concerned that the new system may not meet regulatory data?privacy rules. Which feasibility dimension should the BA assess?
    Answer: Legal Feasibility (part of the Feasibility Study). It evaluates compliance with laws and regulations.


Last?Minute Cram Sheet (10 One?Liners)

  1. Strategy Analysis is the BABOK knowledge area where Risk Register and Feasibility Study are created.
  2. Risk Register = Input for Solution Evaluation; Output for Business Case.
  3. Probability?Impact Matrix = visual prioritization tool; high?probability & high?impact = “red” risks.
  4. Feasibility Study covers Technical, Operational, Economic, Legal, Schedule dimensions.
  5. Cost?Benefit Analysis must be quantitative for high?value projects; it feeds the Business Case.
  6. SWOT is a qualitative technique; use it early to surface strategic risks.
  7. Decision?Tree = “what?if” modeling; useful when multiple solution alternatives exist.
  8. Monte Carlo Simulation = probabilistic risk modeling; produces a Simulation Report.
  9. Stakeholder Risk Appetite Assessment-Risk Appetite Matrix-aligns mitigation with governance.
  10. Exam trap: “Elicitation” is the activity; requirements are the output. The BA elicits information, not the requirements themselves.

Good luck – you’ve got the concepts, the techniques, and the exam?ready shortcuts! ?