Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
"High I.T. Failure Rate: A Management Prospect"
Blekinge Institute of Technology, School of Management.
2006 (English)Independent thesis Advanced level (degree of Master (One Year))Student thesisAlternative title
"Hög I.T. Underlåtenhet Rate : En förvaltningskommitté Prospect" (Swedish)
Abstract [en]

Software industry is growing day by day and software is going more complex and diverse with increase in cost and rate of failure. This increase in size and complexity of software projects has negative impact on the software productivity, schedule and effort. Organizations are demanding high quality products to increase their productivity and profits. It is common that they are facing some serious problems even after spending a large sum of money. So, its alarming situation and the concerned parties should take effective steps to resolve software project failure problem. Above all this, we are facing a high rate of software failure putting software industry on stake. This study revolves around the core issue of finding the root causes of software project failure with respect to organizational factors. In this, I have tried to find the organizational factors contributing towards the failure of software projects. I have done this study with the help of literature review and questionnaire survey. There could be one or several factors responsible for the software projects failure, which are mentioned in chapter two. I have slightly touched the Information Technology for digging deep into the failure and for understanding this phenomenon. Software failure is the biggest challenge faced by IT as well as business people. There is strong need to find the root causes of software project failure and mitigate them. For controlling this failure problem management can perform its role and I have discussed the role of management in defining, measuring, controlling and implementation of software projects. A project is considered failure when it is not able to show the anticipated results and it is happened when team is not able to fulfill the requirements of the project e.g. overruns time, overruns resources, lack of conformance with initial requirements specifications. I have tried to find out the answers of my research questions through literature review and empirical study. Root causes of software project failure are presented and validated through literature review, data analysis, discussion, and findings. A comprehensive analysis of empirical data and discussion will give you the insight into the problem and my effort to sort out them in a precise way. For the purpose of knowing the solution of this study, I will refer you towards the conclusion and recommendation. The concerned or interested people can get benefit from this research study and definitely it will help them to avoid software project failure. The contribution of the research is twofold. First, it will be helpful for the software making professionals/companies and secondly, it will be helpful for decision makers/users (Organizations), when they are going to buy or implement a software project for enhancing their productivity.

Abstract [sv]

This study revolves around the core issue of finding the root causes of software project failure with respect to organizational factors. In this study, I have tried to find the organizational factors contributing towards the failure of software projects. Study is comprises of literature review and questionnaire survey. There could be one or several factors responsible for the software projects failure. I have finalized some important causes of software failure on the basis of literature review and empirical study in chapter two. Further these finalized causes of software project failure are again validated with the help of questionnaire survey in chapter four. I have presented a comprehensive analysis of the gathered data from respondents. For avoiding any aspect of the analysis, I have further added a detailed discussion on data gathered through survey. I have slightly touched the Information Technology with respect to management’s role in software project development. Information Technology is playing a very vital role in today’s organizations for competing on world level. Software failure is the biggest challenge faced by IT as well as business people. In this way, software failure is very important issue for software development firms as well as buyer and user firms. There is strong need to find the root causes of software project failure and mitigate them. In currant age, the effective use of IT is a success factor for any organization. It is only possible if we link IT with organizational goals. Business and IT managers need to learn that how they can measure, manage and justify technology as a business matter. The example of ideal organization is that which gives value to the collaboration, openness, and communication. The insight gain through this research is the basis for describing the solution for software failure problem and it is presented in chapter six (Conclusion and Recommendations) briefly. The concerned parties will be able to get the benefits from this study to avoid the failure problem. The contribution of this research is twofold. First, it will be helpful for the software making professionals/companies and secondly, it will be helpful for decision makers/users (Organizations). Especially, when they are going to buy or implementing a software project for enhancing their productivity.

Place, publisher, year, edition, pages
2006. , 62 p.
Keyword [en]
Failure, Software Project Management, IT Management, Organizational Factors, Causes of Software Project Failure
National Category
Business Administration Software Engineering
Identifiers
URN: urn:nbn:se:bth-5255Local ID: oai:bth.se:arkivexA2D89F56B7C5E6A2C12575D80056DFFBOAI: oai:DiVA.org:bth-5255DiVA: diva2:832626
Uppsok
Technology
Supervisors
Available from: 2015-04-22 Created: 2009-06-17 Last updated: 2015-06-30Bibliographically approved

Open Access in DiVA

fulltext(269 kB)231 downloads
File information
File name FULLTEXT01.pdfFile size 269 kBChecksum SHA-512
a75da19499c80c01f67eec9bf8c150ab2fc1406ddf2c157dc90a760efb117c3f616e53c110affc48f12c0204c60bdcd2f0163c60968a94164995e8fc413b98ce
Type fulltextMimetype application/pdf

By organisation
School of Management
Business AdministrationSoftware Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 231 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

Total: 246 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf