[albertopv]

> Only the developers can decide when a feature is ready

It's the business that pays the wages. Also, time to market is most important (for everyone but Apple), coming later with a better product often doesn't mean a viable business. Problem is almost nobody is promoted for maintaining or improving an existing product, no C-level is interested in tech debt management/reduction, anywhere.

[freilanzer]

> It's the business that pays the wages.

It's the developers who do the work.

[Lutger]

Everybody does the work. For an enterprise, its administration or HR who actually pay the wages. The business certainly doesn't, they think up the model and the features, the business problems.

I find this whole thing very confusing, there are no factions actually and everybody contributes, and has more or less the same outcomes as their ultimate interest. Maybe not the shareholders. Those truly don't do any work at all, but extract value out of the work done by those who are paid a wage. They only bring in capital.

The real reason developers should be able to mandate when something is 'good enough' is because it is their expertise, just as 'the business' decides what features should be build (those that solve a business problem). Just like a medical doctor decides on the treatment and not the manager of the hospital.

While pumping out features or 'solving business problems' brings in the money, security risks can, at its worst, instantly terminate the whole business. But developers don't want the company to go bankrupt because they spend a year eliminating every risk. Similarly product people won't like their company to die because they squeezed out an extra hour or two out of the sprint by avoiding any security work. A serious enterprise is, or should be, concerned with risks as well as 'velocity'.