I love this post! These days, “agile” seems to be the buzzword everyone is throwing around—teams, services, and operations all need to be “agile.” But when you scratch beneath the surface, it often feels like just the “right” thing to say, rather than something truly practiced. After all, who would admit to using “waterfall,” the supposed bad word of project management?

At a recent conference, a colleague and I laughed about how often people claim to use agile methods, only to describe processes that are clearly sequential and waterfall in nature. So, what is agile? As the post highlights, it’s not about sprints, Kanban boards, or any other artefacts. Agile is a mindset—a way of working that focuses on delivering value to users as quickly as possible. That is why you have sprints because you want to deliver value at the end of the sprint.
The agile mindset also embraces failure as a necessary step in the process. It’s about learning fast, iterating, and embedding those lessons to create something valuable—quickly.
Instead of just saying “we’re agile,” I’d love to see more people showing what agile means to them in action. Let’s move past the buzzword and truly start being agile.
Are you and your team “agile”?


