Introduction to Large Scale Scrum (LeSS)

Large Scale Scrum (LeSS) is a scaling framework that enables organizations to efficiently apply Scrum principles and practices in larger, multi-team settings. Developed by Craig Larman and Bas Vodde, LeSS builds upon the core concepts of Scrum and extends them to accommodate the complexities of coordinating multiple teams working towards a shared goal. By emphasizing simplicity, flexibility, and adaptability, LeSS provides a practical and effective approach to scaling Agile methodologies while maintaining the core values of transparency, inspection, and adaptation.

Importance of effective LeSS Planning

Effective planning is a crucial aspect of the Large Scale Scrum (LeSS) framework, as it enables teams to coordinate their efforts, manage dependencies, and ensure alignment with organizational goals. A well-executed LeSS planning process helps teams maintain focus on high-priority work items and fosters efficient use of resources. Moreover, it encourages cross-team collaboration, allowing teams to share knowledge and insights, leading to continuous improvement. By emphasizing the importance of planning, LeSS ensures that organizations can scale their Agile practices while maintaining agility, responsiveness, and a strong focus on delivering customer value.

Overview of LeSS Framework

Basic principles of LeSS

The Large Scale Scrum (LeSS) framework is founded on five fundamental principles that guide its implementation and practice. These principles are:

  1. Empirical Process Control: LeSS relies on transparency, inspection, and adaptation, promoting evidence-based decision-making and continuous improvement.
  2. Whole-Product Focus: Teams concentrate on delivering an integrated, valuable product, encouraging collaboration and a shared understanding of the project vision.
  3. Customer-Centric: LeSS prioritizes delivering value to customers, emphasizing features that address their needs and provide a positive user experience.
  4. Lean Thinking: LeSS embraces eliminating waste, focusing on value-adding activities, and promoting a sustainable pace of work.
  5. Systems Thinking: LeSS encourages viewing the organization as a complex system, recognizing that optimizing individual components may not lead to overall improvement.

By adhering to these principles, LeSS ensures that organizations can scale their Agile practices effectively while maintaining the essential values and practices that make Scrum successful.

Two LeSS frameworks: LeSS and LeSS Huge

The Large Scale Scrum (LeSS) framework comprises two distinct approaches to accommodate organizations of varying sizes and complexity: LeSS and LeSS Huge.

  1. LeSS: The basic LeSS framework is designed to scale Scrum in organizations with 2 to 8 teams working on the same product. It emphasizes simplicity and minimal overhead, allowing teams to collaborate more effectively and maintain a strong focus on delivering customer value. In LeSS, teams share a single Product Backlog and a Product Owner and participate in joint planning, review, and retrospective events.
  2. LeSS Huge: LeSS Huge is tailored for organizations with more than eight teams working on one product. It introduces the concept of Requirement Areas, which are large, customer-centric groupings of related Product Backlog items. Each Requirement Area has its dedicated Area Product Owner, typically involving 4 to 8 teams working together. LeSS Huge maintains the core principles and practices of LeSS while providing additional guidance and structure to manage the increased complexity of larger organizations.

Both frameworks are designed to scale Agile practices efficiently while maintaining the essential values and practices of Scrum, ensuring that organizations of various sizes can benefit from the LeSS approach.

Key roles in LeSS (Product Owner, Scrum Master, Feature Team)

In the Large Scale Scrum (LeSS) framework, three key roles drive the successful execution of the scaled Scrum process. These roles are:

  1. Product Owner (PO): The Product Owner represents the interests of stakeholders and customers, ensuring that the product delivers value to users. In LeSS, the PO manages and prioritizes the Product Backlog for multiple teams. They work closely with the Feature Teams to clarify requirements, provide feedback, and ensure that the product aligns with the overall vision and goals.
  2. Scrum Master (SM): The Scrum Master is a servant-leader who helps teams adopt and improve the LeSS framework. Their primary responsibility is facilitating the Scrum process, removing impediments, and coaching the teams in effective Agile practices. In a LeSS environment, the SM also plays a crucial role in promoting cross-team collaboration, ensuring that teams share knowledge and learn from each other.
  3. Feature Team: A Feature Team is a cross-functional, self-organizing group that delivers a complete, end-to-end customer-centric feature. These teams comprise members with diverse skill sets, enabling them to handle all aspects of product development, from design to testing and deployment. In LeSS, multiple Feature Teams work together on the same Product Backlog, collaborating and coordinating their efforts to ensure a cohesive, high-quality product.

These roles form the foundation of the LeSS framework, working together to drive the effective execution of the scaled Scrum process and deliver value to customers.

LeSS artifacts (Product Backlog, Sprint Backlog, Definition of Done)

