Organizational debt can create technical debt and may be the single biggest cause.
Even if you make it with technical debt, somewhere in your org, someone's life is worse because of that technical debt, but the cause was probably organizational debt. The good employees see it sooner and suffer it longer or leave before others see it. A downward spiral in other words with entropy increasing.
Organizational debt can create technical debt and may be the single biggest cause.
I agree with this. E.g. an organisation without a clear and concrete vision (but with a lot of fantasy) is inherently creating technical debt since it's unclear to the developers what exactly needs to build and what the important parts are. It's usually that within these organisations every other week a new feature is dreamt up by management that HAS to be included asap or the company might miss out to the competition.
Usually management in these type of organisations also LOVE Agile which to them pretty much means; just make shit up as you go along.
This sound's like an application of Conway's law. Sometimes you make a bad technical decision because the "right" way involves to many political fights
Comments
Organizational debt can create technical debt and may be the single biggest cause.
Even if you make it with technical debt, somewhere in your org, someone's life is worse because of that technical debt, but the cause was probably organizational debt. The good employees see it sooner and suffer it longer or leave before others see it. A downward spiral in other words with entropy increasing.
I agree with this. E.g. an organisation without a clear and concrete vision (but with a lot of fantasy) is inherently creating technical debt since it's unclear to the developers what exactly needs to build and what the important parts are. It's usually that within these organisations every other week a new feature is dreamt up by management that HAS to be included asap or the company might miss out to the competition.
Usually management in these type of organisations also LOVE Agile which to them pretty much means; just make shit up as you go along.
Exactly on the vision and fantasy.
Worse on the consequence: lots of "new" features are TOP 1, and the last unfinished top 1 just been cancelled in its first week.
Agile though, those sprints are never called failed, but move on like nothing changed.
This sound's like an application of Conway's law. Sometimes you make a bad technical decision because the "right" way involves to many political fights
http://en.wikipedia.org/wiki/Conway%27s_law