Re^2: Musings: Why do well-intentioned projects go so wrong, so often?

in reply to Re: Musings: Why do well-intentioned projects go so wrong, so often?
in thread Musings: Why do well-intentioned projects go so wrong, so often?

I'm with you on this one. My corp is always saying that we need a complete set of requirements to start the work.

I couldn't disagree more. As soon as you have enough requirements, you should start and then start iterating through solutions. What's "enough"? I'd leave that up to the lead developer.

--
I used to drive a Heisenbergmobile, but every time I looked at the speedometer, I got lost.

Comment on Re^2: Musings: Why do well-intentioned projects go so wrong, so often?

Replies are listed 'Best First'.
Re^3: Musings: Why do well-intentioned projects go so wrong, so often? by chromatic (Archbishop) on Dec 04, 2007 at 16:49 UTC
My corp is always saying that we need a complete set of requirements to start the work. If you had a complete set of requirements in detail sufficient to describe the problem to solve in its entirety, you would already have the complete source code to the software.	[reply]

In Section Meditations