There's better-than-even odds that if you're reading this, you think you want to learn an approach to scale agile development.
Surprisingly, LeSS (Large-Scale Scrum) is about not about scaling. It's about descaling and simplification of the limiting organizational structures so that many teams can work together on one product as simply as possible to towards the system optimizing goals of (1) highest value from global perspective and (2) agility to change cheaply based on learning.
But there's a change problem that you the reader are part of... If I had to boil down about 40 years of this work to one key idea, it is:
You must own, not rent, your change and organizational design.
And to own it, senior managers that have the authority to change the organizational design (eliminating groups, roles, sites, policies, etc.) have to do learning and change. LeSS is not about superficial techniques that don't impact the structure.
What learning? To start, the following pre-readings before our first call.
I'm Craig Larman, the creator (along with my friend and colleague Bas Vodde) of LeSS (Large-Scale Scrum), the author of three books on scaling lean thinking & agile development, and have focused for decades helping organizations succeed with scaling (or more precisely, descaling) with LeSS.
Welcome to learning more about your system and you creating something appropriate for your context!
For background, I'm Craig Larman, the co-creator (along with my friend and colleague Bas Vodde) of LeSS (Large-Scale Scrum), the author of the several books on scaling lean & agile development, and have focused for many years on helping organizations succeed with scaling with LeSS (see LeSS.works). Broadly, I'm trying to reduce suffering in development ;) — for customers, your economics, and developers. There's no good reason that development can't be successful, useful, and fun.
Before I start to work with a management team that is interested in introducing LeSS, and before we meet together for a 2-4 day "informed consent" workshop or course, these are the pre-readings I urge all participants to study before we start.
Why? Real lean thinking and agile (which involves systems thinking) adoption are the exact opposite of the "copying without knowledge" and "install this solution and you will be successful" silver-bullet sales pitches associated with fads and consulting-company "grand solutions." Rather, real lean thinking and agile systems thinking involve real thinking ;)
That is, that people (especially including the senior managers) take the time to deeply grasp (1) the nature of their system, (2) the root causes of its issues, (3) the complexities of its system dynamics, (4) the deeper concepts of LeSS, with a focus on why not what, and only then (5) create a situationally-appropriate organizational design experiment based on these ideas and principles — instead of the typical "adopt our solution and you will be agile" sales pitch.
This approach, LeSS, is not offering a prescribed checklist of so-called "best practices." Is that a problem? Such checklists sound seductively simple and appealing and easy, but they inhibit (1) contextual solutions, (2) thinking and understanding deeply, (3) a learning organization, (4) owning rather than renting your ideas and insights, and (5) a continuous improvement culture. Such "best practice solutions and checklists" promote conformance over learning, and copying over insight.
I recommend you do not simply decide to adopt LeSS. Rather, I recommend that you take the time to carefully learn, apply sober reflection, and then make an informed consent decision to try a non-trivial experiment — or not. Therefore, I recommend that the starting process is this:
1. Carefully study these pre-readings.
2. Discuss them amongst yourselves.
3. Participate in a 2 to 4-day "Informed Consent" workshop or course with me, where I will help you learn more in depth, explore your system with you, and answer all your questions about the implications and next steps.
4. After I leave, you together take a careful and considered decision to consent to the next step, or decide to decline continuing.
5. If your group decides with careful informed consent to go forward with an experiment, then I will help you in the next major phases: (1) LeSS Preparation, and (2) LeSS Sprint1.
2. The following chapters from our first LeSS book Scaling Lean & Agile Development: Thinking and Organizational Tools with LeSS:
Systems Thinking (or the equivalent Systems Thinking chapter at less.works) Lean Thinking (or the equivalent Lean Thinking chapter at less.works) Queuing Theory (or the equivalent Queuing Theory chapter at less.works) Feature Teams (or the equivalent Feature Teams chapter at infoq.com) Teams (or the equivalent Teams chapter at less.works)
3. The following chapters from the book The Fifth Discipline. This book comes from researchers at the MIT Sloan School of Management, was named one of the seminal management books of the last 75 years by the Harvard Business Review, and has been one of the best-selling (multi-million) and most influential management books of all time, for very good reasons. It's available in both p-book and e-book formats.
Give Me a Lever Long Enough Does Your Organization Have a Learning Disability? Prisoners of the System, or Prisoners of our own Thinking? The Laws of the Fifth Discipline Personal Mastery Mental Models
4. The following chapters from our third LeSS book Large-Scale Scrum: More with LeSS:
Chapter 2: LeSS, or the equivalent chapter online Chapter 3: Adoption Chapter 4: Organize by Customer Value Chapter 5: Management Chapter 7: Product