Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Six Reasons for Software Project Failure
Six Reasons <ul><li>Surveys covering over 8,000 projects indicate that major sources of software project failure lie </li>...
Six Reasons <ul><li>Source: Barry Boehm, IEEE Software, September/October 2002, page 97. </li></ul><ul><li>Surveys conduct...
The Top Six Reasons <ul><li>Incomplete requirements </li></ul><ul><li>Lack of user involvement </li></ul><ul><li>Lack of r...
Six Reasons <ul><li>None  of the six have to do with choices of platform, development environment, language, or hardware. ...
The reasons for software project failure  have to do with  processes for determining What is desired What is needed What i...
So the critical factors for a successful project are methods and mechanisms that can  draw out this information at the beg...
We can help. System Guides 408-356-5793
Upcoming SlideShare
Loading in …5
×

Six Reasons For Software Project Failure

24,569 views

Published on

Software projects fail because of failed communications.

Published in: Technology

Six Reasons For Software Project Failure

  1. 1. Six Reasons for Software Project Failure
  2. 2. Six Reasons <ul><li>Surveys covering over 8,000 projects indicate that major sources of software project failure lie </li></ul><ul><ul><li>less with shortfalls in formal methods skills </li></ul></ul><ul><ul><li>more with shortfalls in skills to deal with stakeholder value propositions . </li></ul></ul>
  3. 3. Six Reasons <ul><li>Source: Barry Boehm, IEEE Software, September/October 2002, page 97. </li></ul><ul><li>Surveys conducted by The Standish Group ( www.standishgroup.com ) of 8,000 projects. </li></ul>
  4. 4. The Top Six Reasons <ul><li>Incomplete requirements </li></ul><ul><li>Lack of user involvement </li></ul><ul><li>Lack of resources </li></ul><ul><li>Unrealistic expectations </li></ul><ul><li>Lack of executive support </li></ul><ul><li>Changing requirements and specifications </li></ul>
  5. 5. Six Reasons <ul><li>None of the six have to do with choices of platform, development environment, language, or hardware. </li></ul><ul><li>Five of the six have to do with </li></ul><ul><li>Communications between </li></ul><ul><ul><li>Builders </li></ul></ul><ul><ul><li>Stakeholders (“Users” or “Clients”) </li></ul></ul>
  6. 6. The reasons for software project failure have to do with processes for determining What is desired What is needed What is possible Who knows Who decides What is lacking among these often does not become evident until the system is implemented.
  7. 7. So the critical factors for a successful project are methods and mechanisms that can draw out this information at the beginning of a project, and throughout it.
  8. 8. We can help. System Guides 408-356-5793

×