LeSS

Events & Ceremonies

Deep dives into every LeSS event. Explore facilitation techniques, ownership, preparation checklists, tips, and expected outcomes.

~1 hour (2-week Sprint)

Sprint Planning Part 1

Multi-team alignment

Sprint Planning Part 1 is a shared event where all teams and the Product Owner meet together. The PO presents the highest-priority items, and teams collaboratively self-select which items each team will work on. This is where whole-product alignment happens.

3 techniques3 participants7 tips
~2 hours (2-week Sprint)

Sprint Planning Part 2

Per-team planning

Sprint Planning Part 2 is done independently by each team. Each team creates their own Sprint Backlog — decomposing selected items into tasks and creating a plan for the Sprint. Teams may coordinate with each other during this phase for items with shared dependencies.

2 techniques3 participants5 tips
15 minutes

Daily Scrum

Per-team daily sync

Standard Scrum Daily Scrum, done per team. In LeSS, cross-team coordination happens organically — team members attend other teams’ Daily Scrums when needed, or simply walk over and talk. There is no mandatory cross-team standup or Scrum-of-Scrums.

2 techniques3 participants5 tips
~10% of Sprint capacity

Product Backlog Refinement

Multi-team & single-team

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.

2 techniques4 participants6 tips
≤4 hours (1-month Sprint)

Sprint Review

Shared, whole-product

In LeSS, there is one Sprint Review for the entire product — all teams together with real customers, users, and stakeholders. Teams demonstrate the integrated product increment, and the PO facilitates adaptive planning based on feedback.

2 techniques4 participants6 tips
Team: ≤1.5hr / Overall: ≤1.5hr

Retrospectives

Team + Overall

LeSS has two levels of retrospective: Team Retrospectives (standard Scrum, per team) and the Overall Retrospective (unique to LeSS). The Overall Retrospective addresses cross-team and systemic issues that individual teams cannot solve alone.

3 techniques2 participants7 tips