If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
Article Series - Why Projects Fail
Software plans often lack common sense (and a) user focus
eWeek reports the FBI is likely to scrap their $170 million Virtual Case File software project. It's not the first big software project to fail, nor will it be the last. What I find interesting is the explantation offered by Eric Lundquist, editor-in-chief of eWeek, in the January 31, 2005 issue. Lundquist speculates (he says he doesn't have first-hand details) it is the compound effects of "too much turnover at the top management levels, too many promises of what the software would be capable of doing, and too little contact with the people who would use the software of a day-to-day basis. He sums it up as, "Software plans often lack common sense (and a) user focus.
We need a new common sense for developing and delivering projects of all types. I'll echo Lundquists speculations and I'll add a few of my own. Projects run well when the planning and execution are tightly coupled in a way that adapts to what the team is learning, innovating, and encountering. Call it agile or call it lean; either way, put the people performing on the project at the center of your concern when managing it.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=03314884-90d1-47e5-acf3-2821313e9fdc)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=4ce3f392-8989-448a-a97a-c1432dd3fce6)
{ 2 comments… read them below or add one }
Yes, we need a common sense for projects that tracks with, well, the way the world actually works.
That said, the FBI project sounds a lot more like a mostly-integration project, than a mostly-software project. That’s one step to common sense – talk about the project in terms of what’s in it. Human practices and humane project organizations help people talk about what’s really going on. It’s necessary, but not sufficient, however.
Building a new piece of software or configuring a package certainily need user involvement from day one.
In typical IT projects project management is done very tightly on MS project and the real human interaction issues cannot be tightly worked in so they fall out. Projects fail.
There unfortunately needs to be a level above project planning where the ultimate outcome is determined, measured and reported on. (not a program office type role) This is a more strategic role. This has to involve multiple stakeholders and manage expectations.
Even with that projects can still fail!!