Business Analysis Skill
Patterns for requirements elicitation, BRDs, process analysis, and stakeholder alignment.
Business Analysis Deliverables
| Deliverable |
Purpose |
Audience |
| Business Case |
Justify investment |
Executives, sponsors |
| BRD |
Document requirements |
All stakeholders |
| Functional Spec |
Detail system behavior |
Dev team, testers |
| Use Cases |
Describe user interactions |
Designers, developers |
| Process Maps |
Visualize workflows |
Process owners, analysts |
| Data Dictionary |
Define data elements |
Technical team |
Requirements Hierarchy
Business Requirements (WHY)
└── Stakeholder Requirements (WHO needs WHAT)
└── Solution Requirements
├── Functional (WHAT it does)
└── Non-Functional (HOW WELL it does it)
└── Transition Requirements (HOW we get there)
BRD Structure
Standard Sections
- Executive Summary — One-page overview for executives
- Business Objectives — Measurable goals (SMART)
- Scope — In scope, out of scope, boundaries
- Stakeholders — Who's involved, their interests
- Current State — As-is process, pain points
- Future State — To-be vision, benefits
- Functional Requirements — What the solution must do
- Non-Functional Requirements — Quality attributes
- Assumptions & Constraints — Known limitations
- Dependencies — External factors
- Risks — What could go wrong
- Glossary — Term definitions
Requirements Writing
SMART Criteria
| Letter |
Meaning |
Test |
| S |
Specific |
Is it clear what's needed? |
| M |
Measurable |
Can we verify it's done? |
| A |
Achievable |
Is it realistic? |
| R |
Relevant |
Does it support objectives? |
| T |
Time-bound |
Is there a deadline? |
Good vs. Bad Requirements
| Bad |
Problem |
Better |
| "System should be fast" |
Not measurable |
"Page load < 2 seconds" |
| "Easy to use" |
Subjective |
"Complete task in < 3 clicks" |
| "Handle all cases" |
Unbounded |
"Support cases A, B, C" |
| "Similar to competitor" |
Vague |
"[Specific features listed]" |
| "Should probably..." |
Uncertain |
"Must" or "Should" (MoSCoW) |
Requirement Attributes
| Attribute |
Purpose |
| ID |
Unique identifier (REQ-001) |
| Description |
What is required |
| Priority |
MoSCoW or numeric |
| Source |
Who requested it |
| Rationale |
Why it's needed |
| Acceptance Criteria |
How to verify |
| Dependencies |
Related requirements |
| Status |
Draft/Approved/Implemented |
Elicitation Techniques
Technique Selection
| Technique |
Best For |
Effort |
| Interviews |
Deep understanding, complex topics |
High |
| Workshops |
Consensus, group decisions |
Medium |
| Surveys |
Broad input, quantitative data |
Low |
| Observation |
Understanding real workflows |
High |
| Document Analysis |
Existing systems, regulations |
Low |
| Prototyping |
Validating concepts, UI |
Medium |
| Focus Groups |
User perspectives, reactions |
Medium |
Interview Best Practices
- Prepare questions in advance
- Start broad, then specific
- Use open-ended questions
- Listen more than talk (80/20)
- Probe with "Why?" and "How?"
- Summarize and confirm understanding
- Document immediately after
Workshop Facilitation
| Phase |
Activities |
| Open |
Objectives, agenda, ground rules |
| Diverge |
Brainstorm, generate options |
| Converge |
Prioritize, decide |
| Close |
Summarize, next steps, thank |
Use Case Development
Use Case Template
Use Case: [UC-001] [Name]
Actor: [Primary actor]
Precondition: [What must be true before]
Trigger: [What initiates the use case]
Main Flow:
1. Actor does X
2. System responds with Y
3. ...
Alternative Flows:
2a. If condition, then...
Exception Flows:
2b. If error, then...
Postcondition: [What is true after]
Business Rules: [Applicable rules]
Use Case Levels
| Level |
Scope |
Example |
| Summary |
Multiple sessions |
"Manage Customer Account" |
| User Goal |
One sitting |
"Place Order" |
| Subfunction |
Part of a step |
"Validate Address" |
Process Analysis
Current State Analysis
- Map as-is process (BPMN, swimlane)
- Identify pain points
- Measure current performance
- Find root causes
- Quantify improvement opportunity
Process Mapping Notations
| Notation |
Best For |
| BPMN |
Detailed, technical processes |
| Swimlane |
Cross-functional workflows |
| Value Stream |
Lean analysis |
| SIPOC |
High-level overview |
SIPOC Template
| S |
I |
P |
O |
C |
| Suppliers |
Inputs |
Process |
Outputs |
Customers |
| Who provides? |
What's needed? |
High-level steps |
What's produced? |
Who receives? |
Gap Analysis
Gap Analysis Framework
Current State → Gap → Future State
│ │ │
▼ ▼ ▼
As-Is What needs To-Be
Process to change Vision
Gap Categories
| Type |
Examples |
| Process |
Missing steps, manual work |
| Technology |
System limitations |
| People |
Skills, capacity |
| Data |
Quality, availability |
| Policy |
Rules, compliance |
Acceptance Criteria
Gherkin Format
Given [precondition]
When [action]
Then [expected result]
And [additional result]
Acceptance Criteria Checklist
Traceability
Traceability Matrix
| Req ID |
Business Objective |
Design |
Test Case |
Status |
| REQ-001 |
OBJ-01 |
DES-005 |
TC-012 |
Passed |
Traceability Benefits
- Ensure all requirements implemented
- Impact analysis for changes
- Test coverage verification
- Audit compliance evidence
Prioritization Techniques
MoSCoW
| Priority |
Meaning |
Guidance |
| Must |
Critical for success |
~60% of effort |
| Should |
Important, not critical |
~20% of effort |
| Could |
Nice to have |
~20% of effort |
| Won't |
Out of scope (this release) |
Documented |
Value vs. Effort Matrix
High Value │ Quick Wins │ Major Projects │
│ (Do first) │ (Plan carefully)│
Low Value │ Fill-ins │ Avoid │
│ (If time) │ (Don't do) │
└────────────┴─────────────────┘
Low Effort High Effort
Kano Model
| Type |
If Present |
If Absent |
| Basic |
Expected, no delight |
Dissatisfied |
| Performance |
More is better |
Less is worse |
| Delighter |
Unexpected joy |
Not missed |
Common BA Pitfalls
| Pitfall |
Prevention |
| Solution jumping |
Ask "why" before "how" |
| Missing stakeholders |
Stakeholder analysis early |
| Gold plating |
Tie everything to objectives |
| Assumption blindness |
Document and validate assumptions |
| Scope creep |
Change control process |
| Analysis paralysis |
Timeboxed analysis, iterate |
1---2name: business-analysis-43description: Patterns for requirements elicitation, BRDs, process analysis, and stakeholder alignment.4tier: standard5applyTo: '**/*brd*,**/*requirement*,**/*stakeholder*,**/*process*'6currency: 2026-04-227metadata:8 source: https://skillmd.com/skills/fabioc-aloha/business-analysis-49---1011# Business Analysis Skill1213> Patterns for requirements elicitation, BRDs, process analysis, and stakeholder alignment.1415## Business Analysis Deliverables1617| Deliverable | Purpose | Audience |18| ----------- | ------- | -------- |19| **Business Case** | Justify investment | Executives, sponsors |20| **BRD** | Document requirements | All stakeholders |21| **Functional Spec** | Detail system behavior | Dev team, testers |22| **Use Cases** | Describe user interactions | Designers, developers |23| **Process Maps** | Visualize workflows | Process owners, analysts |24| **Data Dictionary** | Define data elements | Technical team |2526## Requirements Hierarchy2728```text29Business Requirements (WHY)30 └── Stakeholder Requirements (WHO needs WHAT)31 └── Solution Requirements32 ├── Functional (WHAT it does)33 └── Non-Functional (HOW WELL it does it)34 └── Transition Requirements (HOW we get there)35```3637## BRD Structure3839### Standard Sections40411. **Executive Summary** — One-page overview for executives422. **Business Objectives** — Measurable goals (SMART)433. **Scope** — In scope, out of scope, boundaries444. **Stakeholders** — Who's involved, their interests455. **Current State** — As-is process, pain points466. **Future State** — To-be vision, benefits477. **Functional Requirements** — What the solution must do488. **Non-Functional Requirements** — Quality attributes499. **Assumptions & Constraints** — Known limitations5010. **Dependencies** — External factors5111. **Risks** — What could go wrong5212. **Glossary** — Term definitions5354### Requirements Writing5556#### SMART Criteria5758| Letter | Meaning | Test |59| ------ | ------- | ---- |60| **S** | Specific | Is it clear what's needed? |61| **M** | Measurable | Can we verify it's done? |62| **A** | Achievable | Is it realistic? |63| **R** | Relevant | Does it support objectives? |64| **T** | Time-bound | Is there a deadline? |6566#### Good vs. Bad Requirements6768| Bad | Problem | Better |69| --- | ------- | ------ |70| "System should be fast" | Not measurable | "Page load < 2 seconds" |71| "Easy to use" | Subjective | "Complete task in < 3 clicks" |72| "Handle all cases" | Unbounded | "Support cases A, B, C" |73| "Similar to competitor" | Vague | "[Specific features listed]" |74| "Should probably..." | Uncertain | "Must" or "Should" (MoSCoW) |7576#### Requirement Attributes7778| Attribute | Purpose |79| --------- | ------- |80| ID | Unique identifier (REQ-001) |81| Description | What is required |82| Priority | MoSCoW or numeric |83| Source | Who requested it |84| Rationale | Why it's needed |85| Acceptance Criteria | How to verify |86| Dependencies | Related requirements |87| Status | Draft/Approved/Implemented |8889## Elicitation Techniques9091### Technique Selection9293| Technique | Best For | Effort |94| --------- | -------- | ------ |95| **Interviews** | Deep understanding, complex topics | High |96| **Workshops** | Consensus, group decisions | Medium |97| **Surveys** | Broad input, quantitative data | Low |98| **Observation** | Understanding real workflows | High |99| **Document Analysis** | Existing systems, regulations | Low |100| **Prototyping** | Validating concepts, UI | Medium |101| **Focus Groups** | User perspectives, reactions | Medium |102103### Interview Best Practices104105- Prepare questions in advance106- Start broad, then specific107- Use open-ended questions108- Listen more than talk (80/20)109- Probe with "Why?" and "How?"110- Summarize and confirm understanding111- Document immediately after112113### Workshop Facilitation114115| Phase | Activities |116| ----- | ---------- |117| **Open** | Objectives, agenda, ground rules |118| **Diverge** | Brainstorm, generate options |119| **Converge** | Prioritize, decide |120| **Close** | Summarize, next steps, thank |121122## Use Case Development123124### Use Case Template125126```text127Use Case: [UC-001] [Name]128Actor: [Primary actor]129Precondition: [What must be true before]130Trigger: [What initiates the use case]131132Main Flow:1331. Actor does X1342. System responds with Y1353. ...136137Alternative Flows:1382a. If condition, then...139140Exception Flows:1412b. If error, then...142143Postcondition: [What is true after]144Business Rules: [Applicable rules]145```146147### Use Case Levels148149| Level | Scope | Example |150| ----- | ----- | ------- |151| **Summary** | Multiple sessions | "Manage Customer Account" |152| **User Goal** | One sitting | "Place Order" |153| **Subfunction** | Part of a step | "Validate Address" |154155## Process Analysis156157### Current State Analysis1581591. Map as-is process (BPMN, swimlane)1602. Identify pain points1613. Measure current performance1624. Find root causes1635. Quantify improvement opportunity164165### Process Mapping Notations166167| Notation | Best For |168| -------- | -------- |169| BPMN | Detailed, technical processes |170| Swimlane | Cross-functional workflows |171| Value Stream | Lean analysis |172| SIPOC | High-level overview |173174### SIPOC Template175176| S | I | P | O | C |177| - | - | - | - | - |178| Suppliers | Inputs | Process | Outputs | Customers |179| Who provides? | What's needed? | High-level steps | What's produced? | Who receives? |180181## Gap Analysis182183### Gap Analysis Framework184185```text186Current State → Gap → Future State187 │ │ │188 ▼ ▼ ▼189 As-Is What needs To-Be190 Process to change Vision191```192193### Gap Categories194195| Type | Examples |196| ---- | -------- |197| **Process** | Missing steps, manual work |198| **Technology** | System limitations |199| **People** | Skills, capacity |200| **Data** | Quality, availability |201| **Policy** | Rules, compliance |202203## Acceptance Criteria204205### Gherkin Format206207```gherkin208Given [precondition]209When [action]210Then [expected result]211And [additional result]212```213214### Acceptance Criteria Checklist215216- [ ] Testable — Can write a test case217- [ ] Clear — Unambiguous language218- [ ] Complete — Covers happy path and edges219- [ ] Independent — Doesn't require other criteria220- [ ] Valuable — Ties to user need221222## Traceability223224### Traceability Matrix225226| Req ID | Business Objective | Design | Test Case | Status |227| ------ | ------------------ | ------ | --------- | ------ |228| REQ-001 | OBJ-01 | DES-005 | TC-012 | Passed |229230### Traceability Benefits231232- Ensure all requirements implemented233- Impact analysis for changes234- Test coverage verification235- Audit compliance evidence236237## Prioritization Techniques238239### MoSCoW240241| Priority | Meaning | Guidance |242| -------- | ------- | -------- |243| **Must** | Critical for success | ~60% of effort |244| **Should** | Important, not critical | ~20% of effort |245| **Could** | Nice to have | ~20% of effort |246| **Won't** | Out of scope (this release) | Documented |247248### Value vs. Effort Matrix249250```text251High Value │ Quick Wins │ Major Projects │252 │ (Do first) │ (Plan carefully)│253Low Value │ Fill-ins │ Avoid │254 │ (If time) │ (Don't do) │255 └────────────┴─────────────────┘256 Low Effort High Effort257```258259### Kano Model260261| Type | If Present | If Absent |262| ---- | ---------- | --------- |263| **Basic** | Expected, no delight | Dissatisfied |264| **Performance** | More is better | Less is worse |265| **Delighter** | Unexpected joy | Not missed |266267## Common BA Pitfalls268269| Pitfall | Prevention |270| ------- | ---------- |271| Solution jumping | Ask "why" before "how" |272| Missing stakeholders | Stakeholder analysis early |273| Gold plating | Tie everything to objectives |274| Assumption blindness | Document and validate assumptions |275| Scope creep | Change control process |276| Analysis paralysis | Timeboxed analysis, iterate |