"For past 5 years, Release 1.0 is consistently projected to be 24-32 months away." I have worked on project like this. Usually it's the sign of management fai

"For past 5 years, Release 1.0 is consistently projected to be 24-32 months away." I have worked on project like this. Usually it's the sign of management failure (poor communication, poorly defined requirements, bad governance, inability to retain knowledgable employees) rather than technical feasibility. It's not like the software is pushing technical boundaries. "Echoing McKinsey, Gershman said that without a strong leadership element, IT projects of this magnitude are almost doomed to fail from the start." This is a big problem. Because employees know these problems will fail, the smartest avoid them like the plague.