Product Backlog Template (Scrum)

Product Goal, ordered backlog with type, rationale, refinement state and estimates, refinement rhythm, optional Definition of Ready, range forecast, health checks

제품 및 프로젝트표준Scrum Guide 2020backlog업데이트됨 2026. 10. 29.

에디터에서 열기.md 다운로드

사용법: Use it when you snapshot or review a Scrum Product Backlog with the team or stakeholders. Fill the Product Goal first, then order items by value toward it and keep one to two Sprints Ready. The main pitfall is a huge unordered list that nobody reads.

미리보기

Product Backlog: [Product name]

A Product Backlog in the sense of the Scrum Guide 2020 (Schwaber and Sutherland, the current revision as of October 2026): the one ordered list of work the Scrum Team draws from, which keeps changing as the team learns what the product needs next, and whose commitment is the Product Goal. This template adds common practice the Scrum Guide does not prescribe (refinement states, estimates in story points, an optional Definition of Ready and a range forecast). Replace every [bracketed] value and every row marked Example.

Document control

Field	Value
Product	[Product name] Example: Tallow Notes, team workspaces
Product Owner	[@product-owner]
Scrum Team	[Team name]
Snapshot date	YYYY-MM-DD
Backlog tool and link	[Tool, link to live backlog]
Definition of Done	[Link to product/definition-of-done document]

Revision history

Version	Date	Author	Change
1.0	YYYY-MM-DD	[@product-owner]	Snapshot for [Sprint Review / stakeholder review]

1. Product Goal

Field	Value
Product Goal	[Future state of the product]
Measure of success	[Metric, baseline, target]
Link to strategy	[Strategy, bet or OKR]
Status	[Active / Fulfilled / Abandoned]
Example: Product Goal	A new team succeeds together in its first week: the second member is editing within 7 days
Example: Measure	Activation of new workspaces from 31% to 40% by 2027-06-30
Example: Link	Bet B1 in product/product-vision-strategy, outcome in product/opportunity-solution-tree

2. Ordered backlog

Order	ID	Item	Type	Value or rationale	Refinement state	Estimate (points)	Cumulative points
[1]	[PBI-NNN]	[Item title]	[Feature / Bug / Tech / Discovery / Compliance]	[Why now]	[New / Refining / Ready]	[N]	[N]
1 (Example)	PBI-101	Choose a starter space by team type when creating a workspace	Feature	Validated by AT-01 (52% chose a starter)	Ready	5	5
2 (Example)	PBI-102	Edit pinned starter notes in place	Feature	AT-02: two of six missed the edit button	Ready	3	8
3 (Example)	PBI-103	Invite colleagues from inside any note	Feature	Shortens path from note to invitation	Ready	5	13
4 (Example)	PBI-107	Fix duplicate note after offline edit on two devices	Bug	Sync guardrail G1 at risk	Ready	2	15
5 (Example)	PBI-108	Keyboard focus order on the invite dialog	Bug	Accessibility (WCAG 2.2 focus order)	Ready	3	18
6 (Example)	PBI-106	Build an offline evaluation set for question search	Discovery	Bet B2 needs a quality baseline before beta	Ready	5	23
7 (Example)	PBI-104	Export the workspace audit log as CSV	Feature	Bet B3, asked by paid teams	Refining	8	31
8 (Example)	PBI-105	Move a workspace to EU data residency	Feature	Bet B3, needs storage design spike first	Refining	13	44
9 (Example)	PBI-110	Show "what changed since you were last here" to returning members	Feature	OPP-2, not yet sized	New	not sized	not summed

Detail for each item (description, acceptance criteria, notes) lives in the item itself; see product/user-story and product/epic for the formats.

3. Refinement

Field	Value
Refinement rhythm	[Example: two 60-minute sessions per two-week Sprint]
Participants	[Product Owner, Developers, invited experts]
Ready buffer target	[Example: 1.5 Sprints of Ready items]
Current Ready buffer	[Example: 23 points Ready (items 1 to 6), about one Sprint at 22.7 average]

Refinement states used in this backlog:

State	Meaning
New	Captured, not yet discussed by the team
Refining	Being clarified, split or sized; open questions remain
Ready	Meets the team's Definition of Ready (section 4), small enough to finish within one Sprint

4. Definition of Ready (optional)

An item is Ready when:

It is linked to the Product Goal or marked as maintenance.
It has a clear description of who benefits and why.
Acceptance criteria are written and agreed by the Product Owner and Developers.
It is sized by the Developers and small enough to finish within one Sprint.
Dependencies and needed designs are known, and none blocks the start.
Privacy, security and accessibility needs are identified where relevant.

5. Forecast

Field	Value
Recent velocity (last three Sprints)	[N, N, N] Example: 21, 24, 23 points
Average	[N] Example: 22.7 points per Sprint
Two-Sprint range	[low to high] Example: 42 (2 x 21) to 48 (2 x 24), average 45.3

Example reading: items 1 to 6 (23 points) are slightly more than one Sprint at the average pace (22.7) and fit only at the high pace (24); product/sprint-planning therefore plans items 1 to 5 (18 points) against about 21 points of capacity and leaves PBI-106 for the following Sprint. Items 1 to 8 (44 points) fit within two Sprints at the average pace (45.3) but not at the low pace (42), so PBI-105 is likely in Sprint 2 and possibly in Sprint 3. Communicate it as "two to three Sprints".

6. Backlog health checks

Check	Answer
Does every item in the top 20 serve the Product Goal or maintenance?	[Yes / No]
Is the Ready buffer within target?	[Yes / No]
Are items older than [six months] reviewed or archived?	[Yes / No, count]
Are bugs and technical work visible in the same order, not in a separate list?	[Yes / No]
Can a stakeholder see why the top items are in that order?	[Yes / No]

Related templates and references

product/definition-of-done, product/sprint-planning, product/sprint-retro, product/user-story, product/epic, product/prioritization, requirements/user-story-map, product/roadmap
Schwaber, K. and Sutherland, J. (2020). The Scrum Guide: https://scrumguides.org/scrum-guide.html (revision list: https://scrumguides.org/revisions.html)

Standard and licence note

Structure aligned with the Product Backlog and Product Goal as described in the Scrum Guide 2020, which is published under CC BY-SA 4.0. This template cites the Guide by name and does not copy its text; all wording is original. Definition of Ready, story points, velocity and range forecasting are common practice, not part of Scrum. Check the current Scrum Guide at scrumguides.org. Template licence: MIT.