2 ms·
He prefaced this saying it might sound too obvious. My reaction was that it's a non-obvious but brilliant way to think about it. That was only reinforced as I c
by dahart 11y ago
He prefaced this saying it might sound too obvious. My reaction was that it's a non-obvious but brilliant way to think about it. That was only reinforced as I continued to read his reasoning.
Thinking this way acknowledges in advance that software is complex, it's more complex than you think it is, and any software project you start is likely to take longer than you think it will. Both sides of a software project or contract ought to know this and say it out loud before starting. More importantly, it underscores that a large software project nearly always starts under pressure. Rarely is something big and expensive undertaken without at least mildly unrealistic goals. Having been there many times, I know the management thinking is often that if we don't have pressure and forces squeezing every bit of developer performance toward unrealistic goals, then we won't even achieve the realistic goals, and we'll be even later than we are.
Contractors are probably most affected by and in need of this way of thinking, though I'm well aware of how hard it is to admit you might be late on something when you're trying to win a contract, especially when the competition makes impossible promises.