In our previous posts on upgrading to Oracle PeopleSoft 9.2, we have discussed getting prepared for planning and completing the planning for your upgrade. Now it’s time to upgrade your PeopleSoft application.

The upgrade to 9.2 from prior versions will feel much like your previous PeopleSoft upgrades, but with a twist; i.e. PeopleSoft Update Manager (PUM). It will be about the same length as before, generally 6 to 9 months depending on your customization level.

The good news is this: This upgrade is your last large upgrade.

Is there anything you can do to make this project better?

Here are a couple of ideas that may be of interest:

  • Black Box Upgrade Lab: Consider using an upgrade lab. A good upgrade lab reduces risk because they should have tools and processes specific to monitoring and executing the technical upgrade steps and improve predictability with tightly controlled schedules, scope and experience completing the upgrade steps.
  • Testing Customizations: If you have customized using a ‘bolt-on’ style, you might try testing the customizations immediately after the initial upgrade pass is complete and known online customizations are reapplied. In this way, you may be able to avoid developer time in reviewing customizations that don’t require changes. Any customizations that don’t pass testing are then passed to the development team to be corrected. This approach, when applied correctly, can significantly decrease development effort.

Once you get to 9.2, you will be doing much smaller updates rather than large upgrades. Therefore, as you go through this upgrade, there are artifacts that should be created with the future in mind.

  • Customization documentation: This continues to require review for impact with every update. You’ll need to look at it more often so it’s important that it is available, complete and up to date.
  • Test scenarios and scripts: You will reuse these with each update to perform regression tests to ensure that existing functionality is not adversely impacted by changes in the software updates. Consider a test automation tool and design the automation to be adaptable for future releases. Focus on your key business processes first.
  • Business Process documentation: At a minimum, you need to know what functionality you are using in the application as you review the changes in the new images released as part of the selective adoption cycle to identify impact.

Now that you are live with 9.2, do you have a selective adoption strategy and plan in place to take advantage of new features and functionality being released and smaller updates on a more frequent basis? Think about how this impacts your resource plan and ongoing sustainment budget and processes.

Note: If you delay keeping up to date with the modules you are using, eventually you could be in a position of having to do a major upgrade project. It makes sense to begin to have a plan.

Want to learn more?

Download to learn more about our Oracle PeopleSoft 9.2 Services and Selective Adoption Strategy.

Oracle PeopleSoft 9.2 Services
Selective Adoption Strategy