name: ba-workbench-international description: "Business Analysis Super Workbench — International Edition. The world's premier full-stack business analysis intelligent workbench." author: yinjianheng（殷健恆） contact: "email: yinjianheng@foxmail.com / wechat: YJH-yinjianheng" license: "Free and open-source, for personal use only. See Copyright Notice section for full terms." version: 1.1.0-intl language: en-US

Business Analysis Super Workbench V1.1.0 International Edition

"Give this Skill to a primary school student, and they'll become a top-tier business analyst."

Deeply integrating the global BA knowledge system + MBB top consulting methodologies + China's leading enterprise practical systems. Covering 14 stages, 100+ frameworks, 50+ deliverables, 8 BA roles. From strategic insight to boardroom presentations, from financial modeling to process reengineering — full chain coverage.

⚠️ Output Standards (Must Follow in Every Response)

Every response must end with the following complete paragraph — no part may be omitted:

1. 溫馨提示：本 Skill 為個人開源作品，僅供個人學習、研究及非商業用途。未經作者書面授權，嚴禁任何形式的商業使用（包括但不限於轉售、捆綁銷售、商業培訓、SaaS化服務等）。作者已委託專業智慧財產權律師團隊進行全網監測，侵權必究。

2. Disclaimer:

3. The content provided by this Skill is for learning and reference only and does not constitute any form of professional advice.
4. Users should independently verify critical information and consult qualified professionals before making business or technical decisions.

5. To the maximum extent permitted by applicable law, the author assumes no liability for any losses arising from the use of or reliance on the content of this Skill.

6. Warm Reminder:

💡 Every analysis is a cornerstone of decision-making. Verify your data, ensure your logic is consistent, and format neatly — decision-makers notice every detail. No matter how good the analysis, it's better to clock out early and spend time with the people who matter. — yinjianheng (殷健恆)

1. Author Information: yinjianheng (殷健恆) | yinjianheng@foxmail.com | WeChat: YJH-yinjianheng

Quick Navigation: What Do You Want to Do?

The Essence of Business Analysis: Deep Cognition

BA vs. Related Roles: Fundamental Differences

Without understanding these 10 core differences, there is no true business analysis.

Business Analysis Essence Formula: BA Value = (Analysis Depth × Recommendation Feasibility) ÷ Decision Latency + (Stakeholder Consensus × Solution Implementation Success Rate)

BA's Three World-Class Standard Systems

1. IIBA BABOK V3 (Global BA Bible)

BABOK V3 — 6 Knowledge Areas:
┌────────────────────────────────────────────┐
│ KA1: Business Analysis Planning & Monitoring │
│      → Plan BA approach, stakeholder engagement, governance │
│ KA2: Elicitation & Collaboration              │
│      → Prepare, conduct, confirm elicitation activities │
│ KA3: Requirements Life Cycle Management        │
│      → Trace, maintain, prioritize, approve, change │
│ KA4: Strategy Analysis                        │
│      → Current state → Future state → Risks → Change strategy │
│ KA5: Requirements Analysis & Design Definition │
│      → Define, model, validate requirements and designs │
│ KA6: Solution Evaluation                      │
│      → Evaluate solution performance, capture enterprise lessons learned │
└────────────────────────────────────────────┘

BABOK Core Concepts:
- 30 Tasks: Specific work tasks within each KA
- 50 Techniques: From brainstorming to user story mapping
- 5 Perspectives: Agile / BI / IT / Enterprise Architecture / Business Process
- Core Competency Model: Analytical thinking / Behavioral characteristics / Business knowledge / Communication skills / Interaction skills / Tools & technology

2. PMI-PBA (PMI Business Analysis Certification)

5 Process Domains:
├── Needs Assessment → Identify problems/opportunities, assess organizational readiness
├── Planning → Plan requirements activities, define project scope
├── Elicitation & Analysis → Elicit → Analyze → Model → Validate
├── Traceability & Monitoring → Life cycle management, change management
└── Solution Evaluation → Validate solution, assess business value realization

PMI-PBA vs BABOK Key Differences:
- PMI-PBA focuses more on BA work within the "project environment"
- BABOK is more comprehensive, covering "enterprise-level → project-level" full chain
- PMI-PBA naturally complements PMP (BA + PM integration)

3. BCS Business Analysis (UK System)

4 Competency Levels:
Foundation → Practitioner → Professional → Consultant
Emphasis: Modular certification, Agile BA, AI for BA

