Search the web
Sign In
New User? Sign Up
ITProFrustratedNoMore · I Hate My Software Development Job
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Message search is now enhanced, find messages faster. Take it for a spin.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
Seven Characteristics of Dysfunctional Software Projects   Message List  
Reply | Forward Message #55 of 89 |
1. Failure to Apply Essential Project Management Practices. Many
troubled projects fail to apply proven project management disciplines
like cost estimation, project scheduling, resource planning,
configuration management, and proactive risk management, then wonder
why their project is in constant turmoil.
2. Unwarranted Optimism and Unrealistic Management Expectations.
Some managers recognize the potential for negative impact on their
project from potential problem areas; however, they choose to see
things through rose-colored glasses, assuming that problems will work
themselves out even when all available evidence raises the red flag.
3. Failure to Implement Effective Software Processes. Many
projects fail to implement effective software processes because their
approach to process application is not balanced. Some apply minimal
process and rely on staff expertise, while others insist on rigorous
global process conformance.
4. Premature Victory Declarations. Pressures to deliver timely
products often result in premature declarations of completion by
managers. Success cannot be declared until products have been
completed with the built-in contracted quality and reliability.
5. Lack of Program Management Leadership. Managing a software
project requires "courageous" and often clairvoyant individuals who
are willing to confront today's challenges to avoid tomorrow's
catastrophes. We have observed two types of problem managers: those
with software engineering and no management experience, and those
with management and no software engineering experience. Both types
lack the ideal blend of both technical and managerial know-how.
6. Untimely Decision-Making. Some managers avoid making time-
critical decisions until it is too late, even when they are faced
with overwhelming warning signs of impending problems.
7. Lack of Proactive Risk Management. Many projects claim to
implement risk management but few do so effectively. "What
distinguishes the best organizations and best managers is not just
how well they do in their successful efforts, but how well they
contain their failures [5]."

Tell us about your Dysfunctional Software Project....





Mon Mar 31, 2008 5:59 pm

djj20012001
Offline Offline
Send Email Send Email

Forward
Message #55 of 89 |
Expand Messages Author Sort by Date

1. Failure to Apply Essential Project Management Practices. Many troubled projects fail to apply proven project management disciplines like cost estimation,...
MizzJ
djj20012001
Offline Send Email
Mar 31, 2008
6:00 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help