Exploring the Business Case Development Process in Inter-Organizational Enterprise System Implementations

Exploring the Business Case Development Process in Inter-Organizational Enterprise System Implementations

Silja Eckartz (University of Twente, The Netherlands), Christiaan Katsma (University of Twente, The Netherlands) and Maya Daneva (University of Twente, the Netherlands)
Copyright: © 2012 |Pages: 18
DOI: 10.4018/irmj.2012040106
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

Creating and negotiating an inter-organizational business case (BC) for multiple-stakeholder enterprise systems is a major challenge. This paper looks closer into the factors that influence the stakeholders’ willingness to share information necessary for the BC development. The authors develop an explanatory framework showing the effect that project constellation has on the development of a shared BC. They identify several factors, such as goal consensus, cultural and semantic similarities and willingness to share information, that mitigate this effect. Subsequently, the authors apply the framework in an inter-organizational case study in which a BC is developed. The findings show that current BC development methods need to be re-stated and complemented by new tools and interventions to support stakeholders in the inter-organizational specific setting. The authors elaborate on the possibilities that group decision support systems might offer to overcome challenges that might be experienced in the BC development process.
Article Preview

Theoretical Background

This section summarizes the findings of the current state of the literature as well as of the available empirical studies. For clarification purposes and to position our line of reasoning we start defining what we mean by the concept of “Business Case.”

We use the definition of a Business Case as an artifact (possibly a document accompanied by designs or models, etc.) that specifies the main rationale and expected value for the ES-adopting organization. The BC evaluates the different implementation options, based on the expected costs, benefits and risks of each option during the entire implementation process (Schubert & William, 2009; Shang & Seddon, 2002; Ward & Daniel, 2006). Ideally it contains more than just a financial analysis. The (non-) financial benefits, business alignment, costs and risks, should be complemented with information on the methods and rationale that were used to quantify the benefits and costs (Schmidt, 2003b). The BC is the result of a BCD process that is deployed between consultants and stakeholders from the ES-adopting organization. The BCD is an iterative, tool-supported process that relies on stakeholders from different parts of the organization with different business knowledge.

Complete Article List

Search this Journal:
Reset
Open Access Articles: Forthcoming
Volume 30: 4 Issues (2017)
Volume 29: 4 Issues (2016)
Volume 28: 4 Issues (2015)
Volume 27: 4 Issues (2014)
Volume 26: 4 Issues (2013)
Volume 25: 4 Issues (2012)
Volume 24: 4 Issues (2011)
Volume 23: 4 Issues (2010)
Volume 22: 4 Issues (2009)
Volume 21: 4 Issues (2008)
Volume 20: 4 Issues (2007)
Volume 19: 4 Issues (2006)
Volume 18: 4 Issues (2005)
Volume 17: 4 Issues (2004)
Volume 16: 4 Issues (2003)
Volume 15: 4 Issues (2002)
Volume 14: 4 Issues (2001)
Volume 13: 4 Issues (2000)
Volume 12: 4 Issues (1999)
Volume 11: 4 Issues (1998)
Volume 10: 4 Issues (1997)
Volume 9: 4 Issues (1996)
Volume 8: 4 Issues (1995)
Volume 7: 4 Issues (1994)
Volume 6: 4 Issues (1993)
Volume 5: 4 Issues (1992)
Volume 4: 4 Issues (1991)
Volume 3: 4 Issues (1990)
Volume 2: 4 Issues (1989)
Volume 1: 1 Issue (1988)
View Complete Journal Contents Listing