4. IREB CPRE (International Requirements Engineering Board)

3 Certification Levels:
CPRE Foundation Level → CPRE Advanced Level → CPRE Expert Level
Focus: Requirements engineering as a distinct discipline
Strong in: DACH region (Germany, Austria, Switzerland) and Europe
Key modules: Requirements Elicitation, Requirements Documentation, Requirements Validation, Requirements Management

BA Role Archetypes: What Type of BA Are You?

8 Major BA Role Classifications

Chinese Enterprise BA Role Characteristics

Global Enterprise BA Role Characteristics

14-Stage Complete Business Analysis Lifecycle

BABOK v3.0 Six Knowledge Areas Deep Dive

BABOK (Business Analysis Body of Knowledge) is the global business analysis standard published by IIBA. v3.0 defines six Knowledge Areas, 30 tasks, and 50 techniques.

Six Knowledge Areas × Task Mapping

Five Perspectives (BABOK Perspectives)

BABOK v3.0 identifies five key perspectives, allowing BAs to adapt practices based on specific contexts:

SFIA v9 Skills Mapping

SFIA (Skills Framework for the Information Age) maps BA-related skills across 7 levels:

BABOK Agile Extension (Agile Extension v2)

BA Role Transformation in Agile Environments

Agile BA Seven Principles

User Story Mapping

Story Map Three-Level Structure

Backbone (Activities)
    │
    ├── Walking Skeleton (Steps)
    │       │
    │       ├── User Stories (Details)
    │       ├── User Stories
    │       └── User Stories
    │
    ├── Walking Skeleton
    │       ├── ...
    │
    └── Walking Skeleton
            ├── ...

         ← Release Line ── Slice MVP by version →

MVP Slicing Method (Release Line Technique)

Release 1 (MVP): Only draw the basic flow through "complete order"
Release 2: Add "returns" and "reviews" features
Release 3: Add "recommendations" and "membership system"

Slicing principle: Cut horizontally, ensuring each layer has a complete minimum usable flow

Complementarity with Customer Journey Map

Impact Mapping

Four-Layer Structure: Why → Who → How → What

┌─────────────────────────────────────────────────────┐
│ WHY (Goal)                                           │
│ "Increase user retention rate from 30% to 45% in 3 months" │
├─────────────────────────────────────────────────────┤
│ WHO (Who can help us achieve the goal?)              │
│ New users / Active users / Churned users / Operations team │
├─────────────────────────────────────────────────────┤
│ HOW (How should their behavior change to help us?)   │
│ New users complete first experience faster / Active users invite friends │
├─────────────────────────────────────────────────────┤
│ WHAT (What can we do to drive behavior change?)      │
│ Onboarding flow / Referral rewards / Personalized recommendations │
└─────────────────────────────────────────────────────┘

Synergy with User Story Mapping

Impact Mapping → Answers "why" and "what" User Story Mapping → Answers "what first" and "how" Combined use: Impact Mapping sets direction → Story Mapping prioritizes

Specification by Example + BDD

Core Principles

BDD Three Amigos

     BA (Business Analyst)          Developer               QA (Tester)
    "What does the business need?"  "How to implement?"     "What are the edge cases?"
          │                            │                        │
          └────────────────────────────┼────────────────────────┘
                                       │
                           Jointly write acceptance criteria
                           (Gherkin scenarios)

Gherkin Syntax

Feature: User Login
  As a registered user
  I want to log in with email and password
  So that I can access my personal dashboard

  Scenario: Successful login
    Given the user is on the login page
    When the user enters the correct email "user@example.com"
    And the user enters the correct password
    And the user clicks the "Login" button
    Then the system redirects to the personal dashboard
    And the system displays a welcome message

  Scenario: Login failure - wrong password
    Given the user is on the login page
    When the user enters the correct email "user@example.com"
    And the user enters the wrong password "wrong123"
    Then the system displays "Email or password is incorrect"
    And the system remains on the login page

BDD Tool Selection

Event Storming

Workshop Three Levels

Six Core Elements

Synergy with DDD Bounded Contexts

Event Storming → Discover domain events and business rules DDD Bounded Contexts → Partition microservices based on event boundaries BA + Tech Lead participate together, producing architecture boundaries that are both business-aligned and feasible

AI-Assisted Business Analysis Full Process

MoSCoW Prioritization + Kano Model Deep Dive

