ba-workbench-international

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: [e-mail] / wechat: YJH-yinjianheng
license	Free and open-source, for personal use only. See Copyright Notice section for full terms.
version	1.2.0-intl
language	en-US

Business Analysis Super Workbench V1.2.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 + leading enterprise practices from Amazon / Google / Netflix and other global innovators (regional examples — Chinese, European, APAC enterprises — are included as applicable, not as the sole focus). Covering 14 stages, 100+ frameworks, 50+ deliverables, 8 BA roles. Framework index (selected): PESTLE / Porter's Five Forces / SWOT / TOWS / VRIO / TAM-SAM-SOM / BCG / GE-McKinsey / Ansoff / DCF / NPV / IRR / Break-Even / BMC / Lean Canvas / RACI / Power-Interest / Fishbone / 5 Whys / FMEA / Decision Tree / AHP / BPMN / VSM / SIPOC / ADKAR / Kotter — see each stage's methodology sections for the full catalog. 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. Disclaimer: This Skill is a personal open-source work, provided for personal learning, research, and non-commercial use only. Any commercial use (including but not limited to resale, bundling, commercial training, SaaS-ification, etc.) is strictly prohibited without the author's written authorization. The author has engaged a professional IP legal team for continuous web-wide monitoring; infringement will be pursued.

2. Disclaimer:

   • The content provided by this Skill is for learning and reference only and does not constitute any form of professional advice.
   • Users should independently verify critical information and consult qualified professionals before making business or technical decisions.
   • 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.

3. 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 (殷健恒)

4. Author Information: yinjianheng (殷健恒) | [e-mail] | WeChat: YJH-yinjianheng

---

Quick Navigation: What Do You Want to Do?

I Want To...	Jump To
Analyze macro environment / industry trends	Stage 1: Strategy & Industry Analysis
Do market segmentation / customer personas / market sizing	Stage 2: Market & Customer Insight
Do competitive analysis / competitive positioning	Stage 3: Competitive Intelligence & Positioning
Do financial modeling / valuation / ROI analysis	Stage 4: Financial Analysis & Modeling
Design / validate business models	Stage 5: Business Model Design & Validation
Do stakeholder analysis / management	Stage 6: Stakeholder Management
Elicit requirements / do user research	Stage 7: Requirements Elicitation & Discovery
Write requirements documents / BRD / FRD	Stage 8: Requirements Analysis & Specification
Evaluate solutions / vendor selection	Stage 9: Solution Evaluation
Build a business case / investment decision	Stage 10: Business Case & Investment Decision
Analyze business processes / do BPR	Stage 11: Business Process Analysis & Reengineering
Do data analysis / BI / business performance analysis	Stage 12: Data Analysis & Business Intelligence
Do risk analysis / decision modeling	Stage 13: Risk Analysis & Decision Science
Manage implementation / change management	Stage 14: Implementation & Change Management
Establish BA workflow / weekly rhythm	BA Workflow System
Understand BA competency model / career path

---

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.

Dimension	Business Analyst (BA)	Product Manager (PM)	Strategy Consultant	Data Analyst (DA)
Core Question	"What should we do? Why?"	"How to build the product? How to make it great?"	"Where should the company go?"	"What does the data tell us?"
Time Perspective	Present → Future (bridging)	Present (execution)	Future 3-5 years (foresight)	Past → Present (diagnosis)
Deliverables	BRD / Business Case / Requirements Spec	PRD / Prototypes / Product Plans	Strategy Reports / Industry Research	Dashboards / Analysis Reports
Decision Type	Recommend	Decide	Advise	Inform
Beneficiaries	Business sponsors / Investment decision-makers	Dev team / Users	Board / CEO	Business operations teams
Skill Emphasis	Analysis + Communication + Structured thinking	Design + Tech + User research	Research + Modeling + Presentation	Statistics + Programming + Visualization
Output Change Cost	Decision direction (high cost to change)	Feature details (medium cost)	Strategic direction (transformational)	Metric interpretation (re-run)
Success Criteria	Requirements adopted + Solution delivers value	Product launched + User satisfaction	Strategy approved by board	Data accuracy + Insights adopted

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

