Cheat sheet

ECBA Cheat Sheet

Understanding Business Analysis

20%of exam

Mindset for Effective Business Analysis

14%of exam

Six Focus AreasSeven BA PrinciplesFive Foundational Competencies29 Underlying CompetenciesFacilitation vs Leadership

Implementing Business Analysis

6%of exam

Predictive vs AdaptiveBA Roles and TitlesReporting StructuresDelivery Lifecycle Fit

Change

10%of exam

Contextual FactorsImpact AnalysisChange DispositionRequirements Traceability

Need

10%of exam

Nine Requirement CharacteristicsAtomic RequirementProblem vs OpportunityRoot Cause Analysis

Solution

10%of exam

Acceptance vs Evaluation CriteriaFeasibility AssessmentRisk Analysis and ManagementVerification vs Validation

Stakeholder

10%of exam

RACI MatrixFour Communication SkillsElicitation TechniquesStakeholder Engagement

Value

10%of exam

Outcome vs OutputPotential vs Realized ValueKPI and IndicatorsValue Measurement

Context

10%of exam

Constraint vs DependencyEnterprise EnvironmentSWOT AnalysisContextual Influencers

Quick Facts

Exam
ECBA
Body
IIBA
Questions
50 multiple-choice
Time
75 minutes
Format
Online, PSI proctored
Fee
$395 (first-year membership included)
Passing
Pass/fail, not published
Domains
9 (Blueprint V1.1)
Validity
Lifetime, no CDUs

BACCM Six Concepts

Change Need Solution Stakeholder Value Context, always interconnected

Change: transformation from needNeed: problem or opportunitySolution: way to satisfy needStakeholder: has change relationshipValue: worth to stakeholderContext: circumstances around change

Requirement vs Design

Requirement

  • Describes what is needed
  • Usable representation of a need

Design

  • Describes how solution works
  • Usable representation of a solution

What comes before how

Requirements Classification Router

  1. Explains why change is neededClassify as Business Requirement
  2. Specific stakeholder need identifiedClassify as Stakeholder Requirement
  3. Describes what solution must doClassify as Functional Requirement
  4. Describes how well it performsClassify as Non-Functional Requirement
  5. Needed only during the transitionClassify as Transition Requirement
  6. Requirement bundles multiple needsSplit into atomic requirements(Violates atomic characteristic)

BACCM Six Core Concepts

Change
Transformation in response to need
Need
Problem or opportunity to address
Solution
Way to satisfy a need
Stakeholder
Has relationship to change or need
Value
Worth to a stakeholder
Context
Circumstances that influence the change

Five BABOK Perspectives

Agile
Iterative, incremental delivery lens
Business Intelligence
Data-driven decision-making lens
Information Technology
IT solution delivery lens
Business Architecture
Enterprise structure and capability lens
Business Process Management
Process improvement and governance lens

Requirements Classification Schema

Business Requirements
Why the change is happening
Stakeholder Requirements
What one stakeholder group needs
Functional Requirements
What the solution must do
Non-Functional Requirements
How well solution must perform
Transition Requirements
Needed only during the change

Facilitation vs Leadership Influencing

Facilitation

  • Guides a group neutrally
  • Group owns the outcome

Leadership and Influencing

  • Persuades toward a direction
  • BA steers the outcome

Neutral guide vs active persuader

Mindset Six Focus Areas

Achieving Outcomes
Aim BA work at outcomes
Discovering Value
Find value continuously, not once
Adopting Principles
Apply the seven BA principles
Deciding on Approach
Choose predictive or adaptive fit
Developing Competencies
Build foundational BA competencies
Using Techniques
Apply foundational BA techniques

Seven BA Standard Principles

See the Whole
Analyze needs in big picture
Think as a Customer
Build for real customer needs
Analyze to Determine Value
Prioritize work that maximizes value
Get Real Using Examples
Use examples for shared understanding
Understand What Is Doable
Analyze operational delivery constraints
Stimulate Collaboration
All stakeholders contribute to value
Avoid Waste
Remove activities that add nothing

Five Foundational Competencies

Adaptability
Adjust to changing circumstances
Facilitation
Guide a group neutrally
Leadership and Influencing
Persuade stakeholders toward direction
Problem Solving
Diagnose and resolve issues
Systems Thinking
See interconnections across the whole

29 Underlying Competency Categories

Analytical Thinking and Problem Solving
7 competencies in this category
Behavioural Characteristics
5 competencies in this category
Business Knowledge
5 competencies in this category
Communication Skills
4 competencies, all testable
Interaction Skills
5 competencies in this category
Tools and Technology
3 competencies in this category

Predictive vs Adaptive Approach

Predictive

  • Requirements defined in detail upfront
  • Formally baselined and controlled

Adaptive

  • Requirements captured at high level
  • Elaborated across iterations

Stable needs vs evolving needs

Six BABOK Knowledge Areas

BA Planning and Monitoring
Plans BA approach and governance
Elicitation and Collaboration
Prepares, conducts, confirms elicitation
Requirements Life Cycle Mgmt
Traces, maintains, prioritizes requirements
Strategy Analysis
Defines current and future state
Requirements Analysis and Design
Specifies, models, verifies, validates
Solution Evaluation
Assesses performance and recommends actions

