> The difference between a user story taking a day or 3 days is negligible compared to its business value. Companies and their leaders care about revenue and costs. They care about customers and growth. They care about time to market.
Um, taking a day vs 3 days is huge. Because the cost of each task is now 300% of what it should be.
Time to market is also absolutely impacted by technical debt, for the same reasons.
Describing this to company leaders in ways they understand is pretty straight forward.
"If we take a week now to fix this problem, we will be able to do 3 times as much work in the same amount of time going forward."
Maybe delivering this feature in 3 days to the important client vs 8 days is important enough to put off the needed refactoring from a business perspective, or maybe not. But now the business leader has enough information to understand the tradeoff and make a decision.
> Describing this to company leaders in ways they understand is pretty straight forward. "If we take a week now to fix this problem, we will be able to do 3 times as much work in the same amount of time going forward."
I’d argue that technical debt that can be resolved in a week is not real technical debt.
And when you’re dealing with “real” technical debt, it’s hard to substitute numbers into that sentence without lying through your teeth. “It will probably take us a month to two months to fix this problem and in terms of product launches it’s completely ambiguous how much faster we’re going to be.” isn't nearly as easy of a sale.
Um, taking a day vs 3 days is huge. Because the cost of each task is now 300% of what it should be.
Time to market is also absolutely impacted by technical debt, for the same reasons.
Describing this to company leaders in ways they understand is pretty straight forward.
"If we take a week now to fix this problem, we will be able to do 3 times as much work in the same amount of time going forward."
Maybe delivering this feature in 3 days to the important client vs 8 days is important enough to put off the needed refactoring from a business perspective, or maybe not. But now the business leader has enough information to understand the tradeoff and make a decision.