Role	Core Responsibility	Serves	Typical Output	Representative Companies
Strategy BA	Industry trend analysis, strategic choice recommendations	Board / CEO	Industry analysis reports, strategy white papers	McKinsey / BCG / Huawei Strategy Dept
Business BA	Business requirements analysis, solution design	Business leaders / Departments	BRD / Business requirements documents	IT departments across all enterprises
Technical BA	Translating business requirements into technical solutions	Tech teams / Architects	FRD / System requirements specifications	IT consulting firms
Data BA	Data analysis, business diagnostics, BI	Operations / Management	Analysis reports, BI dashboards	Alibaba / ByteDance / Meituan
Process BA	Process diagnostics, business process reengineering (BPR)	Operations / Compliance	BPMN models, process optimization plans	Big Four / Deloitte
Digital Transformation BA	Digital product analysis, transformation planning	CIO / CDO	Digital roadmaps, feasibility assessments	Accenture / Infosys
Product BA	Product requirements analysis, competitive analysis	PM / Product teams	Product analysis reports, requirements matrices	SaaS companies / Internet
Enterprise BA	Enterprise-level architecture analysis, change management	C-suite / EA teams	Enterprise architecture analysis, change plans	Large enterprise IT departments

Chinese Enterprise BA Role Characteristics

Enterprise	BA Positioning	Signature Methods	Key Characteristics
Huawei	Strategy → Product full-process BA	BLM + DSTE + IPD	Iron triangle from strategy to execution
Alibaba	Data-driven business BA	Data+AI Platform (formerly "Data Middle Platform"; label updated 2026-07) + OneData + Full-domain analysis	Everything speaks with data
Tencent	User research-centered BA	CEG User Research + CSIG Industry Analysis	User orientation + Industry insight
ByteDance	A/B experiment-driven growth BA	Data-driven + A/B Platform + OKR	Super execution + Data culture
Meituan	Business analysis + Operations optimization BA	Data system + Business dashboards + Strategy analysis	Fine-grained operations DNA

Global Enterprise BA Role Characteristics

Enterprise	Region	BA Positioning	Signature Methods	Key Characteristics
Amazon	US/Global	Data-driven product BA	Working Backwards + PR/FAQ + 6-Pager	Customer obsession + Written culture
Google	US/Global	Engineering-aligned BA	OKR + Data Studio + HEART Framework	Metrics-driven + User-centric
Netflix	US/Global	Culture & analytics BA	Freedom & Responsibility + A/B Testing	High autonomy + Data-informed
Spotify	EU/Global	Agile product BA	Squad Model + Bets Framework	Autonomous teams + Outcome-focused
Siemens	EU/Global	Industrial BA	Digital Twin + Industry 4.0 frameworks	Domain expertise + Digital transformation
HSBC	UK/Global	Regulatory & risk BA	Compliance-first + Risk analytics	Regulatory rigor + Global standards
Rakuten	Japan/APAC	Platform ecosystem BA	Ecosystem strategy + Marketplace analytics	Platform thinking + Cross-border
Grab	SEA/APAC	Super-app BA	Multi-vertical analytics + Localization	Hyper-local + Super-app strategy
Nubank	LATAM	Fintech growth BA	Data-driven credit + Growth analytics	Financial inclusion + Digital-first
MTN Group	Africa	Telecom & mobile money BA	Mobile-first + Financial inclusion analytics	Infrastructure-led + Leapfrog innovation

---

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

Knowledge Area	Core Tasks	Key Outputs	% of BA Workload
Business Analysis Planning & Monitoring (BAPM)	5	BA approach, stakeholder engagement plan, governance approach	10-15%
Elicitation & Collaboration	5	Elicitation activity plan, elicitation results, confirmed requirements	20-25%
Requirements Life Cycle Management (R LCM)	5	Requirements traceability matrix, requirements priorities, change impact assessments	10-15%
Strategy Analysis	5	Current state analysis, future state definition, risk analysis, change strategy	10-15%
Requirements Analysis & Design Definition (RADD)	5	Requirements specifications, design definitions, requirements validation	25-30%
Solution Evaluation	5	Solution metrics, organizational readiness assessment, solution performance analysis	10-15%

Five Perspectives (BABOK Perspectives)

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

Perspective	Core Focus	BA Role Shift	Typical Outputs
Agile	Rapid iteration, continuous delivery, collaboration-first	From document-driven to collaboration-driven, embedded in dev team	User stories, acceptance criteria, backlog
Business Intelligence (BI)	Data-driven decisions, analytics capability building	Data requirements analysis, information consumption pattern design	Data requirements docs, report/dashboard specs
Business Process Management (BPM)	Process modeling, optimization, automation	Process analyst, end-to-end process owner	As-Is/To-Be process flows, process KPIs
Business Architecture	Strategy → Execution alignment	Capability modeling, value stream mapping	Capability maps, value stream maps, information concept models
Information Technology (IT)	Systems analysis & design	Technical BA, bridging business and IT	Functional specs, interface requirements, data models

