This thesis entitled "Software project failure In Bangladesh", submitted by Abdirahman Yusuf Abdihafid, ID to the Department of Software Engineering, Daffodil International University has been accepted as satisfactory for the partial fulfillment of the requirements for the degree of M.Sc in Software Engineering and approved as to its style and content. Asraf Ali Lecturer Department of Software Engineering Faculty of Science and Information Technology Påskelilje International University, great help during the writing of this thesis, really, he is the one who gave me the encouragement to become really what I am today. Khaled Sohel, Assistant Professor for his guidance, encouragement and utmost support throughout my program to see me successful.
Touhid Bhuiyan, Associate Professor and Head of Department of Software Engineering, Daffodil International University, for his guidance and encouragement. My deepest appreciation goes to my beloved families, and in particular to my father Yusuf abdihafid Omar and my mother Hayaad Abdilahi Warsame and my uncle Shaakir Abdihafid Omar and my uncle Abdiqani Abdihafid Omar, who have given me a lot of support, patience , understanding and material. in all aspects of my life and my other things that I can't mention here And I want to thank my best friend Juweria Ahmed Omar for her great support and always helping me by supporting me with positive words and encourages me to move forward each day. I also want to thank and appreciate my siblings: Salama Yusuf Abdihafid, Sowda Yusuf Abdihafid, Najma Yusuf Abdihafid, Nadiira Yusuf Abdihfid, Mohamed yususf Abdihafid, Abdirisaaq Yusuf Abdihafid for their support and encouragement.
This study investigated the problem of software project failure in Bangladesh, it also investigated the causes of software project failure and how to reduce the software project failure in Bangladesh Addiction we made the correlation in our variables to know the relationship between them. The results show that software project failure in Bangladesh is due to lack of experience and knowledge of requirements analyst system analyst programmer and software taster .in terms of reducing software project failure in Bangladesh and how to prevent this problem was described.
INTRODUCTION
- Background
- Research Motivation
- Problem Statement
- Research Scope
- Thesis Organization
Since the handling intensity of PC was a fundamental asset, emphasis was placed on the mechanization of the current procedure. Be that as it may, even after such extreme changes in business forms, needs, mechanical advancements and powerfulness in business condition, lots of data framework projects. Since preparation of the intensity of the PC was a fundamental asset, emphasis was placed on the robotization of the current procedure.
However, even after such extreme changes in business forms, needs, innovative improvement and empowering business conditions, data framework enterprise platoons fall flat or are in a quandary. Our research questions are to reveal the perceived causality and interrelationships between process areas and to assess the importance of software project failure analysis. This study reflects the causes and consequences of finding software project failure in Bangladesh.
This thesis consists of five chapters which will cover the finding and development of project failure in Bangladesh. Chapter One: This chapter introduces the introduction of software project failure Also the background of software projects.
Overview
Background of The Software Project Failure
- Common causes of software project failures
- Lack of User Input
- Incomplete Requirements and Specifications
- Changing Requirements & Specifications
- Lack of Executive Support
- New Technology, Technology Incompetence / Illiteracy
- Lack of Resources
- Unrealistic Expectations
- Does not need IT Anymore
- Lack of IT Management
- Lack of Planning
- Poor communication
- Poor Risk Management
The Standish Group (2013) overview concluded that lack of customer input was rated by 12.8% of respondents as the number 1 explanation behind ventures being tested, for example the venture is up and running, however over budget, on the timer and offers fewer highlights and capacities than originally shown. Another 12.4% of respondents concluded lack of customer input was the number 2 explanation behind the companies. The overview of the Standish Group (1995) assumed that changing prerequisites was rated as the number 3 goal behind the activities being tested, and the lack of customer involvement as the number 6 explanation behind the weakening of enterprises.
The available research was broken down to find out what the effect and explanations behind the absence of official help are. The review by the Standish Group (2001) concluded that 7.5% of respondents indicated absence of official help as the number 4 reason behind activities being prevented. Absence of official help was rated as the number 5 purpose behind ventures tested by 9.3% of respondents.
The Standish Group (1995) review assumed that innovation inadequacy was evaluated by 7.0% of respondents as the number 5 goal behind activities being tested. The accessible research was examined to find out the effect and purposes behind absence of assets. The Standish Group (1995) review assumed that absence of assets was rated by 6.4% of respondents as the number 6 purpose behind activities being tested.
Another 10.6% of respondents ranked lack of assets as the No. 3 goal behind corporate downsizing. Standish Group's (2009) overview assumed that customers not looking for the deal was rated by 7.5% of respondents as goal number 8. The available research was broken down to understand what is the effect and goals behind the lack of IT by executives .
The overview of the Standish Group (1995) concluded that the lack of Information Technology managers was rated by 6.2% of respondents as the number 9 explanation behind the weakening of enterprises. The available research was investigated to understand what the effect is and the explanations behind the lack of regulation. The Standish Group (1995) overview concluded that lack of regulation was rated by 8.7% of respondents as the number 7 explanation behind enterprise disruption.
Introduction
Research Subject and Instrumentation
Data Collection Procedure
Statistical Analysis
Reliability and validity
Research design
Introduction
Experimental Results
Descriptive Analysis
- Sex Response
- Participants Experiences in Terms of Role respondents
- Do you have any failure software project in your company?
- Title of Software project Failure?
- Starting and Dead line month and year of failure software project for the Development?
- Completing Month and Year?
- did the failure software project was delivered to any client and Month Year?
- is the failure software project stop from clients?
- Reason for stopping the failure software project with stopping date month and year?
- did the failure software projects was analyzed by any system analyst?
- How many year experiences had system analyst?
- Educational and qualification of the system analyst?
- Educational and qualification of the system analyst?
- did the failure software project was gathered the requirements by any Requirement
- How many year experiences had requirement analyst?
- Educational Qualification of the requirement analyst?
- Major of Education Qualification of Requirement Analyst?
- did the failure software project was developed by programmer?
- How many year experiences had programmer?
- Educational Qualification of programmer?
- Major of education Qualification programmer?
- did the failure software project was tasted by any taster?
- How many year experiences had Taster?
- Educational Qualification of the Tester?
- Major of Education Qualification Tester?
This table above shows the title of software project failures that the respondent's responses under our questionnaire collected. 23 © Daffodil International University Table 4.3.8 above shows the software project failure start date and date. This table above shows the reason for stopping the software project by date and date between 2010 and 2019.
The above table shows that the respondents have a major education is Information Technology 18(22.5%), the respondents are computer science 8(10.0%), the respondents are software engineers 6(7.5%), the respondents are Other. Information technology (IT) respondent of 18 (22.5%) have computer science and engineering 8 (10.0%), respondents have software engineering, majority have information technology. This table above shows respondents 48(60.0%) answer NO it means software project error was not tasted any taste 32(40.0%) respondent answer that software project error tasted something tester answer Yes.
This table above shows the experience of taste. respondents 36(45.0%) respondent have less than one year experience and 27(33.8%) respondent have 1 year experience 17(21.3%) respondent have 3 years experience. The table above shows the respondents 44(55.0%) have bachelor's degree 20(25.0%), the respondent has bachelor's degree 6(7.5%) the respondent has high school diploma 9(11.3%) the respondent has other majority have bachelor's degree. This table above shows the respondents 37(46.3%) respondent have computer science engineering 19(23.8%) respondent have software engineering 24(30.0%) respondent have information technology.
We have previously conducted a study3 in which we assessed whether two forms of informed consent procedure – a written informed consent procedure and an audio-visual [AV] recording of it (in the same clinical trial) differed from each other in terms of the level of understanding of the study by the participant with using a pre-validated questionnaire.
Introduction
Summary of the Study
- Participants Experiences in Terms of Role respondents?
- did the failure software projects was analyzed by any system analyst?
- Did the failure software project was gathered the requirements by any requirement
- Did the failure software project was developed by programmer?
- Did the failure software project was tasted by any taster?
Conclusion
Recommendations
Systems analysts are very important if we want to develop the software for which we have the data questionnaire. The survey we made among the total 80 respondents of the questionnaire said that the systems analyst experiences are 40% percent 0 years experience, which means we have less than 1 year and we focus on increasing the experience of the analyst required, another point we see in our data is the analyst's education a bachelor's degree and the percentage of that is 66.3%.
To reduce software project failure?
34;Why Do Information Technology Projects Fail?" Conference on ENTERprise Information Systems / International Conference on Project, 2016: 10. 34;Success and failure factors for e-government projects: A." Faculty of Computers and Information, Cairo University, Giza, Egypt, 2013: 9. 34;What factors lead to failure in software projects?" software project failure, software project management, failure factors, project risk, 2017: 9.
34;Reliability and validity analysis on the relationship between learning space, student satisfaction and perceived performance using SMART-PLS.".
