
"For decades, software people have warned that the later you make a change, the more expensive it becomes. Many of us have seen this expressed as a steep curve: changes are cheap early in a project, but become dramatically more expensive later-especially after release. This curve has been influential. It has shaped how teams plan, how managers manage, and how organizations justify heavy upfront analysis."
"Boehm's work in the 1970s and 1980s helped define modern software engineering economics. His research was serious, credible, and grounded in the types of projects that were common at the time. Software was expensive to build. Tools were primitive. Integration was painful. Testing was often manual. Deployment was slow and risky. If you discovered a major requirement change late, you might be looking at months of redesign, recoding, and retesting."
"The problem isn't that Boehm was wrong. The problem is that we treated his findings as if they were timeless. Boehm gave us a snapshot. Over time, we turned it into a law of nature. The curve hasn't disappeared, but it's far flatter than most people assume."
The cost-of-change curve, popularized by Barry Boehm's research in the 1970s-1980s, warned that modifying software becomes exponentially more expensive later in projects. This principle shaped planning, management, and organizational practices for decades. However, the curve's validity has diminished significantly. While Boehm's observations were accurate for his era—when software was expensive to build, tools were primitive, integration was painful, and deployment was risky—the modern development environment has changed dramatically. Contemporary tools, practices, and methodologies have substantially reduced the cost differential between early and late changes. The curve remains relevant but is considerably flatter than most practitioners assume, reflecting how technological advancement and evolving development practices have transformed software economics.
#cost-of-change-curve #software-development-economics #agile-practices #technical-debt #modern-development-tools
Read at Mountaingoatsoftware
Unable to calculate read time
Collection
[
|
...
]