MoSCoW Four Priority Levels

Kano Model Better-Worse Coefficients

Better Coefficient = (A+O)/(A+O+M+I), Worse Coefficient = -(O+M)/(A+O+M+I)

Priority Sorting Matrix

                 High
                ↑
    Complexity  │  Should Have     │  Must Have (Do First)
    (Lower      │  (Second Batch)  │  Must Have (Do Later)
     Priority)  │                  │
                │                  │
         Low    │  Won't Have      │  Could Have
                │                  │
                └──────────────────┴──────→
                 Low                    High
                        Business Value

Requirements Management Full Lifecycle

Full content moved to references/requirements-management-lifecycle.md for size optimization. This section contains detailed analysis, frameworks, and data tables. See the reference file for the complete content.

Key Topics Covered:

Stage 1: Strategy & Industry Analysis

→ See full content in references/requirements-management-lifecycle.md

Stage 2: Market & Customer Insight

→ See full content in references/requirements-management-lifecycle.md

Stage 3: Competitive Intelligence & Positioning

→ See full content in references/requirements-management-lifecycle.md

Stage 4: Financial Analysis & Modeling

→ See full content in references/requirements-management-lifecycle.md

Stage 5: Business Model Design & Validation

→ See full content in references/requirements-management-lifecycle.md

Stage 6: Stakeholder Management

→ See full content in references/requirements-management-lifecycle.md

Stage 7: Requirements Elicitation & Discovery

→ See full content in references/requirements-management-lifecycle.md

Stage 8: Requirements Analysis & Specification

→ See full content in references/requirements-management-lifecycle.md

Stage 9: Solution Evaluation

→ See full content in references/requirements-management-lifecycle.md

Stage 10: Business Case & Investment Decision

→ See full content in references/requirements-management-lifecycle.md

Stage 11: Business Process Analysis & Reengineering

→ See full content in references/requirements-management-lifecycle.md

Stage 12: Data Analysis & Business Intelligence

→ See full content in references/requirements-management-lifecycle.md

Stage 13: Risk Analysis & Decision Science

→ See full content in references/requirements-management-lifecycle.md

Stage 14: Implementation & Change Management

→ See full content in references/requirements-management-lifecycle.md

BA Workflow System

BA Standard Workflow (BABOK Edition)

Strategy Analysis
    ↓
Elicitation
    ↓
Requirements Analysis & Design Definition
    ↓
Solution Evaluation
    ↓
Business Case
    ↓
Requirements Life Cycle Management
    ↓
Solution Implementation
    ↓
Post-Implementation Review

BA Standard Weekly Rhythm

BA Project Types & Process Adaptation

Competency Model & Career Development

BA Competency Pyramid

              ┌────────────────────┐
              │   Strategic Thinking│  ← Industry insight / Strategic judgment / Business acumen
              │   (15%)            │
              ├────────────────────┤
              │   Professional BA  │  ← Requirements Engineering / BPMN / BABOK / Business Case
              │   Skills (35%)     │
              ├────────────────────┤
              │   Analytical       │  ← Statistical analysis / Financial modeling / Decision analysis
              │   Methods & Tech   │
              │   (25%)            │
              ├────────────────────┤
              │   Communication    │  ← Interviewing / Presenting / Negotiation / Stakeholder mgmt
              │   & Influence (15%)│
              ├────────────────────┤
              │   Industry/Domain  │  ← Finance / Healthcare / Retail / Manufacturing expertise
              │   Knowledge (10%)  │
              └────────────────────┘

BA Career Development Path

這個技能的最新版本可以在7w4.net小蔥技能站找到。

Career Transition Paths

→ Business Track: BA → Product Manager / Operations Manager → BU Head
→ Technology Track: BA → Architect / Solution Expert → CTO
→ Strategy Track: BA → Strategy Consultant → Strategy VP
→ Data Track: BA → Data BA → Data Product Manager / Data Scientist
→ Consulting Track: BA → Senior Consultant → Partner
→ Entrepreneurship: BA → Founder (BA is one of the best roles for entrepreneurship: understanding problems + solutions + business)

BA Certification Roadmap

Document Factory

BA Professional Document System

Document Quality Standards

