Your vote matters here! Login and vote now.
By mswatcher
via srtsolutions.com
Submitted: Jul 22 2008 / 11:50
It's been repeated so often that now it's not even questioned: Software projects fail not because of technology missteps, but because of 'business issues'. That's a catch all phrase for misunderstanding business needs, implementing the wrong features, or poor resource management.
But like so many items that have become conventional wisdom, this one is also only right some of the time. Sometimes projects fail because of technical issues. Like every other profession, there is a bell curve of skills and abilities. Some developers (and architects, testers, and designers) just aren't real professionals, and don't follow a professional software development practice of any sort.
In particular, our business, SRT Solutions, often helps companies whose primary skill is not software development. It's in whatever





Comments
paul_houle replied ago:
Huh? An unclear article.
What exactly is a "Technical Reason?" Because the developers were unskilled? (Failure of the hiring process?) Because an inappropriate technology was chosen for implementation (Uhhhh... Isn't that decision part of the process?)
Voters For This Link (1)
Voters Against This Link (1)