I'm not really sure this argument makes sense. Plenty of software I've built is finished, it does the thing I need it to do and I haven't touched it in years. Adding features just because is not a useful way to spend anyone's time, doubly so in a business context.
> Adding features just because is not a useful way to spend anyone's time, doubly so in a business context.
You could make this statement about anything. "Building a new hospital wing just because is not a useful way to spend anyone's time", "Adding an extra drive-thru lane just because is not a useful way to spend anyone's time". The point is that it's not "just because", it's because you believe it can grow your revenue.
On the other hand, if you don't believe that, then don't invest. Nobody's saying you have to. If you think my comment is saying that, you've misread it.
> You could make this statement about anything. "Building a new hospital wing just because is not a useful way to spend anyone's time", "Adding an extra drive-thru lane just because is not a useful way to spend anyone's time". The point is that it's not "just because", it's because you believe it can grow your revenue.
You can, but do you really need the same sized team to add an extra lane to a drive-through as you needed to build the entire restaurant's building, kitchens, etc?
Do you need the same sized team to add a new wing to a building as the team that built the existing building(s)?
Hospitals expand because they either already don't or they project they won't meet demand. It's the same story with drive-thrus. These are things that are measured and analyzed. Adding features in the blind hope that more features equals more revenue is exactly how companies stagnate and burn. There's plenty of successful software products out there that are finished as far as the feature set goes, you'll find they power most of the industries outside of IT.
