No-risk: um processo para aplicação de gerência de risco de projetos de software focados em sistemas de informação

The fast-paced rhythm of changes and the search for better results has made the world more and more concerned about Software Project Management. However, unexpected problems can generate a great impact on this process, such as cost excess, schedule delay, problems related to the quality of the project and the lack of functionality. The present work was based on a research carried out to identify and quantify the main risk factors in Software Projects for Information Systems, along with the project managers related to companies in the Information Technology (IT) area, on a national level. Such study aimed to determine the proper dimension of these factors, allowing the possible inherent risks to the project execution to receive proper care. Along with this study, a research has been made for some processes of Software Projects Risk Management (SPRM) in literature, aiming to get a theoretical base for a deepened focus on this subject. As a result of this research, we observed the inexistence of a SPRM process that focused on a specific project dimension. That is, none of the studied processes considered prioritizing and defining specific techniques or strategies for a determined dimension of the project (such as cost, schedule and quality) in behalf of its importance. In order to fill these gaps a SPRM process, called No-Risk, was developed. It is applied to the cost, schedule and quality dimensions of the projects. It was developed to be integrated with a software development process, focused on information systems. The proposition of this process has as a basic premise to evaluate and analyze possible risks, based on the risk factors previously scanned. To evaluate this proposition, the process was applied to an information system Software Project of an IT focused company. Key-words: Project Management, Risk Management, Project Life Cycle, Information System. vi

[1]  Keshnee Padayachee,et al.  An interpretive study of software risk management perspectives , 2002 .

[2]  Tom Gilb,et al.  Principles of software engineering management , 1988 .

[3]  Ralph Keelling Gestão de projetos: uma abordagem global , 2006 .

[4]  Capers Jones,et al.  Assessment and control of software risks , 1994, Yourdon Press Computing Series.

[5]  Luqi Software evolution through rapid prototyping , 1989, Computer.

[6]  Kathy Schwalbe,et al.  Information Technology Project Management , 1999 .

[7]  Norm Brown,et al.  Industrial-Strength Management Strategies , 1996, IEEE Softw..

[8]  Karl E. Wiegers Read My Lips: No New Models! , 1998, IEEE Softw..

[9]  Mark Keil,et al.  Software project risks and their effect on outcomes , 2004, CACM.

[10]  Elaine M. Hall,et al.  Managing Risk: Methods for Software Systems Development , 1998 .

[11]  Robert N. Charette,et al.  Software Engineering Risk Analysis and Management , 1989 .

[12]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[13]  Guilherme Horta Travassos,et al.  Introdução à Engenharia de Software Experimental , 2002 .

[14]  Cláudio Bezerra Leopoldino Avaliação de riscos em desenvolvimento de software , 2004 .

[15]  B. Boehm Software risk management: principles and practices , 1991, IEEE Software.

[16]  Peter Kaiser,et al.  An industrial case study of implementing software risk management , 2001, ESEC/FSE-9.

[17]  O. Fernando Engenharia de Software , 2006 .

[18]  Tzvi Raz,et al.  Use and benefits of tools for project risk management , 2001 .

[19]  Edna Lúcia da Silva,et al.  Metodologia da pesquisa e elaboração de dissertação , 2001 .

[20]  Terry Williams,et al.  Assessing Extension of Time delays on major projects , 2003 .

[21]  Terence Patrick Rout,et al.  The Rapid Assessment of Software Process Capability , 2000 .

[22]  Robert N. Charette,et al.  Large-Scale Project Management Is Risk Management , 1996, IEEE Softw..