This presentation explores the role of Backlogs for defining and shaping Agile product development and feature delivery.

1. Agile “Back to Basics” Series
Perfect Backlogs
Vienna Scrum Meetup
3 July 2023
Peter Croÿ, MSc
Agile Enthusiast

2. Back to Basics Meetups
Previous Meetup Events:
• The Agile Mindset - Agile Manifesto explained
• Scrum processes - When and how to apply them
Today’s session is about Backlogs in Scrum:
• What are Backlogs?
• Why and when do we need them?
• How do we create and handle Backlogs?
Vienna Scrum Meetup 2

3. What are Backlogs?
Backlogs definition from the 2020 Scrum guide:
• Product Backlog
The Product Backlog is an emergent, ordered list of what
is needed to improve the product. It is the single source of
work undertaken by all Scrum Teams.
• Sprint Backlog
The Sprint Backlog is composed of the Sprint Goal (why),
the set of Product Backlog items selected for the Sprint
(what), as well as an actionable plan for delivering and
committing the Increment (how) by a single Scrum Team.
Vienna Scrum Meetup 3

4. Product vs. Sprint Backlog
Vienna Scrum Meetup 4
Product Backlog
Work Item (Ready)
Work Item (Ready)
Work Item (Ready)
Work Item (Ready)
Work Item (Planned)
Work Item (Planned)
Work Item (Idea)
Work Item (Idea)
Sprint Backlog
Work Item
Task Task
Task Task
Task
Task
Work Item
Task Task
Task Task
Task
Ready for Sprint
planning (items
for 2+ Sprints)
Plan Items (not
refined yet)
Ideas for
features and
enhancements

5. How to Create a Sprint Backlog?
• Schedule a Sprint planning meeting for each team
• PO presents “prioritised, ready items” from the
Product Backlog and explains product and user value
• Team selects, analyses, estimates & plans items from the
Product Backlog for execution and delivery during Sprint
• Result is a Sprint Backlog: A committed list of user stories
Important: A Sprint Backlog is specific to each team,
while the Product Backlog is common across all teams
Vienna Scrum Meetup 5

6. How to Create a Product Backlog?
• Put the Product Goal in the Product Backlog
Describe wishes and future states of the product which
serve as a target for the Scrum Team to plan against.
All items in the Product Backlog emerge continually to
define the “what” that will fulfil the Product Goal.
Vienna Scrum Meetup 6
Capture
Vision
Ideas
Feedback
Organise
Describe
Refine
Order
Prioritise
Urgency
Value
Dependency
Execute
Sprints
Reviews
Delivery

7. Typical Product Backlog Contents
• Product Features
Epics, Enablers, User Stories, Tasks
• Bugs & Defects
Changes, Corrections, Usability
• Technical work
Technical Debt, New Architecture, Upgrades, Refactoring
• Knowledge acquisition
Planning Tasks, Lean Business Cases (MVP), Research
Vienna Scrum Meetup 7

8. Product Backlog Refinement
• What? Meetings to enhance Backlog items; Using DEEP may help:
Detailed appropriately, Estimated, Emergent, and Prioritized
• Why? Get Backlog items into ”ready” state for Sprint planning
• Who? Product Owner, Development Team, Stakeholders
• When? Ongoing, regular process, min. 1x review per Sprint
• How? Use guidelines in a list: “Definition of Ready” (DoR)
- Understand: Explain items to architects/developers for feedback
- Shape: Split, size and estimate items to fit into Sprint iterations
- Remove obstacles: Research dependencies - on teams and technical
- Order: Prioritise items according to value and product requirements
Caution: Avoid “stage-gating” for Backlog items refinement!
Vienna Scrum Meetup 8

9. Product Backlog Survival Tips
• Keep the Product Backlog focussed, short & manageable
• Backlog management is not a one-person job
• Product Backlog should not be “complete”
• Focus the Backlog on “what” & “why” – not the “how”
• Maximise the product value, not the number of features
• Make the Backlog transparent for everyone
• Decide what NOT to do early - learn to say “no”
Vienna Scrum Meetup 9

10. Want to discuss
more about Backlogs?
Vienna Scrum Meetup 10