@byllgrim@mastodon.xyz No kind of stupid; you're absolutely right. In most process usage, waterfall means strict waterfall, i.e., one pass, but it's disingenuous in all other process models to say, "We don't do waterfall.". Waterfall is the description of how software development works in a perfect world. All the other processes try to describe how software development works in the real world.
The reason there are heated process arguments is management. (More in next post)
@byllgrim@mastodon.xyz Management of software development is a whole different subject matter from actual software development. Processes often mix these two domains, which then results in bad process.
Even in the face of good process, bad mangers can ruin the process' reputation, which is pretty much what happened to waterfall. Most developers know iterations will occur to fix errors made, but bad managers won't allow reentry, "We're done with that stage! Don't you know how to do software?"
