Business Analysis 101: BA Foundations Enterprise Analysis vs Business Analysis

What This Is

Enterprise Analysis is the strategic, organization‑wide effort that determines what the enterprise needs to achieve its business goals and why those needs exist. It sits at the top of the Business Analysis lifecycle and feeds the more detailed Business Analysis work (requirements elicitation, modeling, validation, etc.).

Real‑world example: A regional bank wants to launch a new digital‑only checking product. Enterprise Analysis uncovers the market opportunity, defines the target customer segment, and decides that a new mobile‑first banking platform is the solution. Business Analysis then takes that solution concept and creates the detailed functional and non‑functional requirements for the mobile app, integration with core banking, and the associated user‑experience designs.

Key Terms & Techniques

• Enterprise Goal – A high‑level business objective (e.g., “Increase digital acquisition by 20 %”). Knowledge Area: Enterprise Analysis; Deliverable: Goal Statement.
• Business Need – The problem or opportunity that drives the initiative (e.g., “Current onboarding takes 7 days, causing churn”). Knowledge Area: Enterprise Analysis; Deliverable: Business Need Statement.
• Stakeholder Map – A diagram that shows who is impacted, their influence, and their interests. Knowledge Area: Enterprise Analysis; Deliverable: Stakeholder Register.
• Value‑Realization Plan – A roadmap that links solution components to measurable benefits (KPIs, ROI). Knowledge Area: Enterprise Analysis; Deliverable: Benefits Realization Plan.
• SWOT Analysis – Assessment of Strengths, Weaknesses, Opportunities, Threats to validate the need. Knowledge Area: Enterprise Analysis; Deliverable: SWOT Matrix.
• Business Capability Model – Hierarchical view of what the organization can do (capabilities, sub‑capabilities). Knowledge Area: Enterprise Analysis; Deliverable: Capability Map.
• Feasibility Assessment – Evaluation of technical, economic, operational, and schedule feasibility. Knowledge Area: Enterprise Analysis; Deliverable: Feasibility Report.
• Solution Scope – The boundary of what the solution will and will not address. Knowledge Area: Business Analysis (Requirements Management & Communication); Deliverable: Scope Statement.
• Use‑Case Diagram (UCD) – Visual representation of actors and functional interactions. Knowledge Area: Business Analysis (Requirements Elicitation & Collaboration); Deliverable: Use‑Case Model.
• MoSCoW Prioritization – Classifies requirements as Must, Should, Could, Won’t. Knowledge Area: Business Analysis (Requirements Analysis & Design Definition); Deliverable: Prioritized Requirements List.
• BPMN (Business Process Model and Notation) – Standard notation for process flowcharts. Knowledge Area: Business Analysis (Requirements Elicitation & Collaboration); Deliverable: Process Model.
• Traceability Matrix – Links each requirement to its source, design, test, and business objective. Knowledge Area: Business Analysis (Requirements Management & Communication); Deliverable: Requirements Traceability Matrix.

Step‑by‑Step / Process Flow

1. Identify & Analyze Enterprise Goals – Review strategic plans, interview senior sponsors, and capture the high‑level objectives that justify the initiative.
2. Define Business Needs & Perform Feasibility – Translate goals into concrete needs, run SWOT and feasibility assessments, and obtain a signed Business Need Statement.
3. Develop Stakeholder Map & Capability Model – List all impacted parties, assess influence, and map existing capabilities to pinpoint gaps the solution must fill.
4. Create Solution Scope & Value‑Realization Plan – Draft a clear scope statement, align each scope element with measurable benefits, and get stakeholder approval.
5. Hand‑off to Detailed Business Analysis – Provide the Enterprise Analysis artefacts (Goal, Need, Scope, Capability Map) to the BA team for requirements elicitation, modeling, and validation.

Common Mistakes

Certification Exam Tips

1. Know the Input/Output pairs – Enterprise Analysis inputs are Strategic Plans, Business Goals, and Enterprise Architecture; its primary outputs are Business Need, Goal Statement, and Scope. Remember the direction of flow.
2. “What comes next?” – If a question describes a Goal Statement and asks the next activity, the correct answer is “Identify Business Needs” (Enterprise Analysis step).
3. Distinguish Knowledge Areas – Anything that deals with “why” (value, justification, feasibility) belongs to Enterprise Analysis; anything that deals with “how” (processes, models, requirements) belongs to Business Analysis.
4. Watch for trap wording – Phrases like “the BA creates the solution” are wrong; the BA defines the solution scope and elicits requirements.

Quick Check Questions

1. Scenario: After a stakeholder workshop, the sponsor asks for a concise statement that links the new mobile app to the bank’s strategic goal of “digital growth”. Which artefact should the BA produce?
   Answer: Goal Statement.
   Justification: Goal Statements translate strategic objectives into measurable, solution‑focused language (Enterprise Analysis output).

2. Scenario: The project team discovers that the current core‑banking system cannot support real‑time transaction processing, a key need for the new product. What should the BA do first?
   Answer: Conduct a Feasibility Assessment (technical and operational).
   Justification: Feasibility determines whether the identified need can be satisfied within constraints before detailed requirements are written.

3. Scenario: Stakeholders disagree on the priority of three features. Which technique is most appropriate to reach consensus quickly?
   Answer: MoSCoW Prioritization (run a facilitated workshop).
   Justification: MoSCoW forces stakeholders to classify features into Must, Should, Could, Won’t, clarifying trade‑offs and aligning expectations.

Last‑Minute Cram Sheet (10 one‑liners)

1. Enterprise Analysis = “Why do we need a solution?” – produces Business Need, Goal Statement, Scope.
2. Business Analysis = “What will the solution do and how?” – produces Requirements, Models, Designs.
3. Input → Output: Strategic Plans → Goal Statement; Business Need → Solution Scope.
4. Stakeholder Register must include role, influence, communication preference.
5. Capability Model shows what the organization can do; gaps become Business Needs.
6. Feasibility Assessment covers technical, economic, operational, schedule dimensions.
7. Value‑Realization Plan links each scope element to a KPI or ROI metric.
8. MoSCoW is a prioritization technique; not a requirement‑validation method.
9. BPMN is the standard notation for process diagrams; use it for process modeling (Business Analysis).
10. ⚠️ Elicitation is the activity; Requirements are the output. The BA elicits information, not requirements themselves.