3 ms·

> why oh why do we prioritise deadlines over productivity I feel this is a tradeoff between latency and bandwidth. Hitting a tight deadline (or Sprint goal) b

> why oh why do we prioritise deadlines over productivity I feel this is a tradeoff between latency and bandwidth. Hitting a tight deadline (or Sprint goal) by creating a bunch of technical debt delivers the feature we need today faster (lower latency). But at the expense of making features tomorrow more difficult to create (lower long-term bandwidth). I think it's OK to prioritize one over the other based on the business needs. But I think it needs to be an explicit decision and tradeoff, and I worry that too often managers choose low latency because they can feel it and see the results, and don't understand the tradeoff they're making.

doctor_eval 3y ago
Right, there are times when you need deadlines and you need to make decisions. Knowing what I know today, I would recommend cutting scope over technical debt, but that's beside the point really. My problem is where the whole project is managed based on deadlines rather than the flow of work. Deadlines kill productivity, but productivity = efficiency = saving money. The financial accounting for these things is complex, but considering most projects run late anyway, why even bother with deadline based management?