Agile software development is not what it is intended to be

by Jeremy Berriault | Dec 12, 2019

What Happened to "Agile"? Returning to Its True Purpose

Agile software delivery originated as a means to enable teams to collaborate, adapt quickly, and deliver tangible value to clients. The original goal was simple: empower teams and focus on meaningful outcomes for users. But somewhere along the way, Agile lost its way. If you’ve seen the “Agile is Dead” video, you know what I mean.

The Original Vision—and the Detour

Robert C. Martin, a signatory of the original Agile Manifesto, has spoken out about this shift. Agile began as a set of principles created by software engineers, for software engineers. It was rooted in the realities of building great software through collaboration and technical excellence.
As Agile’s popularity grew, certification programs exploded. Suddenly, anyone could attend a two-day course, receive a certificate, and claim to be an Agile expert. This “siren song” of certification drew in project managers and business professionals—many of whom lacked deep software experience.

The Rise of Certification—and the Loss of Focus

With certifications came a new wave of leaders, often more focused on process and project management than on true technical mastery. The movement shifted away from its roots. Agile became about following checklists and rigid processes, rather than empowering teams and delivering value.
The core spirit of Agile—adaptability, technical excellence, and continuous improvement—got lost.

Bring Agility Back to Its Roots

Want to restore Agile to its original intent and make it work for your team?
Let’s cut through the noise, focus on what really matters, and build an Agile culture that delivers true value.
Reach out at jberriault@berriaultandassociates.com and let’s get back to what Agile was meant to be.

So according to Robert C. Martin, Agile was originally created for programmers by programmers. But it has now gotten off track. There is now a counter-movement that emerged after the split (when the original idea of Agile got tainted by thoughtless management). This counter-movement is Software Craftsmanship, and it has its Manifesto, too.

Apparently, it tries to go back to the original promise of Agile, which was, according to Kent Beck, to heal the divide between business and programming. It also strives to fix what Agile broke – namely, it urges developers to deliver not only “working software,” but also “well-crafted software.”

Visit Why software developers (quite honestly) hate Agile

As with any idea, there are some, where individuals will take it and manipulate it to what they want to see. As a result. Most of the time, it is a lack of knowledge on how it to work or outright negligence of following the guidance it provides. The full value is there, and it is within reach for organizations. Through training, collaboration and knowledge management, these values can be achieved.