Computerworld - Discussions with project managers about the key causes of failed and challenged projects always raise two primary issues: half-baked or harebrained ideas becoming projects, and excessive scope creep.
Traditionally, senior management is charged with conceiving ideas that will drive the organization toward profitability and industry leadership. Hence, there is immense pressure on executives to deliver innovative ideas that can be turned into products and services for profit and competitive advantage. Unfortunately, these visions are often intertwined with any number of half-baked and, at times, harebrained ideas. When half-baked and harebrained ideas get communicated to them, many project managers don't object because of a culture of not questioning the senior people. The general thinking is, "How could they be wrong?"
Another big contributor to failed and challenged projects is the inevitable scope creep. We all know that at times customers can be unreasonable and unrealistic in their expectations, but they're also subject to external pressures they can't control -- government regulations, competitive positioning, emerging opportunities and the classic "silver bullet" syndrome, also known as Management by Magazine. (This occurs when the customer reads an article on an airplane while 35,000 feet over Kansas and forms a new vision.)
But forcing the team to agree to continuous scope creep is clearly not the solution. And you get hit with a double whammy when projects are built around half-baked ideas. A half-baked idea that turns into a project with extensive scope creep is a nightmare.
What can project managers do to minimize these problems? Simply stated: Learn to say no.
Of course, project managers may feel that they don't have the ability or wherewithal to say no and that their only option is to do as they're told, even though they know that the outcome may harm the organization. This begrudging compliance is an unfortunate attitude in any circumstance. In the extreme case, it can lead to disaster.
This is where the concept of intelligent disobedience comes into play. Intelligent disobedience is a trait clearly illustrated by guide dogs for the blind: At an intersection, based on traffic sounds and a general sense of safety, the blind person initiates the move to cross the street, giving a signal to the dog. If traffic is blocking the crosswalk, however, the guide dog will disobey the move-forward command. In guide-dog training lingo, intelligent disobedience is the dog's response when it senses that the path ahead is dangerous. It disobeys even though the owner wants to proceed.
Now consider a different scenario: The dog disobeys the owner's command because it sees traffic blocking
- Why Projects Fail CIOs are expected to deliver more projects that transform business, and do so on time, on budget and with limited resources.
- Why Today's Software Development Projects Fail By establishing more accountability for quality with developers, organizations are able to improve their software quality outcomes in more effective ways than traditional...
- Review: Box beats Dropbox - and all the rest - for business Box trumps Dropbox, Engyte, Citrix ShareFile, EMC Syncplicity, and OwnCloud with rich mix of file sync, file sharing, user management, deep reporting and...
- AIIM SharePoint Industry Watch AIIM surveyed its 65,000 community members to look at how the enterprise is reacting to social aspects, why organizations are exploring social, who...
- Leveraging the Cloud for Dev/Test This video discusses some of the key considerations that IT organizations should take into account when moving test and development projects to the...
- Cloud Knowledge Vault Learn how your organization can benefit from the scalability, flexibility, and performance that the cloud offers through the short videos and other resources... All Project Management White Papers | Webcasts