The large scale scrum framework is one of the most popularly used agile frameworks that exist. Implemented by numerous organizations, this slideshow summarizes all the key elements of the framework that you need to know in a glance.

1. Kendis
Large Scale Scrum (LeSS)
Framework at a Glance

2. Large Scale Scrum
LeSS
(/lɛs/) abbreviation

3. It is a scaled up one Team scrum framework, that can
be applied to multiple agile teams consisting of
hundreds or even thousands of individuals which are
focused towards building one large or small sized
products.

4. It is a simple, minimalistic, lean and transparent
framework that has less enforcement of rules,
processes and maintains focus on having visibility
into the work being done to create the solution.

5. Participants Cross-functional and self-
managing Feature Teams.
Scrum Master who guides the
teams on how to work in LeSS.
One Product Owner who
manages the product backlog by
defining and prioritizing its
contents.
1
2
3
Area Product Owner focuses
on the product backlog of their
specific area of requirements
only in LeSS Huge.
4

6. Execution
in LeSS
There is a single Product Backlog
from where items are selected.
The selected items are
discussed by the team.
Planning is done on how to
complete those items in order to
achieve the sprint goals.
1
2
3
4 Sprints are started that could
last for 1-4 weeks. A deliverable
product is created in every
sprint iteratively and
incrementally.

7. A product backlog refinement
session is done where the
customer and the teams discuss
how the existing requirements
can be improved or if new
requirements should be added.
DevOps and Continuous
Integration ensures smooth
delivery to the customer where
a deliverable is a shippable
increment at the end of every
sprint.
5
6

8. Highlights
One Definition of Done for all
teams.
There are two types of
implementing LesS.
Basic LeSS that has up to eight
teams (of eight people each).
and LeSS Huge is for up to a few
thousand people on one
product. Items are in basic LeSS
while Epics exist in LeSS Huge.
1
2

9. Teams are feature-oriented and
regularly integrate their work
with one another that helps in
reducing dependencies.
3
Daily Scrum is held
independently by each Team,
though a member of Team A
may observe Team B’s Daily
Scrum, to increase information
sharing.
4

10. There are design and
architecture workshops to align
synergy across all the teams and
focus towards the end product.
5
Frequent retrospectives and
inspect and adapt sessions
done to ensure continuous
improvement.
6

11. 7 There is also a retrospective
where all the teams, product
owners, scrum masters and the
management work to
understand any impediments
that affect the delivery of the
product. Teams regularly have
their own retrospectives,
reviewing what is done to
continuously improve.

12. Reference
https://less.works/less/framework/index

13. "No one can whistle a
symphony. It takes a whole
orchestra to play it."
H.E Luccock

14. For more information
Contact us at: team@kendis.io
Or visit us: www.kendis.io