S105465GC10 Mod08 27aug

Oracle Cloud Project
Management for Partners

Module 8 – Implementation Approach for
Cloud Solutions in Scope
Student Guide
S105465GC10
Learn more from Oracle University at education.oracle.com

Copyright © 2020, Oracle and/or its affiliates.
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training
course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle.
The information contained in this document is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of
such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software
documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure,
modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered
hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable
contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
Third-Party Content, Products, and Services Disclaimer
This documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not
be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
Module 8 - Implementation Approach for
Cloud Solutions in Scope
Oracle Cloud Project Management Training for Partners
Oracle Alliances & Channels

Safe harbor statement
The following 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, timing, and pricing of any features or functionality described for Oracle’s
products may change and remains at the sole discretion of Oracle Corporation.
Statements in this presentation relating to Oracle’s future plans, expectations, beliefs, intentions and
prospects are “forward-looking statements” and are subject to material risks and uncertainties. A
detailed discussion of these factors and other risks that affect our business is contained in Oracle’s
Securities and Exchange Commission (SEC) filings, including our most recent reports on Form 10-K and
Form 10-Q under the heading “Risk Factors.” These filings are available on the SEC’s website or on
Oracle’s website at http://www.oracle.com/investor. All information in this presentation is current as of
September 2019 and Oracle undertakes no duty to update any statement in light of new information or
future events.
2 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Sarkis Kerkezian, PMP, MBA, TOGAF
Director, Partner Implementation Advisory

Oracle Channel & Alliances

Learning Objectives
Implementation Approach for Cloud Solutions in Scope
By the end of this Module you should be able to:

• Understand the difference among the various Implementation Approaches to Cloud Solutions
• Explain the Solution, Requirement and Innovation Driven approaches
• Depict the difference between various approaches
• Describe the Agile Manifesto and the key Principles
• Understand the concept and importance of DevOps
• Explain the key concepts of DAD – Disciplined Agile Delivery
• Understand the key concepts of gathering software requirements through Personas
• Understand the Use case model and where and how to use
• Plan Your project scope with the appropriate Implementation Approach

Oracle Cloud Delivery Framework
Analyze & Plan & Configure & Validate & Transition & Sustain &
Prepare Design Build Test Go Live Realize
Project Management & Governance

Cloud Provisioning & Cloud Security,
Environments Identity & User Continuous Testing Support Plan &
Knowledge Areas
Management Management Strategy & Plan Adoption Strategy
Project Management Implementation

Cloud Architecture Data Management
Plan & Delivery Approach for Cloud
Envisioning & Planning & Migration Plan
Approach Solutions in Scope*
Training & Knowledge

Project Objectives & Risk & Issue Mgmt. Organizational Change &
Transfer Strategy &
Business KPIs (Including SR Mgmt.) Communication Mgmt.
Plan
Project Artifacts, Deliverables & Milestones
* * *
ERPM SCM HCM Analytics Security Autonomous Application

CX Integration
SaaS PaaS Database Development OCI

Oracle Cloud Delivery Framework
Knowledge Area - Implementation Approach for Cloud Solutions in Scope
Project Management & Governance
• To identify and decide the implementation approach for

Implementation
the cloud solution component in scope (SaaS, PaaS, OCI)
Approach for
Cloud Solutions and determine the activities and tasks to be included
in Scope project plan and WBS – Work Breakdown Structure
Project Artifacts, Deliverables & Milestones
SaaS PaaS OCI

Part 1- Understanding the Solution,
Requirement & Innovation Driven Approaches

SaaS, PaaS, OCI Cloud Solution Components
Different Implementation approaches and scenarios can be considered based on the

solution/technology components in Scope
Solution Driven Hybrid / Agile
Requirement Driven
Waterfall/Predictive
Innovation Driven Agile / Adaptive