Change Disposition Path

  1. Change request is receivedRun impact analysis first
  2. Benefit outweighs cost and riskApprove the change
  3. Cost or risk too highReject the change
  4. Timing or priority unclearDefer the change
  5. Requirement fails verificationFix wording, resubmit(Checks it was written right)
  6. Requirement fails validationRevisit business objective link(Checks the right one was built)

Change and Context Terms

Organizational Factors
Structure, culture, process, policy
Environmental Factors
Regulation, market, competitor, technology
Impact Analysis
Uses traceability to find effects
Change Disposition
Approve, reject, or defer change
Constraint
Internal restriction on solution options

MoSCoW Priority Order

Must Should Could Wont have this time

Must: non-negotiable requirementShould: important, not criticalCould: nice to haveWont: deferred this scope

Good Requirement Traits

Atomic, complete, consistent, concise, feasible, unambiguous, testable, prioritized, understandable

Atomic: one self-contained needTestable: verifiable pass or failUnambiguous: single interpretation onlyPrioritized: ranked by importance

Verification vs Validation

Verification

  • Checks requirement written correctly
  • Confirms right level of abstraction

Validation

  • Checks correct requirement chosen
  • Confirms link to business goal

Built right vs right built

Solution Evaluation Terms

Acceptance Criteria
Minimum needed to be acceptable
Evaluation Criteria
Compares competing solution options
Technical Feasibility
Can it be built now
Operational Feasibility
Can org run it daily
Economic Feasibility
Is it cost-effective overall
Requirements Verification
Was it written correctly
Requirements Validation
Was the right one chosen

RACI Matrix Roles

Responsible, Accountable, Consulted, Informed define stakeholder roles

Responsible: does the workAccountable: exactly one ownerConsulted: two-way input firstInformed: notified after the fact

Elicitation Technique Selector

  1. Few stakeholders, sensitive topicUse a one-on-one interview
  2. Need fast group consensusRun a facilitated workshop
  3. Want high volume of ideasUse a brainstorming session
  4. As-is state already documentedPerform document analysis
  5. Need to see real taskObserve via job shadowing
  6. Need shared visual understandingBuild a prototype

Elicitation Techniques

Brainstorming
Generates ideas, defers judgment
Interviews
One-on-one, structured or unstructured
Workshops
Facilitated group reaches consensus
Document Analysis
Reviews existing documentation for as-is
Observation
Active or passive job shadowing
Prototyping
Builds shared visual understanding

Stakeholder Analysis Tools

RACI Matrix
Responsible, Accountable, Consulted, Informed
Communication Skills
Verbal, non-verbal, written, listening
Structured Interview
Fixed list of questions
Unstructured Interview
Open-ended topic exploration

Output vs Outcome

Output

  • Tangible artifact produced
  • Example: a new report

Outcome

  • Benefit realized from output
  • Example: faster decisions made

Track outcomes, not outputs

Value Measurement Terms

Output
Tangible artifact a change produces
Outcome
End benefit realized from output
Potential Value
Value expected before implementation
Realized Value
Value confirmed after solution use
Leading vs Lagging Indicator
Predicts vs confirms performance

Constraint vs Dependency

Constraint

  • Internal restriction on options
  • Imposed by org or team

Dependency

  • One element relies on another
  • A relationship between elements

Limits choice vs creates order

Prioritization and Strategy Techniques

MoSCoW Prioritization
Sorts into Must Should Could Wont
SWOT Analysis
Strengths, weaknesses, opportunities, threats
Root Cause Analysis
5 Whys or fishbone diagram
User Stories
As a, I want, so that
Risk Analysis and Management
Weighs implementation and adoption risk

Common Traps

Need vs Solution Jump

Jumping to a solution too early Understand the need before solving

Verification Is Not Validation

Verification checks it was written correctly Validation checks the right one chosen

Wont Have Is Not Rejected

Wont have means deferred, not rejected Can return in a later scope

ECBA Has No Cut Score

IIBA never publishes a passing score Result is only pass or fail

Nine Domains Replaced Six KAs

Blueprint V1.1 restructured around BACCM Old KAs are now background material

Accountable Is Always One Person

RACI has exactly one accountable owner Multiple people can be responsible

Facilitation Is Not Leadership

Facilitation stays neutral, guides the group Leadership actively persuades a direction

Last Minute

  1. 1.ECBA: 50 questions, 75 minutes
  2. 2.Nine domains replaced the old KAs
  3. 3.Foundations 40%, practical BACCM domains 60%
  4. 4.No work experience required for ECBA
  5. 5.Fee $395, first-year membership included
  6. 6.ECBA never expires, no CDUs needed
  7. 7.BACCM concepts are always interconnected
  8. 8.MoSCoW ranks Must, Should, Could, Wont
  9. 9.RACI: only one Accountable role
  10. 10.Verification checks correctness; validation checks value
  11. 11.No separate ECBA application fee
  12. 12.Result shown immediately: pass or fail
Same family resources

Explore More IIBA Certifications

Continue into nearby exams from the same family. Each card keeps practice questions, study guides, flashcards, videos, and articles in one place.