Implementing and improving the SEI risk management method in a university software project;Implementación y mejora del método de gestión riesgos del SEI en un proyecto universitario de desarrollo de software

IEEE Latin America Transactions

Volumn 3, Issue 1, 2005, Pages 90-97

  Esteves, José ^a   Pastor, Joan A ^b   Rodríguez, Nuria ^c   Roy, Ramon ^c  

^a IE BUSINESS SCHOOL   (Spain)

^b UNIVERSITAT INTERNACIONAL DE CATALUNYA   (Spain)

^c UNIVERSITAT POLITÈCNICA DE CATALUNYA   (Spain)

Author keywords

Continuous risk management; CRM; Organizational risks; Risk management methods; Software project management

Indexed keywords

CONTINUOUS RISK MANAGEMENT; CRM; ORGANIZATIONAL RISKS; RISK MANAGEMENT METHODS; SOFTWARE PROJECT MANAGEMENT;

PROJECT MANAGEMENT; RISK ANALYSIS; RISK MANAGEMENT; SEEBECK EFFECT;

SOFTWARE DESIGN;

EID: 63049131981     PISSN: 15480992     EISSN: None     Source Type: Journal    
DOI: 10.1109/TLA.2005.1468667     Document Type: Conference Paper

References (18)

1. Adler, P., Shenhar, A. (1990). Adapting your technological base: the organizational challenge, Sloan management review, pp. 25-37.
2. Boehm, B. (1988). A Spiral Model of Software Development and Enhancement, IEEE Computer, 21, pp. 61-72.
3. Doherty N., King, M. (2001). An investigation of the factors affecting the successful treatment of organizational issues in systems development projects, European journal of information systems, 10, pp. 147-160. (Pubitemid 33365259)
4. Hartwick J., Barki J. (1994). Explaining the Role of User Participation in Information System Use, Management Science, 40(4), pp. 440-465.
5. Hoffman T. (1998). Risk management still a wild frontier, Computerworld, 32(7), p. 10.
6. Jiang, J., Klein, G., Discenza, R. (2001). Information Systems Success as impacted by risks and development strategies, IEEE transactions on Engineering Management, 48(1), pp. 46-55. (Pubitemid 32404515)
7. Keil M., Cule E., Lyytinen K., Schmidt R. (1998). A Framework for identifying software project risks, Communications of the ACM, 41(11), pp. 76-83.
8. Mitchell T. (1997). Matching Motivational Intervention to Organizational Contexts, Research in Organizational Behavior, 19, pp. 57-149.
9. Moynihan T. (1997). How Experienced Project Managers Assess Risk, IEEE software, pp. 35-41.
10. Roppponen, J., Lyytinen, K. (2000). Components of Software Development Risk: Hot to address Them?, IEEE transactions on software engineering, 26(2), pp. 98-111.
11. Schmidt, R., Lyytinen K., Keil M., Cule P. (2001). Identifying software project risks, an international Delphi study, journal of management information systems, 17(4), pp. 5-36.
12. Carr M., Konda S., Monarch I., Ulrich F., Walker C. (1993). Taxonomy- Based Risk Identification, Technical Report CMU/SEI-93-TR-6, Software Engineering Institute, Carnegie Mellon University.
13. KLCI (2001). Software Risk management Practices - 2001, KLCI research group report, available at ttp://www.klci.com (2001).
14. Walsh K., Schneider H. (2002). The role of motivation and risk behavior in software development success, Information research, 7(3), Available at http://InformationR.net/ir/7-3/paper129.html
15. Esteves J., Pastor J. (2000). Towards the Unification of Critical Success Factors for ERP implementations, 10th Annual BIT conference, Manchester, UK.
16. Kontio, J. (1997). Empirical Evaluation of a risk management Method, SEI conference on risk management, USA.
17. Kontio, J. Getto, G., Landes, D. (1998). Experiences in improving risk management processes using the concepts of the Riskit method, SIGSOFT'98 sixth international symposium on he foundations of software engineering.
18. Padayachee K. (2002). An Interpretive Study of Software risk management Perspectives, South African Institute for Computer Scientists and Information Technologists (SAICIST) conference.