Unlock your organisation’s full potential with Advanced Product Delivery

Get In Touch

The term “Agile” has been widely adopted and, as a result, often misunderstood. As someone who has worked deeply with Agile frameworks for years, I’ve seen the evolution of Agile from its early collaborative days to a term that, in some ways, has become almost contaminated. This is why I and many professionals at APD (Agile Product Development) prefer to use the term “Empirical Value Delivery” instead. Let me explain why.

The Dilution of “Agile”

Agile’s Early Days: Collaboration and Innovation

Back in the mid-1990s, Agile frameworks emerged from a period of intense collaboration among pioneers. These innovators shared ideas, debated methods, and used conferences to explore how Agile could transform the way we work. The core concept of Agile was simple: do something, get feedback, and improve. It was a mindset of continuous learning and adaptation.

As Agile grew in popularity, the results were undeniable. More and more organizations wanted to adopt Agile, which led to its wide-scale implementation. However, this surge in interest came with challenges that diluted the effectiveness of Agile.

Large Organizations and Misguided Agile Implementations

When large organizations began adopting Agile, they often did so without truly understanding its core principles. They sought to implement Agile quickly and efficiently, but they didn’t always grasp what made it work. Executives weren’t fully committed to the values of Agile, which left impediments unresolved and old control structures in place.

This is where things started to go wrong. Large organizations poured huge amounts of money into Agile adoptions that ultimately failed. Why? Because Agile was treated like a checklist rather than a philosophy. People were hired who didn’t deeply understand the values or principles behind Agile, and the focus was more on “doing Agile” rather than delivering value.

  • 🛑 Executives kept old control structures
  • 🛑 Impediments weren’t removed
  • 🛑 Agile became a mechanical process
  • 🛑 Feedback loops were ignored

Why Empirical Value Delivery is a Better Approach

The Problem with Agile for Agile’s Sake

When organizations try to implement Agile just to say they are “doing Agile,” they miss the point. Agile isn’t the goal—delivering value is. Whether you’re using Scrum, Kanban, or any other Agile framework, the goal is to deliver something valuable to the customer and then get feedback.

This is why I prefer the term “Empirical Value Delivery”. It’s rooted in empiricism, a principle that Ken Schwaber and Jeff Sutherland (the creators of Scrum) wrote about in the Scrum Guide. Empiricism is all about transparency, inspection, and adaptation. In simple terms, it’s about getting something done, showing it transparently, inspecting the results, and adapting based on feedback.

  • ✔️ Transparency: Be open about what’s being delivered and how
  • ✔️ Inspection: Regularly check if you’re on the right track
  • ✔️ Adaptation: Make changes based on feedback

Focus on Value, Not Frameworks

Too often, organizations focus on Agile frameworks as ends in themselves. But no one should be doing Scrum just to do Scrum. The point is to deliver value. Frameworks like Scrum, Kanban, or XP (Extreme Programming) are just tools to help you achieve that.

If you’re doing Scrum and it’s not delivering value to your customers, then it’s time to re-evaluate. Don’t stick to the framework just because you were told to. Use feedback loops to adjust and improve.

  • 🟢 Deliver value: Focus on what benefits your customer
  • 🟢 Get feedback: Use that feedback to improve your product
  • 🟢 Adapt: Be flexible and willing to change course

The Pitfalls of Mechanistic Agile

Unfortunately, with the influx of people into the Agile space who didn’t understand its core principles, mechanistic Agile became a common problem. By this, I mean the unthinking execution of frameworks. People started doing Agile just to check a box, rather than truly engaging with the values behind it.

This led to watered-down practices like:

  • 🛑 Half-hour daily standups that lacked focus
  • 🛑 Teams ignoring accountabilities
  • 🛑 No real value being delivered
  • 🛑 Impediments left unresolved
  • 🛑 Organizational challenges being swept under the rug

When Agile is implemented without a deep understanding of its purpose, it doesn’t work. It’s not enough to just follow the mechanics of Agile—teams need to understand the why behind the practices.

The Empirical Value Delivery Mindset

Reframing Agile as Empirical Value Delivery allows us to get back to what really matters: delivering value and using feedback to improve. At APD, we emphasize this mindset with all of our clients. It’s about getting things done, getting feedback, and then changing the systems within your organization to support more effective value delivery.

When you adopt an empirical approach, you may surface some uncomfortable truths about your organization. And that’s a good thing.

Unearthing Organizational Problems

In my experience, the clients I’ve worked with who have been most successful in their Agile transformations are those who embraced the tough phase of unearthing systemic problems. When you bring in empiricism—when you start focusing on transparency, inspection, and adaptation—you’ll begin to see the cracks in the system. It’s these cracks that need attention.

  • 💡 Transparency reveals issues that were previously hidden
  • 💡 Inspection shows where processes or systems are failing
  • 💡 Adaptation means facing those problems head-on and resolving them

This is how true agility works. It’s not always easy, but it’s necessary if you want to see real, lasting change.

The Role of Values in Empirical Value Delivery

Agile isn’t just about practices—it’s also about values. Scrum values like commitment, focus, openness, respect, and courage play a huge role in making Empirical Value Delivery successful. Without these values, your organization is likely to revert to old habits.

Ask yourself:

  • ❓ How are you using these values in your organization?
  • ❓ What does transparency mean to you?
  • ❓ How are you encouraging openness and respect within your teams?

These values are the foundation of an empirical approach to value delivery, and without them, your Agile transformation is likely to falter.

Conclusion: Why Empirical Value Delivery is the Future

In a world where the term “Agile” has been stretched thin and sometimes misunderstood, reframing the conversation around Empirical Value Delivery helps organizations focus on what really matters: delivering value to customers.

If you want your Agile transformation to succeed, don’t just follow the mechanics of a framework. Instead, adopt a mindset of transparency, inspection, and adaptation, and focus on delivering value to your customers. It’s tough, but it’s worth it.

  • ✔️ Focus on value, not frameworks
  • ✔️ Embrace transparency and feedback
  • ✔️ Resolve organizational challenges
  • ✔️ Live the values of Scrum

By doing this, you’ll not only deliver more value to your customers, but you’ll also build a more resilient, adaptable, and successful organization. 🚀 Let’s get to work.

Latest Post

Call Us Today!

Call us today to discuss how we can drive your success forward

+44(0)77 3751 6521