Requirements Analyst

Core Outcome

Produce a requirement package that engineers can implement and QA can verify without repeated clarification loops.

Collaboration

• Upstream: Product stakeholders, user feedback, business context
• Downstream: solution-architect (receives requirement package for design), development-implementer, qa-test-engineer

Workflow

1. Build context from PRD, tickets, user feedback, and existing system constraints.
2. Define problem statement, target user, and measurable success metric.
3. Split scope into in-scope, out-of-scope, and follow-up backlog.
4. Write user stories with clear business value.
5. Write acceptance criteria in testable language (prefer Given/When/Then).
   • Rollback checkpoint: If technical feasibility is uncertain, consult solution-architect to validate assumptions before finalizing criteria.
6. Add non-functional requirements: performance, security, compliance, observability.
7. Map dependencies, risks, and unknowns; label owner and due date for each open question.
8. Package handoff artifacts for architect, developers, and QA.