Understanding Business Analysis
20%of exam
Mindset for Effective Business Analysis
14%of exam
Implementing Business Analysis
6%of exam
Change
10%of exam
Need
10%of exam
Solution
10%of exam
Stakeholder
10%of exam
Value
10%of exam
Context
10%of exam
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
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
- Explains why change is needed→Classify as Business Requirement
- Specific stakeholder need identified→Classify as Stakeholder Requirement
- Describes what solution must do→Classify as Functional Requirement
- Describes how well it performs→Classify as Non-Functional Requirement
- Needed only during the transition→Classify as Transition Requirement
- Requirement bundles multiple needs→Split 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
- Change request is received→Run impact analysis first
- Benefit outweighs cost and risk→Approve the change
- Cost or risk too high→Reject the change
- Timing or priority unclear→Defer the change
- Requirement fails verification→Fix wording, resubmit(Checks it was written right)
- Requirement fails validation→Revisit 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
Good Requirement Traits
Atomic, complete, consistent, concise, feasible, unambiguous, testable, prioritized, understandable
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
Elicitation Technique Selector
- Few stakeholders, sensitive topic→Use a one-on-one interview
- Need fast group consensus→Run a facilitated workshop
- Want high volume of ideas→Use a brainstorming session
- As-is state already documented→Perform document analysis
- Need to see real task→Observe via job shadowing
- Need shared visual understanding→Build 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.ECBA: 50 questions, 75 minutes
- 2.Nine domains replaced the old KAs
- 3.Foundations 40%, practical BACCM domains 60%
- 4.No work experience required for ECBA
- 5.Fee $395, first-year membership included
- 6.ECBA never expires, no CDUs needed
- 7.BACCM concepts are always interconnected
- 8.MoSCoW ranks Must, Should, Could, Wont
- 9.RACI: only one Accountable role
- 10.Verification checks correctness; validation checks value
- 11.No separate ECBA application fee
- 12.Result shown immediately: pass or fail
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.
More From This Family
Videos and articles for deeper review.
