Business Analysis (BA)
From "writing documents" to "writing specs a machine can follow": tight acceptance criteria, edge cases included, passing the Spec Fidelity gate.
Process
Organisation
Who does what, and hands what to whom.
14 functions plus the client, connected by 51 named hand-offs. Each function is a ROLE, not a large department: on small projects one person holds several roles, but the doer (R) is still kept apart from the approver (A) wherever possible.
Hand-offs
Hand-off map between functions
hands off receives external (client)Click a function to see its flow.
Sales & Presales
Understand the client’s need and commit only to what the team can deliver.
Hands off to
- : Intake ticket and call notes
- : Go/no-go recommendation with the scorecard
- : Negotiated commercial terms
- : Committed milestones and client expectations
Receives from
- : Signed contract to share with the client
- : Go/no-go decisions
›Responsibilities, outputs, skills
Responsibilities
- Receive requests and act as the first point of contact
- Qualify opportunities (BANT) and recommend go/no-go
- Write and present proposals, negotiate commercial terms
Outputs
- Intake ticket, call notes
- Qualification scorecard
- Proposal & quote (sent privately)
Skills
- Active listening and open questions
- Understanding cost and high-level estimation
- Writing clear, honest proposals
RACI
Overall RACI matrix
Each cell is the function’s strongest role in that stage (A > R > C > I), merged automatically from each stage’s detailed RACI. Empty: not involved. Click a stage number for the per-activity RACI.
| Function | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sales & Presales | A | A | — | A | R | — | — | — | — | — | — | — | — | — | — | — | — | — | — | C | — |
| Business Analysis (BA) | R | C | A | R | R | A | R | — | — | R | R | C | — | — | A | — | R | R | — | R | — |
| UX/UI Design | — | — | R | C | — | C | A | — | — | C | — | — | — | — | — | — | — | — | — | A | — |
| Solution Architecture | C | A | A | A | R | A | — | A | — | C | — | C | — | — | — | — | — | — | — | C | R |
| Project Management / Scrum Master | I | R | C | A | A | I | I | I | A | A | C | C | — | — | A | A | A | A | A | A | A |
| Engineering (FE · BE · Mobile) | — | C | — | R | — | — | R | R | A | A | R | A | R | C | A | A | R | C | A | R | R |
| Quality Assurance (QA/QC) | — | — | — | C | — | R | C | C | R | — | R | A | R | — | R | R | R | C | R | — | R |
| Application Security (AppSec) | — | C | — | — | C | R | — | A | C | C | C | — | A | C | — | C | C | R | A | — | R |
| DevOps / SRE | — | — | — | — | — | C | — | C | A | — | A | R | A | A | A | A | A | A | A | — | A |
| Infrastructure & Network | — | — | — | — | — | — | — | C | R | — | — | — | R | A | — | — | — | — | — | — | R |
| Data & AI | — | — | R | — | — | — | — | R | — | A | A | — | — | C | R | — | A | — | — | A | A |
| Support & Customer Success | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | C | A | — | A | R | R |
| Legal & Finance | A | A | — | C | A | — | — | — | — | — | — | — | A | — | I | — | — | A | — | — | A |
| Project Management Office (PMO) | — | A | — | A | A | — | — | — | C | — | — | — | — | — | — | — | — | A | — | — | — |
| Client (Product Owner / sponsor) | C | C | A | A | R | A | A | A | C | C | A | I | C | C | A | C | A | R | R | A | A |
Rdoes the workAaccountable, final sign-offCconsulted beforeIinformed after
- Discover (00–02)
- Define (03–05)
- Design (06–07)
- Build (08–10)
- Verify (11–13)
- Ship (14–17)
- Run (18–20)
In the overview a stage can show several A’s because each activity has its own accountable owner; in a stage’s detailed RACI every activity has exactly one A.
Working with AI
The roles stay — their focus shifts
AI drafts faster, so each role’s value moves to specification, evaluation and permission limits. The approver (A) is still a person, not a tool. AI-native delivery
Engineering (FE · BE · Mobile)
Write fewer lines, read more: hand AI work per story, review what it generates carefully, and own everything you approve.
Quality Assurance (QA/QC)
From running tests to owning the evaluation policy: pass / fail criteria, eval sets, and keeping the verdict separate from the tool that wrote or repaired the tests.
DevOps / SRE
Set the limits for AI agents: what they may read, where they may write, which commands they may run; no production write access; an audit trail to trace back.