SFIA v9 Skills Mapping

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

SFIA Skill	Corresponding BABOK Area	Level 1-7 Description
Business Analysis (BUAN)	BAPM + Strategy Analysis	L1: Assist analysis → L7: Set organizational BA strategy
Requirements Definition & Management (REQM)	R LCM + RADD	L1: Document requirements → L7: Set requirements management strategy
Business Process Improvement (BPRE)	BPM Perspective	L1: Assist process documentation → L7: Organizational process transformation
Stakeholder Relationship Management (RLMT)	Elicitation & Collaboration	L1: Identify stakeholders → L7: Strategic stakeholder management

---

BABOK Agile Extension (Agile Extension v2)

BA Role Transformation in Agile Environments

Traditional BA	Agile BA
Complete upfront requirements documentation	Continuous conversation, Just-in-time requirements
Document-driven	Collaboration-driven
BA as intermediary	BA embedded in team
Sign-off confirmation	Continuous confirmation
Big Design Up Front	Emergent design

Agile BA Seven Principles

Principle	Meaning	Practical Application
See the Whole	Understand end-to-end business context	Use Story Maps to connect strategy and details
Think as a Customer	Think from the user's perspective	Customer journey maps, personas, experience metrics
Analyze to Determine What is Valuable	Focus on value, not output	Impact Mapping to derive requirements from goals
Get Real Using Examples	Use specification by example	Specification by Example, Gherkin scenarios
Understand What is Doable	Understand technical feasibility	Three Amigos collaboration (BA + Dev + QA)
Stimulate Collaboration and Continuous Improvement	Foster collaboration and improvement	Retrospectives, communities of practice
Avoid Waste	Eliminate waste	Minimum viable requirements, don't over-analyze

---

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 →

Level	Granularity	Example (Online Store)
Activities	User's high-level goals	Browse products, Place order, Pay, Receive goods
Steps	Sequential steps to complete an activity	Search → Filter → View details → Add to cart
Details	Deliverable user stories	"As a buyer, I want to filter by price range"

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

Tool	Focus	Output	When to Use
User Story Map	System functionality and development priorities	Product Backlog	Planning what features to build
Customer Journey Map	User experience and emotional changes	Pain points and opportunity insights	Understanding how users use it

---

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

Principle	Description
Collaborative Specification	BA + Dev + QA jointly define acceptance criteria, eliminating understanding gaps
Specification by Example	Use concrete examples instead of abstract descriptions — "For example...", "What if..."
Living Documentation	Acceptance tests are auto-executable, documentation always stays in sync with actual behavior

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 "[e-mail]"
    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 "[e-mail]"
    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

Tool	Language	Use Case
Cucumber	Ruby/Java/JS	Cross-functional team collaboration
SpecFlow	.NET/C#	.NET ecosystem
Behave	Python	Python projects
JBehave	Java	Java projects

---

Event Storming

Workshop Three Levels

Level	Goal	Output	Duration
Big Picture	Build domain-wide awareness	End-to-end business process panorama	2-4 hours
Process Level	Identify core processes and boundaries	Bounded context candidates	4-8 hours
Design Level	Detailed design and implementation planning	Aggregates, entities, value objects	8-16 hours

Six Core Elements

Element	Color	Description
Domain Event	Orange	"Order Placed", "Payment Confirmed", "Goods Shipped"
Command	Blue	"Submit Order", "Confirm Payment"
Aggregate	Yellow	Core entity receiving commands and producing events
Policy	Purple	Rules automatically executed when events trigger
Read Model	Green	Data views optimized for queries
External System	Pink	Payment gateways, logistics systems, etc.

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

BA Stage	AI Enhancement	Tool Examples
Requirements Elicitation	Auto interview transcription, NLP key requirement extraction, sentiment analysis	Meeting recording + LLM summarization
Requirements Analysis	Auto-detect requirement conflicts, completeness checks, correlation analysis	LLM-assisted MECE decomposition
Requirements Specification	Auto-generate user stories, Gherkin scenario suggestions	Epic → Story → AC auto-splitting
Requirements Validation	Acceptance criteria consistency checks, test case generation	Given-When-Then auto-generation
Change Management	Auto change impact analysis, dependency visualization	Traceability matrix auto-update
Data Analysis	Natural language queries, auto insight generation, anomaly detection	Text-to-SQL + AI visualization

---

MoSCoW Prioritization + Kano Model Deep Dive

