Release Change Planning Flashcards

1
Q

What is the objective of release change planning?

A

Provide best practice guidance and helpful resources to the customer on Release Change Planning utilizing:
Release Management Review
Configuration Change Review

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the customer value associated with release change planning?

A

Provides a framework for customers to create a governance plan to prepare for updates.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the scope of regression testing? What should be tested?

A
Functional testing:
Break / fix code, defects
Enhancements
Configuration Changes
Interfaces
User interfaces

Non-functional testing:
Software application updates.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is automated regression testing ART?

A

A software testing technique that utilizes computer-based testing tools and techniques. Applies the work flow, plan, scripts and other processes within a regression testing methodology.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is Opt-In?

A

An operational procedure in which customers are given the opportunity to activate/adopt new product features/function on their own schedule/timeline. This allows the customer to decide when they want to move a new feature into production, and allows them more time for testing than would be available for a mandatory update.

Oracle’s Fusion applications offer customers the option of adopting new features/function on their own schedule.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is a mandatory update?

A

An update the customer must take on the schedule dictated by the software provider. The update or feature/function is part of a package that will be loaded into the customer’s environment on a specific schedule for both their staging and production environments.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Does an optional update ever become mandatory?

A

Opt-in feature/function that is introduced in an update will usually expire in either the next update or the one that follows the next update. For example, if new feature/function is introduced in update N, the opt-in will usually expire in update N+1 or update N+2.

When the opt-in expires, the testing period for the new feature reverts to the same two-week period for a mandatory update.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What should a customer consider when evaluating a new feature?

A
  • Is the change optional or mandatory?
    • What impact will it have on the business?
    • Who are the key stakeholders who will be impacted by this change?
    • Have the stakeholders weighed in on the change? If so, what are their views? If not, reach out to them.
    • When is the best time to deploy the change into production?
    • How does the timing affect adoption and deployment?
    • How does adoption affect the testing plan?
    • How will the users be educated on the change?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How many annual updates are their for the Oracle Back Office SaaS products?

A
  1. EPM cloud has 12 (updates are included in monthly maintenance)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are Oracle cloud notifications?

A

Customer notifications containing important information regarding maintenance, updates, refreshes, scheduling modifications, and more. When applicable, dates/times, next steps, and helpful doc links are also included.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Who receives the notifications at the customer?

A

When Oracle activates a new cloud service, only a few individuals (Service Administrators, Account Administrators) are initially set up to receive these communications.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

How does the client add contacts to receive notifications?

A

The customer service admins:

  1. Sign in to My Services
  2. Click on the Users link (in the grey bar at the top right of screen)
  3. Select the Contacts tab
  4. Click the Add Notification Contact button. Add the contact.
  5. Click on the Notification Preferences tab
  6. Specify the notification delivery preferences for that contact
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is release change planning?

A

Governance plan for customers to use to prepare for updates.
Incorporates the Change Management Checklist.

Focus on:
Determine the Impact of proposed changes
Categorize the change by business unit or process
Assess Technical and Business Readiness
Plan for Documentation and Training Impact
Determine Operational Readiness

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What 2 activities are included in release change planning?

A

Release Management Review

Configuration Change Review

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is a release management review?

A

A discussion with customers about upcoming new features in the next release update. Limited in scope, utilizes the release management info put together by the SMEs. There is no template for a RMR, you select the slides by pillar by product that you want to use.

Increases customer adoption because many customers do not look at Cloud Readiness release notes or attend webinars in preparation for the next update.

Process:
Highlight key new features by pillar.
Present Pre-built PowerPoint decks to the customers.
Decks are posted by release cycle (quarterly or monthly in some cases).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What steps should be included in planning an update?

A
  1. Determine what updates are mandatory, and which are optional
    “Break/Fix” code is mandatory
    New feature/function may be optional, depending upon the product (e.g. Fusion new feature/function may be adopted on your own schedule until, at some point, they become mandatory)
  2. Communicate Updates with Management in Advance
    Any new feature/function should be discussed for potential impact to the business
    If new feature/function adoption is optional, discuss the benefits to the business
    Prepare for any “break/fix” updates that impact the business
  3. Create a Test Plan
    Mandatory updates have a two-week testing window before they are loaded into Production.
    Mandatory new feature/function has the same two-week testing window. These should be tested to ensure that they do not impact current configuration.
    Optional updates allow for flexibility in testing
17
Q

What are 3 test plan considerations?

A

A. Mandatory Updates Only

  • There’s a two-week testing window before they are loaded into Production.
  • Plan to start testing as soon as the Staging environment is updated.
  • Pay particular attention to any fixes associated with Service Requests you have submitted.
  • New feature/function that is mandatory should be tested to ensure it doesn’t impact current configuration.

B. Optional New Feature/Function
Consider taking additional time to test before turning on the feature in Production
Plan for UAT of new features.

C. Deferred New Feature/Function may become Mandatory
Once optional new features become mandatory, testing time reverts to the two-week mandatory update timeline
Plan ahead to avoid being forced into a two-week test for new feature/function

18
Q

What types of non-functional testing should also be performed?

A
Performance 
Load/Stress
Security 
Network 
Interface
19
Q

What business advisory service does release management review fall under?

A

Business Continuity Assurance

20
Q

What business advisory service does configuration change review fall under?

A

Business Continuity Assurance

21
Q

What business advisory service does emergency changes and updates review fall under?

A

Compliance and Governance

22
Q

What does the release management review team do?

A

For each product update, the team creates a ppt deck that highlights key features. CSMs present the decks to their customers.

23
Q

What does the emergency change update and alert team do?

A

Document deprecations and EOL.

24
Q

What does the configuration change review team do?

A

Document setup recommendations.

25
Q

What is regression testing?

A

Run and rerun functional and non-functional tests on an application instance.

26
Q

When should you deliver the RMR?

A

For all products (with the exception of EPM), this service should be offered quarterly as the release updates are published.

27
Q

When should you deliver the CCR?

A

This service should be delivered together with the first Release Management Review session post go-live.
Should match the product’s update cycle (i.e. quarterly or monthly).

28
Q

What is a configuration change review?

A

It is a process to get ready to take opt-in features included in a quarterly update.

29
Q

What is the customer value associated with the change change review?

A

Summary of all opt-in features by business process specific to the customer’s product footprint; understand the value and how to get ready.

30
Q

How do you prepare the configuration change review?

A
  • Identify the services (i.e. scope)
  • Identify the products within the pillars
  • Identify the business processes
  • Locate the Cloud Readiness page for each applicable pillar
  • Within the Cloud Readiness page, select the product by pillar, go to What’s New
  • Review Features Summary; Look for Customer Action Required