Packaged Software: Selection And Implementation Policies

Adoption of information systems innovations by individuals: A study of processes involving contextual, adopter, and influencer actions

“…The organization may design and develop the innovation in-house or it may outsource the design and development of the innovation to external vendors (Sabherwal & Robey, 1995). In contrast to this ''make" option, the organization may opt to ''buy" the innovation as a packaged or commercial off-the-shelf software solution and use it as is or have it customized for the context (Attewell, 1992;Janson & Subramanian, 1996;Lassila & Brancheau, 1999). Subsequent to its acquisition, the organization may implement the innovation so that it is available for use by individuals (Lewis & Seibold, 1990).…”

Organizational adoption of enterprise resource planning systems: A conceptual framework

“…The incompatibility of features with the organization's information needs and business processes is an important problem associated with implementing any packaged software (Janson & Subramanian, 1996;Lucas, Walton, & Ginzberg, 1988;Somers & Nelson, 2003). This problem can only be solved by adapting the organization to the package through extensive BPR (Kremers & Van Dissel, 2000;Somers & Nelson, 2003).…”

The Social Shaping of Packaged Software Selection

“…For small to medium sized enterprises (SMEs), organisational size influences what can be a lengthy and costly decision-making process and, therefore, they often rely heavily on vendor support and presentations (Janson and Subramanian, 1995) to inform the decision, rather than carrying out detailed requirements analysis (Olsen and Saetre 2007). Yet reliance on vendor-supplied material exacerbates the likelihood that the adopted package will fail to meet user requirements (Keil and Tiwana, 2006).…”

“…With packaged software, the functionalist literature suggests that in order to achieve the "best fit" between product functionality and organisational needs, an understanding of user requirements is critical (Bansler and Havn, 1994;Chau, 1995;Nelson et al, 1996;Sharland, 1991;Stefanou, 2001) and that this will lead to successful implementation and usage (Janson and Subramanian, 1995). User involvement in package selection is seen as essential for determining functionality requirements (Akkermans and van Helden, 2002;Al-Mudimigh et al, 2001;Gremillion, 1982) and it is argued that assessing these needs is necessary for scoping the project in order to reduce costly changes (Markus and Tanis, 2000).…”