Requirements Template¶
Add stakeholders
Add new stakeholders to the table below.
| Role | Person | Status |
|---|---|---|
| Author | 🔵 In review | |
| Reviewer | Kriti Godey | 🟡 In progress |
| Reviewer | Brent Moran | 🟠In revision |
| Reviewer | Zack Krida | 🟢 Approved |
The Problem¶
Describe the problem.
- What is the “business problem” that the user is trying to solve?
- Current pain points: how is the user solving this problem now, either within Mathesar, or otherwise?
- Why is it worth solving now?: explain why we think this problem is worth solving now (high-level feasibility, signals).
Use Cases¶
Write use cases.
Use cases. User persona-related synthesis (if any).
Success Criteria¶
Create success criteria.
What are our externally measurable success criteria? How much time is it worth spending on solving this problem (T-shirt size)?
Requirements¶
Write requirements.
Classic user stories or basic requirements.