Implementation Approaches for Cloud
Solution Driven Requirement Driven Innovation Driven
SaaS Applications like: • Integrations (Oracle integration • Chat Bots (Oracle Digital Assistant)
• Fusion Apps (HCM, Cloud) • Oracle Content and Experience
Engagement, ERP, SCM) • Oracle Process Cloud • PaaS Extension
• Taleo • Custom Application Development
• Security (IDCS & others)
• Mobile Apps
• Service Cloud (Right Now) • BI Analytics • Oracle Visual Cloud Builder
• Field Service (TOA) • OCI – Move & Improve • Emerging Technologies
• Commerce (ATG) • Marketing (Eloqua, Responsys • Others
• CPQ • EPM
• Others…
TOOLS & TECHNIQUES

• Set Up/Configuration • Documenting Requirements - Personas & Use Case Model to gather
Questionnaires Requirements
• Analysis/Design/build/Test
• Iterative Workshops based - Agile (Scrum, XP Programming, lean,
Kanban, Crystal, SAFe etc.
Solution Driven Approach Solution Driven
Mainly applicable for Cloud Application Services (SaaS)
An approach based on the use of a pre-defined

business solution as the proposed customer business
solution; tailoring to the desired business outcomes
during the project progressively refining the
configuration through iterations
• focuses on mapping a business function to pre-defined
solution with embedded and highly configurable
processes producing a clearly defined output.
• foundational elements of the business solution are
already reflected in the components that comprise the
pre-defined solution.
• seeks to avoid, or minimize, customizations by promoting
leading practice use of standard functionality to meet
common business needs. Progressive Refinement

Solution Driven Approach
Mainly applicable for Cloud Application Services (SaaS)
Typically comprises of:

• business process models (or business flows) based on the Oracle
Modern Best Practices depicting the functionality included
• Pre-determined setup values that enable a working application
instance to be established quickly for familiarization/mapping
purposes
• Pre-defined demo/test scripts based on the pre-defined setup
values, which can be used to demonstrate the functionality
included.
• Guided Configuration based questionnaires to set up the
application in minimum time
• Predefined Distinct roles with Job roles, duties, roles and
responsibility matrix
• Embedded transactional reports (OTBI reports)

Solution Driven is Iterative and Incremental
“Think a little…Do a little…Show a little…Think a little more…”
Business
Drivers
Business
Information
Requirements
Gathering
Requirements
Analysis Analysis
Analysis
Design
Design
Implementation
Implementation
Test
Test
Waterfall Iterative and Incremental

Timeboxing
Iterative workshops requires time-boxing
Structured Timebox
Free Format Timebox

Iterative Solution Driven Approach – A bit Waterfall-y
Allowing for Frequent Customer Inspection & Feedback
Iteration 1 Iteration 2 … Iteration N GO LIVE
Requirements Requirements Requirements UAT
Analysis Analysis Analysis Launch Readiness
Design Design Design

Release to PRODUCTION
Implementation Implementation Implementation
Test Test Test
Customer – Inspection, Customer – Inspection, Customer – Inspection,

Acceptance, & Feedback Acceptance, & Feedback Acceptance, & Feedback

Develop a Two Level Work plan Approach
Project Management Framework
Implementation Plan
Project Execution and Control
Analyze Plan Validate Transition Sustain
Configure & Build
& Prepare & Design & Test & Go Live & Realize
Project Project
Iteration 1 Iteration 2 Iteration 3
Startup Closure
Activity 1 Activity 1 Activity 1
2 – 3 weeks
2–6 Weeks
} 4 – 6 weeks
Simple configuration (i.e. cloud, solution-driven) Complex modeling
Custom application development Complex or extensive configuration
Complex extension or custom development
Requirement Driven Approach
Applicable mainly for OCI, some PaaS and few SaaS Components Requirement Driven
An approach that is based on identifying requirements at the

outset of the project through interviews, process modeling
workshops, etc., and crafting a business solution based on those
requirements during the project.
A structured delivery approach that is based on contractual
deliverables and based on heavy documentation starting by
scope definition, requirements gathering, analysis, design,
development and testing in an sequence.
For example: designing a report or developing integrations
whereby functional and technical specifications are created first to
detail areas such as field mapping prior to commencing
development.

Requirement Driven Approach
Applicable mainly for OCI, some PaaS and few SaaS Components Requirement Driven
Requirements
Analysis
Design
Development
Testing
Deployment
Maintenance

Innovation Driven – Agile
PaaS4SaaS & Native Cloud Apps, Application Development Innovation Driven
> Agile isn’t a methodology at all, but a set of principles for developing software
> Agile is “collaborating to iteratively deliver whatever works”
> Agile is described as a flexible, iterative design and build process
• Emphasising adaptability to changing situations
• Ongoing communication among and within the project team and the client
• Dynamic environments with changing or evolving requirements (ie software and game
development)
> Agile projects are characterized by:
• A series of tasks that are conceived, executed and adapted as the situation demands
• Not pre-planned
> Being Agile helps teams respond to unpredictability through:
• Incremental
• Iterative work processes

Traditional vs. Agile Project Management
Predictive Adaptive
Traditional Agile
Plan-driven Unplanned
Disciplined Undisciplined
“Agility is the ability to balance flexibility and stability.”

Source: Highsmith, James A., Agile Project Management:
Creating Innovative Products, Boston: Addison-Wesley, 2004, p. 16

Where on the agility spectrum would an Airplane
Landing System project fall?
Predictive Adaptive
787 Dreamliner Tablet Game

The Major Paradigm Shift
Waterfall (Predictive) vs Agile (Adaptive)
Waterfall Agile
FIXED CONSTRAINTS Requirements Cost Schedule
Value/Vision
Driven
And then…
PLAN
Driven
ESTIMATES Cost Schedule Features

The plan Creates cost/Schedule Release theme and feature intent
Estimates drive estimates
Part 2 – Agile, Scrum & DevOps

Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over Process and tools
Working software over Comprehensive documentation
Customer collaboration over Contract negotiation
Responding to change over Following a plan
While we value the things on the right, we value the things on the left more.
Source: www.agilemanifesto.org

12 Principles of Agile
1 Deliver
Value 2 Embrace
Change 3 Deliver
Frequently 4 Work
Together
Our highest priority is to Welcome changing requirements, Deliver working software Business people and developers
satisfy the customer through even late in development. Agile frequently, from a couple of must work together daily
early and continuous delivery processes harness change for the weeks to a couple of months, with throughout the project.
of valuable software. customer’s competitive a preference for the shorter
advantage. timescale.
5 Motivated
Individuals 6 Face to – Face
Conversation 7 Working
Software 8 Sustainable
Pace
Build projects around motivated The most efficient and Agile processes promote
Working software is the
individuals. Give them the effective method of conveying sustainable development. The
primary measure of
environment and support they information to and within the sponsors, developers, and users
development team is face-to- progress. should be able to maintain a
need, then trust them to get the job
done. face conversation. constant pace indefinitely.
9 Technical
Excellence
10 Simple
Solutions
Simplicity — the art of
11 Self- Organizing
Teams
The best architectures,
12 Reflect
& Adjust
At regular intervals, the team
Continuous attention to maximizing the amount of requirements, and designs reflects on how to become
technical excellence and good work not done — is essential. emerge from self-organizing more effective, then tunes and
design enhances agility. teams. adjusts its behavior accordingly.

Agile Project Management
Characteristics
• Iterative, incremental delivery

• Integral customer involvement
• Change-readiness – the ability to create and
respond to change
• Leverage human strengths and cross-
functional teams

Scrum Flow Daily Scrum Meeting
24 hours
Feedback
Sprint Planning Meeting

2 – 4 weeks
Sprint Backlog
Sprint Goal
Potentially Shippable
Product Increment
Product Backlog
As prioritized by Product Owner
Sprint Review and Retrospective

Feedback Meetings

Assessing Progress
Taking Corrective Action
Burn-Down Chart
Burn-Down Chart Team is behind.

May need to remove items from the
sprint/iteration.
Team is ahead.
May need to add items
to the sprint/iteration.

Sprints embedded in Cloud Delivery Framework
Built 1 Built 2 Built 3

Continuous Planning
Act
• Planning is done in a top-
down/bottom-up manner.
• Level of detail matches
planning horizon. Adjust Plan
• Estimates for
iterations/sprints done by
project team.
Do

Innovation Driven Agile Development Identify a Problem &
Minimum Viable Product – MVP Define a Use Case
Fix and Continuous
improve and Ideas Design a concept to
enhance the product solve the problem of
the Use Case
Learn Faster
✓ Split Tests Learn Build Build Faster
✓ Customer Development ✓ Unit Tests
✓ Five Whys ✓ Usability Tests
✓ Customer Advisory Board How MVP ✓
✓
Continuous Integration
Incremental Deployment
✓ Falsifiable Hypotheses
✓ Product Owner Works ✓
✓
Free & Open Source
Cloud Computing
✓ Accountability
✓ Cross – Functional Teams ✓ Cluster Immune System
✓ Semi – autonomous Teams Data Code ✓ Just –in-Time Scalability
✓ Smoke Tests ✓ Developer Sandbox
✓ Minimum Viable Product
Collect feedback
from usage data
Measure Faster Measure Measure Faster
Build a Prototype
✓ Split Tests prioritize the core
✓ Funnel Analysis features
✓ Continuous Deployment
✓ Cohort Analysis
✓ Usability Tests
✓ Net Promotor Scope
✓ Real Time Monitoring
✓ Search Engine Marketing
✓ Customer Liaison Test the use case
✓ Predictive Monitoring
and evolve more
30 Copyright © 2020, Oracle and/or its affiliates. All rights reserved features for Go Live
Achieving Agility
Not JUST a change in methodology
• Change in the “culture” of the Customer

Enterprise
• Adapting to agile across the enterprise
• Changing focus from “tactical” project level
to “strategic”
• Business sponsors ownership of projects
• Strategic thinking critical for the business

Focus Shift
“What is Agile?” to “How can we apply Agile?”

• Mastering the cultural evolution to agile approach
• Applying agile concepts at the strategic or portfolio level.

Agile Suitability Assessment
1. Buy in and support to Approach

2. Trust in Team
3. Decision Making & Empowerment to the Team
4. Team Size
5. Experience – Skills Levels
6. Access to the customer
7. Likelihood of change and level of uncertainty
8. Criticality of Product/Service
9. Incremental Delivery
33 Copyright © 2020, Oracle and/or its affiliates. All rights reserved Source: PMI Agile Practice Guide
DevOps
Introduction

What is DevOps?
DevOps is a culture, movement or practice

that emphasizes the collaboration and
communication of both software
developers and other information- Development
QA
technology (IT) professionals while
DevOps
automating the process of software
delivery and infrastructure changes. It
aims at establishing a culture and
environment where building, testing,and
releasing software, can happen rapidly, Operations
frequently, and more reliably.

Goals and Benefits of DevOps
Goals Benefits
• Environment Stabilization
• Fast Development Methodologies
Enforces consistency, increase up-time
• Fast Quality Assurance
• Shorter Development Cycle
Methodologies
Manage requirements and code-
• Fast Deployment Methodologies
repository
• Faster time to market
• Increased Release Velocity
• Iteration & Continuous Feedback
Continuous build, push-button
(strong and continuous
deployments
communication between
• Reduced Defects
stakeholders — the end users
Regiment processes, automated testing
and customers, product owners,
• Process Metrics
development, quality assurance,
Track both time at each stage, and the
and production engineers)
errors and exceptions

The DevOps Cycle
In the Context of Cloud
Plan: task management, schedules Plan

Code: code development and code review, source code
management tools, code merging Monitor Code
Build: continuous integration tools, version control tools,
build status
Test: continuous testing tools that provide feedback on
business risks, determine performance
Release: change management, release approvals, release DEV
Operate OPS Build
automation
Operate: infrastructure setup, changes (scalability),
configuration and management, as code tools, capacity
planning, & resource management, security check,
service deployment, high availability (HA), data recovery, Deploy Test
log/backup management, database management
Monitor: service performance monitoring, log
Release
monitoring, end user experience, incident management

CI/CD – Continuous Integration Continuous Delivery
Continuous Deployment
Plan Code Build Test Release Deploy Operate
Continuous Integration Continuous Delivery
Continuous Deployment
Continuous integration (CI) is a process for developers and testers collaboratively validate new code
Continuous delivery (CD) is the process of continuously creating releasable artifacts
CI/CD is a process for continuous development, testing, and delivery of new code

Context of CI/CD
Value & Collaboration through lifecycles
Plan Code Build Test Release Deploy Operate
DevOps
Continuous Delivery
Value
Continuous Integration
Agile Development
Collaboration

Agile DevOps Process
Sprint
Continuous Feedback Continuous Feedback
Review
Daily
CI
Scrum
Agile
Continuous Feedback
Continuous Feedback DevOps
Sprint
CT
Phases
CI: Continuous Integration
CT: Continuous Testing
Continuous Feedback CD Continuous Feedback CD: Continuous Delivery

Build a DevOps Culture
Recommended Steps for Partners
▪ Let Dev + Ops collaborate to find solutions

Empower Change ▪ Let Dev + Ops jointly pick tools. Limit corporate mandates
From the Bottom Up ▪ Don’t restrict the choice of public cloud solutions
▪ Put Dev + Ops people under same line-level managers

Align Interests ▪ Change the way you measure/reward performance
▪ Flatten org chart to reduce fiefdoms
▪ Hire technical people who are skilled in DevOps

Bring In New Blood ▪ Set up training for DevOps skills
▪ Bring in consultants to help get started
▪ Sponsor teambuilding events

Build Trust ▪ Give Dev + Ops common goals to work towards
▪ When there's a failure, don't dwell on Dev or Ops failure

SAFe: Framework for Scaling Agile

Agile Methodologies, Frameworks, and Processes
A number of core Agile methodologies share the same philosophy expressed in the Agile Manifesto.
However, they have different practices, processes, and techniques.
Some of the Key Agile Methodologies are:
• SCRUM - www.scrum.org or Scrum Alliance www.scrumalliance.org
• Extreme Programming (XP) - www.extremeprogramming.org
• Crystal - www.toolsqa.com/agile/crystal-method
• Lean - en.wikipedia.org/wiki/Lean_software_development
• Kanban - www.kanban.university/
• Agile Project Management - www.apm.org.uk
• Feature Driven Development - agilemodeling.com/essays/fdd.htm
• Open UP - https://www.eclipse.org/epf/general/OpenUP.pdf
• Dynamic System Development Method (DSDM) - www.agilebusiness.org/page/whatisdsdm
• Scaled Agile - https://www.scaledagile.com/
• Disciplined Agile - https://www.pmi.org/disciplined-agile
Disciplined Agile (DA)
DA Toolkit
• Disciplined Agile (DA) is a hybrid toolkit

build upon the solid foundation of
other methods and software process
frameworks.
• DA adopts practices and strategies
from existing sources and provides
advice for when and how to apply them
together
• Has a Risk-Value goal driven Delivery
Lifecycle, scalable enabling teams
choose their way of working (WoW)
• DAD enables teams to adopt a guided
continuous improvement approach to
solution delivery.

Disciplined Agile
The four layers of the DA toolkit
1. Disciplined Agile Delivery (DAD)

2. Disciplined DevOps
3. Disciplined Agile IT (DAIT)
4. Disciplined Agile Enterprise (DAE)
DAIT addresses how to apply agile

and lean strategies to all aspects of
Information Technology (IT)
processes. DAIT extends Disciplined
DevOps, which in turn extends DAD

Disciplined Agile Enterprise (DAE)

Disciplined Agile Delivery - The Agile lifecycle
Scrum Based

Leveraging Agile & Scrum in Tandem with CDF Lifecycles
Making parallels with the DA Toolkit
Highest Priority
(M’s & S’s)
Enterprise
MoSCoW Iteration Reviews

Feedback

Both Scrum and Iterative Solution Driven Approach employ the approach of
“Think a little…Do a little…Show a little…Think a little more…”
Solution Driven Iterations Scrum: Sprints

Integrating all the Implementation Approaches Together
Requirements
Analysis
Business
Drivers Design
Configuration
Requirements Development
Analysis
Testing
Design
Deployment
Innovations: Scrum - Sprints
Implementation
Test Maintenance
Requirement Driven: Design & Built

Solution driven: Iterative Configurations

Part 3 – Gathering Requirements Using
Personas & Use Cases

Gathering
Requirements
• User Stories
• SRS – Software Requirement Specification
• Story Mapping
• WireFrame
• Personas
• Use Case Diagrams

Personas
For software Requirement Gathering & User Experience
A persona, in user-centric design is a fictional

character created to represent a user type that might
use a site, brand, or product in a similar way.
Personas are used as part of a user-centered

design process for designing software and are also
considered a part of interaction Design (IxD)
Creating personas help understand users' needs,

experiences, behaviors and goals.
personas are synthesized from data collected from

interviews with users captured in 1–2-page
descriptions that include behavioral patterns, goals,
skills, attitudes, with a few fictional personal details
to make the persona a realistic character.

10 Steps to Personas Development
Step by Step Guide
1. Finding the Users

2. Building a Hypothesis
3. Verifications
4. Finding Patterns
5. Constructing Personas
6. Defining Situations
7. Validation and Buy-in
8. Dissemination of Knowledge
9. Creating Scenarios
10.On-Going Development
54 Copyright © 2020, Oracle and/or its affiliates. All rights reserved Source: Lene Nielsen: User Focus & Innovation
Leveraging Use Case Model
To Gather Requirements in Cloud Projects
A use case is the specification of a set of actions performed by a system, which yield an observable
result, that is, typically, of value for one or more actors or other stakeholders of the system.”
Use case analysis is a technique for eliciting,

analyzing, documenting, and communicating
the functional requirements of a business or
system.
• Natural way to organize functional
requirements
• Easier for users to understand
than traditional textual
requirements

Provide a Context for Requirements
Leverage Use Case Model
Business IT
Stakeholders Stakeholders
Use Cases
Business Functional
Objectives Requirements

The Value of Use Cases
Discover
Stakeholder
Priorities
Explain what the
system will do
Focus on
requirements, not
design
Plan and manage
project
Provide foundation
for test cases

The (System) Use Case Model Use Case Diagram
A Use Case Model includes both diagrams Use Case

Order #1
Skis
and text
• The picture is called the Use Case Use Case
Return #2
Skis
Diagram
• The text is called the Use Case
Manage #3
Profile
Use Case Details
Actor
Use Case Details – Use Case #1

Actor Does System Does
1. The use case begins when the 2. The system responds by
customer selects the option to providing a list of …
use case #1

Developing Use Case Model
Example
Online Banking System
Transfer <<actor>>
Between CPS
Accounts
Pay a Bill Now
Set Up
Payment
Customer Schedule
Manage List
of Payees <<actor>>
XYZ Credit Bureau
Apply for a
Select User Loan
Preferences
Review Loan for Manage User

Approval Preferences System Administrator
Loan Approver

Further Readings and Links
• Agile Project Management with Scrum by Ken Schwaber

• Agile Estimating and Planning by Mike Cohn
• The Agile Manifesto: www.agilemanifesto.org
• Agile Alliance www.agilealliance.org
• Agile Practice Guide (APG) - www.pmi.org/pmbok-guide-standards/practice-guides/agile
• Agile at Scale by the Harvard Business Review: www.hbr.org/2018/05/agile-at-scale
• Agile Software Development: A gentle introduction: www.agile-process.org
• DevOps: https://devops.com/
• https://en.wikipedia.org/wiki/DevOps (check the references)

DevOps - Resources
to Help Make the Change

Conclusion
Now that you have completed this module, you should be able to :
• Understand the difference among the various Implementation Approaches to Cloud Solutions
• Explain the Solution, Requirement and Innovation Driven approaches
• Depict the difference between various approaches
• Describe the Agile Manifesto and the key Principles
• Understand the concept and importance of DevOps
• Explain the key concepts of DAD – Disciplined Agile Delivery
• Understand the key concepts of gathering software requirements through Personas
• Understand the Use case model and where and how to use
• Plan Your project scope with the appropriate Implementation Approach

Thank You
Oracle Cloud Project Management Training

Oracle Partner Network

S105465GC10 Mod08 27aug

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

S105465GC10 Mod08 27aug

Uploaded by

Copyright:

Available Formats

Oracle Cloud Project

Management for Partners

Learn more from Oracle University at education.oracle.com

Restricted Rights Notice

Third-Party Content, Products, and Services Disclaimer

Oracle Alliances & Channels

2 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Director, Partner Implementation Advisory

3 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

By the end of this Module you should be able to:

4 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Project Management & Governance

Management Management Strategy & Plan Adoption Strategy

Project Management Implementation

Training & Knowledge

Project Artifacts, Deliverables & Milestones

ERPM SCM HCM Analytics Security Autonomous Application

5 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Project Management & Governance

• To identify and decide the implementation approach for

Project Artifacts, Deliverables & Milestones

SaaS PaaS OCI

7 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Different Implementation approaches and scenarios can be considered based on the

Solution Driven Hybrid / Agile

Innovation Driven Agile / Adaptive

Solution Driven Requirement Driven Innovation Driven

TOOLS & TECHNIQUES

An approach based on the use of a pre-defined

10 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Typically comprises of:

11 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Waterfall Iterative and Incremental

12 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Free Format Timebox

13 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Iteration 1 Iteration 2 … Iteration N GO LIVE

Requirements Requirements Requirements UAT

Analysis Analysis Analysis Launch Readiness

Design Design Design

Test Test Test

Customer – Inspection, Customer – Inspection, Customer – Inspection,

14 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

An approach that is based on identifying requirements at the

16 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

17 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

18 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

“Agility is the ability to balance flexibility and stability.”

19 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

20 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

ESTIMATES Cost Schedule Features

22 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Individuals and interactions over Process and tools

Working software over Comprehensive documentation

Customer collaboration over Contract negotiation

Responding to change over Following a plan

23 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

24 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

• Iterative, incremental delivery

25 Copyright © 2020, Oracle and/or its affiliates. All rights reserved

Sprint Planning Meeting

Sprint Review and Retrospective

26 Copyright © 2020, Oracle and/or its affiliates. All rights reserved