AT#33: Why we need a new Agile Manifesto

AT#33: Why we need a new Agile Manifesto

AT#33: Why we need a new Agile Manifesto

The Agile Manifesto, created by seventeen guys from the field of software engineering eighteen years ago has certainly changed the way we create software solutions fundamentally and radically. The great majority of software development projects is done using agile practices like Scrum. Today, everybody knows the famous “we value X over Y” statements:

In recent years, ideas for scaling agile to a company-wide scope (eg, SAFe ©) and approaches to the “agile organization” have become increasingly popular. Nowadays everything needs to be “Agile”,

a clear sign that we are at the “peak of inflected expectations” (to speak with Gartner’s hype cycle).

Everybody inventing a “new” agile approach refers to the Agile Manifesto as the fundament.

But how can a Manifesto that has been created with the focus on software development for single solutions be a solid fundament for enterprise-wide agility?

The simple answer: it can’t.

What is missing? Values that are mandatory to scale Agile. The existing agile manifesto is solution focused but not enterprise-aware. This might be one reason that emerging practices for scaling Agile (like SAFe@, LeSS, Nexus,…) and the “agile organization” are still immature, success stories rare.

 

Suggestions for an Agile Manifesto 2.0

In his “Disciplined Agile” approach, Architectural Thinking Associations’s Leadership Team member Scott Ambler suggests a “Disciplined Agile Manifesto“. It is the basis for the Manifesto extensions we discuss  in this blog. Sentences in italic are quotes to the Disciplined Agile Manifesto:

1. Sustainable Solutions, not just software. Where the original manifesto focused on software development, a term which too many people have understood to mean only software development, DA suggests that we should focus on solution delivery. In short, we prefer solutions (software + hardware + supporting documentation + business process + organization structure) over just software. Solutions should be sustainable, which means that their business value is maximized from an enterprise-wide and long-term viewpoint.

2. Stakeholders, not just customers. Where the original manifesto focused on customers, we suggest that we focus on the full range of stakeholders instead. We prefer stakeholders – end users, operations people, sustainment people, audit, finance, and many more – over just customers. Last, but maybe most important: the enterprise as a whole must be treated as a customer.

3. Malleable Plans, not just responding to change. We agree that responding to change is mandatory in today’s volatile surroundings. But with General Dwight D. Eisenhower: “In preparing for battle, I have always found that plans are useless, but planning is indispensable” we believe that “malleable” plans are better than purely ad-hoc agility.

4. Enterprise-awareness over point solutions. We believe that following the current Agile Manifesto and its focus on the “end-user” blindly leads to point solutions that can be a catastrophe from an enterprise-wide viewpoint on the long-term. Business people should adopt an architectural thinking mindset and become aware of the dependencies with other business units. Lean business architecture models should be the basis for all strategic decisions.

 

And this is what a new agile manifesto could look like:

If you want to discuss and co-create a new Manifesto with us, please feel free to contact us at office@architectural-thinking.com

Previous Posts:

AT#17: Architectural Thinking – the Success Factor for Scaled Agile

AT#10: Technical Debt – the ignored Killer of “Agile” Enterprises

AT#8: Agile goes awry when loosing Balance between Speed and Sustainability

Please spread the Ideas of Architectural Thinking!
LinkedIn
Facebook
RSS
SOCIALICON

Comments are closed.

close

Please spread the Ideas of Architectural Thinking!