Scaling agile in large organizations | Atlassian (2024)

Why are companies scaling agile?

Today, businesses need to be able to adapt, at enterprise scale, in order to stay competitive. The means to do so: responding to customers' evolving needs and delighting them in the process, providing flexible/customizable solutions, supporting teams of teams working on a unified front, shifting mindsets to place technology as a strategic enabler, and inspiring agile ways of working outside of software and IT teams.

But without a clear-cut plan or framework, it’s increasingly harder for companies that are scaling to predict delivery, manage cross-team dependencies, and focus on the right business objectives.As a result, this often leads to a decline in customer satisfaction, loss of market share or revenue, and more.

All of this is prompting companies to invest heavily in agile – to either capture the benefits of scaling agile frameworks that their software teams might have seen or to remain competitive in today’s market. But while large enterprises all might agree on the need for scalingagile frameworks, how to do it and what it looks like is a completely different discussion.

So, what is agile at scale?

Agile at scale is the ability to drive agile at the team level, while applying the same sustainable principles, practices, and outcomes at other layers of the organization.

Scaling agile frameworks is a cultural transformation, where the business’ people, practices, and tools are committed to improving collaboration and the organization’s ability to execute against its strategy.

Ultimately, changes across these areas will help decentralize decision-making, create greater transparency and alignment around work, and increase speed to market, all while hard coding the values of agile into the DNA of the organization.

Where are you on your agile at scale journey?

We like to chart how far along an organization is in its journey of scaling agile frameworksby looking at how teams and individuals are adopting agile practices.

Organizations at the beginning of their journey may only have pockets of people practicing agile, and work may be dominated by traditional project management procedures focused on managing a project from conception through to delivery.

Organizations that are further along may have scaled agile practices in play (or even the use of a framework). This may prompt cross-functional teams to organize in a way that improves efficiency, keeps them laser-focused on the value they deliver, and helps them navigate change by empowering them to make proactive decisions thathelp meet their businessobjectives.

No matter where you find yourself today, acknowledge and respect your position, and start from there.

Popular frameworks for scaling agile

There’s no right way to scale agile. But many organizations have had great success evolving their processes, teams, and cultures using frameworks for scaling agile.

Here’s a brief overview of the top agile scaling frameworksframeworks to explore:

SAFe

The Scaled Agile Framework® (SAFe®) is a set of organization and workflow patterns for implementing agile practices at enterprise scale. It was formed around three primary bodies of knowledge: agile software development, lean product development, and systems thinking. SAFe promotes alignment, collaboration, and delivery across large numbers of agile teams.

LeSS

Large-Scale Scrum (LeSS) is essentially regular scrum applied to large-scale development. LeSS is based on the idea that scaling frameworks should be minimalistic (i.e. include less rules, roles, and artifacts) to drive success. However, both LeSS and SAFe share some common patterns: Scrum at the team level, many teams sharing a backlog, collaborative planning across multiple teams, along with the general principles of pull and self-organization that any smaller agile team may be familiar with.

DA

Disciplined Agile (DA), previously referred to as Disciplined Agile Delivery (DAD), is a learning-oriented process decision framework for IT solution delivery. It provides a solid foundation from which to scale agile solution delivery within enterprise-class organizations. DA utilizes scrum and kanban, along with transformation knowledge in areas like HR and finance, governance, DevOps, portfolio management. and more. DA is often considered more flexible and easier to scale than other methods.

Spotify

Spotify’s approach wasn’t meant to be a framework per se, but the organization’s take on agile has organically emerged as one. The Spotify model is a people-driven, autonomous framework for scaling agile. It stresses the importance of culture and networks and provides an example for dealing with multiple teams in a product development organization.

Scrum@Scale (S@S)

Scrum@Scale is an extension of the scrum framework. Scrum@Scale is generally adopted by organizations that have already implemented scrum successfully at the team level and are looking to spread it throughout the organization. The main goal is to align growing organizations around one common and shared set of goals. Coordination is managed through a Scrum of Scrums, which is comprised of Scrum Masters from each team, and a MetaScrum made up of product owners.

Understanding the difference between agile scaling frameworks

