| Story ID | User Story | Priority (MoSCoW) | Effort Estimate (Story Points) | Dependencies |
|---|---|---|---|---|
| US-001 | Create new projects | Must-have | 3 | None |
| US-002 | Assign tasks to team members | Must-have | 3 | US-001 |
| US-003 | Update task progress | Must-have | 2 | US-002 |
| US-004 | Generate reports | Should-have | 4 | US-003 |
| US-005 | Receive notifications | Must-have | 2 | US-002, US-003 |
| US-006 | Manage user roles | Must-have | 4 | None |
| US-007 | Upload project-related documents | Should-have | 3 | US-002 |
| US-008 | System logs for security tracking | Could-have | 2 | None |
| US-009 | Search tasks | Must-have | 2 | US-001 |
| US-010 | Encrypt user data for security | Must-have | 3 | None |
✅ Justification for prioritization:
- Must-have stories directly impact project management and task execution.
- Should-have features enhance user experience and productivity.
- Could-have stories add extra functionality but are not critical for the MVP.