Transforming Myself Before Transforming the World: A Personal Take on Agile Transformation

I remember the first time I heard Rumi's quote,

“Yesterday I was clever, so I wanted to change the world. Today I am wise, so I am changing myself.”

It struck a chord with me, especially as I navigated my own Agile journey. At the beginning of this transformation adventure, I was all fired up, armed with frameworks and methodologies, eager to make everything around me better. I wanted to "fix" the teams, streamline the processes, and, frankly, revolutionize the way things worked. But, as many of us have discovered, the real world doesn’t always cooperate with our grand plans. I’d go into teams with a clear vision of how Agile “should” be done, only to be met with resistance, confusion, or zero-interest vibes. It was frustrating! I was following the book, the Agile manifesto, the frameworks—so why wasn’t it working?

It took a while, but I started to realize something crucial: I was so focused on changing others that I hadn’t really looked at myself. Was I truly embodying the Agile principles I was preaching? Was I being open, adaptable, and collaborative? Or was I just trying to get everyone else to follow a process?

I had the same “Boss Fight Moment” after one of the challenging retrospective. I was facilitating the session, trying to get the team to open up about their blockers and challenges. But the conversation kept hitting a wall. People were holding back, hesitant to share. And then it hit me: I wasn’t really creating a safe space for them. I was so intent on “doing” Agile—following the process, sticking to the script—that I wasn’t being Agile. I wasn’t truly listening or connecting with them.

That moment was humbling. I realized I needed to change my approach before expecting any change from them. So, I started small. I began sharing my own struggles and learning moments with the team. I opened up about my challenges with understanding Agile frameworks and how, despite all my knowledge, I was still learning. It wasn’t easy to show that vulnerability, but it made a huge difference. The team began to see me not as someone imposing a methodology on them, but as a fellow traveler on this journey. Conversations became more genuine, and slowly, trust started to build.

It was then that I truly understood the difference between “doing Agile” and “being Agile.” “Doing” was all about following processes, checking boxes, and sticking to the framework. But “being”—oh, that was a whole different ball game. “Being” Agile meant embracing the values and principles in every interaction, every decision, and every mistake. It meant being okay with not having all the answers and being willing to learn and adapt, just like I was asking my team to do.

I also learned the hard way that frameworks are just tools, not solutions. When I first started, I treated frameworks like they were magic spells. I thought if I could just get everyone to stick to the ceremonies and practices, things would magically improve. But that’s not how it works, is it? Frameworks provide structure, sure, but they don’t solve problems. People do.

This realization changed my whole approach. Instead of rigidly adhering to a specific framework, I started using them as flexible tools, adapting them to fit the unique needs of each team. I stopped being so hung up on whether we were “doing Scrum” or “doing Kanban” perfectly. Instead, I focused on whether we were fostering collaboration, transparency, and continuous improvement. Were we really living the values of Agile, or just going through the motions?

And let me tell you, when I started to shift my mindset, the results were amazing. Teams became more engaged. We started to have real conversations about what was and wasn’t working. We began experimenting, failing, learning, and then trying again. It wasn’t smooth sailing all the time—far from it. But those bumps and setbacks became learning opportunities rather than sources of frustration.

The biggest lesson I learned through all this is that true transformation begins with you. If you want to change the world around you, start by changing yourself. It sounds simple, but it’s powerful. When I started to live and breathe the Agile mindset—really embodying openness, curiosity, and adaptability—it had a ripple effect. Our teams picked up on it. They started to reflect those same behaviors and attitudes. It wasn’t about me teaching them Agile anymore; it was about us growing and learning together.

In the end, Agile isn’t something you do; it’s something you are.

It’s not about frameworks or ceremonies but about a mindset that embraces change, seeks to improve, and values people over processes. And yes, it’s an ongoing journey. I still stumble, I still get things wrong, but that’s part of it too. The important thing is to keep evolving, to keep updating that “software” version of yourself, so you’re ready to tackle whatever comes next.

So, if you’re on this Agile transformation journey—whether as a coach, a leader, or a team member—remember that the most significant change starts with you. Don’t just look at how others can be better. Look at how you can grow, adapt, and, most importantly, be Agile in your own way. The world around you will follow suit, one step at a time.

Growth happens when you stop planning for change and start becoming the change.

#Leadership #AgileTransformation #PersonalGrowth #ChangeManagement #Mindset #ContinuousImprovement