2004
DOI: 10.1016/j.im.2003.12.007
|View full text |Cite
|
Sign up to set email alerts
|

Understanding software project risk: a cluster analysis

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

3
207
1
18

Year Published

2008
2008
2017
2017

Publication Types

Select...
7
3

Relationship

0
10

Authors

Journals

citations
Cited by 315 publications
(246 citation statements)
references
References 49 publications
3
207
1
18
Order By: Relevance
“…Additional approaches (e.g Al-Ahmad et al 2009;Barclay 2008;Dwivedi et al 2013b;Kappelman et al 2006;Schmidt et al 2001;Wallace et al 2004;Yeo 2002) have provided alternative perspectives on common causes of IS project failure, for example the concept of "project escalation" (Keil et al 1998). Strong and Volkoff (2010) provide a technology focused categorization of enterprise system failure in organizations, proposing the concept of "organization-enterprise system misfit" to explain IS failure.…”
Section: Information Systems Successmentioning
confidence: 99%
“…Additional approaches (e.g Al-Ahmad et al 2009;Barclay 2008;Dwivedi et al 2013b;Kappelman et al 2006;Schmidt et al 2001;Wallace et al 2004;Yeo 2002) have provided alternative perspectives on common causes of IS project failure, for example the concept of "project escalation" (Keil et al 1998). Strong and Volkoff (2010) provide a technology focused categorization of enterprise system failure in organizations, proposing the concept of "organization-enterprise system misfit" to explain IS failure.…”
Section: Information Systems Successmentioning
confidence: 99%
“…Following catalogues of requirement risks [17][18][19][20], argumentation schemes addressing the analysis of requirement risks can be proposed. To formulate these templates, requirement risks were analyzed according to the key RE tasks [1].…”
Section: Argumentation Schemes For the Collaborative Management mentioning
confidence: 99%
“…The users understand the difficulty to show the benefits obtained with the use of risk management, lack of resources for the function, lack of experience with the techniques and time for application (Kwak & Stoddard, 2004;Lyons & Skitmore, 2004;Wallace et al, 2004), in addition to the low authority and lack of ability of the project managers as limiting factors to their management (Globerson & Zwikael, 2002). This statement lead to the following proposition: Most problems in projects is managerial and not technical (Shenhar & Dvir, 2007).…”
Section: Theoretical Frameworkmentioning
confidence: 99%