Re:How real-world corruption works
by jerf on Wednesday May 26, 2010 @11:35AM
(#1380515)
The truly fundamental flaw is deeper than that. The fundamental flaw is that the bid process is intrinsically built on one party making a future commitment of results. It is impossible to actually commit to future results; there's too many confounding factors, which I really shouldn't have to list to anyone here. This impossibility is the foundation of the system. When you put something impossible at the foundation of the system, the entire rest of the system chokes and bends around it in a most distressing way.
As notauser correctly observed before I could beat him/her to it, this is virtually identical to the way most of our jobs work. Management asks for commitments of dates and times, and the mere fact that this is literally impossible does not stop them. I am not kidding or being metaphorical about that "impossible", I mean it literally. And they do have their reasons, but the mere fact they have reasons does not prevent the entire system from getting horrifically distorted as it builds itself around the impossible primitives, producing the nonsensical and nonfunctional results we are all familiar with.
The really, really, really key insight of Agile is to reduce the amount of impossibility built into the base of the system, and the smart Agile-using engineering team lead will take every advantage of that they can. Unfortunately, Agile really only works when all sides are capable of cooperating; it can survive internal-type rivalry, but where everyone is still in the same company. I can't imagine how to make Agile work in the face of hostile agents, which is what this contract situation is.
Re:How real-world corruption works
by eru on Wednesday May 26, 2010 @09:00PM
(#1382333)
If you can give a probability distribution instead of a fixed time, you may be able to make the commitment less pathological. Of course, as time goes on, the standard deviation of your distribution should go down, since more and more is known.
As notauser correctly observed before I could beat him/her to it, this is virtually identical to the way most of our jobs work. Management asks for commitments of dates and times, and the mere fact that this is literally impossible does not stop them. I am not kidding or being metaphorical about that "impossible", I mean it literally. And they do have their reasons, but the mere fact they have reasons does not prevent the entire system from getting horrifically distorted as it builds itself around the impossible primitives, producing the nonsensical and nonfunctional results we are all familiar with.
The really, really, really key insight of Agile is to reduce the amount of impossibility built into the base of the system, and the smart Agile-using engineering team lead will take every advantage of that they can. Unfortunately, Agile really only works when all sides are capable of cooperating; it can survive internal-type rivalry, but where everyone is still in the same company. I can't imagine how to make Agile work in the face of hostile agents, which is what this contract situation is.