Depending on who or what you read, most software and systems projects (over 50%) end up as unsuccessful/failures: over budget, late, and/or fail to meet the user needs. As a worldwide phenomenon, studies continue to expound on why projects fail (poor requirements, underfunding, overoptimistic estimates, unreasonable schedules, lack of management commitment, etc.) but few studies focus on what it takes for projects to succeed.
What do you think makes a project (of any kind) successful? What is more important to project success:
1. The processes involved (e.g., formal project management, standards, shortened development life cycles, agility…); or
2. The people involved (e.g., the right team makeup, a good mix of skills, a motivated workforce, engaged users); or
3. Trust (e.g., collaboration rather than negotiation between customers and suppliers, reliance, cooperative teamwork; communication); or
4. Something else (e.g., other factors such as CMMI, tool sets, unlimited budgets, Steve Jobs on the team, …); or
5. Some “magical” combination of the above; or
6. None of these?
Across industries and across the world, is there a difference in what makes a project successful? Are there certain factors that predispose a project for success (or failure?)
What do YOU think? Inquiring minds are interested in hearing from you… (please post a comment or send me a private email to dekkers (at) qualityplustech (dot) com).
Thank you!
Carol
from my experience, the projects that were most needed and therefore bringing in the most money were artificially dragged out to keep the source of income viable. Of course, the project sponser would eventually get tired of paying for excuses and just give up. So it is the idea of a money cow that usually kills the best projects.
Reblogged this on lava kafle kathmandu nepal.
people