The Agile Daily Standup - AgileDad
Original podcast
Where to listenCopy share link
AI Is Changing The Economics of Software Development - Mike Cohn
996 words · 1 speaker
Everyone knows I love receiving email from Mike Cohn, and this week is no exception. He starts out, "For decades, we repeated a warning in software development. The later you make a change, the more expensive it becomes." Many of us learned this from Barry Bone's famous "Cost of Change Curve." Based on research from the 1970s and 1980s, it showed a steep rise. Changes were cheap early in a project, but dramatically more expensive later, especially after a release. In that era, the curve made perfect sense. Let's pause.
Mike, I was a little tight in the 70s and 80s. So I don't know that I remember that as well as you do. No, I think we're about the same age. I'm just picking on you. Software was expensive to build. Tools were primitive, testing was manual, integration was painful. A late requirement could mean months of redesign, recoding, and retesting. Late changes really was disastrous. But here's the issue. We've treated that curve as timeless. It wasn't a law of physics, it was a snapshot of how software worked at the time. And the economics of software have dramatically changed. The curve has been flattening for decades. Long before Agile became mainstream, the cost of change was already falling.
IDEs, integrated development environments, made coding and debugging dramatically faster. Automated tests and continuous integration reduced the fear of breaking things. Modular architectures reduced ripple effects across systems. Each of these flattened the curve a little more and a little more. Then Agile came along. Agile didn't magically make change cheap. It recognized that change was becoming affordable and built a way of working that leveraged that change. Kent Beck captured it perfectly with the subtitle of his book, "Extreme Programming", which explained "Embrace Change."
That statement was not motivational fluff. It was an economic claim. If we can keep the cost of change low, we can learn continually. Short iterations, customer collaboration, refactoring, backlogs, and backlogs instead of fixed master plans. All of these reduce the penalty of being wrong. And guess what? AI is the flattening of the curve again. Now we're seeing another shift. AI assisted development tools are reducing the time required for humans to write and revise code. This may sound simple, but it really isn't. When coding gets faster, experimentation gets cheaper. Trying an idea is cheaper. Revising an idea is cheaper. Throwing away an approach and trying something different is cheaper.
AI is making code feel less construct, less like construction and more like revision. And when that happens, the bottleneck shifts. The cost of change becomes less about writing code and more about waiting for feedback. In other words, the primary cost of change increasingly becomes feedback delay rather than development effort. But there's part that hasn't gotten cheaper. Understanding the users is still hard work. Product discovery is still hard work. Organizational decision making is still hard work. The hard part hasn't disappeared. It just moved. It shifted. For decades, we acted as if coding was the hardest part of software development. That's no longer true. Today, the hardest part is often figuring out what to build and learning whether it works or not.
But once we have feedback, acting on it now is cheaper than ever. That's the key economic shift. So what does this mean to you? Great question. Many organizations still operate with approval process designed for a world where late change was catastrophic. In many companies, the slowest part of delivery isn't the coding. It's waiting for the permission. Yet the cost of change has fallen, and it has. Then the biggest risk isn't changing too late. The biggest risk becomes learning too late. Requirements don't need to be perfect. They need to be revisable. Locking them down early may reduce change, but it increases the risk of building the wrong thing. So yes, do discovery. Think carefully.
Understand your users, but don't over invest in trying to get everything right upfront. Modern software development rewards adaptability more than accuracy. If you still fear change, you may be managing like it's 2005. Stop trying to make perfect requirements. Instead, perfect your feedback loop in order to succeed with Agile. Mike, this is one where I respectfully agree and partially disagree. Let's talk about it for a second. The part that I agree with is that I do believe the cost of change is reducing 100%. But what I'm seeing in organizations is that they are trying to make assumptions way too early and going through that loop over and over and over again. Is this the rock you were looking for? Is how about this one? Is this the rock? Is this the rock?
What they don't realize is they're standing on a pile that has 1,734,323 rocks and a few pebbles. The point I'm trying to make is it sometimes it's easier to gain a preliminary understanding of what you're trying to do before you dive in. So you don't spend time going through each and every one of those rocks trying to figure out which one's the right one. However, I do understand what you're saying. In the same vein, don't wait so long to get everything perfect in your requirements that you don't deliver anything. Figure out what you feel the customer needs, confirm that it's true in discovery and get to work. As long as you're not cycling on the hamsterware where you feel like you're constantly busy, but not delivering anything of value, then I feel like there's great value in what you
describe. Mike, as always, thank you for the wonderful email. If you have a topic you want us to discuss or if you want to send me an email, reach out to us, [email protected]. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well and stay agile, my friends. Until next time, do take care. Bye now.
Page updated November 6, 2026 · transcript and summary are machine-generated