4 ms·
Projects fail for all kinds of reasons. Usually many reasons at the same time. While I am sure that _some_ fail because of the abject inexperience of the staff
by crispyambulance 8y ago
Projects fail for all kinds of reasons. Usually many reasons at the same time.
While I am sure that _some_ fail because of the abject inexperience of the staff running them, this is hardly ever the complete story. Moreover, projects do fail even with a fully experienced, fully vetted staff running the show.
The article just seems like a consultant marketing his acumen. There's nothing wrong with that. But keep in mind, he dropped in over a weekend and spent a few hours detailing problems that needed fixing and the staff subsequently made corrections and released on time.
It could easily go the other way too. The "inexperienced" team could have instead brought in another seasoned consultant who, after a few hours, got the wrong idea and led them down the wrong path precipitating an even larger slippage of ship date. THAT HAPPENS TOO and I suspect it is even more common.
- anyzen 8y ago> Moreover, projects do fail even with a fully experienced, fully vetted staff running the show. Sure - but in that case they usually don't fail because of technical decisions (which is what OP was talking about). There are however many other ways a project can fail (bad management mostly).
- HeavyStorm 8y agoI don't really agree. Sure, many projects fail for reasons other than developer experience but in many years of many more projects, developer skill was the most frequent reason. Of course, that's probably more true of my environment (third world country, enterprise software) than others.