BA Core Sub-Skill
Parent: faion-business-analyst
Focus: Core BA practices - planning, elicitation, lifecycle management, strategy, evaluation
Context Discovery
Auto-Investigation
| Signal |
Check For |
Why |
.aidocs/ |
Requirements docs, stakeholder lists |
BA artifacts present |
docs/ or requirements/ |
Existing requirement patterns |
Documentation standards |
STAKEHOLDERS.md |
Stakeholder registry |
BA governance exists |
requirements.md |
Requirements format (user stories, use cases) |
Elicitation approach |
Discovery Questions
questions:
- question: "Do you have existing requirements documentation?"
options:
- label: "Yes, user stories (agile)"
description: "Agile BA approach needed"
- label: "Yes, formal requirements docs"
description: "Traditional BA approach needed"
- label: "No documentation yet"
description: "Start with elicitation"
- label: "Mixed/inconsistent"
description: "Requirements lifecycle management needed"
- question: "What's the current state of requirements?"
options:
- label: "Planning phase"
description: "Use ba-planning, stakeholder-analysis"
- label: "Gathering requirements"
description: "Use elicitation-techniques"
- label: "Analyzing/prioritizing"
description: "Use requirements-prioritization"
- label: "Validating/refining"
description: "Use requirements-validation"
- question: "Are you working in an agile or traditional environment?"
options:
- label: "Agile/Scrum"
description: "Apply agile-ba-frameworks"
- label: "Waterfall/traditional"
description: "Apply traditional BA lifecycle"
- label: "Hybrid"
description: "Mix methodologies as needed"
Methodologies (21)
Planning & Governance (2)
- ba-planning.md - Define BA approach and deliverables
- stakeholder-analysis.md - Identify and analyze stakeholders
Elicitation (1)
- elicitation-techniques.md - Interviews, workshops, surveys, observation
Requirements Lifecycle (6)
- requirements-traceability.md - Track requirement relationships
- requirements-lifecycle.md - Manage requirements over time
- requirements-prioritization.md - MoSCoW, RICE, Kano, value/effort
- requirements-documentation.md - Formal requirements documentation
- requirements-validation.md - Validate against business goals
- ba-requirements-mgmt.md - Maintenance, change impact
Strategy Analysis (3)
- strategy-analysis.md - Current/future state, gap analysis
- strategy-basics.md - Risk, change strategy fundamentals
- strategy-methods.md - Solution options, 50 techniques
Solution Evaluation (1)
- solution-assessment.md - Measure, assess, improve
Governance & Support (2)
- ba-governance.md - Governance, communication, prep
- ba-strategic-partnership.md - Innovation leadership
Modern Practices (6)
- agile-ba-frameworks.md - Scrum, scaled agile
- ai-enabled-business-analysis.md - GenAI, agentic AI
- process-mining-automation.md - RPA, automation
- data-driven-requirements.md - Analytics-informed prioritization
- modern-ba-framework.md - BA Framework 2025-2026
- ba-trends-summary.md - Current trends
When to Use
| If you need... |
Methodology |
| Define BA approach |
ba-planning |
| Map stakeholders |
stakeholder-analysis |
| Gather requirements |
elicitation-techniques |
| Track requirement links |
requirements-traceability |
| Prioritize backlog |
requirements-prioritization |
| Manage requirement changes |
requirements-lifecycle |
| Analyze current vs future state |
strategy-analysis |
| Evaluate delivered solution |
solution-assessment |
| Work in agile environment |
agile-ba-frameworks |
| Leverage AI for BA work |
ai-enabled-business-analysis |
BA Core Sub-Skill v1.0
1---2name: faion-ba-core3description: BA Core: Planning, elicitation, requirements lifecycle, strategy analysis, solution evaluation. 21 methodologies.4---5
6# BA Core Sub-Skill
7
8**Parent:** faion-business-analyst
9**Focus:** Core BA practices - planning, elicitation, lifecycle management, strategy, evaluation
10
11---
12
13## Context Discovery
14
15### Auto-Investigation
16
17| Signal | Check For | Why |
18|--------|-----------|-----|
19| `.aidocs/` | Requirements docs, stakeholder lists | BA artifacts present |
20| `docs/` or `requirements/` | Existing requirement patterns | Documentation standards |
21| `STAKEHOLDERS.md` | Stakeholder registry | BA governance exists |
22| `requirements.md` | Requirements format (user stories, use cases) | Elicitation approach |
23
24### Discovery Questions
25
26```yaml
27questions:
28 - question: "Do you have existing requirements documentation?"
29 options:
30 - label: "Yes, user stories (agile)"
31 description: "Agile BA approach needed"
32 - label: "Yes, formal requirements docs"
33 description: "Traditional BA approach needed"
34 - label: "No documentation yet"
35 description: "Start with elicitation"
36 - label: "Mixed/inconsistent"
37 description: "Requirements lifecycle management needed"
38
39 - question: "What's the current state of requirements?"
40 options:
41 - label: "Planning phase"
42 description: "Use ba-planning, stakeholder-analysis"
43 - label: "Gathering requirements"
44 description: "Use elicitation-techniques"
45 - label: "Analyzing/prioritizing"
46 description: "Use requirements-prioritization"
47 - label: "Validating/refining"
48 description: "Use requirements-validation"
49
50 - question: "Are you working in an agile or traditional environment?"
51 options:
52 - label: "Agile/Scrum"
53 description: "Apply agile-ba-frameworks"
54 - label: "Waterfall/traditional"
55 description: "Apply traditional BA lifecycle"
56 - label: "Hybrid"
57 description: "Mix methodologies as needed"
58```
59
60---
61
62## Methodologies (21)
63
64### Planning & Governance (2)
65- ba-planning.md - Define BA approach and deliverables
66- stakeholder-analysis.md - Identify and analyze stakeholders
67
68### Elicitation (1)
69- elicitation-techniques.md - Interviews, workshops, surveys, observation
70
71### Requirements Lifecycle (6)
72- requirements-traceability.md - Track requirement relationships
73- requirements-lifecycle.md - Manage requirements over time
74- requirements-prioritization.md - MoSCoW, RICE, Kano, value/effort
75- requirements-documentation.md - Formal requirements documentation
76- requirements-validation.md - Validate against business goals
77- ba-requirements-mgmt.md - Maintenance, change impact
78
79### Strategy Analysis (3)
80- strategy-analysis.md - Current/future state, gap analysis
81- strategy-basics.md - Risk, change strategy fundamentals
82- strategy-methods.md - Solution options, 50 techniques
83
84### Solution Evaluation (1)
85- solution-assessment.md - Measure, assess, improve
86
87### Governance & Support (2)
88- ba-governance.md - Governance, communication, prep
89- ba-strategic-partnership.md - Innovation leadership
90
91### Modern Practices (6)
92- agile-ba-frameworks.md - Scrum, scaled agile
93- ai-enabled-business-analysis.md - GenAI, agentic AI
94- process-mining-automation.md - RPA, automation
95- data-driven-requirements.md - Analytics-informed prioritization
96- modern-ba-framework.md - BA Framework 2025-2026
97- ba-trends-summary.md - Current trends
98
99---
100
101## When to Use
102
103| If you need... | Methodology |
104|----------------|-------------|
105| Define BA approach | ba-planning |
106| Map stakeholders | stakeholder-analysis |
107| Gather requirements | elicitation-techniques |
108| Track requirement links | requirements-traceability |
109| Prioritize backlog | requirements-prioritization |
110| Manage requirement changes | requirements-lifecycle |
111| Analyze current vs future state | strategy-analysis |
112| Evaluate delivered solution | solution-assessment |
113| Work in agile environment | agile-ba-frameworks |
114| Leverage AI for BA work | ai-enabled-business-analysis |
115
116---
117
118*BA Core Sub-Skill v1.0*
majiayu000