Down Under: Business Process Maturity and Technology (IT)
In his Column this month, John Jeston describes an all too familiar scenario. An organization purchases an expensive ERP system, the IT department develops and implements a application. Three years later, an external review discovers it`s not working. What went wrong? John`s analysis suggests that the maturity level of the business unit had not been identified or considered in the development of the application resulting in an unsuccessful implementation. John offers three possible solutions to the problem and proposes the one most likely to succeed in the circumstance.
Down Under: Business Process Maturity and Technology (IT)
June 4, 2013 , By