SQLServerCentral Editorial

Failed IT Projects

,

https://www.marinis.name/intro/Blog/Entries/2008/8/26_A_Failed_project_files/shapeimage_1.jpgYEA.

Yet another explanation for why projects fail in IT.  This one tries to look at behavioral economics, and the irrational behavior that people engage in. We aren't extremely logical beings that pursue profit or self-interest in a completely rational manner.  At least, I don't think we are.

Many people would probably like to think that they are as logical as Mr. Spock, but the truth is that we rarely are. We aren't the Economic Man, acting as efficient agents for our own self interest, but nor are we simple beings overly influenced by advertising, context, or any other method of presenting us with choices. We are somewhere in between, and more complex than any type of analogy that is used to model us.

IT projects fail for all sorts of reasons. To a large extent I believe that we really don't understand exactly how we should build software, and highly underestimate the complexity. I think building software is like building a business, and that's not a simple task. If it were, then most businesses would succeed and not fail. I do think that software is an immature industry and we have a lot to learn about how to better manage our work. I think that like businesses, we have so many opinions, so many ideas on what is important, and on what works well. I think this variety of ideas is often combined with inexperienced management and project management, resulting in projects that don't move forward in a well-engineered manner.

Microsoft has done an amazing job, from my perspective, with engineering SQL Server. At a time when it seems that many large software projects, including Windows, regularly run late, Microsoft has moved to a well engineered, consistent, release-every-18-months cycle. After SQL Server 2005, the next 2 releases have been on a well defined schedule, and been successful. There are bugs, and things I'd do differently, but the products have been well managed and well developed as software projects. I have every reason to believe that SQL 11 will release around 18 months after R2, sometime in late 2011.

We can get better, and I hope many of us will, but I think it requires not only more professional habits and skills from developers, but also from managers.

Steve Jones


The Voice of the DBA Podcasts

Everyday Jones

The podcast feeds are available at sqlservercentral.mevio.com. Comments are definitely appreciated and wanted, and you can get feeds from there. Overall RSS Feed:

or now on iTunes!

Today's podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

You can also follow Steve Jones on Twitter:

Rate

You rated this post out of 5. Change rating

Share

Share

Rate

You rated this post out of 5. Change rating