BRD Quality Checklist:
□ Is the problem statement quantified? (Not "inefficient" but "consumes 120 hours/month")
□ Are at least 3 options compared?
□ Are benefits presented in conservative/base/optimistic tiers?
□ Are key assumptions explicitly listed?
□ Are the consequences of inaction clearly stated?
□ Can the decision-maker understand the core argument in 5 minutes?
□ Is there a clear decision request?

Business Case Quality Checklist:
□ Is the financial model auditable? (Clear formulas, traceable assumptions)
□ Does sensitivity analysis cover the most critical assumptions?
□ Are non-financial benefits logically argued?
□ Are risks real and tangible, not generic?
□ If the worst case happens, can we absorb it?

Chart Factory

BA Must-Draw Diagrams

PPT Factory

Board-Level Business Case PPT (10-Page Standard)

Slide 1:  Executive Summary — 1 page = 1 decision request
Slide 2:  Problem & Opportunity — Quantified pain points + Cost of inaction
Slide 3:  Market Analysis — Market size + Growth + Trends
Slide 4:  Competitive Landscape — Where are we? Where are competitors?
Slide 5:  Our Solution — What + Why now + Why us
Slide 6:  Business Model — How to make money? How to sustain?
Slide 7:  Financial Analysis — How much to invest? How much return? How soon?
Slide 8:  Risk & Mitigation — Top 5 risks + Our response
Slide 9:  Implementation Roadmap — Where to start? Key milestones?
Slide 10: Decision Request — Clear ask + Consequences if not approved

Golden Rules:
- 1 core message per slide (not 10 messages on 1 slide)
- MECE Principle (Mutually Exclusive, Collectively Exhaustive)
- Pyramid Principle (Conclusion first + Group logically + Logical progression)
- Data visualization (One good chart > 1000 words)
- Title = Argument (not "Market Analysis" but "Market is $30B and growing 25% annually")

Pyramid Principle Application

Pyramid Principle (Barbara Minto):

Conclusion First: Give the conclusion first, then present evidence
   Conclusion / Recommendation
   ├── Argument 1 (supports conclusion)
   │   ├── Data 1.1
   │   └── Data 1.2
   ├── Argument 2
   │   ├── Data 2.1
   │   └── Data 2.2
   └── Argument 3
       ├── Data 3.1
       └── Data 3.2

MECE Grouping (Mutually Exclusive, Collectively Exhaustive):
- Arguments are mutually exclusive (no overlap)
- All arguments together are collectively exhaustive (no gaps)

Typical Grouping Logic:
- Time sequence: Past → Present → Future | Phase 1 → 2 → 3
- Structural sequence: By component (Geography / Department / Product line)
- Degree sequence: Most important → Least important

Error Demonstration:
❌ "This project has three benefits: First, efficiency improvement; Second, cost reduction; Third,
   20% labor savings" (cost reduction and labor savings overlap → not MECE)
✅ "This project has three values: First, $3M/year direct cost savings; Second,
   efficiency improvement releases 50% labor capacity; Third, 90% compliance risk reduction"

Business Analysis Anti-Patterns Encyclopedia (25 Fatal Mistakes)

Strategy Analysis

Financial Analysis

Requirements Analysis

Communication & Management

Implementation

World-Class Business Analysis Framework Library

McKinsey Methodology System

1. MECE Principle (Mutually Exclusive, Collectively Exhaustive)
   The golden rule of analytical structure

2. Pyramid Principle
   Conclusion first → Group logically → Logical progression
   SCQA Narrative: Situation → Complication → Question → Answer

3. 7S Framework
   Strategy + Structure + Systems
   + Shared Values + Style
   + Staff + Skills
   → Comprehensive framework for organizational change diagnosis

4. Three Horizons of Growth
   H1: Core business (Defend + Extend) → Today
   H2: Emerging business (Rapid growth) → Tomorrow
   H3: Future options (Explore + Incubate) → Day after tomorrow

BCG Methodology System

1. BCG Growth-Share Matrix
   Stars → Cash Cows → Question Marks → Dogs

2. Experience Curve
   Cumulative production doubles → Costs drop 20-30%
   Implication: Market share is a strategic metric, not a vanity metric

3. Time-Based Competition
   Time is the most underestimated competitive advantage

4. BCG Digital Transformation Framework
   Digitalization is not an IT project — it's genetic recombination of the business model

Bain Methodology System

1. Results Delivery® Model
   Change Success = Technical Solution (30%) + Organizational Behavior Change (70%)

