1999
DOI: 10.2307/249488
|View full text |Cite
|
Sign up to set email alerts
|

The Impact of Goals on Software Project Management: An Experimental Investigation

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
35
0
2

Year Published

2002
2002
2019
2019

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 82 publications
(38 citation statements)
references
References 41 publications
1
35
0
2
Order By: Relevance
“…It is clear that the framing of decisions plays an important role in judgment and decision making [38], and that in software project environments, explicit and concrete goals play an important role in influencing preferences and behavior [39].…”
Section: B Goals and Time Horizonsmentioning
confidence: 99%
“…It is clear that the framing of decisions plays an important role in judgment and decision making [38], and that in software project environments, explicit and concrete goals play an important role in influencing preferences and behavior [39].…”
Section: B Goals and Time Horizonsmentioning
confidence: 99%
“…Prior research has asked the question why many IS projects seem to take a life of their own (Mayr 2002) and continue to bind resources despite the trouble they cause (Abdel-Hamid et al 1999;Keil 1995;Keil et al 2000;Lee et al 2012). Answers to those questions were mainly rooted in psychological processes that explain biases in human decision making such as escalation of commitment to self-justify past behavior (Keil et al 2000), the sunk-cost effect (Keil et al 2000;Lee et al 2012), or the completion effect (Keil et al 2000;Lee et al 2012).…”
Section: Contribution To Is Project Escalation Literaturementioning
confidence: 99%
“…The gap is partly because the ERP adoption cost identification and estimation is a complex chore [4,5,10,[14][15][16][17][18][19]; it requires attentive analysis of both direct and indirect (usually hidden) costs. Moreover, the established and extensively used software cost estimation models e.g.…”
Section: Study Backgroundmentioning
confidence: 99%
“…COCOMO (COnstructive COst MOdel) [20] are not adequate to an ERP setting [5, 10-12, 14, 21]. COCOMO and analogous models are primarily focused on estimating software development costs, and some of their considered cost factors might not be valid for ERP adoption projects, as lines of code (KLOC) and development time (D) are not pertinent factors in an ERP context [10,14,17,[21][22][23]. Nevertheless, these models could be relevant to ERP vendors when pricing their ERP packages.…”
Section: Study Backgroundmentioning
confidence: 99%