Large Scale Scrum (LeSS): A Systemic Approach to Organizational Change

Play video
This article is a summary of a YouTube video "Overview of Large Scale Scrum (LeSS) @Agile Practitioners Association of Nigeria" by Adaptive Ecosystems by KSTS Consulting
TLDR Large Scale Scrum (LeSS) is a deep systemic approach to organizational change that requires cultural transformation, leadership participation, and proper training and structure for teams to effectively implement and benefit from it.

Key insights

  • 💡
    The importance of culture, mindset, and behaviors in an organization is often overlooked in favor of focusing on processes and policies.
  • 📊
    Successful agile adoption requires the informed consent and support of senior management who are responsible for organizational design and decision-making.
  • 🔄
    Large-scale Scrum advocates for a dual approach of coaching and training individuals and teams, as well as educating and teaching senior management, to ensure effective organizational design and decision-making.
  • 🌍
    Superficial agile transformations only address trivial elements, while true success lies in deep and narrow changes that encompass organizational structure, HR policies, vendor management, finance, and budgeting.
  • 🤔
    Mistaking a bunch of component teams running side by side and scrumming as scaling is a common misconception, as true scaling involves teams working together on the same product.
  • 💡
    In Large Scale Scrum (LeSS), teams work concurrently and coordinate directly with each other, eliminating the need for translation layers like managers or supervisors.
  • 🤔
    Large-scale scrum should focus on sustainable and meaningful organizational design and dynamics, rather than superficial changes like updating job titles in the HR database.
  • 💡
    The role of a scrum master should be taken seriously and not just seen as a label, requiring proper incentives, expectations, and a career path within the organization.
  • 💡
    Team maturity is crucial in the adoption of Large Scale Scrum (LeSS), as self-design teams are able to set their own organizational context.

Q&A

  • What is Large Scale Scrum (LeSS)?

    Large Scale Scrum (LeSS) is a deep systemic approach to organizational change that requires cultural transformation, leadership participation, and proper training and structure for teams to effectively implement and benefit from it.

  • What resources are available for self-study of Large Scale Scrum (LeSS)?

    There are accessibility and resources available for self-study of Large Scale Scrum (LeSS), including three books since 2008 that document the core principles, framework, rules, guides, and numerous experiments.

  • What is more important in Large Scale Scrum (LeSS) - culture or metrics?

    In Large Scale Scrum (LeSS), culture, mindset, behaviors, norms, values, processes, and policies are more important than metrics like mattress velocities, OTRS rags, and maturity levels.

  • How can organizational resistance to change be addressed in Large Scale Scrum (LeSS)?

    The success of Large Scale Scrum (LeSS) is proportional to how effectively it addresses organizational resistance to change and leadership participation, and simply adopting superficial changes without improving anything will only lead to temporary success.

  • What areas should be considered for successful adoption of Large Scale Scrum (LeSS)?

    To achieve significant systemic changes in an organization, it is necessary to consider various areas such as legal practices, product management, HR policies, and strategies, and obtain informed consent from senior management for successful adoption.

Timestamped Summary

  • 📚
    00:00
    Large Scale Scrum (LeSS) is a well-established and meaningful way of working that emphasizes the importance of culture, mindset, and leadership participation in addressing organizational resistance to change, while metrics and superficial changes alone will only lead to temporary success.
  • 📚
    07:35
    Large Scale Scrum (LeSS) emphasizes deep systemic changes in an organization's structure, policies, and practices, involving active involvement from managers, coaching for individuals and teams, and voluntary participation, rather than focusing on superficial elements like metrics and tools.
  • 🔍
    13:52
    Large Scale Scrum (LeSS) is about multiple teams working on different products with a common goal, requiring months of preparation, synchronous coordination, and direct communication for collaboration.
  • 🔑
    22:46
    In large scale scrum, it is important to have properly trained individuals in roles like scrum master and product owner, with direct information flow from users to the product owner, and a shift in focus for the scrum master from product to organizational design over time, along with proper recognition and incentives for full-time scrum masters.
  • 📚
    29:11
    Teams in Large Scale Scrum (LeSS) should prioritize directly from the product owner, avoid fake product owners, have a properly structured team, and work on complete features for flexibility and efficiency in product development.
  • 📚
    37:48
    To effectively implement Large Scale Scrum (LeSS), it is important to have a strong understanding of Scrum, seek guidance from experienced consultants, have supportive individuals internally, be patient, and be aware of organizational design dysfunctions that may need to be addressed.
  • 📚
    43:31
    Large Scale Scrum (LeSS) is a popular and effective approach for agile practitioners, but it may not be suitable for all companies; implementing it requires understanding, assessing the situation, and relying on credible consultants.
  • 📚
    56:15
    Reach out to the speaker for guidance and resources to increase awareness of Large Scale Scrum (LeSS) and access free content and information.
Play video
This article is a summary of a YouTube video "Overview of Large Scale Scrum (LeSS) @Agile Practitioners Association of Nigeria" by Adaptive Ecosystems by KSTS Consulting
4.7 (11 votes)
Report the article Report the article
Thanks for feedback Thank you for the feedback

We’ve got the additional info