2 ms·
To me, the _real_ thing that matters isn't quite date or budget, but something that somehow acts as an umbrella to both of them: the promise. When you promise t
by youknownothing 7mo ago
To me, the _real_ thing that matters isn't quite date or budget, but something that somehow acts as an umbrella to both of them: the promise. When you promise to deliver something by a day, or within a budget, it's very clear whether you met your promise or didn't. However, when it comes to functionalities, there is more of a grey area: you can start to argue that something _mostly_ works, that some bugs are always inherent, or that this functionality actually is not really needed because the problem can be fixed in an operational way, or that the requirements have changed, or that it was just a nice-to-have... but money/time don't have this grey areas.
- evilantnie 7mo agoI feel like everyone in this reply chain is looking at this from a different angle of Fast, Good, Cheap. Pick two.
- tharkun__ 7mo agoThat was literally the first thing I thought reading from OP comment down to your parent. Then I thought: Sure but management made the devs promise these things. We don't do it of our own volition (exceptions prove the rule - some people are conditioned to do it of course).
- elliotec 7mo agoExactly. The old Iron Triangle. One of the three will always be most important depending on the constraints. Two of them will be possible.