Scaling agile frameworkscan add unnecessary processes when they’re applied without thought or intent. But codifying shared rituals, common roles, and guiding principles for scaling agile in your organization has clear benefits, especially when the organization is new to agile ways of working. Here’s a helpful resource to guide your understanding of how each framework applies in these key areas.

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Long term planning and strategy

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Multi agile teams

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Team of Teams

SAFe (Scaled Agile Framework)

Agile Release Train (ART)

LeSS (Large Scale Scrum) & LeSS Huge

Area

Spotify

Tribes

DA
(Disciplined Agile)

Scrum@Scale

Scrum of Scrums

PM/PO

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Scrum Master / Agile Coach

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Release Engineer / Group Manager

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Agile practice (scrum, kanban, etc.)

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Demo

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Retros

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Customer driven / value focused

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Dependency management

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Strategy transparency

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Portfolio management

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Release on demand

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Risk Management

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

DevOps

SAFe (Scaled Agile Framework)

LeSS (Large Scale Scrum) & LeSS Huge

Spotify

DA
(Disciplined Agile)

Scrum@Scale

Processes: Defined and prescribed Defined with recommendations Not clearly defined

As you can see, when examined closely, these agile scaling frameworks incorporate common organizational patterns involved in scaling agile. Regardless of whether or not you adopt a framework, we believe that by adoptingsome or all of these core patterns, you can reap many of the benefits of scaling agile in your organization.

7 essential principles for practicing agile at scale

While we acknowledge there isn’t any one-size-fits-all approach to scaling agile frameworks, there are seven essential principles for practicing agile at scale, which should be considered. These principles are “must-haves,” meaning, it'll be near impossible to be successful without them.

Regardless of whether you plan to use a framework or simply some practices,consider the below as guiding principles for what can be borrowed or formalized in your own organization.

  1. Defined roles and organizational structure changes
  2. Customer-centric organization and development
  3. Agile/scrum practices and cadence
  4. Adoption maturity (Take time to change)
  5. Dependency improvements
  6. Bottom-up & top-down buy-in (Actually change)
  7. People, Lean, and systems thinking

For more details on these principles and what they look like in practice, jump to our “Beyond the basics of scaling agile: the new rules to transformational agility” whitepaper below.

So, where to begin?

Scaling agile is not easy, and won’t happen overnight! Whether your organization goes all-in on a scaled agile framework, or implements a homegrown process, remember that “agile at scale” is not the end goal. The end goal is to effectively execute your strategy.

Keep trying new ideas and making incremental improvements with this aim in mind.And, don’t forget that the tools you use to support your business can play an important part in scaling agile.

A key component of agile is open and consistent communication. At Atlassian, weshare projects and goal updates and discover what other teams are working on. By building a shared understanding of the context of work, we know what’s being worked on, why, who’s working on what, and the progress of work.

For a deeper dive into the topics we’ve covered on this page, check out our “Beyond the basics of scaling agile: the new rules to transformational agility” whitepaper. Packed full of helpful information and anecdotes from experienced agilists, it’s definitely worth a read.

Scaling agile in large organizations | Atlassian (1)

Beyond the basics of scaling agile

Ensure your organization’s agile practices are built to last

Download our whitepaper to learn the new rules to transformational agility.

Download the whitepaper

For more details on how Atlassian can support you on your agile journey, visit our agile at scale solutions pageorcompare the features of our agile at scale products.

Scaling agile in large organizations | Atlassian (2)

Josh Berman

Josh is a Product Marketing Manager on Atlassian’s agile at scale solutions team. When he’s not writing about agile best practices you can find him hiking the greenbelt in Austin, Texas.

Scaling agile in large organizations | Atlassian (2024)

FAQs

What is the main issue when agile is scaling to large systems? ›

Scaling agility presents significant challenges in coordinating multiple teams. Agile methods assume a single, focused team, but in a large enterprise with multiple or geographically dispersed teams, the coordination of efforts can become complex (Leffingwell, 2007).

Why is it difficult to scale agile software development methods for use in very large software projects? ›

The prominent challenges are a lack of testing strategies, chaos in sprint execution and deadlines, ignoring coding standards, and requirements scoping. By being aware of these challenges, projects in similar contexts may better synchro- nize their activities and reap the benefits of agile at large-scale.

Is agile good for large scale projects? ›

Agile methodologies are often best suited for small, cross-functional teams and may be less effective when applied to large, complex projects with multiple teams and stakeholders.