Several Large Scale Scrum (LeSS) framework artifacts help guide the development process and ensure alignment with the overall product vision. The primary LeSS artifacts include

  1. Product Backlog: The Product Backlog is a prioritized list of features, enhancements, and bug fixes the organization wishes to develop for the product. In LeSS, multiple teams share a Product Backlog, which the Product Owner manages. This shared backlog promotes collaboration, reduces redundancy, and helps maintain a unified product vision across teams.
  2. Sprint Backlog: The Sprint Backlog is a subset of the Product Backlog that the Feature Teams commit to completing during a specific Sprint. The Sprint Backlog serves as a roadmap for the team’s work during the Sprint, ensuring that they remain focused on high-priority items and collaborate effectively. Each team creates its own Sprint Backlog during the Sprint Planning event, selecting items from the shared Product Backlog.
  3. Definition of Done (DoD): The Definition of Done is a shared understanding of the quality and completeness criteria a product increment must meet before being considered “done.” The DoD ensures that all teams maintain a consistent level of quality and helps prevent technical debt from accumulating. In LeSS, all teams establish the DoD collaboratively, promoting transparency and fostering a shared commitment to delivering high-quality work.

These artifacts provide the necessary structure for effective planning, execution, and collaboration within the LeSS framework, enabling teams to focus on delivering customer value while maintaining consistent quality and alignment with the product vision.

LeSS Planning Process

The Large Scale Scrum (LeSS) planning process encompasses several critical steps that help coordinate multiple teams, ensure alignment with the product vision, and promote continuous improvement. This process includes

Synchronization of Multiple Teams:

In LeSS, synchronization among teams is vital to work harmoniously toward the shared product vision. Teams align their efforts through joint planning, review, and retrospective events, as well as continuous communication and collaboration throughout the Sprint. This synchronization allows for effective management of dependencies and prevents work duplication, ultimately resulting in a more efficient and cohesive product development process.

Product Backlog Refinement:

Product Backlog Refinement is an ongoing process in which the Product Owner and Feature Teams collaborate to refine and clarify the Product Backlog items. This process involves breaking down larger items into smaller, more manageable tasks, providing estimates, and prioritizing items based on value, risk, and dependencies. Product Backlog Refinement helps ensure that the teams clearly understand the work, allowing for more accurate planning and smoother Sprint execution.

Sprint Planning:

Sprint Planning in LeSS is divided into two parts:

  1. Sprint Planning One: During this event, the Product Owner presents the top-priority Product Backlog items to the Feature Teams. Teams collectively discuss, clarify, and tentatively select items to work on during the upcoming Sprint, considering each team’s dependencies and capacity.
  2. Sprint Planning Two: Individual Feature Teams plan the work required to complete the selected items in this phase. Teams identify dependencies, coordinate with other teams to manage these dependencies and define their Sprint Backlog and Sprint Goal. This planning ensures that teams understand their objectives and the work needed to achieve them.

Review and Retrospective:

At the end of each Sprint, LeSS teams participate in the joint review and retrospective events to inspect their progress, gather feedback, and identify areas for improvement.

  1. Joint Sprint Review: During this event, Feature Teams demonstrate the completed work to stakeholders, Product Owner, and other teams. They gather feedback, discuss new insights, and update the Product Backlog as needed.
  2. Overall Retrospective: In the Overall Retrospective, representatives from all Feature Teams come together to identify and discuss areas for improvement in the overall LeSS implementation. Teams share their experiences, learn from each other, and collaboratively decide on changes to the process for future Sprints.

The LeSS planning process provides a structured approach to managing the complexities of large-scale product development, ensuring that teams collaborate effectively, maintain alignment with the product vision, and continuously improve their practices.

Effective LeSS Planning Techniques

To ensure successful Large Scale Scrum (LeSS) planning, organizations should adopt the following techniques:

Ensuring Cross-Functional Teams:

Cross-functional teams are essential in LeSS, as they enable Feature Teams to take ownership of all aspects of product development, from design to deployment. By assembling teams with diverse skill sets, organizations can minimize handoffs, reduce dependencies, and promote a shared understanding of the product vision. Encouraging team members to develop their skills and knowledge further continuously contributes to the effectiveness of cross-functional teams.

Emphasizing “Just Barely Good Enough” Artifacts:

In LeSS, it is crucial to balance creating comprehensive documentation and maintaining agility. The “Just Barely Good Enough” (JBGE) principle suggests that teams should create artifacts that provide sufficient information to make informed decisions without excessive documentation. This approach allows teams to quickly adapt to changing requirements while avoiding wasted effort on over-detailed planning.

Promoting Strong Communication and Collaboration:

Effective communication and collaboration are fundamental to the success of LeSS planning. Teams should establish open communication channels within their own teams and across the organization to share knowledge, resolve dependencies, and align their efforts. Techniques such as co-location, daily stand-up meetings, and visual management tools can facilitate communication and promote transparency.

Continuously Adapting and Improving the Planning Process:

A core principle of LeSS is the continuous improvement of the planning process. Teams should actively seek feedback from stakeholders, customers, and other teams to identify areas for improvement. By incorporating insights from retrospectives and reviews, teams can refine their planning techniques, adapt to changing circumstances, and achieve better results in future Sprints.

By adopting these effective planning techniques, organizations can ensure a smooth and efficient LeSS implementation, driving greater collaboration and alignment and ultimately delivering high-quality products to customers.

Common Challenges in LeSS Planning

Implementing Large Scale Scrum (LeSS) planning in an organization can present several challenges, including:

