Immediately after reading the article struck me as too short. From personal experience I know that these problems have more detail and can be discussed thoroughly. After second thought though I realise that the actual problem is very simple: Either invest in quality work and reap the benefits soon ([weeks, not months](https://martinfowler.com/bliki/DesignStaminaHypothesis.html)), or skimp from the start and get stuck in costly software development.
I see many teams still so stuck in the old (yes, really old) ways that I fear we haven't even started making a dent into simple things like more frequent feedback loops....
I have to admit that, over the years, I have changed my "sales message" or "pitch message" away from emphasizing code quality, craftsmanship, and software engineering, due to the constant "push back" from most conventional leaders and peers. Instead, I emphasize that agile, done well, cuts costs and delivers business value (increased revenue, reduced costs) sooner and more reliably. These are things they claim to care about. But everyone seems to demand the results, *without* making the investment needed to achieve them. Well, who wouldn't want to receive such great benefits? And get them "for free?" But one must be "adult" and "mature" enough to do the hard work and make the investments necessary to achieve those results. And that's where I find things to be lacking.
Immediately after reading the article struck me as too short. From personal experience I know that these problems have more detail and can be discussed thoroughly. After second thought though I realise that the actual problem is very simple: Either invest in quality work and reap the benefits soon ([weeks, not months](https://martinfowler.com/bliki/DesignStaminaHypothesis.html)), or skimp from the start and get stuck in costly software development.
Why do you think this shift happened Bob?
I see many teams still so stuck in the old (yes, really old) ways that I fear we haven't even started making a dent into simple things like more frequent feedback loops....
Am I missing something?
My point in writing this, Vasco, was that I'm seeing many teams/organizations moving on from some of the "good, old practices."
Point being, not everything old is bad.
Engineering practices, quality practices, and design/architecture practices being amongst some of the best agile practices.
I have to admit that, over the years, I have changed my "sales message" or "pitch message" away from emphasizing code quality, craftsmanship, and software engineering, due to the constant "push back" from most conventional leaders and peers. Instead, I emphasize that agile, done well, cuts costs and delivers business value (increased revenue, reduced costs) sooner and more reliably. These are things they claim to care about. But everyone seems to demand the results, *without* making the investment needed to achieve them. Well, who wouldn't want to receive such great benefits? And get them "for free?" But one must be "adult" and "mature" enough to do the hard work and make the investments necessary to achieve those results. And that's where I find things to be lacking.