Which of the following are frameworks for scaling agile in a larger organization? ›

Answer. Scrum of Scrums and Disciplined Agile Delivery (DAD) are two frameworks for scaling Agile in larger organizations. Scrum of Scrums facilitates cross-team coordination, while DAD provides strategic guidance for iterative delivery that can be applied to complex enterprises.

Why agile fails in large organizations? ›

When there's a lack of overall organizational support or unwillingness by team members to follow Agile principles and values, it likely will fail. It's also likely that your Agile team will need to intersect on projects with non-Agile team members.

What are five key considerations for scaling an agile project? ›

Let's examine each scaling factor one at a time:
  • Team size. Teams can range in size from two people to twenty to two hundred or more. ...
  • Geographic distribution. ...
  • Organizational distribution. ...
  • Skill availability. ...
  • Compliance. ...
  • Domain complexity. ...
  • Solution complexity.

Why does scaled agile fail? ›

Scaled Agile Framework confines team members to their specific roles, not giving them much flexibility or freedom.

Why do people hate Scaled Agile Framework? ›

SAFe, or the Scaled Agile Framework, is a methodology for managing large-scale software development projects. While some people find it to be a useful tool for coordinating complex projects and aligning teams, others have criticized it for being overly prescriptive and inflexible.

What is the most used scaling method for Agile? ›

SAFe® – Scaled Agile Framework

It is based on Lean and Agile methods' pillars, and has become one of the most popular agile approaches, together with Scrum.

Why is scaling Agile important? ›

Scaling Agile offers the ability to clearly and consistently see how ARTs or teams of teams are delivering, measure their progress, and gauge the financial impact of their work.

Can large Organisations be Agile? ›

Established corporations can achieve organizational agility, so long as they approach it as a mindset rather than a process.

What is the agile scaling strategy? ›

Scaling agile frameworks is a cultural transformation, where the business' people, practices, and tools are committed to improving collaboration and the organization's ability to execute against its strategy.

What is large scale agile transformation? ›

In short, it is a large agile digital transformation project aiming to digitize daily work tools, to modernize project management in a more agile mode and to improve team collaboration.

What are the choices of large scale agile frameworks? ›

So, let's get you clear on the most important characteristics of SIX frameworks for scaling your agile adoption.
  • Scaled Agile Framework (SAFe) ...
  • Scrum@Scale (SaS) ...
  • Large Scale Scrum (LeSS) ...
  • Nexus. ...
  • Disciplined Agile (DA) ...
  • Enterprise Kanban, aka Portfolio Kanban.
Jan 10, 2024

Which of the following is the true challenge when scaling agile projects up to a larger size? ›

Iteration length.

The challenge of implementing shorter iterations may be one of the biggest challenges in scaling Agile to build larger, more complex software systems.

What are some basic barriers to introducing agile methods into large companies? ›

20 Common Challenges When Introducing Agile (And How To Overcome Them)
  • Resistance To Change. ...
  • Lack Of Clarity About What Agile Is. ...
  • Reluctance To Empower Team Members. ...
  • The Need For Robust Daily Communication. ...
  • Taking The Team's Focus Off The Customer. ...
  • The Comfort Of 'Going With The Flow' ...
  • Insufficient Support From Leaders.
Dec 6, 2023

Why is it difficult to apply agile PM to large scale projects? ›

Complexity: Large-scale projects tend to be more complex than smaller projects, and therefore, require more planning, organization, and management. The larger the project, the more difficult it is to manage changes that can come from the adoption of agile practices.

Top Articles
Latest Posts
Article information

Author: Jeremiah Abshire

Last Updated:

Views: 6122

Rating: 4.3 / 5 (74 voted)

Reviews: 81% of readers found this page helpful

Author information

Name: Jeremiah Abshire

Birthday: 1993-09-14

Address: Apt. 425 92748 Jannie Centers, Port Nikitaville, VT 82110

Phone: +8096210939894

Job: Lead Healthcare Manager

Hobby: Watching movies, Watching movies, Knapping, LARPing, Coffee roasting, Lacemaking, Gaming

Introduction: My name is Jeremiah Abshire, I am a outstanding, kind, clever, hilarious, curious, hilarious, outstanding person who loves writing and wants to share my knowledge and understanding with you.