Having just completed implementing your enterprise-wide software, you are about lean back, put your feet up on the desk, and enjoy the fruits of your labor. Not so fast! While you were completing your implementation project, a new release of the software may have already hit the street or, for sure, there is one in the pipeline. Now you are faced with the decision as to if and when to take on the new release. Maybe now is the time to look at how a new class of software tools, enterprise process improvement (EPI), can assist you in the upgrade decision.
code that is being altered, a service pack should be able to be installed with little effort or testing. Alternatively, in addition to code changes, a new release can encompass new functionality, new data elements, and revised workflows and processes. While we will discuss the costs and tasks involved with implementing a new release, it should be obvious that many of the activities you completed in the original software implementation will have to be repeated, hence, the quandary as to whether to install