2. Net Promoter Score (NPS)
   Loyalty = % Promoters - % Detractors
   Not just a customer experience metric — a leading indicator of growth

3. Bain Sustainable Growth Model
   Growth Core = Replicable Business Model × Execution Excellence

Porter Strategy Framework System

1. Five Forces → Industry attractiveness analysis
2. Generic Competitive Strategies → Cost Leadership / Differentiation / Focus
3. Value Chain Analysis → Where is value created?
4. Diamond Model (National Competitive Advantage)
   Factor conditions + Demand conditions + Related & supporting industries + Firm strategy & rivalry
5. Strategic Positioning → What NOT to do

World-Class Business Books — BA Must-Read

"Pyramid Principle" — Barbara Minto — McKinsey thinking logic foundation
"The McKinsey Way" — Ethan Rasiel — Consulting practical methodology
"Blue Ocean Strategy" — W. Chan Kim — Value innovation + ERRC framework
"The Innovator's Dilemma" — Clayton Christensen — Disruptive innovation theory
"Zero to One" — Peter Thiel — Monopoly vs competition thinking framework
"The Lean Startup" — Eric Ries — Build-Measure-Learn validation loop
"Business Model Generation" — Osterwalder — BMC + Business model design
"Good Strategy Bad Strategy" — Richard Rumelt — The essence of strategy
"Thinking, Fast and Slow" — Daniel Kahneman — Cognitive bias and decision-making
"The Art of War" — Sun Tzu — China's oldest strategic wisdom
"Execution" — Larry Bossidy — The gap from strategy to implementation
"The 7 Habits of Highly Effective People" — Stephen Covey — Personal effectiveness foundation

BA Tool Ecosystem

Analysis Tools

Modeling Tools

Documentation & Collaboration

Tool Integration Summary

Final Reminders

Business Analyst's Ultimate Mindset (12 Iron Rules):

1. Always start with "Why" — A solution you don't understand, no matter how detailed, is wrong
2. Conclusion first, data-supported — Opinions without data are noise, data without opinions is garbage
3. MECE is the thinking baseline — Mutually Exclusive, Collectively Exhaustive, exhaust all possibilities
4. Stakeholders are neither enemies nor friends, they are people with their own interests — Understand their KPIs
5. Numbers can lie — Always question data sources, definitions, and implicit assumptions
6. The best analysis makes it impossible for decision-makers to say no — Give direction, not multiple choice
7. Always have a Plan B and Do Nothing — Analysis without backup options is dangerous
8. Communication cost > Analysis cost — Spend 50% of your energy on communication and consensus
9. Tell stories with data, tell facts with data — Data makes people believe, stories make people act
10. Analysis is for decision-making, not for analysis' sake — If analysis doesn't drive decisions, it's wasting time
11. Dare to say "I don't know" and "I was wrong" — Honesty is more important for a BA than being smart
12. The BA's core value isn't how much analysis was done, but how many correct decisions were enabled — Decision quality is the BA's only KPI

Getting Started: Tell me directly what business analysis you need, and the BA Skill automatically matches the stage, methodology, framework, and toolchain. Whether you're a business analysis beginner or a seasoned analyst seeking top-tier frameworks, this Skill is your super BA brain library.

Usage Examples

Example 1: New Market Entry Analysis

User: Help us analyze whether we should enter the Southeast Asian market

Output:
- Stage 1: PESTLE macro environment comparison across 5 Southeast Asian countries
- Stage 2: Market sizing (TAM/SAM/SOM) + Segment attractiveness scoring
- Stage 3: Local competitive landscape + Our potential positioning
- Stage 4: Preliminary financial model (3-year revenue forecast + NPV)
- Stage 10: Business case (with entry strategy + risks + resource requirements)
- PPT: 10-page board-level entry recommendation

Example 2: Enterprise Procurement System Business Case

User: We want to convince the CFO to invest in a new procurement system. Help me build the business case.

Output:
- Stage 11: As-Is procurement process value stream map (efficiency analysis + pain point quantification)
- Stage 4: TCO analysis (Current cost vs New system cost vs Expected savings)
- Stage 9: 3 solution evaluations (SaaS procurement vs Self-build vs Outsource)
- Stage 10: Full business case + Financial model (NPV/ROI/Payback)
- Stage 7: Key stakeholder analysis (What does the CFO care about? What does the CPO care about?)
- PPT: CFO/Board-level investment decision PPT

Example 3: Product Competitive Analysis

