Risk management in software development projects in Spain: a state of art
DOI:
https://doi.org/10.17533/udea.redin.13376Keywords:
software development, project management standards, survey, risk managementAbstract
Software is today a critical element in every system. The development and implementation of computer programs is influenced by many varied risks which should be managed properly. Risk management in software projects is an activity addressed in several software methodologies, but the different workgroups and organizations apply it in practice in many different ways. A preliminary study has been conducted among Spanish software professionals and developers. It reveals interest in risk management and its techniques, but it also shows that serious deficiencies as well as attitudes which do not help to this activity. These preliminary data represent a basis for a deeper and more detailed analysis of risk management practices which might lead to more effective and practical solutions.
Downloads
References
J. Lions, Chairman. Ariane 501. Ed. Inquiry Board Report. ESA y CNES. Paris, France. 1996. pp.1-60.
Information Management and Technology Division. GAO/IMTEC-92-26 Patriot Missile Software Problem. General Accounting office. Washington DC., USA. 1992. pp.1-16. Available on: http://www.gao.gov/products/IMTEC-92-26. Accessed: August 6, 2012.
P. Neumann. Forum on Risks to the Public In Computers and Related Systems. Committee on Computers and Public Policy of the Association for Computing Machinery. 1985. Available on: http:// catless.ncl.ac.uk/Risks. Accessed: August 4, 2012.
Webster’s On-line dictionary. 2005. Available on: http://www.websters-online-dictionary.org. Accessed: July 2, 2012.
Defense Systems Management College. Risk Assesment Techniques. 1st ed. Ed. Fort Velvoir. Virginia, USA. 1983. pp. 1-18.
W. Rowe. An Anatomy of Risk. 1st ed. Ed. Krieger Publishing Co. Florida, USA. 1988 . pp. 1-488.
L. Rosenberg, A. Hammer, T. Gallo. Continuous Risk Management at NASA. Applied Software Measurement / Software Management Conference. San Jose, USA. 1999. pp. 1-34.
R. Charette. Software Engineering Risk Analysis and Management. 1st ed. Ed. McGraw-Hill. New York, USA. 1989. pp. 1-325.
M. Stamatelatos, H. Dezfuli.. Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners. 2nd ed. Available on: http://www.hq.nasa.gov/office/codeq/risk/index.htm. Accessed: November 28, 2013.
Project Management Institute. PMBOK: A Guide to the Project Management Body of Knowledge. 2000. Ed. Newton Square. Pensylvania, USA. 2000. pp. 1-211.
Real Academia Española. Diccionario de la lengua española. 22nd ed. Ed. Espasa libros, S. L.U. Madrid, España. 2001. pp. 1975-1976.
ECSS Secretariat. ESA-ESTEC Requirements & Standards. ECSS-M-00-03a. Space Project Management. Risk management. 1ª ed. Ed. ESAESTEC. Noordwijk, The Netherlands. 2000. pp. 1-40.
Corporate Air Force Systems Command. Software Risk Abatement. Boehm, Barry W. (editor) Software Risk Management. 1ª ed. Ed.IEEE Press. Piscataway, USA. 1989. pp. 148-171.
A. Moore, A. Fearon, M. Alcock. Implementation of Opportunity and Risk Management in BAE SYSTEMS Astute Class Limited - A Case Study. Proceedings of the Fourth European Project Management Conference, PMI Europe2001. London, UK. 2001. pp. 1-7.
J. Ansell, F. Wharton. Risk Analysis Assessment and Management.1ª ed. Ed. John Willey & Sons LTD. Chichester, England. 1992. pp. 1-220.
J. Calvo, L. Maté, T. San Feliú. A Risk Management Approach. T.NATO AC/243 Panel 11 Research Study Group 3. Madrid, España. 1993. pp.1-22.
J. Ropponen, L. Kalle. “Components of software development risk; how to address them? A project manager survey”. IEEE Transactions on Software Engineering. Vol. 26. 2000. pp. 98-112. DOI: https://doi.org/10.1109/32.841112
J. Verner, S. Overmyer, K. McCain. “In The 25 Years Since The Mythical Man-Month What Have We Learned About Project Management?”. Information and Software Technology. Vol. 41. 1999. pp. 1021- 1026. DOI: https://doi.org/10.1016/S0950-5849(99)00077-4
J. Verner, W. Evanco. The state of the practice of software effort estimation in business organizations. Proceedings of ESCOM-SCOPE Conference. Munich, Germany. 2000. pp. 1-5.
J. Procaccino, J. Verner. Early Risk factors for Software Development. Proceedings of the 12th European Software Control and Metrics Conference. London, England. 2001. pp. 107-116.
C. Robbie, T. Nakatsu. “A comparative study of important risk factors involved in offshore and domestic outsourcing of software development projects: A two-panel Delphi study”. Information & Management. Vol. 46. 2009. pp. 57-68. DOI: https://doi.org/10.1016/j.im.2008.11.005
B. Gallagher, P. Case, R. Creel, S. Kushner, R. Williams. A Taxonomy of Operational Risks (CMU/ SEI-2005-TN-36).1st ed. Ed. Carnegie Mellon Software Engineering Institute. Pittsburgh, USA. 2005. pp.1-29.
G. Manrique. “Método para la construcción de una taxonomía: estructura base para riesgos en outsourcing de software”. Revista Facultad de Ingeniería de la Universidad de Antioquía. Nº 60. 2011. pp. 92-101.
R. Kendall, D. Post, J. Carver, D. Henderson, D. Fisher. A Proposed Taxonomy for Software Development Risks for High-Performance Computing (HPC) Scientific/ Engineering Applications. Ed. Software Engineering Institute. Pittsburgh, USA. 2007. pp. 1-27. DOI: https://doi.org/10.21236/ADA468594
H. Barki, S. Rivard, J. Talbot. “Toward an Assessment of Software Development Risk”. Journal of Management Information Systems.Vol. 10. 1993. pp. 203-225. DOI: https://doi.org/10.1080/07421222.1993.11518006
T. Demarco, T. Lister. Waltzing With Bears: Managing Risks on Software Projects. 1ª ed. Ed. Dorset House Publishing Company. New York, USA. 2003. pp.1- 208.
D. Houston, J. Collofello. “Finding the Influential Factors in Software Process Simulation Models”. Journal of Systems and Software. Vol. 59. 2001. pp. 259-270. DOI: https://doi.org/10.1016/S0164-1212(01)00067-X
T. Capers Jones. Estimating Software Costs. 2ª ed. Ed. McGraw-Hill Professional. New York, USA. 2007. pp. 1-644.
R. Schmidt, K. Lyytinen, M. Keil, P. Cule. “Identifying Software Project Risks: An International Delphi Study”. Journal of Management Information Systems. Vol. 17. 2001. pp. 5-36. DOI: https://doi.org/10.1080/07421222.2001.11045662
T. San Feliú. MANRIS. Método de Análisis de Riesgos de Sistemas de Información. Tesis doctoral de la Universidad de Castilla-La Mancha. Toledo, España. 2000. pp. 1-219.
J. Pereira, N. Cerpa, R. N. Risk factors in software development projects: Exploratory analysis of the Chilean software industry. Proceedings of the First Experimental Software Engineering Latin American Workshop. Brazilia, Brazil. 2004. pp.51-56.
E. Oz, J. Sosik. “Why information systems projects are abandoned: a leadership and communication theory and exploratory study”. Journal of Computer Information Systems. Vol 41. 2000. pp. 66-78.
K. Walsh, H. Schneider. “The role of motivation and risk behavior in software development success”. Information Research. Vol. 7. 2002. Available on: http://InformationR.net/ir/7-3/paper129.html . Accessed: July 1, 2012.
J. Pinto, D. Slevin. “Project success: definitions and measurement techniques”. Project Management Journal. Vol. 1. 1988. pp. 67-73.
D. Baccarini. “The Logical Framework Method for Defining Project Success”. Project Management Journal. 1999. Vol. 30. pp. 25-32. DOI: https://doi.org/10.1177/875697289903000405
C. Wohlin, A. Mayrhauser. “Assessing Project Success using Subjective Evaluation factors”. Software Quality Journal. Vol. 9. 2001. pp. 43-70.
R. Pressman. Software Engineering: A Practitioners Approach. 7ª ed. Ed. McGraw Hill. New York, USA. 2009. pp.1-895.
C. Schmitz. Lime Survey: the free & open source survey software tool!. Available on: http://www.limesurvey.org/. Accessed: July 1, 2012.
Google Team. Google Docs Help: Create, send, share, and edit a form. Available on: http://support.google.com/docs/bin/answer.py?hl=en&answer=87809. Accessed: July 1, 2012.
Ministerio de Economía y Hacienda. Real Decreto 475/2007, de 13 de abril, por el que se aprueba la Clasificación Nacional de Actividades Económicas 2009 (CNAE-2009). Boletín Oficial del Estado. Nº 102. Madrid, España. 2007. pp. 18572-18593.
Unión Europea. Reglamento (ce) no 451/2008 del Parlamento Europeo y del Consejo. Diario Oficial de la Unión Europea. Nº. 145. 2008. pp. 145/65- 145/226.
M. Philips. CMMI Today. Software Engineering Institute. Pitsburgh, USA. 2004. Available on: http://resources.sei.cmu.edu/library/asset-view.cfm?assetID=21074. Accessed: July 2, 2012.
Unión Europea. Recomendación de la Comisión de 29 de Octubre de 2009 relativa al uso de la Clasificación Internacional Uniforme de Ocupaciones (CIUO-08). Diario Oficial de la Unión Europea. Nº. 292. 2009. pp. 292/31-292/47.
K. De Bakker. “Communicative Project Risk Management in IT Projects”. CEPIS Upgrade. Vol. 12. 2012. pp. 59-66.
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2018 Revista Facultad de Ingeniería
![Creative Commons License](http://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png)
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Revista Facultad de Ingeniería, Universidad de Antioquia is licensed under the Creative Commons Attribution BY-NC-SA 4.0 license. https://creativecommons.org/licenses/by-nc-sa/4.0/deed.en
You are free to:
Share — copy and redistribute the material in any medium or format
Adapt — remix, transform, and build upon the material
Under the following terms:
Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
NonCommercial — You may not use the material for commercial purposes.
ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
The material published in the journal can be distributed, copied and exhibited by third parties if the respective credits are given to the journal. No commercial benefit can be obtained and derivative works must be under the same license terms as the original work.