sábado, 20 de fevereiro de 2016

sexta-feira, 19 de fevereiro de 2016

On software project failures

Software projects fail a lot. And since software is on most modern equipments (read carefully: almost everywhere) most equipments will also fail when running faulty software produced by some of those projects. This is one of the reasons current systems (meaning hardware + software) will also fail a lot.

How much do software projects fail? It's an interesting question and here are some possible "answers":


The latter study, published on Dr. Dobbs (which is now inactive BTW), criticizes the CHAOS report. On any case, a good percentage of projects fail and / or are challenged (they do not meet the on-quality, on-budget, on-schedule initial criteria). Just look at the trailer, I mean, just look at the numbers.

Welcome home!

Of course this is not your home. It is mine! So keep off the fence. Except if you want to learn a little bit more on software development.

Some of us reading this have already been through software development projects. Projects are projects: Each one of it is special (if it weren't they would be called "product deployment", "services", or something alike). Bespoke development (i.e. custom-made) has to address a number of... "challenges" of almost any kind. So in reality you are out in the wild. And if you don't take the proper measures you«ll probably get bitten, In time (and with experience) you'll learn what does this means, and most of the times the harder way (more on this also later on).

So why not learn a little bit more on process(es) so that you go along the road a little bit more aware and informed?

If you've reached this final line, you're good: You probably are willing to learn a little bit more. Keep on reading. Here or elsewhere,