Your organization implemented Agile practices and saw success in delivery speed, employee engagement and customer happiness. Now your boss wants to use these practices across the organization, which begs the question: Can Agile scale? The short answer is that while Agile can scale to the point of transforming organizations as a whole, there are some […]
Your organization implemented Agile practices and saw success in delivery speed, employee engagement and customer happiness. Now your boss wants to use these practices across the organization, which begs the question: Can Agile scale? The short answer is that while Agile can scale to the point of transforming organizations as a whole, there are some misconceptions we must tackle on Agile scaling before taking the leap.
First, what do we mean when we say Agile scaling? Agile scaling is the practice of running Agile methodologies across multiple teams. This can be multiple Agile teams working on one product, or multiple teams working on multiple products; these two examples are considered product delivery scaling. There is also organizational scaling – specifically, Agile concepts are scaled horizontally (across) and vertically (up) through an entire organization. At this stage, we are taking Agile concepts outside of software development and into different divisions of the organization.
Before jumping in feet-first, here are three common misconceptions you’ll want to address:
We’ve heard people say, “Agile means there are no rules,” and apply the same myth to scaling. Different approaches in Agile scaling have their own rules and set up different human systems. An example of this is the SAFe approach.
SAFe (Scaled Agile Framework) is a set of organization and workflow patterns meant to guide enterprises in scaling lean and agile practices. SAFe promotes alignment, collaboration and delivery across large numbers of agile teams. Developed by and for practitioners in order to Agile software development, lean product development and systems thinking, SAFe can be very prescriptive in that they tell you exactly what to do.
In some instances, SAFe may be too prescriptive and not suitable for many large-scale agile projects; your organization will have to look to other approaches instead.
We’ve heard people say, “If it worked for one team, it will work for every team.” Agile scaling has multiple approaches based on the size and complexity of the project(s) or organization. We already covered SAFe, but below are other frameworks in which Agile can scale.
Kanban: Management method around the creation of products with an emphasis on continual delivery while not overburdening the development team. Like Scrum, Kanban is a process designed to help teams work together more effectively and is based on 3 principles:
LeSS: Provides two different large-scale Scrum frameworks: LeSS (Up to 8 teams of 8 people each) and LeSS Huge (Up to a few thousand people on one product). Most of the scaling elements of LeSS are focused on directing the attention of all of the teams onto the whole product instead of “my part.” Global and “end-to-end” focus are perhaps the dominant problems to solve in scaling. The two frameworks – which are basically single-team Scrum scaled up – are:
Scrum at Scale: Framework where Scrum team networks, operating consistently with the Scrum Guide, can address complex problems while creatively delivering products of the highest possible value. These “products” may be hardware, software, complex integrated systems, processes, services, etc., depending on the domain of the Scrum teams.
We’ve heard people say, “Agile practices just apply to the technology delivered.” Agile started as a way to better align the business and IT departments within organizations, but Agile scaling takes this emphasis on alignment even further. For teams to see the benefit, the non-IT department must adapt their practices and increase cross-organization collaboration. Frameworks like SAFe and LeSS can work for non-software but include a lot of software-specific considerations. Kanban, however, originated in the manufacturing industry and involved almost no technology teams.
Some reasons non-technical teams are choosing Agile scaling are:
Now that we covered different examples of Agile scaling frameworks and debunked some misconceptions, the next steps will be deciding which framework works best for your organization.
Get your fill on Agile scaling with our other posts in the series:
Whether your budget is based on the fiscal year, the school year, or the calendar...
It’s well over halfway through the year, and if you’re like most people, you set a fitness goal. Have you stuck to it? We know how hard it...