Why Scale? When choose each scaling approach? SAFe? LeSS? Enterprise Kanban? Other? Scaling experts will compare the different approaches, share from their experience and answer questions from the audience. This is the LeSS section presented by Sagi Smolarski

1. Sagi Smolarski - AgileSparks
MORE
LeSSwith
Craig LarmanBas Vodde

2. CT1
iOS
CT3
API
CT2
Android
CT4
Server
CT5
Big Data
CT6
Engine
F1
COMPONENT
the
TEAMS
F2Which components are
involved? What is the API
between them
System
Architect
System
Testing
Does the overall feature /
system work?
Is the overall
project on time?
PMO

3. Mel Conway
CONWAY’S
LAW

4. PRODUCT
✔ Customer-Centric Teams
FT1 FT2 FT3
PO
SM
Communities of
Practice
FEATURE
TEAM
the
F1
F2

5. ✔ Customer-centric
✔ Self-organizing
✔ Cross functional
✔ Co-located
✔ All Product Roles are inside the team.
FEATURE
TEAM
the

6. PRODUCT
CENTRIC
✔ One Product Sprint
✔ One PSPI (Potentially Shippable Product Increment)
✔ One Product Owner
✔ One Definition of Done
✔ One Product Backlog
✔ One Code base
✔ Continuous Integration
✔ One Build.

7. PRODUCT
SPRINT
the

8. ✔ Very few rules
✔ Many experiments
✔ 543 x Try..., Avoid...
✔ Scaling Scrum... can be just Scrum
✔ LeSS is More
LeSS
MINIMALis

9. LeSS
HUGE> 8 teams

10. “...any change initiative will be reduced to redefining or
overloading the new terminology to mean basically the same as
status quo.”
“Culture follows structure”
TRANSITIONING
LESSto

11. ?
LeSS Book
(WIP)
Certified LeSS Practitioner Training (3 days)
less.works
LEARNING
LESS

12. CASE
STUDIES
https://less.works/case-studies/index.html

13. The End