Managing Dependencies Between Teams:

In LeSS, coordinating the work of multiple Feature Teams can be complex, especially when there are dependencies between teams. To manage these dependencies effectively, teams should identify and discuss them during Sprint Planning and maintain open communication channels throughout the Sprint. Visualization tools like dependency maps can help teams track and resolve dependencies more efficiently.

Ensuring Effective Communication at Scale:

Effective communication can become increasingly challenging as the number of teams and individuals in a LeSS implementation grows. Organizations should invest in robust communication infrastructure, including tools and processes, to facilitate information sharing and collaboration. Regularly scheduled joint events, such as Sprint Planning, Review, and Retrospective, can also help promote communication across teams and ensure alignment.

Balancing Autonomy and Alignment:

One of the challenges in LeSS planning is finding the right balance between team autonomy and alignment with the overall product vision. While empowering teams to make decisions and self-organize is essential, they must remain aligned with the organization’s goals and priorities. Regular communication with the Product Owner, clear articulation of the product vision, and a shared understanding of the Definition of Done can help balance autonomy and alignment.

Overcoming Organizational Resistance to Change:

LeSS planning often requires significant organizational structure, culture, and practice changes. Resistance to change can be a significant obstacle in implementing LeSS successfully. To overcome this resistance, organizations should involve stakeholders at all levels in decision-making, provide ongoing training and support, and demonstrate the benefits of LeSS planning through incremental successes.

By understanding and addressing these common challenges, organizations can ensure a smoother transition to the LeSS planning process, ultimately reaping the benefits of scaled Agile practices.

Tips for Successful LeSS Planning

To ensure the success of Large Scale Scrum (LeSS) planning in your organization, consider the following tips:

Invest in Coaching and Training:

Providing adequate coaching and training for team members, Scrum Masters, and Product Owners is essential for a successful LeSS implementation. Investing in professional development helps individuals better understand their roles and responsibilities, master Agile practices, and adapt to the LeSS framework more effectively. External coaches with experience in LeSS can also provide valuable guidance and support during the transition period.

Establish a Clear Vision and Shared Goals:

A well-defined product vision and shared goals provide a strong foundation for LeSS planning. Engaging stakeholders and teams to develop the vision ensures alignment and fosters a sense of ownership. Communicating the vision and goals clearly and regularly helps maintain focus and guides teams in decision-making throughout the planning process.

Embrace a Culture of Continuous Improvement:

In LeSS, continuous improvement is not just a principle but a mindset that should permeate the organization. Encourage teams to reflect on their performance, identify areas for improvement, and experiment with new approaches. By fostering a culture that embraces change and learning, your organization will be better equipped to adapt to evolving market conditions and customer needs.

Foster Transparency and Trust Among Team Members:

Transparency and trust are vital for the success of LeSS planning. Promote open communication, share information freely, and encourage teams to be candid about their progress, challenges, and achievements. By cultivating an environment of trust, you empower teams to collaborate more effectively, take ownership of their work, and ultimately deliver better results.

By following these tips, your organization will be well-prepared to overcome the challenges of implementing LeSS planning and can fully leverage the benefits of scaled Agile practices.


Recap of LeSS Planning Process:

Throughout this article, we have explored the Large Scale Scrum (LeSS) planning process, which provides a framework for scaling Agile practices across multiple teams. This process encompasses synchronization of teams, refining the Product Backlog, Sprint Planning, and conducting joint review and retrospective events. We have also discussed the key roles, artifacts, and principles that underpin LeSS, as well as the challenges and best practices associated with its implementation.

Importance of Effective Planning in Achieving Organizational Goals:

Effective planning ensures teams work cohesively towards a shared vision and deliver high-quality products that meet customer needs. By adopting the LeSS planning process, organizations can achieve greater alignment, efficiency, and adaptability in their product development efforts, ultimately driving better business outcomes and more satisfied customers.

Encouragement to Embrace LeSS for Large-Scale Agile Success:

If your organization wants to scale Agile practices effectively, consider embracing the LeSS framework. With its emphasis on collaboration, continuous improvement, and customer-centricity, LeSS can help your organization achieve greater agility and success in today’s competitive and rapidly changing business landscape. As you embark on your LeSS journey, remember the tips and techniques discussed in this article. Remember that a commitment to learning, adaptation, and open communication will be instrumental in realizing the full potential of Large Scale Scrum.


  • Larman, C., & Vodde, B. (2016). Large-Scale Scrum: More with LeSS. Addison-Wesley Professional. Amazon
  • Schwaber, K., & Sutherland, J. (2017). The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game.
  • (n.d.). LeSS Principles.
  • (n.d.). LeSS Framework.
  • (n.d.). LeSS Events.
  • Cohn, M. (2010). Succeeding with Agile: Software Development Using Scrum. Addison-Wesley Professional. Amazon
  • Appelo, J. (2011). Management 3.0: Leading Agile Developers, Developing Agile Leaders. Addison-Wesley Professional. Amazon
  • Adkins, L. (2010). Coaching Agile Teams: A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition. Addison-Wesley Professional. Amazon