Agile delivery has hit a tipping point, with the majority of IT organizations finding some level of agile success. For these organizations, the next logical step is to scale this success into an "enterprise adoption", taking the value they are getting from a single team and replicating it.

This is often where it all starts to go wrong. Enterprise agile adoption is a large endeavor requiring changes to many processes and systems and adoption of new tools. Because of its size and visibility, it becomes a "strategic initiative" with large amounts of funding, plans, and oversight. Ironically, for the majority of these programs, it is done following a waterfall process with phase gates and deliverables. Activities like "Roll out JIRA" and "Train everyone on agile fundamentals" become the focus, with the agile adoption team is being measured on the number of people who become agile by getting the tools and having the training.

But isn’t adopting agile a complex problem? And, isn’t the whole reason why we have adopted agile to solve complex problems? Shouldn’t we approach the agile adoption in an agile way?

It is time to use agile to adopt agile. But what does that mean?

At the heart of all agile approaches and Scrum, in particular, are two concepts: Firstly, an empirical approach through inspection and adaption. This means that instead of breaking the work into activities, teams instead focus on outcomes and deliver on that outcome, incrementally. Sprints or iterations are the motion to execute on those incremental experiments. Daily Scrums, Sprint Reviews and Retrospectives are tools used to focus the team on inspection and adaption. Secondly, inspired by Lean Thinking, is the idea of empowered, self-organizing teams who can get work done. In practical terms, this means allowing teams to do anything necessary, within reason, to execute on their goal without any constraints of job role, authority level or even location.

Applying those concepts to scaling agile means:

This does not mean that the shift to agile will be easy or that issues such as lack of empowered product owners, no access to legacy test environments, and legacy system integration issues will magically disappear. But, by focusing on an empowered change team who uses an empirical process to incrementally roll out agile, organizations will be much more likely to improve and see change vs. measuring metrics that don’t always lead to value.

Also, this simple approach highlights the fundamental shift to agility, which is a movement away from relying on process and systems to resolve issues and integrate work to a team-centric approach with a lightweight model for improved transparency. With this approach, even if the organization does not become agile, at least everyone knows what happened and has the experience to prove it.

Dave West is CEO and Product Owner with Scrum.org. He is a frequent keynote at major industry conferences and is a widely published author of articles and research reports, along with his acclaimed book: Head First Object-Oriented Analysis and Design, that helped define new software modeling and application development processes. He led the development of the Rational Unified Process (RUP) for IBM/Rational. West managed Ivar Jacobson Consulting for North America. Then as VP, research director Forrester research. Prior to joining Scrum.org he was Chief Product Officer at Tasktop where he was responsible for product management, engineering and architecture.