This invites the question: what is the relationship between "technical debt" and the tragedy of the commons?[1]
Open Source doesn't exist in a pure Commons mode at the enterprise; there is usually a mix of open/proprietary code at stake.
The various methodologies (agile/waterfall/&c) seem to dance around a fundamental problem: people don't scale, prioritize, estimate, or react to inputs in any consistent way.
(Agile likes to assume an elite ninja cadre and enlightened customers--great, when one finds them.)
Nor does there seem to be an "answer" pending, except for with the marketing crew.
Open Source doesn't exist in a pure Commons mode at the enterprise; there is usually a mix of open/proprietary code at stake.
The various methodologies (agile/waterfall/&c) seem to dance around a fundamental problem: people don't scale, prioritize, estimate, or react to inputs in any consistent way.
(Agile likes to assume an elite ninja cadre and enlightened customers--great, when one finds them.)
Nor does there seem to be an "answer" pending, except for with the marketing crew.
[1] https://en.m.wikipedia.org/wiki/Tragedy_of_the_commons