Expert knowledge in project planning, requirements gathering, user stories, and scope management. Use when planning new projects or features.
Comprehensive knowledge for planning software projects from ideation to execution.
Questions to Ask:
Requirement Types:
**As a** [type of user]
**I want** [goal/desire]
**So that** [benefit/value]
**Acceptance Criteria:**
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
**Priority:** P0/P1/P2
**Estimate:** S/M/L/XL
MoSCoW Method:
Priority Levels: | Priority | Description | Timeline | |----------|-------------|----------| | P0 | Critical | Immediate | | P1 | High | This sprint | | P2 | Medium | Next sprint | | P3 | Low | Backlog |
T-Shirt Sizing: | Size | Complexity | Time | |------|------------|------| | XS | Trivial | < 1 hour | | S | Simple | 1-4 hours | | M | Medium | 4-8 hours | | L | Complex | 1-3 days | | XL | Very Complex | > 3 days |
Story Points (Fibonacci): 1, 2, 3, 5, 8, 13, 21
In Scope:
Out of Scope:
| Risk | Likelihood | Impact | Mitigation | |------|------------|--------|------------| | Scope creep | High | High | Strict change control | | Technical debt | Medium | Medium | Regular refactoring | | Key person dependency | Medium | High | Documentation, pairing |
# Project: [Name]
## Overview
[1-2 sentence description]
## Problem Statement
[What problem does this solve?]
## Goals
1. [Primary goal]
2. [Secondary goal]
3. [Tertiary goal]
## Success Metrics
- [Metric 1]: [Target]
- [Metric 2]: [Target]
## Scope
### In Scope
- [Feature 1]
- [Feature 2]
### Out of Scope
- [Excluded 1]
- [Excluded 2]
## Timeline
- Phase 1: [Date]
- Phase 2: [Date]
- Launch: [Date]
# Epic: [Name]
## Description
[What this epic accomplishes]
## User Stories
- [ ] US-001: [Story]
- [ ] US-002: [Story]
## Acceptance Criteria
- [ ] [Criterion]
## Dependencies
- [Dependency 1]
Category:business