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.
maintenance cost improvement
to make up missed maintenance payments and you must agree to come up to a supportable release level in a specified period of time. Therefore, before you go off maintenance, make sure that you understand the conditions to resume support. Option 3: Skip A Release (The Ugly) The third option is the middle-of-the-road alternative. Under this option you decide to implement every other release, skipping a release and catching up on the next one. The theory is that, if it costs x dollars to implement a release,