Welcome to the InfoSci Platform
Prioritizing Packaged Software Implementation Projects: The Significance of Gaps

Prioritizing Packaged Software Implementation Projects: The Significance of Gaps

Nicholas J. Rowland
Copyright: © 2013 |Pages: 18
ISBN13: 9781466641532|ISBN10: 1466641533|EISBN13: 9781466641549
DOI: 10.4018/978-1-4666-4153-2.ch020
Cite Chapter Cite Chapter

MLA

Rowland, Nicholas J. "Prioritizing Packaged Software Implementation Projects: The Significance of Gaps." Enterprise Resource Planning: Concepts, Methodologies, Tools, and Applications, edited by Information Resources Management Association, IGI Global, 2013, pp. 329-346. https://doi.org/10.4018/978-1-4666-4153-2.ch020

APA

Rowland, N. J. (2013). Prioritizing Packaged Software Implementation Projects: The Significance of Gaps. In I. Management Association (Ed.), Enterprise Resource Planning: Concepts, Methodologies, Tools, and Applications (pp. 329-346). IGI Global. https://doi.org/10.4018/978-1-4666-4153-2.ch020

Chicago

Rowland, Nicholas J. "Prioritizing Packaged Software Implementation Projects: The Significance of Gaps." In Enterprise Resource Planning: Concepts, Methodologies, Tools, and Applications, edited by Information Resources Management Association, 329-346. Hershey, PA: IGI Global, 2013. https://doi.org/10.4018/978-1-4666-4153-2.ch020

Export Reference

Mendeley
Favorite

Abstract

This chapter examines the dynamics of prioritizing implementation projects. Building on the notion of “fit-gap” work, this chapter emphasizes the significance of “de-prioritization” as a practical technique for managing Enterprise Resource Planning (ERP) implementation projects. “Fit-gap” is a term that resonates with current academic and professional discussions concerning the use of customization and work-arounds necessary to coax suboptimal implementations into functioning properly as the systems age. These are not idle matters given the near irreversibility of ERP projects once initiated and the reported high probability of failure following implementation. Drawn from in-depth interviews and internal documents collected from a multiyear organizational case study of ERP in an institution of higher education, this chapter reports on various uses, interpretations, and consequences of prioritization techniques used to manage implementation projects. In practice, the idea that complex software implementations can be theoretically reduced to mere gaps in fit serves to obscure the political conflict and ambiguous economic accounting that underlie committee work devoted to identifying gaps, deliberating on possible fits, and then prioritizing which gaps are fit immediately and others scheduled for fit later on. In conclusion, while fit-gap committee work is openly intended to result in fewer customizations overall, de-prioritization, as a management technique, appears to “remove without removing” agenda items from the implementation schedule. The upshot for managers: placing such decisions in purgatory delays indefinitely investments of time and finances into customizing new software to fit old policies, and all the work-arounds necessary to shore-up any lingering idiosyncrasies.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.