{"id":5941,"date":"2022-05-25T07:12:48","date_gmt":"2022-05-25T07:12:48","guid":{"rendered":"https:\/\/www.booksofall.com\/pl\/?post_type=product&p=5941"},"modified":"2022-06-20T00:16:43","modified_gmt":"2022-06-20T00:16:43","slug":"how-to-manage-multiple-scrum-teams-with-less-framework","status":"publish","type":"product","link":"https:\/\/www.booksofall.com\/pl\/how-to-manage-multiple-scrum-teams-with-less-framework\/","title":{"rendered":"How to Manage Multiple Scrum Teams with LeSS Framework"},"content":{"rendered":"

How to Manage Multiple Scrum Teams with LeSS Framework<\/h3>\n

4-5 minutes<\/p>\n

LeSS (Large-scale Scrum), like regular Scrum, is a framework for development in which the details need to be filled in by the teams and evolved iteration by iteration, team by team. It reflects the lean thinking pillar of continuous improvement. It is a collection of suggestions for inspecting and adapting the product and process when there are many teams \u2013 at least two teams and up to groups of 500 or 1000 people.<\/p>\n

LeSS Framework is not \u201cnew and improved Scrum.\u201d Rather, it is regular Scrum, an empirical process framework in which you can inspect and adapt to any method and work in a group of any size. Large-scale Scrum is a set of additional rules and the set of tips that we have seen work in large multi-team, multisite, and offshore agile development initiatives. These tips are experiments to try in the context of the classic Scrum framework.<\/p>\n

What is a LeSS Framework?<\/h3>\n

LeSS framework keeps it very simple and that\u2019s why the LeSS framework is often be mentioned with the slogan: \u201cLeSS is more with LeSS\u201d. The idea is that LeSS defines a \u201cbarely sufficient methodology\u201d (a key idea in the early agile days) for a group to scale, to enable shipping every Sprint, and to enable transparency and empirical process control.<\/p>\n

Rather than pushing a large and complex set of processes, structures, roles, and artifacts on to a group, there are more learning and adaption, less following and conformance. More value, less bureaucracy, and so on. The team should scale up a simple framework from simple elements, rather than attempt to \u201ctailor down\u201d a complex process frame work and the Philosophy of LeSS Framework is listed as follows:<\/p>\n

    \n
  1. Empirical process control rather than following a process recipe<\/li>\n
  2. A cross-functional real team together that does everything end-to-end (from UX analysis to testing to HI design to architecture to documentation, with no other teams required)<\/li>\n
  3. A team which is composed of multi-functional \u201cT-shaped\u201d workers rather than single-function mono-specialists<\/li>\n
  4. A team follows the direction a real business-side owner of the product responsible for ROI (e.g., head of product management) rather than an IT project manager or business analyst<\/li>\n<\/ol>\n

    The Structure of LeSS Framework: Basic vs Huge<\/h3>\n

    LeSS provides two different large-scale Scrum frameworks. Most of the scaling elements of LeSS are focused on directing the attention of all of the teams onto the whole product instead of \u201cmy part.\u201d Global and \u201cend-to-end\u201d focus are perhaps the dominant problems to solve in scaling. The two frameworks \u2013 which are single-team Scrum scaled up \u2013 are:<\/p>\n

    LeSS Basic -Up to eight teams with eight people each<\/h3>\n
      \n
    1. The Structure of the organization using real teams as the basic organizational building block and each team is (1) self-managing, (2) cross-functional, (3) co-located, and (4) long-lived.<\/li>\n
    2. The majority of the teams are customer-focused feature teams.<\/li>\n<\/ol>\n

      LeSS Huge \u2013 Up to a few thousand people on one product<\/h3>\n
        \n
      1. LeSS Huge applies to products with \u201c8+\u201d teams.<\/li>\n
      2. 2. Avoid applying LeSS Huge for smaller product groups as it will result in more overhead and local optimizations.<\/li>\n
      3. LeSS rules apply to LeSS Huge, unless otherwise stated. Each Requirement Area actslike the basic LeSS framework.<\/li>\n<\/ol>\n

        Summary<\/h3>\n

        You can organize multiple Scrum teams in many different ways, such as LeSS, Nexus, SAFe, DAD and Scrum@Scale based on our work with these frameworks which sharesome common patterns: Scrum at team level, many teams sharing a backlog, planning is done collaboratively across teams and the general principles of pull and self-organization. If you know Scrum well, LeSS Framework is the \u201cno-brainer\u201d framework for scaling the teams for your organization.<\/p>\n","protected":false},"excerpt":{"rendered":"