Prioritization: [quarter / backlog]
RICE-scored backlog – explicit trade-offs
사용법: Quarterly planning fights. RICE makes assumptions visible; the "not doing" list is the real output.
미리보기
Prioritization: [quarter / backlog]
Scored backlog – the framework makes trade-offs explicit and debatable instead of loudest-voice wins.
| Field | Value |
|---|---|
| Period | [quarter / cycle] |
| Owner | @name |
| Framework | RICE / WSJF / MoSCoW |
| Date | YYYY-MM-DD |
RICE scoring
- Reach: users affected per period
- Impact: 3 massive / 2 high / 1 medium / 0.5 low / 0.25 minimal
- Confidence: 100% / 80% / 50%
- Effort: person-weeks
| Initiative | Reach | Impact | Confidence | Effort | Score |
|---|---|---|---|---|---|
| [name] | N | N | N% | N wks | N |
| [name] |
Ranked list
| Rank | Initiative | Score | Committed? |
|---|---|---|---|
| 1 | Yes / No | ||
| 2 |
Deliberately not doing
| Item | Why not | Revisit when |
|---|---|---|
Saying no in writing is the whole point – revisit conditions keep the "no" honest instead of permanent.
Capacity check
- Available: N person-weeks
- Committed total: N person-weeks
- Buffer for interrupts: N%
Dependencies & risks
| Initiative | Depends on | Risk if delayed |
|---|---|---|