---
name: ba-playbook
description: "What a Business Analyst reaches for in RBA Skills to scope work, run discovery, turn needs into testable stories, and track decisions through delivery."
disciplines:
  - business-analysis
tags:
  - playbook
  - role-guide
  - ba
author:
  name: Kassie Gibbons
  url: https://rba.com
---

# Business Analyst Playbook

BAs translate business needs into clear, testable requirements — the bridge between what clients say they want and what the team builds. Nothing gets built that wasn't asked for; nothing asked for gets missed. This is your RBA Skills toolkit.

## Estimating — size the BA workstream

| Reach for | Why |
|---|---|
| **estimate-sow-builder** → `build-estimate` | BA hours and deliverable breakdown. |
| **estimate-sow-builder** → `draft-sow` | Review or draft the services and work-products section. |

## Envision — structured discovery

| Reach for | Why |
|---|---|
| **envision-toolkit** → `stakeholder-interview-guide` | Structured discovery interviews. |
| **discovery-synthesizer** (`discovery-interview-synthesis`, `requirements-workshop`, `five-whys-root-cause`) | Synthesize interviews, run requirements workshops, dig to root causes. |
| **envision-toolkit** → `project-kickoff-deck` | Contribute to kickoff materials. |

## Create — requirements as testable stories

| Reach for | Why |
|---|---|
| `user-story-writer` skill | Requirements as testable user stories. |
| `uat-test-case-writer` skill | Client-executable test cases derived from acceptance criteria. |
| `jira-azdo-ticket-writer` skill | Push stories into Jira / Azure DevOps. |
| **project-management** → `raid-log-builder` | Log decisions and issues. |
| **project-management** → `rasci-chart-builder` | Clarify who owns what. |

## Deliver — close the loop

| Reach for | Why |
|---|---|
| **project-management** → `project-closure-report` | Contribute lessons learned. |

## BA Tips

- **"So that" is not optional.** Every user story needs a business-value justification. If you can't write it, the story isn't ready.
- **Acceptance criteria = test cases.** Write AC well and UAT writes itself.
- **The RAID log decisions tab is your change control.** Log every significant decision the moment it's made.