2015
DOI: 10.17705/1cais.03722
|View full text |Cite
|
Sign up to set email alerts
|

Customer Satisfaction in IS Projects: Assessing the Role of Process and Product Performance

Abstract: Despite extensive research over the past several decades, assessing information system (IS) project success is still a challenging endeavor. While the traditional approach takes process performance (time and budget) and product performance (functional and non-functional requirements) into account, the contemporary perspective acknowledges the more comprehensive character of project success and emphasizes the criticality of stakeholder satisfaction. Continuing previous research, we propose and test a model with… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

2
8
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 8 publications
(10 citation statements)
references
References 76 publications
2
8
0
Order By: Relevance
“…Extant research addresses the complexity of ITPS by adopting different success dimensions [6,13]. Likewise, we distinguish between ITPMS and ITPS as two independent success dimensions, each with its own success criteria [4,[14][15][16]. This distinction bears two advantages: On the one hand, it appears not to be too complex for practical application.…”
Section: Success Dimensions and Success Criteriamentioning
confidence: 99%
See 1 more Smart Citation
“…Extant research addresses the complexity of ITPS by adopting different success dimensions [6,13]. Likewise, we distinguish between ITPMS and ITPS as two independent success dimensions, each with its own success criteria [4,[14][15][16]. This distinction bears two advantages: On the one hand, it appears not to be too complex for practical application.…”
Section: Success Dimensions and Success Criteriamentioning
confidence: 99%
“…Furthermore, these project failures are not only critical due to cost and time overruns or quality shortcomings, but the consequences of some of these project failures can even threaten the entire company [3]. Despite these challenges for the successful implementation of IT projects, a comprehensive theory of IT project success seems to be omitted by research [4]. To the best of our knowledge, former research has often depicted detailed analyses of success factors but neglected their interrelation with success dimensions (e.g., [5]).…”
Section: Introductionmentioning
confidence: 99%
“…The factors that contribute to customer satisfaction are both time and role dependent [7,16,21,25,26,27]. For an end user, the project outcome (in relation to the business objectives) determines the satisfaction [25,28,29]. Acquisition/project management team members have a different perspective on projects than end users: where end-users and their management place significant emphasis on the project outcome, an acquisition/projectmanagement team puts more emphasis on the way a project is conducted and how defects are handled [17,18,21].…”
Section: The Importance Of Delivery Qualitymentioning
confidence: 99%
“…Our first hypothesis questions the relevance of Delivery Quality when this product is clearly lacking in quality. Quantitative studies [24,29,30] each independently show that when a project does not deliver the right product it can not be compensated by Delivery Quality. However, these studies completely focus on end user satisfaction in a post-project evaluation.…”
Section: The Importance Of Delivery Qualitymentioning
confidence: 99%
“…There is a great deal of discussion concerning the criteria that should be used to designate an implementation a failure (Basten et al 2011 ; Basten and Pankratz 2015 ; Lech 2013a ; Yeo 2002 ), leading to considerable research on implementation success and failure factors regarding both Information Systems in general, and Enterprise Systems in particular. However, there is no doubt that many ES projects still face problems with meeting their original scope, budget, and/or schedule (Belassi and Tukel 1996 ; Dezdar and Sulaiman 2009 ; Kappelman et al 2006 ; Mu et al 2015 ; Nah and Delgado 2006 ; Nelson 2007 ; Ram et al 2014 ; Somers and Nelson 2001 ; Schmidt et al 2001 ; Soja and Paliwoda-Pękosz 2009 ; Yeo 2002 ).…”
Section: Introductionmentioning
confidence: 99%