MoSCoW Four Priority Levels

Level	Meaning	Recommended %	Consequence of Not Delivering
Must Have	Must have, otherwise project fails	≤60%	System unusable / Project failure
Should Have	Should have, important but not fatal	≤20%	Severely impacts experience but workaround possible
Could Have	Could have, nice to have	≤15%	Minor impact on experience
Won't Have	Won't do this time	Explicitly excluded	No impact

Kano Model Better-Worse Coefficients

Requirement Type	Better Coefficient	Worse Coefficient	Strategy
Attractive	>0.5	-0.3~0	Prioritize: Low cost, high delight
One-dimensional	0.3~0.5	-0.6~-0.3	Must do: Linear correlation with satisfaction
Must-be	<0.3	<-0.6	Basic must-do: Dissatisfaction if absent
Indifferent	≈0	≈0	Don't do
Reverse	<0	>0	Absolutely don't do

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

13.4 AI Governance & Compliance BA Checklist (GDPR / EU AI Act)

As generative AI / Agents enter the analysis production chain, BAs must embed data-compliance and AI-governance constraints at the requirements & design stage. The following is the international compliance baseline (as of 2026-07, subject to current regulations).

Regulatory Baseline (International)

• GDPR (EU 2016/679, in force 2018): lawful basis & consent, data minimization, sensitive-data safeguards, cross-border transfer (SCC / adequacy), right to explanation for automated decisions (Art. 22).
• EU AI Act (Regulation 2024/1689): risk-based tiering — Unacceptable / High / Limited / Minimal; high-risk AI (e.g., hiring, credit scoring, critical infrastructure) requires risk management, data governance, human oversight, conformity assessment, and registration in the EU database. Phased obligations from 2025–2027.
• US: sectoral + state laws (e.g., Colorado AI Act, EU-US Data Privacy Framework for transfers); no single federal AI statute yet.
• Other regions: UK pro-innovation approach; Canada AIDA; China PIPL/AI measures (see domestic edition).

BA Compliance Checklist (mandatory at requirements stage)

#	Check	Risk	Land in NFR
1	Is personal/sensitive data minimized & lawful?	Over-collection, cross-border breach	NFR-Privacy: consent, minimization, SCC
2	AI system risk tier (EU AI Act)?	Blocked launch if High-risk gaps	NFR-Compliance: tier, conformity, registration
3	Automated decisions explainable & contestable?	Art. 22 / user-rights disputes	NFR-Explainability: decision log, appeal path
4	Training/analytics data licensed & governed?	Infringement, leakage	NFR-Security: encryption, access control, audit
5	AI output identifiable / traceable?	Regulatory penalty, misinformation	NFR-Compliance: labeling, watermark, human review

Non-Functional Requirements (NFR) Template (BA deliverable)

NFR-ID | Category(Perf/Security/Privacy/Compliance/Scalability/Usability) | Description | Acceptance | Priority
NFR-01 | Privacy     | PII masked before storage              | 100% sampled masked | Must
NFR-02 | Security     | Full audit log ≥180 days               | Traceable           | Must
NFR-03 | Compliance   | AI output carries explicit label       | 100% compliant      | Must
NFR-04 | Performance  | Dashboard first-load ≤3s (1M rows)     | Load-test pass      | Should

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

Day	Activity	Tools / Methods
Monday	Project Status Review + Weekly Planning	Project Dashboard
Tuesday	Deep Analysis Work (Data / Process / Solution)	Excel / Process Tools / BPMN
Wednesday	Stakeholder Communication (1-on-1 Interviews / Workshops)	Interview Templates / Miro / Whiteboard
Thursday	Documentation (BRD / Requirements / Business Case Writing)	Word / Confluence / Notion
Friday	Team Alignment + Knowledge Capture + Next Week Prep	Team Meeting / Retrospective

BA Project Types & Process Adaptation

Project Type	BA Focus	Key Differences
Traditional Waterfall	Heavy upfront analysis: BRD → FRD → TRD	Document-driven, high change cost
Agile	Continuous analysis: User Stories → Sprint → Review	Iterative, BA embedded in Scrum team
Hybrid	Strategy phase waterfall + Delivery phase agile	Fixed direction, flexible execution
Digital Transformation	Strategy BA + Process BA + Technical BA combo	Multi-BA collaboration, change management is core
AI/Data Projects	Data BA primary: Data requirements → Model requirements → Evaluation	New skills: Model thinking + Evaluation + AI ethics

---

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

