Free product template
Backlog prioritisation (RICE and MoSCoW)
Reach, impact, confidence and effort for every item, a MoSCoW board, and why for every number.
It opens with this template loaded and runs in your browser. You don't need an account to use it; a free account saves your work and exports it.
The job it does
Before quarterly planning or when stakeholders disagree on what comes next: a ranking you can defend. It comes with its own checks, so after you change it you can see at a glance that it still does the job.
What's inside
This is the template exactly as the Product & BA Lab opens it, read-only. Open it to run it, change it and export it.
- 1 document
- Exports as Markdown and CSV
Score the backlog with RICE, sort it with MoSCoW and write why for every number, so the ranking survives the meeting. Swap in your own items and numbers.
- Every item has reach, impact, confidence and effort, and a “why”
- “Must” items take at most 60% of the effort
Reach is counted in store staff a quarter. RICE = reach × impact × confidence ÷ effort (person-months).
| Rank | Item | Reach | Impact | Confidence | Effort | RICE | MoSCoW | Why |
|---|---|---|---|---|---|---|---|---|
| 1 | Scan expiry dates with the camera | 2,400 | High (2) | 80% | 2 | 1,920 | must | Every store does expiry checks daily; two pilot stores halved the time. |
| 2 | Goods-received photo proof | 900 | Medium (1) | 80% | 0.5 | 1,440 | must | Receiving staff in 320 stores; disputes with suppliers drop when there is a photo. |
| 3 | Price-check history | 3,000 | Low (0.5) | 80% | 1 | 1,200 | should | Most staff price-check; a small time saving each time. |
| 4 | Dark mode | 3,200 | Minimal (0.25) | 100% | 1 | 800 | could | Everyone sees it, but it changes little about the work. |
| 5 | Offline stock counts | 1,800 | Massive (3) | 50% | 4 | 675 | should | Huge if it works, but we have not tested how often counts are lost. |
The lesson behind it
Learn why it works, with a podcast and a quiz for each lesson.
More product templates
Requirements traceability matrix
Requirements, user stories and test cases, linked, with every coverage gap highlighted.
PRD for a new feature
Problem with numbers, users, goals and non-goals, measurable metrics with a guardrail, user stories with acceptance criteria, scope, risks and launch.
Sprint plan
People, days off and focus factor, a sprint goal, the stories that carry it, a burndown preview and a board.