Adopting Agile using Waterfall

Something that bothers me, is when organizations go out to adopt Agile, but try to do it using traditional program management or waterfall methods. “It’s the only thing they know” – you might say. But if it is, how are you doing the adoption? You have to have Agile coaches or Scrum Masters or Agile practitioners. Someone who knows how Agile works. And why wouldn’t you ask them to organize the adoption.

If you see value in adopting Agile, why not do it correctly? And if you don’t, and treat it as a fad – just don’t do it. Or better yet, let those that want to, do it and let it grow and spread organically. Otherwise, you’ll alienate both the practitioners as well as those that don’t want to change.

Is this just an anti-pattern of “those that can’t do, teach”?

(Note: I do say anti-pattern. I’ve had many amazing teachers throughout my life).


Why I’m not pumped today

In a couple of hours, I’ll be teaching a class on Kanban. I should be pumped – I mean it’s expected from a trainer, right? But I’m not.

Why? It’s a “mandatory” class.

At the risk of sounding like a zealot, I’ll admit that I find Agile not dissimilar to religion. Sure, you can force people to come to the temple/church/stand-up, follow the rituals, repeat the prayers/three questions/etc, but unless the people believe in what they’re doing, it’s for naught.

The way to convince people, is to show through your own life/work that these practices make a difference, make you happy, make it easier to achieve your goals. And when they see it, they will want it for themselves.

Hey, maybe if I’m pumped, I’ll convince some of my audience.