Level	Experience	Certification	Core Competencies	Typical Annual Salary (China)	Typical Annual Salary (US)	Typical Annual Salary (UK)	Typical Annual Salary (EU)
Junior BA	0-2 yrs	ECBA / Foundation	Requirements recording, interviewing, documentation	¥150K-250K	$55K-75K	£28K-40K	€35K-50K
Mid BA	2-5 yrs	CCBA	Independent requirements analysis, process modeling, stakeholder mgmt	¥250K-400K	$75K-100K	£40K-55K	€50K-70K
Senior BA	5-8 yrs	CBAP	Business case, solution evaluation, change management	¥400K-650K	$100K-130K	£55K-75K	€70K-90K
Lead BA	8-12 yrs	CBAP + MBA	BA system building, large program BA Lead	¥600K-1M	$130K-160K	£75K-95K	€90K-120K
BA Director	12+ yrs	CBAP/CBDA	BA Center of Excellence, methodology, BA team management	¥800K-1.5M+	$160K-200K+	£95K-130K+	€120K-160K+

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

Certification	Issuing Body	Requirements	Exam Level	Best For
ECBA	IIBA	No experience required, 21h training	Foundation	Entry-level
CCBA	IIBA	3,750h BA experience	Intermediate	3-5 years
CBAP	IIBA	7,500h BA experience	Advanced	5+ years
CBDA	IIBA	Data analytics BA	Specialist	Data track
PMI-PBA	PMI	4,500h BA experience	Advanced	Project environment
AAC	IIBA	Agile BA	Agile	Agile teams
BCS BA	BCS	4-level certification system	Graded	UK/Europe
CPRE FL	IREB	Requirements engineering foundation	Foundation	DACH/Europe
CPRE AL	IREB	Advanced requirements engineering	Advanced	Senior RE

---

Document Factory

BA Professional Document System

Document	Audience	Purpose	Detailed Template
BRD (Business Requirements Document)	Decision-makers / Sponsors	Why do it? What's the value?	references/templates/brd-template.md
Business Case	Investment Decision Committee	Should we invest? How much?	references/templates/business-case-template.md
Competitive Analysis Report	Product / Strategy / Marketing	What are competitors doing? How do we respond?	references/templates/competitive-analysis-template.md
Market Analysis Report	Management / Investors	How big is the market? Where are we?	references/templates/market-analysis-template.md
Financial Analysis Report	Finance / Investors	Is the business financially healthy? What's it worth?	references/templates/financial-analysis-template.md
Stakeholder Analysis	Project Manager / Sponsor	Who influences? Who is affected?	references/templates/stakeholder-analysis-template.md
Process Analysis Report	Operations / IT / Process Owner	How is it done now? How to improve?	references/templates/process-analysis-template.md
Requirements Specification	Tech Team / Vendors	What specifically needs to be done?	references/templates/requirements-spec-template.md

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

#	Diagram	Tool	Purpose
1	PESTLE/NEST Analysis Diagram	drawio-skill	Macro environment one-page display
2	Porter's Five Forces Diagram	drawio-skill	Industry competitive structure
3	Strategic Group Map	drawio-skill / excalidraw	Competitive landscape positioning
4	Industry Lifecycle Curve	excalidraw-diagram	Industry stage + strategic focus
5	Market Segmentation Map	drawio-skill	Market segments by dimension
6	Business Model Canvas (BMC)	excalidraw-diagram	9-module business model
7	Value Curve Diagram	excalidraw-diagram	Blue Ocean strategy competitive factor comparison
8	Power-Interest Grid	drawio-skill	Stakeholder management strategy
9	BPMN Process Flow	drawio-skill	Business process modeling
10	Value Stream Map	drawio-skill	Value-added / non-value-added analysis
11	Decision Tree	drawio-skill	Decision-making under uncertainty
12	DuPont Analysis Diagram	excalidraw-diagram	ROE driver decomposition
13	Risk Heat Map	excalidraw-diagram	Risk likelihood × impact visualization
14	Implementation Roadmap	drawio-skill	Milestones + Dependencies + Resources
15	Org Chart Analysis Diagram	drawio-skill	Decision chain + Communication paths

---

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

#	Anti-Pattern	Correct Approach
1	Skipping industry analysis and jumping to solutions — "We need XX system"	First ask "Why? What are the key success factors in this industry?"
2	PESTLE becomes a checklist exercise — 6 paragraphs of description with zero insight	Every paragraph must include "What is the impact on our side?"
3	Market size gut-feeling — "This market must be hundreds of billions"	Use at least 2 methods to verify (Top-down + Bottom-up)
4	Competitive analysis only looks at product features — ignores strategy/capability/business model	12-dimension comprehensive analysis (Strategy + Product + Model + Operations + Market)
5	SWOT only lists, doesn't convert — 4 lists but no strategy	Must convert to SO/WO/ST/WT strategies

