LeSS Framework Flow

ONE Product Backlog for the entire product, regardless of team count. Owned by the single PO. Customer-centric features, not component tasks.

ONE Product Owner for the entire product. Full content authority. Facilitates direct team-customer connection. Does not work alone on refinement.

Dedicated full-time role. Serves 1–3 teams. Focuses on the overall organizational system, not just one team. Drives LeSS adoption and organizational change.

Teams work DIRECTLY with customers and the PO. Multi-team sessions for shared items; single-team for specific items. The key dependency-reduction activity.

ALL teams together with PO. PO presents priorities. Teams self-select items. Dependencies surfaced. One shared session.

Each team plans independently. Decompose items into tasks. Teams coordinate directly with each other for dependencies. PO available.

Cross-functional, cross-component, full-stack feature team. Can deliver end-to-end customer features independently. Self-managing.

Another feature team working from the same Product Backlog. May coordinate with Team A through direct conversation, not ceremonies.

Feature teams are long-lived, co-located, and customer-focused. All teams share one codebase with collective ownership.

LeSS supports 2–8 feature teams. Each is cross-functional and can deliver any feature from the Product Backlog.

Standard 15-min per team. No Scrum-of-Scrums. Cross-team coordination through ‘just talk’ — team members attend other teams’ standups or walk over.

ALL teams integrate into ONE shared codebase continuously. No team branches. Collective code ownership. This is a hard technical requirement for LeSS.

Test-driven development, clean code, and refactoring are not optional. They are structural enablers for multi-team development on shared code.

ONE potentially shippable Product Increment from ALL teams combined. Not separate increments per team — one integrated whole product.

ONE Sprint Review for the entire product. All teams together with real customers, users, stakeholders. Demo the integrated product.

Standard team retro per team. Issues that can’t be solved by one team alone are elevated to the Overall Retrospective.

UNIQUE to LeSS. Team reps + SM(s) + PO + managers address cross-team and organizational systemic issues that individual teams cannot solve.

Teams work DIRECTLY with real customers and users — in refinement, Sprint Review, and throughout the Sprint. No intermediary layer.