closer look: developing fluid - oracle...title implementing a selective adoption strategy created...

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |

Closer Look: Developing Fluid Applications


Implementing Selective Adoption• Selective Adoption – Goals and benefits of PeopleSoft’s new delivery

model.

• The Proactive Organization – How your organization must prepare to take advantage of the benefits of selective adoption.


Topics

Understanding Selective Adoption

Building a Proactive Organization Plan

Additional Resources


Selective Adoption Goals

• Incrementally deliver new enhancements.

• Eliminate major upgrades.

• Take only what you want.

• Take changes when you want.

• Retain strategic customizations.


Old: Bundles and Upgrades

• Frequent maintenance

• Take all maintenance

• Recommend staying current

• Infrequent enhancements

• Major upgrade every 3‒4 years

• No incremental changes

New: Selective Adoption

• Frequent maintenance

• Take selective maintenance

• Determine stay current strategy

• Frequent enhancements

• No major upgrades

• Incremental changes 2‒3 times/year

PeopleSoft Delivery Model


Topics





Proactive Organization• A proactive organization will create

the internal business processes, practices, and relationships that optimize the benefits of the new delivery model, in every product phase:–Planning and analysis

–System implementation

–Rollout


Your Proactive Organization Plan

• Change your mindset.

• Create an annual schedule.

• Stay on a current version of PeopleTools.

• Automate your testing.

• Roll out incremental change.


Old:

• Business process drives software

• Customizations are readily available

• Maintenance is deferred

• Focus on optimizing transactions

• Business systems are static

New:

• Delivered process is basis

• Customization is disciplined

• Maintenance is frequent

• Focus on optimizing system

• Business systems are agile

Mindset Changes


• Work with everyone to help them understand and adopt change.

• Reinforce need for and value of change:

– Project funding

– Roles and responsibilities

– Project/Product governance

• None of this is easy or automatic. There is a deep entrenchment of what has worked in the past.

Mindset Change


Plan Your Schedule• Schedule should cover maintenance, new features, and customizations.

• Maintenance includes:

– Bugs, legs/regs

– Stay current

–Opportunity value of having system ready for change

• Enhancements should be:

– Evaluated

– Rolled out incrementally


• Example Schedule:

–Minor release 4 times a year• 1.5 to 2 month projects

• Regulations and bug fixes

• Minor user requests

• Feb, May, Aug, Nov

–Major releases 2 times a year• 5-month major project

• New enhancements

• Get current plans

• Apr, Sept

Plan Your Schedule


• PeopleTools updates are the same as they have always been.

• PeopleTools license says:

– Full support for 12 months after next release.

– Limited support for additional 12 months.

• May be required to be on a supported version in order to apply maintenance.

PeopleTools Maintenance Policy


Minimum PeopleTools version can be found on the Cumulative Feature Overview and in Update Image Contents List spreadsheet available for each Update Image

PeopleTools Maintenance Policy


Test Automation Strategy• Testing is the largest part of any project.

• Start your regression tests by:

– Automating testing of mature products, not new development.

– Having functional users design tests and technical users build and run tests.

– Implementing a test documentation policy, which is key.

• Build repeatable portable tests:

–Migrate tests from environments.

– Page prompting allows for direct page access (navigation free).

– Scroll prompting to identify by key not index.

– Cross reference reports.


Rolling Out Incremental Change• New analyst role:

– Understand what is coming and what is there:• Planned Features and Enhancements Info Center

• Cumulative Feature Overview Tool

–Work with IT and LOB owners to keep them informed about what is available and what the impacts are.

– Develop short-term and long-term adoption plans.

– Identify enhancement priorities.


Summary

• It is the proactive organization that will gain the most from selective adoption.

• Take the time to respond to the new way PeopleSoft delivers maintenance and enhancements.

• Look at your internal processes and evaluate them based on the new delivery model.

• Develop new working relationships between IT and LOB.


Topics






• Whitepaper: How to Gain Value From Selective Adoption

–My Oracle Support Doc ID 1934210.1

• PeopleSoft Online Help - PeopleSoft PeopleTools 8.54

– Change Assistant and Update Manager

• PeopleSoft Update Manager (PUM) Home Page –My Oracle Support Doc ID Doc ID 1641843.2


Additional Resources, Continued

Getting Starting with your PeopleSoft Upgrade training on Oracle Learning Library

Oracle University Training

• PeopleSoft Lifecycle Management Rel 8.53 (4 day course)

• PeopleSoft Update Manager Rel 8.54 (2 day course)

• PeopleSoft Lifecycle Mgmt & Update Manager Accelerated (5-days)


Safe Harbor Statement

The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

closer look: developing fluid - oracle...title implementing a selective adoption strategy created...

Documents