Large-Scale Scrum (LeSS)

LeSS is a framework for scaling scrum to multiple teams working together on a product. It starts at the foundation with a scrum team, as defined by Ken Schwaber and Jeff Sutherland in the Scrum Guide, and is applied to multiple teams working together on a single product.

LeSS is forged from over six hundred experiments conducted as part of expanding scrum practices. At the time, Scrum was seen as a supportive framework for small, composite teams only. Later, the LeSS rules were added to more thoroughly define the basics. With the rules, the implementation of LeSS is better supported and it is more easily carried out within an organization.

LeSS Principles

LeSS defines ten principles for applying scrum to the entire organization. They help responsible teams with a higher customer focus work together. Teams focus on learning, transparency and delivering customer-centric value. They are principles that product organizations need to be able to react competitively and quickly in a rapidly changing market.

The ten principles of LeSS are:

1. Large-Scale Scrum (LeSS) is scrum.

2. Empirical Process Control is the foundation where the process is based on experience and experimentation rather than detailed in advance planning.

3. Transparency so that all facets of the Scrum process can be observed by everyone.

4. More with less. Complex product development does not require complex solutions. It requires a deep understanding of the essence of the problems, which can then be solved with simpler solutions.

5. Focus on the whole product. There is no value in parts or half working parts.

6. Maintain customer focus as Scrum is more widely adopted.

7. Continuous improvement towards perfection is a Lean principle. It is based on practice and concepts, such as Go See, kaizen, value and waste, perfection challenge, work toward flow and respect for people.

8. Systems thinking.

9. Lean thinking is a proven practice that scales to large-scale developments, as demonstrated by Toyota and many others.

10. Queue theory provides insight into why traditional development approaches are unnecessarily slow and offers solutions.

LeSS versus SAFe

Although LeSS is increasing in popularity among organizations with many software development teams, other frameworks, such as Disciplined Agile Delivery, are also becoming more popular. One of the leading frameworks is currently Scaled Agile Framework® (SAFe).

There are similarities between LeSS and SAFe. For example: both frameworks start with scaling scrum and add principles such as Lean thinking and customer focus. However, LeSS differs in that it focuses on simplifying the organizational structure and is therefore more flexible and adaptable.

SAFe adds additional roles, such as the Release Train Engineer (RTE), Solution Train Engineer (STE) and Epic Owners. It also adds processes, artifacts, and organizational changes. Some organizations are not (yet) ready for this, although those organizations have successful agile teams that apply scrum well. LeSS is not as complex as other frameworks.

Practical example

A large company that develops vehicles and machines for the agricultural and construction sectors was struggling with missed delivery dates and quality problems. With the introduction of the LeSS framework, the company undertook an organizational restructuring, establishing cross-functional teams with a product owner and a high-quality product backlog.

Within six months, the company was already seeing improvements. The teams were more focused and able to plan reliably and deliver more predictably. The quality issues that plagued the releases were resolved. Teams began to deliver on time more consistently.

Want to know more?

AgileInFocus.nl offers various training courses that provide practical tools and tips for successfully deploying Scrum with multiple Scrum teams. We can also provide you with tailor-made advice on scaling Scrum in your organization or contribute ideas to make your organization competitive in a rapidly changing market.