Components of Software Development Risk: How to Address Them? A Project Manager Survey
By J. Ropponen, Kalle J. Lyytinen. IEEE Trans. Software Eng., 2000
444 citations recorded by the source corpus.
Subfields: Information Systems, Management Science and Operations Research
View Paper: https://www.semanticscholar.org/paper/07975ba1de3116be9200adecf9c8948eb2832000
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
- Paul L. Bannerman
- Rory V. O'Connor
- Barbara A. Kitchenham
- Paul M. Clarke
- Shari Lawrence Pfleeger
- Gwanhoo Lee
- Henri Barki
- Weidong Xia
In Management Science and Operations Research
- Rory V. O'Connor
- Barbara A. Kitchenham
- Paul M. Clarke
- Shari Lawrence Pfleeger
- Gwanhoo Lee
- Henri Barki
- Weidong Xia
- Suzanne Rivard
Citations in the corpus
- Risk and risk management in software projects: A reassessment (2008, background): “Frameworks categorizing risks according to their perceived source are the most common (e.g., Barki et al., 1993; Boehm and Ross, 1989; Cule et al., 2000; Davis, 1982; DeMarco and Lister, 2003; Jiang et al., 2002; Keil et al., 1998; Lucas, 1981; McFarlan, 1981; McKeen and Smith, 2003; Ropponen and Ly”
- Principles of survey research: part 1: turning lemons into lemonade (2001, unknown): “Description of the Finnish study Recently, Ropponen and Lyytinen (2000) described their exanfination of risk management practices.”
- The situational factors that affect the software development process: Towards a comprehensive reference framework (2012, background): “Ropponen and Lyytinen [47] acknowledge that some of the environmental factors may be beyond the control of the project manager (e.g. setting project deadlines and making decisions relating to subcontracting).”
- Preliminary Guidelines for Empirical Research in Software Engineering (2002, unknown): “For example, Ropponen and Lyytinen [ 40 ] surveyed project managers about their experiences of various risk factors.”
- Complexity of Information Systems Development Projects: Conceptualization and Measurement Development (2005, methodology): “Finally, one item was used to assess changes in users’ information needs [12, 58, 59].”
- Principles of survey research: part 5: populations and samples (2002, background): “A Finnish survey [4] aimed at investigating project risk and risk management strategies.”
- An Integrative Contingency Model of Software Project Risk Management (2001, background): “Moreover, only five articles, drawn from two studies, tested a priori hypotheses that incorporated more than two variables related to software risk management [40, 41, 42, 46, 47].”