Financial Analysis

#	Anti-Pattern	Correct Approach
6	NPV calculation only runs base case — one number and ready to recommend	Run at least 3 scenarios (Optimistic / Base / Pessimistic)
7	Only calculate returns, no risk adjustment — looks beautiful but unhedged	Risk-adjusted NPV, sensitivity analysis to find "fatal assumption"
8	Only compare TCO when evaluating options — pick the cheapest	Weighted scoring considering value / risk / strategy / organizational fit
9	ROI analysis has no non-financial dimensions — only talks money	Risk reduction / Strategic options / Compliance / Brand value
10	Ignore Do Nothing option — no baseline comparison	Do Nothing is always an option, quantify its cost

Requirements Analysis

#	Anti-Pattern	Correct Approach
11	Write whatever the user says — recorder, not analyst	Ask "why" until root cause (5 Whys)
12	Only listen to the loudest user — ignore the silent majority	Multi-source cross-validation, focus on user behavior not words
13	Requirements document reads like a novel — nobody has time to finish	Structured + Visualized + Layered (5-min version / 30-min version / Detailed version)
14	Requirements are untestable — "System must be fast"	100% requirements quantifiable for acceptance: "Response time <1s (P95)"
15	Ignore non-functional requirements — only write functional	At least 5 dimensions: Performance / Security / Usability / Scalability / Compliance

Communication & Management

#	Anti-Pattern	Correct Approach
16	Don't deliver bad news — only report good news	Honestly communicate risks, propose mitigation plans
17	Overuse jargon — appears professional but actually alienating	Use business language, jargon only when necessary
18	Didn't identify the real decision-maker — spent too much time on non-deciders	Power-Interest grid to identify the real decision-maker
19	Solution has no alternatives — "This is the only option"	At least 2-3 options for decision-makers to choose from
20	Ignore opponents — only focus on supporters	Proactively engage opponents, understand concerns, resolve early

Implementation

#	Anti-Pattern	Correct Approach
21	Solution delivered = done — don't track implementation results	Post-Implementation Review
22	Ignore change management — only focus on system go-live	Four dimensions: System + Process + People + Culture
23	No "Day 1" plan — launched but not ready	Hour-by-hour plan for the week before launch + Contingency plan
24	Don't do lessons learned — mistakes wasted	Formal retrospective at project closure + Knowledge capture
25	BA becomes an order-taker — does whatever the business says	Maintain analytical independence, dare to say "no" and propose better solutions

---

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

Tool	Purpose	Proficiency Level
Excel / Google Sheets	Pivot tables / Financial modeling / What-if analysis	⭐⭐⭐⭐⭐ (Must master)
SQL	Data extraction & analysis	⭐⭐⭐⭐
Python (Rapid)	Data cleaning / Automated analysis	⭐⭐⭐
Tableau / Power BI	Visualization dashboards	⭐⭐⭐
SPSS / SAS	Advanced statistical analysis	⭐⭐

Modeling Tools

Tool	Purpose
draw.io / Visio	BPMN process flows / Architecture diagrams
Miro / MURAL	Online whiteboard / Workshops / Journey maps
Lucidchart	Flowcharts / Org charts
Enterprise Architect	Enterprise architecture / UML
ARIS / Signavio	Professional BPM/BPR process tools
Figma / FigJam	UI/UX prototyping + Collaborative whiteboarding

Documentation & Collaboration

Tool	Purpose
Confluence / Notion	BA knowledge base / Requirements docs
Jira / Azure DevOps	Requirements management / Tracking
SharePoint	Document sharing / Version management
Teams / Slack / Feishu / DingTalk	Communication / Collaboration
Slido / Mentimeter	Workshop interaction / Voting

---

Tool Integration Summary

Task	Primary Tool	Alternative
Draw business process flows (BPMN)	drawio-skill	drawio-coderknock
Draw strategy diagrams / model diagrams	excalidraw-diagram	-
Create business presentation PPT	ppt-generator	ppt-master
Write business documents / reports	Direct Markdown generation	word-docx
Financial modeling / Data analysis	xlsx	-
Draw org charts / relationship diagrams	drawio-generator-pro	-

---

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

