Cool undocumented feature
I hate it when I don't have time to blog. I'd like if I could tell you what I've been doing, but let's leave it at this: I am enjoying…
I hate it when I don't have time to blog. I'd like if I could tell you what I've been doing, but let's leave it at this: I am enjoying…
It’s a well known fact that IT projects fail every so often. Standish Group has been researching the success and failure factors of IT projects for a decade and a half, and they publish their results in their CHAOS report every two years or so. According to their 2006 report, only about 35% of projects can be categorized as successful, while 65% are declared unsuccessful. In this report, word unsuccessful can mean anything from exceeding time and/or budget (46% of projects) or failing altogether (19% of them). With such a huge proportion of projects going astray, maybe there was something wrong with these projects from the very beginning. Were the time and budget unrealistic? Were the project requirements, or even objectives, unrealistic? Maybe. Or maybe not. How can you tell?