1999
DOI: 10.1201/1078/43197.16.3.19990601/31311.3
|View full text |Cite
|
Sign up to set email alerts
|

Risk Management Skills Needed in A Packaged Software Environment

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

2001
2001
2011
2011

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 23 publications
(11 citation statements)
references
References 1 publication
0
10
0
Order By: Relevance
“…Confronted with selecting the product that most closely matches their needs, this process within the organisation involves making trade-offs (Keil and Tiwana 2006). Therefore, many adopters eventually select a package on the basis of a persuasive sales pitch (Butler, 1999), as vendor's attempt to influence customers regarding the appropriateness of the fit between their organisational needs and the technology that the vendors represent (Wybo, 2007). The fit between product functionality and user requirements may appear problematic as packages address their requirements in an unfamiliar or unacceptable way, since many are built with "generic users" (Bansler and Havn, 1996) in mind and seldom translate easily across boundaries, either between organisations or within the same sector (Pollock and Cornford, 2004).…”
Section: Packaged Software Selection: Understanding User Requirementsmentioning
confidence: 99%
See 1 more Smart Citation
“…Confronted with selecting the product that most closely matches their needs, this process within the organisation involves making trade-offs (Keil and Tiwana 2006). Therefore, many adopters eventually select a package on the basis of a persuasive sales pitch (Butler, 1999), as vendor's attempt to influence customers regarding the appropriateness of the fit between their organisational needs and the technology that the vendors represent (Wybo, 2007). The fit between product functionality and user requirements may appear problematic as packages address their requirements in an unfamiliar or unacceptable way, since many are built with "generic users" (Bansler and Havn, 1996) in mind and seldom translate easily across boundaries, either between organisations or within the same sector (Pollock and Cornford, 2004).…”
Section: Packaged Software Selection: Understanding User Requirementsmentioning
confidence: 99%
“…Studies have shown that the purchase of global software packages is often motivated by expectations of the future direction and development of vendor products (Butler, 1999;Sawyer, 2001) and the vendor's perceived strength and stability (Chau, 1994) as much as by specific internal needs. For example, one study showed that a company selected SAP because it was perceived as the market leader in ERP packages, as opposed to being the appropriate package for the organisation (Dolmetsch et al, 1998).…”
Section: Packaged Software Selection: Final Selection and Purchasementioning
confidence: 99%
“…Typical issues include the need to form a suitable project team (Cliffe, 1999;Al-Mashari et al, 2003), assess different software vendors and the packages they offer (Hecht, 1997;Butler, 1999;Rao, 2000;Bernroider and Koch, 2001;Wei and Wang, 2004), and assess the impact that integrated systems are likely to have on the company once they have been implemented (Laughlin, 1999;Al-Mudimigh et al, 2001). Despite various authors discussing specific issues, Lee (1998) states that few attempts have been made to compile them into a structured methodology that could be used to guide companies through the steps they need to take prior to making a decision on whether or not to integrate their systems.…”
Section: Literature Review and Research Scopementioning
confidence: 99%
“…However, it has been suggested that packaged software may have limitations such as problems of flexibility, functionality, cost, control and impacts upon competitiveness (Holland and Light 2001, Butler 1999, Lucas et. al.…”
Section: Limitations Of Crm Packagesmentioning
confidence: 99%
“…Certainly the stampede toward the implementation of CRM packages, and hitherto the recognition of the need to manage customer relationships is acutely reflected in increase in the size of the market during this time. For example, during 1998-1999 Systems, the market leader, saw revenue rise by 93 per cent to $790.9m (Goodley and Bennett 2000).…”
Section: Informationmentioning
confidence: 99%