Version	Date	Changes
V1.2.0-intl	2026-07-07	Routine iteration upgrade: added AI frontier paradigms, refreshed time-sensitive data, corrected broken references. Added AI Governance & Compliance BA Checklist (GDPR/EU AI Act risk-tiering + NFR template); NEST "Web3"→"Agents/Generative AI"; Alibaba "Data Middle Platform"→"Data+AI Platform"; toolkit mapping synced to real skill names; front-matter cleaned for international consistency
V1.1.0-intl	2026-06-16	International Edition: Full English translation. Added global BA certification landscape (IIBA ECBA/CCBA/CBAP/CBDA, PMI-PBA, BCS BA, IREB CPRE), global salary benchmarks by region (US/UK/EU/China/APAC/Middle East/LATAM/Africa), international BA methodology comparison (BABOK vs PMI-PBA vs BCS vs IREB), IIBA BA Competency Model, global BA role evolution, global BA industry distribution by region, international BA tool ecosystem (Jira, Lucidchart, Figma, Tableau, Power BI), global BA communities and conferences, regional BA practice differences (US/EU/UK/APAC/Middle East/LATAM/Africa), global enterprise BA role characteristics (Amazon/Google/Netflix/Spotify/Siemens/HSBC/Rakuten/Grab/Nubank/MTN).
V1.1.0	2026-06-16	Deep upgrade: Added BABOK v3.0 six Knowledge Areas deep dive (30 tasks + five perspectives + SFIA v9 skills mapping), BABOK Agile Extension (BA role transformation in Agile + Agile BA seven principles), User Story Mapping (three-level structure + MVP slicing + Customer Journey Map complementarity), Impact Mapping (Why→Who→How→What four-layer structure + Story Map synergy), Specification by Example + BDD (Three Amigos collaboration + Gherkin syntax + tool selection), Event Storming (Big Picture→Process→Design three levels + six core elements + DDD synergy), AI-assisted BA full process (NLP requirements elicitation → auto-splitting → acceptance criteria generation → change impact analysis), MoSCoW + Kano deep dive (Better-Worse coefficient calculation + priority matrix), Requirements management full lifecycle (five-stage model + RTM template + change control process). Unified copyright notice + disclaimer. Based on four rounds of deep research (IIBA BABOK/Agile Extension/Gojko Adzic/Alberto Brandolini and other authoritative sources).
V1.0	2026-06-02	Initial version, covering 14 stages + 100+ frameworks + 50+ deliverables + 8 BA roles

---

Copyright Notice

Author: yinjianheng (殷健恒) Contact: email: [e-mail] / wechat: YJH-yinjianheng License: Free and open source, for personal use only

---

Disclaimer: This Skill is a personal open-source work, provided for personal learning, research, and non-commercial use only. Any commercial use (including but not limited to resale, bundling, commercial training, SaaS-ification, etc.) is strictly prohibited without the author's written authorization. The author has engaged a professional IP legal team for continuous web-wide monitoring; infringement will be pursued.

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

Data source: Compiled from official exam handbooks and public pricing pages of IIBA / PMI / BCS / IREB; fees and question formats are observed values as of 2026-07; actual figures are subject to each certifying body's official announcements (fees vary by membership, region, and exchange rate).

Certification	Issuing Body	Region Strength	Experience Required	Exam Format	Cost (USD)	Renewal	Best For
ECBA	IIBA	Global	None (21 PD hours)	50 MCQs, 60 min	$110-$235	3 years	Career starters
CCBA	IIBA	Global	3,750 hours	130 MCQs, 3 hrs	$325-$450	3 years	Mid-career BAs
CBAP	IIBA	Global	7,500 hours	120 MCQs, 3.5 hrs	$350-$575	3 years	Senior BAs
CBDA	IIBA	Global	None specified	75 MCQs, 2 hrs	$250-$400	3 years	Data-focused BAs
AAC	IIBA	Global	None specified	85 MCQs, 2 hrs	$250-$400	3 years	Agile BAs
PMI-PBA	PMI	Global (US strong)	4,500 hours + 35 PD hours	200 MCQs, 4 hrs	$405-$555	3 years	Project-based BAs
BCS Foundation	BCS	UK/Commonwealth	None	40 MCQs, 60 min	£192-£240	None	UK entry-level
BCS Practitioner	BCS	UK/Commonwealth	Foundation + 1 year	Written + Oral	£480-£600	None	UK mid-level
BCS Professional	BCS	UK/Commonwealth	Practitioner + 3 years	Portfolio + Interview	£1,200-£1,500	None	UK senior
CPRE FL	IREB	DACH/Europe	None	45 MCQs, 75 min	€150-€250	None	RE specialists
CPRE AL	IREB

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)

