Less Events
Product Backlog Refinement
Multi-team & single-team · Timebox: ~10% of Sprint capacity
Overview
In LeSS, Product Backlog Refinement is the critical event for cross-team learning and customer connection. It happens in both multi-team and single-team formats, with teams working directly with real customers and users — not through requirement documents.
Event Ownership
Owned / Facilitated By
Product Owner (facilitates customer access) / Teams (do the refinement work)
PO connects teams directly with real customers, users, and stakeholders
Teams do the actual refinement work — understanding, estimating, splitting items
PO provides strategic context but doesn’t write detailed requirements for teams
SMs coach teams in effective refinement techniques
Who Should Be Present
Multi-Team PBR
Multiple teams together with PO, customers/users. Used for items that affect multiple teams or require shared understanding
Single-Team PBR
One team with PO (or customer/user). Used for items specific to one team’s upcoming work
Product Owner
Facilitates access to customers. Provides priority and value context. Available for questions
Customers/Users
Participate directly — explain needs, answer questions, provide feedback on proposed solutions
Preparation Checklist
01PO: Identify items needing refinement in upcoming 2–3 Sprints
02PO: Arrange customer/user participation for refinement sessions
03Teams: Review items before refinement sessions
04SMs: Ensure refinement is scheduled and teams understand the format