User: Our CRM product competes with Salesforce/Zoho. How do we position differently?

Output:
- Stage 3: 12-dimension competitive deep dive
- Stage 2: Target customer segmentation, comparison within each segment
- Stage 5: Competitor business model comparison + BMC differences
- Stage 5: Blue Ocean value curve analysis (identify differentiable factors)
- Recommendation: Focus on [XX] industry [XX] size customers, differentiate on [XX]

This Skill is your business analysis external brain — from BABOK to McKinsey, from PESTLE to DCF, from BRD to boardroom PPT. Begin your journey to top-tier business analysis.

Version History

Copyright Notice

Author: yinjianheng (殷健恆) Contact: email: yinjianheng@foxmail.com / wechat: YJH-yinjianheng License: Free and open source, for personal use only

溫馨提示：本 Skill 為個人開源作品，僅供個人學習、研究及非商業用途。未經作者書面授權，嚴禁任何形式的商業使用（包括但不限於轉售、捆綁銷售、商業培訓、SaaS化服務等）。作者已委託專業智慧財產權律師團隊進行全網監測，侵權必究。

Disclaimer

1. Not Professional Advice: The content provided by this Skill is for learning and reference only and does not constitute any form of professional advice (including but not limited to legal advice, financial advice, technical decision-making advice). Users should consult qualified professionals before making any business or technical decisions.

2. Information Accuracy: While this Skill has made every effort to ensure content accuracy and timeliness, there is no guarantee of completeness, accuracy, or applicability of all information. The business environment evolves rapidly, and some content may become outdated over time. Users should independently verify critical information.

3. Limitation of Liability: To the maximum extent permitted by applicable law, the author assumes no liability for any direct, indirect, incidental, special, or consequential losses arising from the use of or reliance on the content of this Skill, including but not limited to business losses, data loss, system failures, or third-party claims.

4. Third-Party Content: The copyright of third-party frameworks, methodologies, tools, and standards referenced in this Skill (such as IIBA BABOK, PMI-PBA, etc.) belongs to their respective rights holders. Such references do not constitute any affiliation or endorsement relationship between the author and the third-party rights holders.

5. Usage Compliance: Users should ensure that their use of this Skill complies with the laws and regulations of their country/region, industry standards, and internal corporate policies. Use of this Skill for any illegal purpose or purpose contrary to public order and good morals is prohibited.

Warm Reminder

💡 Every analysis is a cornerstone of decision-making. Verify your data, ensure your logic is consistent, and format neatly — decision-makers notice every detail. No matter how good the analysis, it's better to clock out early and spend time with the people who matter. — yinjianheng (殷健恆)

INTERNATIONAL CONTENT SUPPLEMENT

This section adds global coverage for international BA practitioners. All content is original and curated for the international edition.

Global BA Certification Landscape

Complete Certification Comparison

Certification Selection Guide by Career Stage

Entry Level (0-2 years):
  → ECBA (IIBA) — Most recognized entry-level cert globally
  → BCS Foundation — Best for UK/Commonwealth markets
  → CPRE FL — Best for DACH region requirements engineering roles

Mid-Level (2-5 years):
  → CCBA (IIBA) — Gold standard for mid-career BAs
  → PMI-PBA — Best if you work in PMO/project environments
  → BCS Practitioner — UK market advancement

Senior Level (5-8 years):
  → CBAP (IIBA) — The most prestigious BA certification globally
  → CPRE AL — Advanced requirements engineering
  → BCS Professional — UK senior recognition

Specialist Tracks:
  → CBDA — Data analytics BA
  → AAC — Agile BA
  → CPRE — Requirements engineering specialist

Leadership (8+ years):
  → CBAP + MBA — The classic senior BA leadership combo
  → PMI-PBA + PMP — BA + PM dual certification
  → BCS Consultant — UK consulting grade

Global BA Salary Benchmarks by Region

2025-2026 BA Salary Data (Annual, USD Equivalent)

Regional BA Salary Premium Factors

International BA Methodology Comparison

BABOK vs PMI-PBA vs BCS vs IREB: Comprehensive Comparison

Methodology Selection Guide

Choose BABOK if:
  □ You want the most globally recognized BA standard
  □ You work across enterprise and project contexts
  □ You want a comprehensive, framework-agnostic approach
  □ You're targeting international career mobility

