LeSSScrum can be scaled to include multiple teams working on the same product thanks to the useof LeSS (Lean Software Development). In order to make scrum principles more easilyimplemented in a business context, the LeSS initiative has set out to develop a set of rulesand guidelines. Because of LeSS's scaling capabilities, the team's attention can be redirectedaway from individual components and back toward the product as a whole. It's the year 2020for Atlassian. One of the most distinguishing characteristics of LeSS is its emphasis onminimizing the amount of overhead associated with collaborating across multiple Scrumteams. Company growth within their own organizations can be accelerated, resulting inincreased agility and efficiency in achieving the desired business outcomes and goals.Expertise from the financial and telecommunications industries contributed to thedevelopment of LeSS into what it is today (Craig Larman, Video).RolesAccording to LeSS, a single product owner should be responsible for multiple teams (up to 8in number). The following are the two frameworks for LeSS:1. LeSS: There are a total of eight teams eligible to compete in this competition (of eightpeople each).Secondly, a single product has the potential to serve hundreds of thousands of people.
Businesses should typically start with basic LeSS before progressing to more complex LeSS.The opportunity to experiment, learn from their mistakes, and receive feedback will providethem with an advantage as they progress to the next stage. The LeSS Huge adoption strategybegins by concentrating on a single requirement area within a larger product, and thengradually expanding the scope of work, the definition of done, and the definition of theproduct as a whole. This is how everything works. Prior to rolling out LeSS across the entireorganization, the company will gain LeSS team experience, expand into a new product area,and gain management support (Atlassian, 2020).ProcessesDuring a LeSS Sprint, which is the same for every team, teams collaborate on the ProductBacklog in order to complete it. At the end of the sprint, all teams come together for a singleSprint Review to discuss their progress.Sprint planning is divided into two parts, in the same way that Scrum is divided. In contrastto traditional Scrum, the Sprint Goal is defined for the first time, and the Product Backlogitems that will assist in achieving it are prioritized in order to achieve it. Each Scrum Teamsends one or more representatives to the meeting in order to keep the total number ofattendees to a bare minimum. Each Development Team should meet in the same physicallocation to ensure that they are all working toward the same goal, which is why LeSS
recommends that this stage of planning be completed at the earliest opportunity (Ageling,2019).