Why information technology software projects fail in South Africa
- Authors: Smith, Jurie
- Date: 2012-08-13
- Subjects: Computer software - Development - Management , Software engineering - Management
- Type: Thesis
- Identifier: uj:9060 , http://hdl.handle.net/10210/5522
- Description: M.B.A. , The aim of this research was to determine why information technology software projects fail in South Africa in order to determine whether there is a cause and cost similarity between international first world and South African IT Software Project failures. This research topic was primarily chosen because there is a lack of research on IT Software project failure in South Africa. The following objectives were defined to support the aim of the research: To ascertain project cost failure statistics sources internationally from relevant literature. To ascertain from literature what has been said about causes/reasons of project failure internationally. To ascertain South African IT Software Project failure statistics and reasons by means of a questionnaire. To determine whether the literature on international IT software project failure and South African IT software project failure compare. The research project was conducted amongst members of the Project Management Institute of South Africa (PMISA). In addition, companies that are not members of PMISA were also contacted and requested to respond to an e-mail questionnaire. It is interesting to note that one of the reasons for projects being challenged and cancelled, deals with, or is related to, requirements. Changing and / unclear user requirements was always listed in the top three reasons for projects being challenged and cancelled. The top three reasons listed by The Standish Group also lists changing and / unclear user requirements in the top three. This research would therefore suggest that effectively dealing with changing and / unclear user requirements would significantly increase project success. In conclusion, the comparison between South African companies and International companies revealed that the causes are for the most part the same, and the costs appear to be vastly different, but similar in trend. As is evident from the research literature, this research topic rarely studied, and therefore additional research can be done to explore this topic.
- Full Text:
Analysis of project management techniques within software engineering in the financial industry
- Authors: Ismail, Mohamed Saliem
- Date: 2013-05-27
- Subjects: Project management , Software engineering - Management , Financial institutions - Management , Financial services industry - Management
- Type: Mini-Dissertation
- Identifier: uj:7548 , http://hdl.handle.net/10210/8406
- Description: M.Ing. (Engineering Management) , Within the last 20 years, technology has progressed remarkably. Secondary market trading in South Africa was at an age where rates were being printed on ticker paper and this was considered real time rates. Deal tickets were completed by hand and the dealing room was complete chaos. Today the advancements of technology have evolved this industry remarkably. With real time rates feeding two or even three systems on screen, trade volumes have increased exponentially. The roles of information technology (IT) and software engineering are seen as support functions within most banking industries and are considered critical elements to any project. The project manager must be able to cope with constant change in the technology environment and intense pressure from stakeholders to produce quality results on time. All means of business are transacted through an electronic platform making the reliance and integrity of software systems critical. Software engineering becomes more than just simply writing a system for some designed purpose. Improper management of systems projects will impact heavily on daily operations. The primary aim of this research study is to investigate project management and portfolio management processes within the financial industry, and to recommend and formulate enhancements to these processes. The study will be conducted on a young and developing investment bank where policy and processes are not yet clearly established. A pilot project management process will be introduced and monitored against the following measurements areas: Quality, Stability, Deliverables, Relationships and Execution.
- Full Text:
'n Raamwerk vir die bestuur van koste tydens programmatuurontwikkeling
- Authors: Loubser, Hennie
- Date: 2015-03-17
- Subjects: Software engineering , Software engineering - Management
- Type: Thesis
- Identifier: uj:13430 , http://hdl.handle.net/10210/13467
- Description: M.Com. (Informatics) , Research into formalised methods for software engineering has resulted in many solutions to the known problems of software development. One of these problems is the difficulty involved In managing the cost of software development. Though attempts are made to solve the problem of budget and schedule overruns during project management, there still seems to be a lack of useful formal methods and approaches. In this dissertation such a formalised approach is presented. This approach Is based on the principle that cost should be actively managed just like any other aspect of software development. Within this framework the management of cost is defined as a process of identifying, estimating, measuring and controlling those factors that Influence the cost of development. Many methods exists through which the estimation of cost can be facilitated. The fact that such methods are available does not seem to solve the problem because cost management Involves more than just cost estimation. The research done to formalise this approach includes a discussion on the background of software engineering and the state of the science. It also includes an investigation Into the use of development metrics. The cost of software development is analyzed to determine the influence of different environmental factors on cost. A few estimation models are also discussed to determine the useability of such methods during cost management. A synopsis of how these subjects are covered In this dissertation is as follows: Chapter one serves as an Introduction to the research by giving a background to the development of software engineering. The limitations of current practices are emphasized and certain research questions are formulated. Chapter two discusses formal methods of development in the form of process models as a basis for the management of development cost. This chapter also analyzes development metrics as a method of measurement during development and cost management. The analysis provides as a framework for the identification and application of metrics during the process of cost management. Chapter three defines the extent of development cost and analyzes all factors contributing to the cost of software. The chapter discusses each of these factors by examining the possible influence of each on the effort of development and the Interdependence of these factors. Chapter four discusses a case study to be applied during discussions In the rest of the dissertation. Chapter five examines different approaches to the estimation of software development cost. The chapter serves as an introduction to subsequent chapters that deal with specific estimation models. Chapter six discusses an estimation model developed by Blokdijk. The chapter gives an overview of the principles Involved in and the application of the model.
- Full Text:
Die bestuur van die sagteware ontwikkelingsproses
- Authors: Ferreira, Daniel Nicolaas Paul
- Date: 2015-03-18
- Subjects: Software engineering - Management
- Type: Thesis
- Identifier: uj:13460 , http://hdl.handle.net/10210/13496
- Description: M.Com. (Business Management) , It is possible to manage the software development process efficiently. It is, however, important to gain a thorough understanding of the software development process and to be able to measure productivity easily and repeatedly. .A concept which may be used with success in the management of a software project is that of software economy. Software economy is achieved when the greatest quantity of software of the highest quality is produced using the smallest amount of resources (people, hardware and software) in the shortest possible time. The extensive software development process model is an important tool which can be used to maintain the various stages of the development process. Important conclusions can be made from the model. One such a conclusion is that adding more people to a project which is running behind schedule, will not help the project to be finished on time, but may even slow the project down further. The most useful and easy to implement metric, the measurement of productivity, is Function Points. Non-technical personnel may use this technique and it can be implemented early in the life cycle of a project. It is possible to successfully manage the software development process by using basic management principles such as planning, organization, monitoring and control together with the necessary adjustments outlined in this work.
- Full Text: