Large Scale Scrum (LESS)

A product development framework that expands Scrum to many teams by offering scaling guidance while keeping Scrum's original goals and principles intact.

Key Points

  • Scales Scrum for multiple teams working on a single product.
  • Relies on one Product Backlog and one Product Owner for the whole product.
  • Adds minimal extra roles and artifacts to preserve core Scrum.
  • Promotes shared Definition of Done and frequent cross-team integration each Sprint.

Example

A company has six teams building a unified analytics platform. Using Large Scale Scrum (LESS), they maintain one Product Backlog prioritized by a single Product Owner. Teams hold a joint Sprint Planning, develop in parallel, integrate continuously, and present one increment at a combined Sprint Review.

PMP Example Question

Which approach extends Scrum for many teams with lightweight scaling guidance while preserving Scrum's original intent?

  1. Scaled Agile Framework (SAFe)
  2. Scrum of Scrums meeting technique
  3. Large Scale Scrum (LESS)
  4. PRINCE2

Correct Answer: C — Large Scale Scrum (LESS)

Explanation: LESS explicitly scales Scrum with guidance that keeps the framework lean and aligned with Scrum's purposes; SAFe adds additional layers, Scrum of Scrums is a coordination practice, and PRINCE2 is not Scrum-based.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across eight teaching sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management and Technology, not on Udemy.

See What Is Included