Jeffrey Phillips talks about him belonging to the prototype-oriented quick and dirty camp rather than the flesh-it-all-out-as-you-go camp.

Where I think Jeffrey fell off the sled a bit was the "dirty" part. What he describes as the benefits of his innate approach (failing early and learning from it rather than failing late) is almost synonymous with risk-driven, incremental development. That is, he could be talking about pretty much any agile method.

Except that he said "dirty."

It's easy for organizations to jump on the agile bandwagon and get all the benefits of quick-and-dirty. It takes a more thorough understanding of the discipline and craftsmanship needed to go beyond quick-and-dirty and into the realm of truly sustainable agile development. The world of quick-and-clean.

Yes, adopting agile methods in certain environments can be harder than you'd hope. You're surrounded by people who don't really understand what you're doing and why, even though you've tried to explain them more than once. Perhaps the most dangerous moments of the adoption journey is when those people think they get it but have really gotten it slightly wrong, sometimes leading to failure. Like in this case.

:)