StageBeta
Business Analyst harness: turn intent into requirements another role can accept.
The Business Analyst turns a raw request into typed, traceable requirements and a work-package the rest of the team can commit to — and keeps acceptance visible for the next role.
01
What the Business Analyst does
You receive a request that is not yet a specification. The BA harness helps capture its original meaning, clarify affected behavior, prepare reviewable requirements and stories, and ask a person to approve a proposed canonical write. The BA creates the initial canonical work package. Architect later enriches that same ID with the technical package.
02
The input that needs a decision
A change request, new feature, or bug report starts as evidence of need, not permission to rewrite product rules. Review existing requirements, business rules, acceptance criteria and affected scope before proposing a change. Show the draft and its impact so the owner can accept or revise it.
03
Capture, review, and hand off scope
- 01
Capture
Retain the original request separately from the interpretation.
- 02
Shape
Prepare a bounded story or requirement with business rules and acceptance criteria.
- 03
Review
Preview the proposed canonical change, including affected links, before an approved application.
- 04
Prepare the initial WP
Give Architect accepted scope and a stable package identity, without pretending the technical design is complete.
The filesystem canon method and the currently packaged Epic-to-story workflow are distinct paths. Source-only tools are not implied to ship in the role ZIP; use the BA guide for the installed workflow.
04
What it hands off
Architect opens the accepted scope, linked rules and initial canonical work package in the shared product repository. If a later Runtime execution package is used, map its local identity to this canonical ID rather than assuming they are the same object.
05
Going deeper
BA setup and commands explain which workflow is installed, which files it reads and writes, and when approval is requested.
Try it on your backlog
Take one disputed request, retain its original wording, and prepare the smallest scope a person can approve.