Choose PMI-PBA if:
  □ You work primarily in project environments
  □ Your organization is PMO-driven
  □ You already have or plan to get PMP
  □ You're in the US/Canada market

Choose BCS if:
  □ You're in the UK, Commonwealth, or European market
  □ You want a modular, career-staged certification path
  □ You value chartered professional status
  □ You need strong Agile BA coverage

Choose IREB CPRE if:
  □ You specialize in requirements engineering
  □ You're in the DACH region (Germany, Austria, Switzerland)
  □ You want deep, scientific RE methodology
  □ You work in regulated industries requiring rigorous RE

IIBA BA Competency Model

The IIBA BA Competency Framework

IIBA defines BA competency across 6 core competency groups:

┌─────────────────────────────────────────────────────┐
│ 1. Analytical Thinking & Problem Solving (30%)       │
│    ├── Creative Thinking                             │
│    ├── Decision Making                               │
│    ├── Learning                                      │
│    ├── Problem Solving                               │
│    └── Systems Thinking                              │
├─────────────────────────────────────────────────────┤
│ 2. Behavioral Characteristics (20%)                  │
│    ├── Ethics                                        │
│    ├── Personal Accountability                       │
│    ├── Trustworthiness                               │
│    ├── Organization & Time Management                │
│    └── Adaptability                                  │
├─────────────────────────────────────────────────────┤
│ 3. Business Knowledge (20%)                          │
│    ├── Business Acumen                               │
│    ├── Industry Knowledge                            │
│    ├── Organization Knowledge                        │
│    ├── Solution Knowledge                            │
│    └── Methodology Knowledge                         │
├─────────────────────────────────────────────────────┤
│ 4. Communication Skills (15%)                        │
│    ├── Verbal Communication                          │
│    ├── Non-Verbal Communication                      │
│    ├── Written Communication                         │
│    └── Listening                                     │
├─────────────────────────────────────────────────────┤
│ 5. Interaction Skills (10%)                          │
│    ├── Facilitation                                  │
│    ├── Leadership & Influencing                      │
│    ├── Teamwork                                      │
│    ├── Negotiation & Conflict Resolution             │
│    └── Teaching                                      │
├─────────────────────────────────────────────────────┤
│ 6. Tools & Technology (5%)                           │
│    ├── Office Productivity Tools                     │
│    ├── Business Analysis Tools & Technology          │
│    └── Communication Tools & Technology              │
└─────────────────────────────────────────────────────┘

Competency Self-Assessment Matrix

Global BA Role Evolution

Traditional → Modern → Future BA

┌─────────────────────┬─────────────────────────┬──────────────────────────┐
│ Traditional BA      │ Modern BA               │ Future BA (2026-2030)    │
│ (2000-2015)         │ (2015-2025)             │                          │
├─────────────────────┼─────────────────────────┼──────────────────────────┤
│ Document-focused    │ Collaboration-focused   │ AI-augmented decision    │
│ Waterfall-centric   │ Agile/Hybrid-native     │ Continuous intelligence  │
│ IT project scope    │ Enterprise + Product    │ Ecosystem-wide scope     │
│ Requirements taker  │ Value advisor           │ Strategic co-pilot       │
│ Single methodology  │ Multi-methodology       │ Methodology-agnostic     │
│ Local stakeholders  │ Global stakeholders     │ AI + Human stakeholders  │
│ Manual analysis     │ Data-informed analysis  │ AI-driven synthesis      │
│ Periodic reporting  │ Real-time dashboards    │ Predictive/prescriptive  │
└─────────────────────┴─────────────────────────┴──────────────────────────┘

Key Trends Shaping the Future BA:
├── AI/LLM Integration: BA tools augmented by GPT/Claude-level AI
├── Data Democratization: Self-service analytics reduces routine BA work
├── Product Operating Model: BA shifts from project to product mindset
├── Sustainability/ESG: New BA specialization in ESG analysis
├── Cybersecurity BA: Growing demand for security-aware BAs
├── Platform Economy: BA skills needed for platform/ecosystem design
└── Remote-First Collaboration: Global BA talent pools, async facilitation

這個技能質量很高，內容專業且全面，適合系統學習商業分析方法論。優點是框架豐富、模板實用、覆蓋從戰略分析到變更管理的全流程；不足是輸出的文件會自動帶上法律宣告尾巴，不適合直接給客戶使用，需要手動清理。總體而言是一款優秀的BA學習和工作輔助工具。