Amidst all the “Agile is dead” we see nowadays in LinkedIn, I decided to take Agile from a more positive light on this episode and retrieve from my mental archives moments that made this whole Agile journey worthwhile.

You know, those moments when everything aligns perfectly and flows so naturally it feels almost effortless. When frameworks stop being something you "do" and becomes something you simply "are." These are the moments that remind me why it wouldn’t have worked better any other way.

Let me share two personal stories that capture these moments perfectly!!!

Many years back, as I stepped out from a contracting gig, I found myself joining this local Hong Kong startup that was teaching computer programming to kids. Imagine: energetic 8 to 15 year-olds learning to code as after school activity while their parents watched nervously from the side, hoping their little ones are the next Bill Gates or Steve Jobs. That was a big expectation 🙂

The mission was inspiring on its own but the technical challenge was real. We needed a “App Store” platform that could be updated quickly and reliably and often on the fly. Kids being kids, they would find the most creative ways to break things or demand features that required immediate platform adjustments. Getting flooded with requests like "Why can't my picture be edited with filters?" or "Why are my App downloads still zero?" were my routine as CTO and Programming instructor at this startup.

Back to when the magic happened, given my focus on fast quality checks and even faster on-demand deployments, I built something beautiful, a codebase and CI/CD pipeline so reliable, that literally allowed me to update and deploy code while sitting in a taxi, heading to deliver a class.

I'm in the back of a Hong Kong taxi with the startup founder, traffic crawling at its usual pace, when I get a message from one of the instructors who was already at the venue where we would deliver the class. "Hey, the kids want to add sound effects to their App screenshots slideshow, but the current version doesn't have it. I know you were working on this last week, do you think we get this in before the next class starts in 30 minutes?"

In the old times, this would have been impossible and I would have said no right away. In an Agile world? I simply pulled out my laptop, picked up the latest code from github, made the code changes, ran our automated test suite (which completed in under 3 minutes), and deployed the update; all while watching the city pass by through the taxi window. By the time I walked into the school, the kids could have access to sound effects for their app slideshows.

This wasn't just about technology as it wasn't anything new or groundbreaking; it was about trust (in the quick feedback loops), and true agility (adapting to changes quickly). I knew I could respond instantly to feedback and fully trust it would work. The App store platform could evolve as fast as the students' and the startup needs. But more important than anything else, I was delivering joy, visible joy, to kids who were discovering the magic of programming and could also understand the impact of what I was doing.

Another beautiful thing? It even influenced the teaching curriculum and the parents started noticing too. Instead of seeing a rigid and static curriculum, they saw a responsive, adaptive learning program that actually fulfilled their children's curiosity.

Now, let me take you to a completely different dimension, the regulation-heavy universe of insurance in Singapore. I was brought in to help a traditional insurance company that was struggling with what they called "slow time to market." They were delivering features, sure, but the value to customers (their agents) was getting lost somewhere in the black holes of process and handoffs.

The initial assessment was quite telling. "We need to ship faster," one tech lead said during our first meeting. "Our competitors are launching new products every quarter, and we're still working on things we started planning last year."

As I was digging deeper, I realized speed wasn't really the problem. They were actually delivering at a decent pace (monthly). The real issue was that agents, the ones using the app for selling insurance to their customers weren't seeing or benefiting from these features quickly enough. There was this massive gap between "feature delivered" and "value realized."

Here's where the magic happened. Instead of just focusing on delivery speed, I changed the conversation to time to value. I started asking different questions: "How quickly can a agent actually be ready to use this new feature?" and "Are we being measured by number of features delivered or by achieving business outcomes?"

A simple yet big change for such a traditional organization was that I suggested to align teams around agents (and business) outcomes rather than siloed departmental teams. Started implementing feedback from customer research that connected directly to real user experiences which meant effectively on-boarding users to adopt the new features and not just relying on real-life trainings. On top of that, prioritizing features was not just by business value, but by how quickly that value could be realized by their agents too.

The change was visible and fast to notice. Not only did their release frequency increase slightly along the way but the agents started seeing and benefiting from new features faster than ever before. They went from a roughly 3-month average time-to-value to under 4 weeks.

The real magic was observing the Agency transformation where Product managers began measuring success by customer adoption, not just feature completion, which in turn led to increase in their business outcomes.

My friends, that's when you know Agile really works.

Reflecting on these experiences and many others like them, I've noticed common ingredients that create these moments:

In the two stories, everyone understood not just what they were building, but why it was important. The kids' programming startup knew they were creating joy and learning opportunities. The insurance team knew they were making agents' lives easier and more effective.

Magic happens when people feel trusted to make decisions and act right away. Whether it's deploying code from a taxi or prioritizing features based on customer feedback, teams need the autonomy to respond to what they learned.

In both stories, we shifted from measuring outputs to measuring impact. It wasn't about how many features were shipped or how many lines of code were written, it was about value created for real people.

The magic accelerates when learning cycles are short and feedback is as fast as immediate. Whether it's kids asking for sound effects and using a reliable CI/CD pipeline or agents struggling to use a new feature, the faster you can sense and respond, the more magical the experience becomes.

None of this magic can work without solid technical practices. Automated testing, continuous integration, and reliable deployment pipelines aren't just "nice to haves". They are the foundation that makes magic possible.

In both environments, people felt safe to try new things, make mistakes, and learn quickly. The kids' programming startup could experiment with new teaching approaches and App store features, and the insurance company could test different ways of delivering value.

When one team experiences this kind of flow and alignment, it spreads. Other teams start asking: "How can we work like that?"

At the kids' programming startup, the magic spread to the whole company, who started using similar rapid-feedback approaches for any kind of work done. At the insurance company, other departments were inspired and tried, in their own ways, adopting customer-outcome thinking in their own work.

Most importantly, these moments create believers. People who experience true agility become its most passionate champions and advocates. They felt what it's like when everything clicks, and they want to recreate that feeling again and again.

The truth is, you can't force magic. But you can create the right conditions where it's more likely to happen:

Start with a clear, compelling purpose. Make sure everyone understands not just what you're building, but why it matters.

Invest in technical excellence. Magic requires a solid foundation. You can't be agile if your deployment process takes three weeks and breaks half the time.

Shorten your feedback loops. The faster you can learn from real users, the faster you can create value that matters.

Empower your people. Give teams the autonomy to make decisions and respond to what they're learning.

Measure what matters. Focus on outcomes and impact, not just activity and output.

Create psychological safety. People need to feel safe to experiment, fail, and learn quickly.

These magic moments aren't one-time events, they shown what's possible when Agile principles are truly embraced.

Whether you're updating code in a taxi to delight kids learning to program, or transforming how an insurance company delivers value to customers, the magic happens when technology, people, and purpose align in service of something bigger and meaningful.

What are your magic moments? When has Agile just clicked for you or for the teams you worked with?

I'd love to hear your stories!