Phase 1 - Requirements¶
Purpose¶
Define what the product must do and what success looks like.
Entry criteria¶
- An idea has been accepted for further work
Required inputs¶
- Problem statement
- Stakeholder needs
- Constraints and assumptions
Activities¶
- Convert the idea into actionable requirements
- Identify scope boundaries
- Highlight risks, dependencies, and non-goals
Engineering responsibilities¶
- Review feasibility and implementation implications when needed
AI-agent responsibilities¶
- Help structure requirements documentation
- Highlight ambiguities or missing details
Required artifacts¶
- Requirements document or equivalent backlog
- Scope boundaries
- Acceptance criteria
Validation¶
- Requirements are coherent, testable, and sufficiently scoped
Exit criteria¶
- Requirements are approved for architecture work
Approval or gate¶
- Requirements gate
Handoff¶
- Move to Phase 2 - Architecture