Elad Sofer - Certified LeSS trainer

follow me on twitter - @eladsof
Large Scale Scrum
About me - Elad Sofer
• Father and husband
• Live in Israel.
• 20 years in Software 

development
• Agile coach
• LeSS certified trainer
Wrong
question!
The sad truth
• Succeeding with one-team-Scrum is
difficult enough.
• You organization is probably bigger
than it needs to be.
• LeSS is not going to help you with
scaling your organization.
The “LeSS” question is:


and…
There are no best practices.
Only good practices within a
specific context
The basic assumptions
Over complexity hurts agility
Larman's Laws of Organizational Behavior
1. Organizations are implicitly optimized to avoid changing
the status quo of middle- and first-level manager and
“specialist” positions & power structures.
2. As a corollary to (1), any change initiative will be
reduced to redefining or overloading the new
terminology to mean basically the same as status quo.
3. As a corollary to (1), any change initiative will be derided
as “purist”, “theoretical”, “revolutionary”, "religion", and
“needing pragmatic customization for local concerns” --
which deflects from addressing weaknesses and
manager/specialist status quo.
4. Culture follows structure.
600 Experiments
2008
Table of contents
1.Introduction
Thinking tools
Organisational tools
2.Systems Thinking
3.Lean Thinking
4.Queueing Theory
5.False Dichotomies
6.Be Agile
7.Feature Teams
8.Teams
9.Requirements Areas
10.Organisation
11.Large-Scale Scrum
2010
Table of contents
1.Introduction
Action tools
2.Large-Scale Scrum
3.Test
4.Product Management
5.Planning
6.Coordination
7.Requirements
8.Design & Architecture
9.Legacy Code
10.Continuous Integration
11.Inspect & Adapt
12.Multisite
13.Offshore
14.Contracts
3 Pages of Rules
2015
http://less.works
10 principles
Big gap
Finally, Some Guides
2016
Table of contents
1.More with LeSS
2.LeSS
LeSS Structure
3.Adoption
4.Organise by
Customer Value
5.Managers
6.ScrumMasters
LeSS Product
7.Product Owner
8.Product Backlog
9.Definition of Done
10.Initial PBR
LeSS Sprint
11.Sprint Planning
12.Sprint
Coordination and
Integration
13.Product Backlog
Refinement
14.Sprint Review
15.Sprint
RetrospectiveMore or LeSS
16.More or LeSS;
Architecture, DevOps
Two Frameworks: LeSS and LeSS Huge
2-8 teams >8 teams
LeSS - Up to 8 teams
Scrum recommends that
the backlog is refined for
~2 sprints ahead
Items per spint per team: 3-4
For 8 teams: at any given moment
~100 backlog items.
LeSS Huge
Upcoming Certified LeSS
Practitioner courses
• April 19, 2017 - Riga, Latvia
• May 10, 2017 - Chicago, United States
• June 19, 2017 - Dublin, Ireland
• July 12, 2017 - Zurich, Switzerland
• August 1, 2017 - Hamburg, Germany
• Learn more at http://less.works
Scaling Agile with LeSS (Large Scale Scrum)

Scaling Agile with LeSS (Large Scale Scrum)

  • 1.
    Elad Sofer -Certified LeSS trainer
 follow me on twitter - @eladsof Large Scale Scrum
  • 2.
    About me -Elad Sofer • Father and husband • Live in Israel. • 20 years in Software 
 development • Agile coach • LeSS certified trainer
  • 4.
  • 5.
    The sad truth •Succeeding with one-team-Scrum is difficult enough. • You organization is probably bigger than it needs to be. • LeSS is not going to help you with scaling your organization.
  • 6.
  • 7.
  • 8.
    and… There are nobest practices. Only good practices within a specific context The basic assumptions Over complexity hurts agility
  • 9.
    Larman's Laws ofOrganizational Behavior 1. Organizations are implicitly optimized to avoid changing the status quo of middle- and first-level manager and “specialist” positions & power structures. 2. As a corollary to (1), any change initiative will be reduced to redefining or overloading the new terminology to mean basically the same as status quo. 3. As a corollary to (1), any change initiative will be derided as “purist”, “theoretical”, “revolutionary”, "religion", and “needing pragmatic customization for local concerns” -- which deflects from addressing weaknesses and manager/specialist status quo. 4. Culture follows structure.
  • 10.
  • 11.
    2008 Table of contents 1.Introduction Thinkingtools Organisational tools 2.Systems Thinking 3.Lean Thinking 4.Queueing Theory 5.False Dichotomies 6.Be Agile 7.Feature Teams 8.Teams 9.Requirements Areas 10.Organisation 11.Large-Scale Scrum
  • 12.
    2010 Table of contents 1.Introduction Actiontools 2.Large-Scale Scrum 3.Test 4.Product Management 5.Planning 6.Coordination 7.Requirements 8.Design & Architecture 9.Legacy Code 10.Continuous Integration 11.Inspect & Adapt 12.Multisite 13.Offshore 14.Contracts
  • 13.
  • 14.
  • 15.
  • 16.
  • 17.
    2016 Table of contents 1.Morewith LeSS 2.LeSS LeSS Structure 3.Adoption 4.Organise by Customer Value 5.Managers 6.ScrumMasters LeSS Product 7.Product Owner 8.Product Backlog 9.Definition of Done 10.Initial PBR LeSS Sprint 11.Sprint Planning 12.Sprint Coordination and Integration 13.Product Backlog Refinement 14.Sprint Review 15.Sprint RetrospectiveMore or LeSS 16.More or LeSS; Architecture, DevOps
  • 19.
    Two Frameworks: LeSSand LeSS Huge 2-8 teams >8 teams
  • 20.
    LeSS - Upto 8 teams
  • 22.
    Scrum recommends that thebacklog is refined for ~2 sprints ahead Items per spint per team: 3-4 For 8 teams: at any given moment ~100 backlog items.
  • 23.
  • 25.
    Upcoming Certified LeSS Practitionercourses • April 19, 2017 - Riga, Latvia • May 10, 2017 - Chicago, United States • June 19, 2017 - Dublin, Ireland • July 12, 2017 - Zurich, Switzerland • August 1, 2017 - Hamburg, Germany • Learn more at http://less.works