=?windows-1252?Q?Re=3A_Can=27t_live_without=85?=

I like to use the term "evolutionary development" for APL-systems
deveopment rather than the established "plan the whole thing first" ..
and then execute !

It is normally in the planning stages ( of STD IT dept. development )
than things go wrong.
The analysts and project meaders are normally too far away from the
nitty-gritty, which means that once the programmer ( or "coder" in the
STD IT sense ) starts to get right down to the code-level, he/she may
discover ( and normally does ) that there is something either :
a) wrong
b) could be done better
c) could mean a complete rethink of the plan
d) simply not feasible

I've seen this happen so many times .. which if often why your STD IT
project gets delayed .... again and again !
.... and often get abandoned later !

I knew one project manager ( and many more of his ilk ) that was
actually proud to have 50 projects under his belt.
The only problem was, that all these projects were "newly initiated
projects" to "patch" the mistakes, lack of forethought and/or simply
ignorance of the subject matter in the initial planning stages of the
system.
They called these "strategic projects" ... as if they were fighting a
"war" and all these mini-projects were the individual "battles".
Needles to say, his budget was in 100's millions $ .. and that was
just for java and C developers !
Sheesh !