3 ms·
> as determined by data--including analysis of the performance of features, market conditions, and other factors What would be refreshing are internal ROI dash
by 0x445442 7y ago
> as determined by data--including analysis of the performance of features, market conditions, and other factors
What would be refreshing are internal ROI dash boards for each project and group instead of just technical dash boards.
On almost every project I've worked on this data is not available and there's never any real evidence presented to the practitioners for things such as tech stack or process decisions. Typically, it's just a bunch of assertions, hand waiving and requests of trust.
- BlueTemplar 7y agoUltimately, we might be running into the issue that the impact is spread over time and cannot be condensed into a single ROI number ?
- TheOtherHobbes 7y agoImpact is spread over time and multiple vectors. So now you have three problems in addition to getting working code the door - prioritising proposed features based on estimates of value, finding accurate metrics for assessing value after release, and mapping value changes over time. The nice thing about feature-driven-development is that it avoids the hard work of having to understand what you're actually doing. You can make the hamster wheel spin really fast and persuade yourself you're really going places. Until the wheel falls off.
- 0x445442 7y agoI have no data to back this up but I'd say the majority of projects I've worked on during my career my time would have been better spent working on things that made the development teams more efficient. That is to say, with rare exception, I don't think the software actually generated anywhere near the benefit it cost to develop and maintain.