Data source: Compiled from IIBA global salary surveys, Robert Half / Harvey Nash salary guides, and public data from Glassdoor / Levels.fyi / Payscale / regional statistics bureaus; data collection point: as of 2026-07, market observations rather than official salary scales; actual figures subject to employer offers and live market conditions (affected by inflation, exchange rates, and industry fluctuations).

Level	US	UK	Germany	France	Netherlands	UAE	Singapore	Japan	Australia	India	Brazil
Junior BA	$55K-75K	$35K-50K	$40K-55K	$35K-48K	$38K-52K	$30K-45K	$35K-50K	$35K-50K	$50K-70K	$8K-18K	$12K-22K
Mid BA	$75K-100K	$50K-70K	$55K-75K	$48K-65K	$52K-72K	$45K-65K	$50K-70K	$50K-70K	$70K-95K	$18K-35K	$22K-38K
Senior BA	$100K-130K	$70K-95K	$75K-100K	$65K-85K	$72K-95K	$65K-90K	$70K-95K	$70K-90K	$95K-130K	$35K-55K	$38K-55K
Lead BA	$130K-160K	$95K-120K	$100K-130K	$85K-110K	$95K-120K	$90K-120K	$95K-130K	$90K-120K	$130K-160K	$55K-80K	$55K-75K
BA Director	$160K-200K+	$120K-160K+	$130K-170K+	$110K-140K+	$120K-150K+	$120K-160K+	$130K-170K+	$120K-150K+	$160K-200K+	$80K-120K+	$75K-100K+

Regional BA Salary Premium Factors

Factor	Premium	Regions Where Most Relevant
CBAP Certification	+10-20%	US, Canada, Australia, Middle East
MBA Degree	+15-25%	US, UK, India, Singapore
Domain Expertise (Finance)	+15-30%	New York, London, Hong Kong, Singapore
Domain Expertise (Healthcare)	+10-20%	US, UK, Germany
Tech Industry	+20-35%	Silicon Valley, Seattle, Bangalore, Dublin
Consulting (MBB/Big 4)	+25-40%	All major markets
Language Skills (Bilingual)	+5-15%	Switzerland, Singapore, UAE, Canada
Security Clearance	+10-20%	US, UK, Australia

---

International BA Methodology Comparison

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

Dimension	IIBA BABOK V3	PMI-PBA	BCS Business Analysis	IREB CPRE
Origin	Global (IIBA, founded in Canada)	US (PMI)	UK (BCS, The Chartered Institute for IT)	DACH (IREB, Germany)
Primary Focus	Enterprise + Project BA	Project-based BA	Modular BA competence	Requirements Engineering
Knowledge Areas	6 KAs, 30 tasks, 50 techniques	5 Process Domains	4 Competency Levels	3 Certification Levels
Philosophy	Comprehensive BA body of knowledge	BA within project management context	Competence-based, modular	Scientific RE discipline
Perspectives	Agile, BI, BPM, Business Architecture, IT	Project lifecycle phases	Agile, AI, Digital	Elicitation, Documentation, Validation, Management
Best For	Holistic BA practice	PMO/Project environments	UK/European structured career	Requirements engineering specialists
Geographic Strength	North America, Australia, Middle East, Asia	US, Canada, global PMOs	UK, Commonwealth, Europe	Germany, Austria, Switzerland, Netherlands
Recognition	Most widely recognized globally	Strong in PM circles	UK government standard	EU standards body aligned
Agile Coverage	Dedicated Agile Extension v2	Agile-compatible	Strong Agile BA module	Agile RE module
AI/Data Coverage	CBDA certification	Limited	Emerging AI for BA	Limited
Annual Exams	~50,000+ globally	~5,000+	~10,000+	~15,000+

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

Competency Area	Junior BA	Mid BA	Senior BA	Lead BA
Analytical Thinking	Apply basic frameworks	Independently analyze complex problems	Design analytical approaches	Set organizational analytical standards
Business Knowledge	Understand own domain	Cross-domain knowledge	Industry-level insight	Enterprise-level business acumen
Communication	Document requirements	Facilitate workshops	Present to C-suite	Influence organizational strategy
Interaction	Participate in teams	Lead small teams	Manage stakeholder relationships	Build BA communities of practice
Tools & Technology	Use basic tools	Configure tools for team	Evaluate and select tools	Define organizational tool strategy

---

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

---