5 ms·
Nothing, inherently, except perhaps the fallacy of comparing a pair of jeans to the rather chaotic and unpredictable world of bespoke systems development. One
by danielbarla 7y ago
Nothing, inherently, except perhaps the fallacy of comparing a pair of jeans to the rather chaotic and unpredictable world of bespoke systems development. One is inherently known (a pair of jeans you've presumably already manufactured), the other is one big unknown, basically.
- ellius 7y agoAircraft, hospitals, hotels — a million complex bespoke things are built every day. Cost and time projections are inevitable.
- marcosdumay 7y ago> Cost and time projections are inevitable. As inevitable as blowing through the projections.
- commandlinefan 7y agoRight. You can imagine a conversation something like: "Ok, how long is this project going to take?" "Well, it's still being defined..." "What do you mean you refuse to tell me how long this project is going to take?" The analogy is so ridiculous that the person making it clearly doesn't even comprehend the domain he's discussing.
- ben509 7y agoHe compared to jeans because they're an extremely trivial purchase that someone would give little thought to, but still demand to know what they cost. The point is that in all cases you need that information, with a major software project you simply need it far more.
- commandlinefan 7y ago> you need And that's the core of the problem (which, ironically in the context of the article, agile methodologies were supposed to address): wanting or needing something to be true/exist doesn't make it so.