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.
used in a live production mode. Similarly, the new release code, vendor-supplied data conversion routines, custom reports, and enhancements may have to be applied to each release. Regardless, a significant amount of time will be required to investigate the impact of skipping a release. The main problem with skipping a release, however, lies in the possibility that problems will be encountered with the go-live release. Is the problem in the skipped release or the go-live release? How do you discover the