Skill Hub — Business Analysis
Turn ambiguity into structured, actionable requirements.
Skills for eliciting needs, mapping stakeholders, analyzing processes, finding gaps, defining acceptance criteria, and discovering business rules. Usable on enterprise, SAP, and data projects.
What this group covers
Business Analysis skills help you work with ambiguity. They provide structured methods for understanding what stakeholders actually need, how work actually happens, what is missing, and how to verify that a solution is correct.
These skills are cross-domain. They apply to SAP implementations, data governance initiatives, integration projects, process redesign, and operational improvement.
Each skill page includes: a working method, diagnostic questions, decision rules, artifact templates, quality checklists, and specific instructions for AI agents.
When to use this group
- A new project starts and no one has written down what must be true for success.
- Stakeholders give conflicting descriptions of the same process.
- An incident keeps recurring and the fix requires understanding how work actually happens, not just how it is documented.
- A change request arrives without clear scope or verification criteria.
- A system replacement is planned and no one knows which business rules the current system enforces.
- A data quality issue spans multiple departments and ownership is unclear.
- You need to define what "done" means before implementation begins.
Skills in this group
Requirements Elicitation
Turn vague stakeholder complaints into structured requirements with assumptions, constraints, risks, and acceptance criteria.
Stakeholder Analysis
Identify who affects or is affected by a change, what they control, what they need, and how to get reliable information from them.
Process Analysis
Document how work actually happens, where it breaks, what systems touch it, and who owns each step.
Gap Analysis
Compare what exists today against what is required, classify the difference, and produce a closure plan with effort and ownership.
Acceptance Criteria
Define how to verify that a requirement is met, before work starts, so that delivery has an unambiguous pass/fail standard.
Business Rules Discovery
Extract the decision logic that governs how a business operates, document it independently of any system, and identify where current systems enforce, violate, or ignore it.
Recommended path through this group
- Stakeholder Analysis — Know who to talk to.
- Requirements Elicitation — Capture what they need.
- Use Case Analysis — Map actors, goals, and system interactions.
- Business Rules Discovery — Understand the logic behind the needs.
- Process Analysis — Map how work happens today.
- Assumption and Constraint Mapping — Surface what the project rests on.
- Gap Analysis — Find what is missing between today and target.
- Scope Boundary Definition — Lock the perimeter before work begins.
- User Story Refinement — Turn needs into sprint-ready backlog items.
- Acceptance Criteria — Define how to verify the solution.
How this group connects to other skills
- Business Analysis + DAMA / Data = Data requirements, quality rules, and governance ownership.
- Business Analysis + Systems Analysis = Entity behavior, lifecycle states, and interface requirements that drive business process design.
- Business Analysis + Decision & Validation = Requirements that are reviewed, traced, and tested with evidence-based decisions.
- Business Analysis + AI-Assisted Analysis = Requirements elicitation, validation, and backlog creation accelerated by AI with human accountability.
- Business Analysis + Architecture = Capability mapping, non-functional requirements, and solution design inputs.
- Business Analysis + SAP AMS = Incident triage, change impact analysis, and operational knowledge capture.
- Business Analysis + Integration = Interface requirements, data mapping, and error handling rules.
Status and limitations
This is a public working interpretation of business analysis practices. It is not official BABOK, IIBA, or SAP documentation. These skills are designed for practical use on real projects, not for certification study.
Every skill page includes a verification status and limitations section. Use these skills as structured starting points, not as authoritative framework substitutes.