No-Risk - A Method for the Application of Risk Management in Software Projects
Abstract
This paper shows a method of software project risk management, called No-Risk, conceived from a developed preliminary study in the form of a searches applied the project managers. Such study had as objective to identify which they are the relevant risk factors in projects of this nature, associates to the cost, schedule and quality dimensions. This method was elaborated for integration with the software development process of a information technology company.
Keywords:
Risk management, Software projects, Risk factors, Software development
References
Braga, R. Werner, C. Mattoso, M. (1999), “Odyssey: A Reuse Enviroment Based on Domain Models”, 2nd IEEE Symposium on Application Specific Systems and Software Engineering Technology, ASSET’99, Richardson, USA, March.
Jalote, P. (2002), “CMM in practice: process for executing software projects at Infosys”, SEI series in software engineering, ISBN, p. 159-174, May.
Kontio, J. (1996), “The Riskit Method for Software Risk Management. Version 1.00”, Computer Science Technical Reports, University of Maryland. College Park, MD.
Machado, C. A. (2002), “A-RISK: Um Método para Identificar e Quantificar Risco de Prazo em Projetos de Desenvolvimento de Software”, Dissertação de Mestrado. Pontifícia Universidade Católica do Paraná PUCPR. Curitiba.
MICROSOFT SOLUTIONS FRAMEWORK. (2004), MSF Risk Management Process, http://www.microsoft.com/msf, October.
PMBOK Guide. (2000), Um Guia do Conjunto de Conhecimentos do Gerenciamento de Projetos. Newtown Square, PA, USA: Project Management Institute.
SEI. (2004), Software Performance Institute. Pittsburgh, http://www.sei.cmu.edu, October.
Sommerville, I. (2003), Engenharia de Software, São Paulo, Ed. Addison Wesley.
THE STANDISH GROUP. (2004), Chaos Report. http://www.standishgroup.com, October.
Wallace, L. Keil, M. (2004), “Software Project Risks And Their Effect On Outcomes”, Communications of The ACM, vol. 47, nr. 4, p. 68-73, April.
Jalote, P. (2002), “CMM in practice: process for executing software projects at Infosys”, SEI series in software engineering, ISBN, p. 159-174, May.
Kontio, J. (1996), “The Riskit Method for Software Risk Management. Version 1.00”, Computer Science Technical Reports, University of Maryland. College Park, MD.
Machado, C. A. (2002), “A-RISK: Um Método para Identificar e Quantificar Risco de Prazo em Projetos de Desenvolvimento de Software”, Dissertação de Mestrado. Pontifícia Universidade Católica do Paraná PUCPR. Curitiba.
MICROSOFT SOLUTIONS FRAMEWORK. (2004), MSF Risk Management Process, http://www.microsoft.com/msf, October.
PMBOK Guide. (2000), Um Guia do Conjunto de Conhecimentos do Gerenciamento de Projetos. Newtown Square, PA, USA: Project Management Institute.
SEI. (2004), Software Performance Institute. Pittsburgh, http://www.sei.cmu.edu, October.
Sommerville, I. (2003), Engenharia de Software, São Paulo, Ed. Addison Wesley.
THE STANDISH GROUP. (2004), Chaos Report. http://www.standishgroup.com, October.
Wallace, L. Keil, M. (2004), “Software Project Risks And Their Effect On Outcomes”, Communications of The ACM, vol. 47, nr. 4, p. 68-73, April.
Published
2005-10-26
How to Cite
OLIVEIRA, Gustavo C.; BASTOS, Ricardo M..
No-Risk - A Method for the Application of Risk Management in Software Projects. In: BRAZILIAN SYMPOSIUM ON INFORMATION SYSTEMS (SBSI), 2. , 2005, Florianópolis.
Anais [...].
Porto Alegre: Sociedade Brasileira de Computação,
2005
.
p. 76-84.
DOI: https://doi.org/10.5753/sbsi.2005.14970.
