Skip to main content

Is it Time to Evolve Beyond the Agile Manifesto?

July 30, 2016

If this post resonates with you, please consider spreading the message so we can educate and inspire the entire professional world together. I invite you to ‘Follow’ my professional journey through LinkedIn and Twitter.

 

~~~


The colorful wall posters are ubiquitous in organizations small and large. And I bet most of us are keenly aware of the 2001 Agile Manifesto and can recite the 4 value statements and 12 principles of Agile software development with supreme clarity. Sometimes compared to the Declaration of Independence, many cherish it as the timeless artifact that ultimately spawned the Agile transformation movement. Over the years, I've relentlessly referred to it and have respectfully challenged organizations to learn from 15+ years of wisdom embedded within the Manifesto.

From 2001 to 2016 - Where are we now?

Fast forward to 2016 and you'll see that we're in a much different place than 2001. The pursuit toward Enterprise Agile and scaling is an industry buzzword and was a major theme at this year's Agile Alliance conference. With Agile2016's attendance at 2,500 strong, the learning and cross-industry collaboration was at an all-time high.

As a conference participant, I used the week as an opportunity to exchange learnings and experiences with Enterprise Coaching peers, as well as other leaders and practitioners across this vast space of "Agile" and Scrum. Through various conversations during the week, the following two themes emerged for me:

 

 


  1. Large Enterprises continue to share many of the same opportunities & challenges.

  2. We agree that a principles-first approach toward Enterprise Agile is essential for the most effective adoption of processes, practices and tools.



  3.  
  4.  


In short, a guiding set of organizational principles helps adapt processes and practices in an organization's context while successfully moving the Agile needle in a meaningful direction.

That said, I invite us to ponder the following provocative question:

 

 

 

 

 

 

 

 

Are the principles in the 2001 Agile Manifesto still relevant in 2016?


 

The mid-week keynote seemed to offer a compelling and potentially polarizing answer. Joshua Kerievsky's talk on Modern Agile focused on the evolution of Agile and our need to keep pace via an adapted set of guiding principles. Here is a picture showing the 4 broad principles from the 2001 Agile Manifesto (left) and the proposed 4 principles for Modern Agile (right):

Manifesto to Modern Agile

 

In his keynote, Kerievsky postulated that the Agile Manifesto was relevant when drafted in 2001, but in present-day, Agile has evolved far beyond its original intentions...rendering the original principles as outdated. What do you think?

This keynote article summarizes Kerievsky's message, so I invite all of us to learn and draw our own conclusions. For those who weren't at Agile2016, this amazing visual summary captured the essence of his talk (credit: Lynne Cazaly):

Modern Agile Visual

 

How do you make Modern Agile real in your organization?

Like the original Manifesto, there is a vast body of knowledge under the covers - including theory & science, thinking tools, practices and skills that must be understood, adopted and mastered in your organization's context. However, without professional safety as a prerequisite, I might suggest that none of this stuff will work for your organization. In short, the 4 principles of Modern Agile are easy to understand .... but extremely difficult to master (just like Scrum) - especially at the size and scale of our largest global enterprises.

How long have we been asking this question?

This question has been posed for a number of years now, most recently at last month's Agile Europe panel discussion, and dating back to Steve Denning's May 2011 Forbes article entitled: Applying "Inspect & Adapt" To The Agile Manifesto. Even The Scrum Guide eats its own dog food by publishing carefully-crafted revisions every few years. But it was intriguing and provocative to see this question reinvigorated yet again on the big stage of Agile2016. So, what's next?

In Closing

I'm not smart or wise enough to predict the future of the Agile movement, but I do feel that now is the time for many larger organizations to figure this out if they want to continuously deliver valuable outcomes and effectively compete in their industries.

 

 

~~~~~~


Is it time to host a well-earned retirement party for the Agile Manifesto and align toward Modern Agile? Where should Lean principles be considered? I invite all of us to engage with this post by sharing your views in the comments section below.

 

 

 

 


What did you think about this post?

Comments (7)


Rick Crawford
12:37 pm August 4, 2016

This may be setting up a false dichotomy.

The values in "modern agile" are more general and hence useful if you want to apply agile in a non-traditional (e.g. non-software or larger-scale) context.
The principles in the agile manifesto are (slightly) more concrete and so more easy to apply, if we are trying to apply them in the context for which they were designed.

In the near future, "modern agile" may get more attention than the manifesto, as people seek to apply agile in new contexts, but the manifesto will still be very useful in the context for which it was designed, which will still exist.


Rick Crawford
02:10 pm August 4, 2016

Then again... saying "modern agile" is more general doesn't capture all the differences. That basically just applies to the red boxes. For example, I'd say that valuing responding to change over following a plan is pretty critical to agile, and it is only partially covered by "experiment and learn quickly".


Rick Crawford
02:52 pm August 4, 2016

Even outside software, the "modern agile" values, as presented, will often be less useful than the agile manifesto. The manifesto tells you what to value over what. i.e. it describes a trade off - one that is common but often ignored - and then tells you which way to go when you find yourself faced with that trade off. The "modern agile" values don't do that. We may agree with making people awesome, but what is the trade off here? Why are we not making people awesome already? Unless you can identify the trade off, it is hard to apply these values.


TH
10:15 am August 18, 2016

"Make people awesome"? Seriously? I mean that doesn't mean anything. otherwise it's just rewording some sentences to make it even more ambiguous. Doesn't sound modern to me.


DigitizedKris
07:39 am August 19, 2016

Really? The Agile Manifesto was always about values - someone far brighter than me actually described it as a social contract which I've always liked - and that is still as relevant today as it was in 2001. Perhaps the 12 principles could do with a little tweak (like release frequency) but they are still in pretty good principles IMO. And please, don't conflate the rituals of methodologies like Scrum with the manifesto.


Alan Larimer
01:17 am August 20, 2016

While I appreciate the intent, some of it feels like generic corporate rah-rah posters. "Make people awesome" is the worst offender. "Deliver value continuously" does not provide much more than its predecessor. "Experiment and learn rapidly" is a great idea yet replacing the previous value leaves the door open for the plan-driven monster to rear its head again.

"Make safety a prerequisite" is marketing gold. That is possibly one of the most challenging aspects of self, team, organizational inspection and adaptation. Most "agilists" have probably experienced environments where honest and constructive feedback is not welcomed, appreciated, acknowledged, discussed, and acted upon. It is a great ideal; one that can be extremely difficult to bring to life.

I would be interested in a discussion to compare and contrast Modern Agile with Alistair's Heart of Agile.


Maja Könninger
08:45 am May 15, 2018

In my opinion sticking to the pinciples of the agile manifesto does make sense. Of course, applying strictly without leaving any space for improvement or flexibility doesnt lead to the desired results. Im an employee of Zenkit, a young start-up which developed a project management tool. Implementing agile methodology is an important topic in our company. To dive deeper into the agile manifesto, I suggest to take a look at the article we´ve recently published https://blog.zenkit.com/unc... Really looking forward to hear your feedback.