Deciding When to Change or Add Business Processes
When upgrading, you should answer the following:
- Are you upgrading to implement the new functionality?
- Are you upgrading your current processes without changing functionality, but may implement the new functionality later?
Implementing your current processes in a new system can mitigate risk in the upgrade. However, your business realities may preclude this approach, especially if the updated processes in the software can improve operations. For example, the business might choose to take advantage of new capabilities as quickly as possible, or it may be more appropriate to modify processes and engage in a coordinated training effort to increase user adoption of the new solution.
Weigh the pros and cons of these approaches to choose the best strategy for your organization.
Related Topics
Treating Your Upgrade Activity as a Formal Company Project
Using an Appropriate Change Management Strategy
Building an Upgrade Team with Broad and Complementary Skills
Utilizing Peer and Oracle Resources
Ensuring the Quality of Your Data
Taking Inventory for Your System
Understanding and Mitigating Project Risks
Calculating New Hardware Sizing
Identifying Custom Code and Scripting
Adhering to Current Tested Configurations Requirements
Implementing the Current P6 EPPM Release and Patches
Minimizing Application Data to Upgrade
Testing a Copy of the Production Database
Leveraging Existing Test Scripts and Plans
Training End Users on the New Solution
Last Published Tuesday, December 12, 2023