Why Waterfall Doesn’t Work
When building software over long release cycles, developers may not see code run until months after it’s written. They might build a “testing harness” so their code can be reached in a debugger (software that lets you detect bugs in other software) and stepped through one statement at a time, but this is not the same as running the code in the way it’s meant to be run in the context of the whole system.
This is one of the main problems with batching features up into releases. It may make a lot of intuitive sense to batch things up. This is how we construct things. If you’re building a house you want to get everything you need to build the foundation over to the job site so you won’t have to stop that step waiting ...
Get Beyond Legacy Code now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
