|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
| ASCII Text | x | ||
| M. van Genuchten, "Why is Software Late? An Empirical Study of Reasons for Delay in Software Development," IEEE Transactions on Software Engineering, vol. 17, no. 6, pp. 582-590, June, 1991. | |||
| BibTex | x | ||
| @article{ 10.1109/32.87283, author = {M. van Genuchten}, title = {Why is Software Late? An Empirical Study of Reasons for Delay in Software Development}, journal ={IEEE Transactions on Software Engineering}, volume = {17}, number = {6}, issn = {0098-5589}, year = {1991}, pages = {582-590}, doi = {http://doi.ieeecomputersociety.org/10.1109/32.87283}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - JOUR JO - IEEE Transactions on Software Engineering TI - Why is Software Late? An Empirical Study of Reasons for Delay in Software Development IS - 6 SN - 0098-5589 SP582 EP590 EPD - 582-590 A1 - M. van Genuchten, PY - 1991 KW - software development; development activities; classification; delay enabled actions; project engineering; software engineering VL - 17 JA - IEEE Transactions on Software Engineering ER - | |||
A study of the reasons for delay in software development is described. The aim of the study was to gain an insight into the reasons for differences between plans and reality in development activities in order to be able to take actions for improvement. A classification was used to determine the reasons. 160 activities, comprising over 15000 hours of work, have been analyzed. The results and interpretations of the results are presented. Insight into the predominant reasons for delay enabled actions for improvements to be taken in the department concerned. Because the distribution of reasons for delay varied widely from one department to another, it is recommended that every department should gain an insight into its reasons for delay in order to be able to take adequate actions for improvement.
[1] V. R. Basili, R. W. Selby, and D. H. Hutchens, "Experimentation in software engineering,"IEEE Trans. Software Eng., vol. SE-12, pp. 733-743, July 1986.
[2] V.R. Basili and H.D. Rombach, "The Tame Project: Towards Improvement-Oriented Software Environments,"IEEE Trans. Software Eng., Vol. SE-14, No. 6, June 1988, pp. 758-773.
[3] Brooks, Jr., Frederick P. 1975.The Mythical Man-Month: Essays on Software Engineering. Reading, Mass., Addison-Wesley.
[4] M. J. I. M. van Genuchten, "Towards a software factory," Ph.D. thesis, Eindhoven Univ. Technology, The Netherlands, 1991.
[5] M. J. I. M. van Genuchten and M. Fierst van Wijnandsbergen, "An empirical study on the control of software development," inProc. Conf. Organization and Information Syst.(Bled, Yugoslavia), Sept. 13-15, 1989, pp. 705-718.
[6] F. J. Heemstra, "Estimation and control of software development projects," Ph.D. thesis, Eindhoven Univ. Technology, Kluwer, Deventer, The Netherlands, 1989.
[7] A. M. Jenkins, J. D. Naumann, and J. C., Wetherbe, "Empirical investigation of systems development practices and results,"Inform. Manage., vol. 7, pp. 73-82, 1984.
[8] F. L. G. van Lierop and R. S. A. Volkers, "Controlling software projects: a matter of measurement," Masters thesis, Faculty of Industrial Eng., Eindhoven Univ. Technology, Kluwer, Deventer, The Netherlands, 1989.
[9] D. Phan, "Information systems project management: an integrated resource planning perspective model," Ph.D. thesis, Dept. Management Inform. Syst., Univ. Arizona, Tucson, 1990.
[10] D. Phan, D. Vogel, and J. Nunamaker, "The search for perfect project management,"Computerworld, pp. 95-100, Sept. 1988.
[11] W. J. A. M. Siskens, F. J. Heemstra, and H. van der Stelt, "Cost control of automation projects: an empirical study" (in Dutch),Informatie, vol. 31, pp. 34-43, Jan. 1989.
[12] H. J. Thambain and D. L. Wilemon, "Criteria for controlling projects according to plan,"Project Management J., pp. 75-81, June 1986.