7 Hábitos De Proyectos No Exitosos

IT & engineering

INSIGHT

Seven habits of unsuccessful projects
Understanding if you are in an out-of-control IT project is important. Here are some traits of failing or soon-to-fail projects.A
Dennis Brandl

It’s hard to stop a project, even when most project members know that there are major problems and no planned solutions.

‘

’

ONLINE
Search Brandl at www.controleng.comfor more IT & Engineering Insight.

s control engineers, we want to be well “in control.” Sometimes this is hard with a large software project. Software is difficult to view and understand duringthe development phase, and many projects can spin out of control without upper management even being aware of problems. Projects can be unsuccessful for many reasons; the most common is a failure to“reboot” the project when it is heading down the wrong path. It’s hard to stop a project, even when most project members know that there are major problems and no planned solutions. For managers, it isknown as the Gamble’s Dilemma: After spending $2 million on a project, it’s a difficult decision to stop it and restart, even if the final total cost will be less and actual time will be shorter.Understanding if you are in an out-of-control project is important. Here are some habits common to uncontrolled projects that might help you identify if yours is one. Few failing or soon-to-fail projectswill exhibit all of these traits. However, if your project has three of more, fix them before your project spins out of control. Or, consider “rebooting” the project with better controls. 1. Noarchitect or architect team. Without a controlling influence to keep a design on track, small changes will accumulate, too often leading down dead ends or to bad decisions. If you don’t know where you areheaded, then any direction seems like the right path. 2. No firm schedule. If no one knows the real schedule, or if the schedule seems to slip one week for every two calendar weeks, then the project...