Study guide
2.3 Plan Business Analysis Governance
CBAP Certified Business Analysis Professional Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & BACCM Framework
1.1 CBAP Exam Structure, Eligibility & Study Plan 1.2 The Business Analysis Core Concept Model (BACCM) 1.3 Key Concepts, Terms & Requirements Classification 1.4 Business Analysis Governance & Stakeholder Engagement Principles
2 Chapter 2: Business Analysis Planning and Monitoring
2.1 Plan Business Analysis Approach 2.2 Plan Stakeholder Engagement 2.3 Plan Business Analysis Governance 2.4 Plan Business Analysis Information Management 2.5 Identify Business Analysis Performance Improvements
3 Chapter 3: Elicitation and Collaboration
3.1 Prepare for Elicitation 3.2 Conduct Elicitation 3.3 Confirm Elicitation Results 3.4 Communicate Business Analysis Information 3.5 Manage Stakeholder Collaboration
4 Chapter 4: Requirements Life Cycle Management
4.1 Trace Requirements 4.2 Maintain Requirements 4.3 Prioritize Requirements 4.4 Assess Requirements Changes 4.5 Approve Requirements
5 Chapter 5: Strategy Analysis
5.1 Analyze Current State 5.2 Define Future State 5.3 Assess Risks 5.4 Define Change Strategy 5.5 Business Case Development & Financial Analysis
6 Chapter 6: Requirements Analysis and Design Definition
6.1 Specify and Model Requirements 6.2 Verify Requirements 6.3 Validate Requirements 6.4 Define Requirements Architecture 6.5 Define Design Options 6.6 Analyze Potential Value and Recommend Solution 6.7 Data Modeling & Process Modeling Techniques 6.8 Use Cases, User Stories & Acceptance Criteria Definition 6.9 Non-Functional Requirements & Solution Constraints
7 Chapter 7: Solution Evaluation
7.1 Measure Solution Performance 7.2 Analyze Performance Measures 7.3 Assess Solution Limitations 7.4 Assess Enterprise Limitations 7.5 Recommend Actions to Increase Solution Value
8 Chapter 8: Underlying Competencies, Techniques & Perspectives
8.1 Analytical Thinking, Problem Solving & Business Knowledge 8.2 Behavioral Characteristics & Interaction Skills 8.3 Core BABOK Techniques Master Review 8.4 Business Analysis Perspectives
2.3 Plan Business Analysis Governance
Key Takeaways Explain This Topic AI
BA Governance defines the decision-making rules, change control mechanics, prioritization frameworks, and sign-off approval workflows.
Change Control workflows mandate formal change request submission, comprehensive impact analysis (cost, scope, schedule, quality, risk), and CCB authorization.
Prioritization frameworks such as MoSCoW, Kano Model, Timeboxing, and Cost-Benefit Analysis provide objective criteria for ranking requirements.
Approval authority levels must be established early to prevent decision bottlenecks and scope creep during requirement baselining.
The Governance Approach ensures that requirement changes maintain alignment with strategic business goals and regulatory mandates.
Last updated: August 2026
- 2.3 Plan Business Analysis Governance
- Overview & Purpose of BABOK Task 3.3
The primary purpose of Plan Business Analysis Governance is to define how decisions are made regarding business analysis work—including requirement prioritization, change control, reviews, approvals, and governance body escalations. Governance provides the structural framework within which business analysts and stakeholders make authoritative choices regarding requirements and designs.
Without an established governance approach, initiatives suffer from uncontrolled scope creep, unresolved decision deadlocks, unauthorized requirement changes, and ambiguous approval states. Effective governance balances control and flexibility, establishing clear accountability while enabling timely decision execution.
Core Elements of Business Analysis Governance
BABOK v3 identifies four critical elements when planning governance:
1. Decision-Making Process
The governance plan must specify how decisions are made when consensus cannot be reached. It answers:
Who are the designated decision-makers? (Individual sponsor vs. Change Control Board vs. Steering Committee).
What decision rule applies? (Unanimous consensus, majority vote, delegated authority, or executive mandate).
What is the escalation path? Clear steps for escalating conflicts when working-level stakeholders disagree.
2. Requirement Prioritization Approach
Prioritization determines the relative importance and order of requirement execution. The BA establishes:
Prioritization Criteria: Value alignment, cost, risk, regulatory compliance, dependency constraints, or time-to-market impact.
Prioritization Formalities & Frameworks:
MoSCoW: Categorizes into Must Have (non-negotiable), Should Have (important but workaround exists), Could Have (desirable delighter), and Won't Have (out of scope for current release).
Kano Model: Classifies features as Basic (Must-be), Performance (Linear satisfaction), or Delighters (Excitement).
Timeboxing / Budgeting: Fixed resource constraints dictate how many high-priority items fit.
3. Change Control Process
Change control defines how changes to baselined requirements and designs are requested, evaluated, and approved. A robust change control workflow includes:
Change Request Submission: Standardized intake capturing change description, rationale, and requester.
Impact Analysis: Assessing the ripple effect across 5 dimensions: Scope, Cost/Effort, Schedule, Quality/Architecture, and Risk.
Decision & Communication: Authorization by the Change Control Board (CCB) and formal update to baseline repositories.
4. Approval Process
The approval process establishes how sign-offs are secured for business analysis deliverables:
Approval Type: Formal written sign-off, digital cryptographic approval, or verbal sprint review approval.
Authority Levels: Setting financial or risk thresholds where local project leads can approve vs. requiring executive sponsor sign-off.
Prioritization Framework Comparison
Technique Primary Focus Best Used For
MoSCoW Categorizing requirements by absolute necessity. Scope management in fixed-deadline releases.
Kano Model Customer satisfaction and perception. Commercial consumer applications & UX enhancement.
Timeboxing Fixed capacity and schedule. Agile iterations and sprint backlog allocation.
Cost-Benefit Ratio Financial return on investment (ROI). Capital expenditure trade-off decisions.
Impact Analysis Dimensions in Change Control
When evaluating a proposed change, the BA must analyze five critical dimensions before presenting recommendations to the CCB:
Scope Impact: Does the change add new features, alter existing logic, or invalidate completed work?
Schedule Impact: Will the change delay milestone deadlines or critical path deliverables?
Cost/Resource Impact: Does it require additional development hours, license fees, or specialist skills?
Quality & Architecture Impact: Does it compromise system security, performance SLAs, or maintainability?
Risk Impact: What new operational, compliance, or technical risks are introduced?
BACCM Alignment in Governance
Change: Ensure that all modifications to baseline requirements are systematically evaluated.
Need: Verify that proposed changes align with underlying enterprise needs.
Solution: Protect solution integrity by preventing unauthorized scope additions.
Stakeholder: Clarify decision-making authority and escalation channels.
Value: Prioritize high-value requirements over low-value requests.
Context: Fit governance rules within organizational policies and compliance standards.
Inputs, Guidelines, and Outputs
Inputs:
Business Analysis Approach: Dictates overall methodology (predictive vs. adaptive).
Stakeholder Engagement Approach: Identifies key decision-makers and approval roles.
Outputs:
Governance Approach: Formally documents decision rules, change control workflows, prioritization frameworks, and approval authorities.
Enterprise Scenario: Emergency Change Request
Scenario: Two weeks prior to deploying a new insurance claims engine, a senior compliance officer submits an urgent change request to add automated tax reporting logic.
Governance Execution: The BA follows the baseline Governance Approach . Instead of immediately modifying code, the BA conducts a 5-dimension impact analysis: adding the logic requires 80 hours, delays deployment by 4 days, but prevents severe non-compliance fines. The BA presents this to the Change Control Board (CCB). The CCB approves the change, adjusts the project baseline, and formalizes the budget revision.
CBAP Exam Tips & Triggers
Exam Trigger: If a stakeholder verbally asks a BA to add a "quick minor feature" to a baselined BRD, the correct BA response is to instruct the stakeholder to submit a formal Change Request for impact analysis .
Exam Trigger: If stakeholders cannot agree on feature priorities, the BA should apply the established Prioritization Framework and escalate unresolved conflicts through the Governance Escalation Path .
Key Distinction: Governance defines how changes are managed; it does NOT mean refusing all changes.