A Rolling Stone Gathers No Pat

I did not learn Agile in a classroom—I learned it on a hill.

Before that, I worked in long cycles: build something, hope it worked, and deal with the consequences later. Then came the stone. Each day I pushed it up. Each night it rolled back down. No completion. No recognition. Just repetition. At first, I resisted; I wanted a plan, an endpoint, a definition of done. But the hill offered none of that. It offered something more honest: immediate feedback and the certainty that I would have to try again tomorrow.

So I changed my approach. I stopped trying to finish the work and started improving how I did it. Each push became a small experiment. I adjusted my movement, refined my path, reduced wasted effort. The work didn’t change, but I did. That’s when real progress began. Iteration replaced frustration. I wasn’t completing the task; I was getting better at it. And over time, what felt like punishment became predictable, even manageable.

Then people started watching. I gave the work meaning, invited them to participate, and turned repetition into ritual. Soon, they were pushing the stone themselves. The system no longer depended on me, it could sustain itself. That’s the truth most people miss: Agile isn’t about finishing. It’s about building something that improves as it continues. I didn’t escape the hill. I optimized it, monetized it, and then walked away.

The hardest part of anything is starting. But once you have to commit, and you commit fully, you can create ownership - and ownership is something you can transfer.

Keep pushing until you create something