2002
DOI: 10.1016/s0263-7863(01)00075-8
|View full text |Cite
|
Sign up to set email alerts
|

Critical failure factors in information system projects

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

3
194
0
12

Year Published

2011
2011
2017
2017

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 276 publications
(209 citation statements)
references
References 2 publications
3
194
0
12
Order By: Relevance
“…The problem in this case is not at the level of construction or usage, but at that of outcomes: we refer to expectation failure when the system does not meet the expectations of one or more groups of stakeholders. Unlike other concepts, this notion takes into account multiple stakeholders' views, and hence fits particularly well with a sociotechnical vision of IS (Yeo, 2002). But the key reason why this concept is relevant is that it evaluates systems according to their objectives, and can therefore state the difference between desired and actual achievements, through the eyes of the multiple stakeholders involved (Lyytinen, 1988, p. 54).…”
Section: Ict Failure In Developing Nations: Design-reality Gapsmentioning
confidence: 99%
“…The problem in this case is not at the level of construction or usage, but at that of outcomes: we refer to expectation failure when the system does not meet the expectations of one or more groups of stakeholders. Unlike other concepts, this notion takes into account multiple stakeholders' views, and hence fits particularly well with a sociotechnical vision of IS (Yeo, 2002). But the key reason why this concept is relevant is that it evaluates systems according to their objectives, and can therefore state the difference between desired and actual achievements, through the eyes of the multiple stakeholders involved (Lyytinen, 1988, p. 54).…”
Section: Ict Failure In Developing Nations: Design-reality Gapsmentioning
confidence: 99%
“…Stage 1: Implementation of the top-down method; authors formulated four project success criteria, namely: efficiency [5], [40], [50]- [51], effectiveness [27], [51], fulfillment of the functional requirements [47], [52], and stakeholder satisfactions [23], [24], [27], [47], [53]. These criteria is formulated based on four project dimensions: resources [24], [27], [33], [39]- [43], managerial [24], [27], [38], [39], [44], directional [5], [22], [24], [37], [43], and environmental [5], [19], [22], [24], [37], [43], [48] dimensions.…”
Section: Results and Discussion: Implementation Of The Proposed Methomentioning
confidence: 99%
“…Wateridge [44] described that each of stakeholders has different attentions in each stage because of their natures. Therefore, the success can be measured based on various stakeholder interests [47] according to the technical issues (short-term), the tactical issues (medium-term), and the strategic issues (long-term).…”
Section: Dimensions Of the Is Project Successmentioning
confidence: 99%
“…Similarly, Hislop et al, (2000) suggests that factors influenced knowledge networks involved in change, such as the type of structure, the power of authority and political involvement. Likewise, Yeo (2002) and Lutz et al, (2013) claim that poor decision making in IT intervention occurs because of the lack of alignment between information technology systems and business objectives as a result of missing key details. These missing details will influence decision-making processes which determine the capacity to change of an organisation in terms of pre-selecting an appropriate change strategy, at the implementation stages and during the post-implementation period (Shipton, Budhwar & Crawshaw, 2012;Judge & Elenkov, 2005).…”
Section: A Conceptual Framework For Decision Support -Cmknmmentioning
confidence: 99%