A1 — Requirements & Backlog

Objective

Create a compact, testable specification for a small software product or feature.

Required artifacts

1. Problem statement and scope.
2. Stakeholder list.
3. At least six functional requirements or user stories.
4. At least four quality requirements/constraints.
5. Acceptance criteria for the highest-priority items.
6. Prioritized backlog with dependencies.
7. One-page requirements review identifying ambiguity and risk.

Quality criteria

Strong submissions are specific, internally consistent, testable, prioritized, and clearly linked to stakeholder value.