<p>Many IT projects that have been developed in recent years are often considered to be unsuccessful. According to a study by Exido up to the 72% of all IT projects are considered to be failed. A failed IT projects means that the organizations that have ordered the new system may have higher costs or/and the system will not be ready in time. If costs are too high the new system might not be installed in the organization or if the system is not completed within the specified time frame the organization can become stagnant.</p><p>In this paper we conduct an investigation of the failure of IT projects there we will examine where, in the systems development lifecycle four different phases, projects fail. We will conduct an empirical study of each phase, where we describe the key steps in the process; we will also investigate failed IT projects that are linked to the current phase. After every empirical study of the phases we perform an analysis in which we describe what we believe is important to consider in the current phase, and which items have an important role in the phase that will contribute to that project fails.</p><p>We believe that the planning phase is the phase that is most important to carry out as detailed as possible when an IT project is developed. This is to ensure that the project will be successful. The phase structure of the whole project and important activities are carried out and they are affecting the other phases.</p>
| Identifer | oai:union.ndltd.org:UPSALLA/oai:DiVA.org:uu-126783 |
| Date | January 2010 |
| Creators | Hellberg, Bernt, Ståhl, Stefan |
| Publisher | Uppsala University, Computer Systems Sciences, Uppsala University, Computer Systems Sciences |
| Source Sets | DiVA Archive at Upsalla University |
| Language | Swedish |
| Detected Language | English |
| Type | Student thesis, text |
Page generated in 0.002 seconds