An Integrative Contingency Model of Software Project Risk Management

By Henri Barki, Suzanne Rivard, Jean Talbot. Journal of Management Information Systems, 2001

489 citations recorded by the source corpus.

Subfields: Information Systems, Management Information Systems

View Paper: https://www.semanticscholar.org/paper/7f676b01f78a24aad7ace39f85041b7c34de1ae6

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

In Management Information Systems

Citations in the corpus

Inhibitors and Enablers as Dual Factor Concepts in Technology Usage (2004, background): “It is interesting to note that risk is a frequently studied antecedent (e.g., Barki et al., 2001; Pavlou, 2003), but there is no research that I am aware of regarding the importance of luck.”
Participation in Development and Implementation - Updating An Old, Tired Concept for Today's IS Contexts (2004, background): “And Barki et al. (2001) studied participation in system development, system implementation, and project management (project reporting and liaison activities).”
The situational factors that affect the software development process: Towards a comprehensive reference framework (2012, background): “The broad risk factor framework introduced in [48] heralded the arrival of more extensive risk factor models.”
Risk and risk management in software projects: A reassessment (2008, methodology): “That is, to adopt a contingency or method engineering approach to project and risk management design (Barki et al., 2001; Ropponen and Lyytinen, 1997, 2000; Shenhar, 2001).”
Expertise Integration and Creativity in Information Systems Development (2005, background): “Thus some of the considerable risk involved in the ISD process stems from the risk that the delivered solution simply fails to meet changing business needs [6, 7].”
Does risk management contribute to IT project success? A meta-analysis of empirical evidence (2010, background): “Better ﬁts between project and environment as well as between risk exposure and the project management proﬁle (Barki et al., 2001) increase project performance.”
ParanoiaEval: Benchmarking Unnecessary Defensive Work in Agentic Coding (2026, unknown): “For each repository, SWE-Factory yields SWE-style base tasks, each comprising an issue-style description, a reference patch, and executable tests.”