Undergoing the application migration journey can be cumbersome and challenging, especially when you have a complex application portfolio that consists of both legacy and newer apps on outdated systems. You are hindered by managing and operating manual processes to address security concerns, regulatory change and policy compliance. You know embarking on the cloud journey is inevitable and deciding where to start is overwhelming. Let us show you how. Join Matt Russell to hear how Pivotal helps large organizations plan and execute their application transformation initiatives by using a set of proven techniques and approaches that help you get started quickly and scale continuously. We use simple tools and start small to redefine current systems, and achieve cloud-native speed and resiliency. Let us show you how Pivotal can help you navigate your journey while instilling confidence along the way. Presenter : Matt Russell, Senior Director, Application Transformation at Pivotal

1. © Copyright 2018 Pivotal Software, Inc. All rights Reserved. Version 1.0
Approaches, Considerations and Stories of Success
Application Migration
Start, Scale and Succeed

2. Introduction
Pivotal is
awesome
Time is short
… so … 2”
deep
Learn how
we do things
Start - Scale
- Succeed
See examples
of some
things
Moving
existing Apps
to cloud

3. Your Application Portfolio is a Mix of Things
CONTAINERS
EVENT-DRIVEN
FUNCTIONS
DATA
MICROSERVICES
Batch
MONOLITHIC
APPLICATIONS
ESBJEE
COTS
MAINFRAME
.NET

4. Embedded OS
(Windows & Linux)
NSX-T
Java | .NET | NodeJS
Pivotal Application
Service (PAS)
Elastic | Packaged Software | Spark
Pivotal Container
Service (PKS)
>cf push >kubectl run
Pivotal Services
Marketplace
Pivotal and
Partner Products
Public Cloud Services
Customer
Managed
Services
OpenServiceBrokerAPI
vSphere
Azure &
Azure StackGoogle CloudAWSOpenstack
Fully Automated
Path to Production
Quantified Business-
Centric Outcomes
A Vision for the Future
Quick iteration of small, frequent releases; fast feedback and adjustment

5. The Struggle is Real “We need to get 200 apps
running in production on cloud
within the next few months.”
“We’ve been modernizing [...] for
the past year. Great, what do you
have running? Nothing.”
“My boss wants a plan to get
4,500 apps into cloud within the
next 2 years.”
“I’d like to get a work stream per BU
spun up so all 25 are working in
parallel – later this year.”
“We’d like to use the Strangler Pattern
and move order processing from
Mainframe to cloud”

6. What is Application Migration Transformation?
Re-Host
Containerize aka
“lift and shift”
Re-Platform
Minimal efforts to run
natively on PAS
Re-Factor
Convert to Cloud
Native aka
“Modernize”
Re-Build
Decompose and
rewrite from the
ground up
Application Portfolio
Funneling Process
Business and Technical filters, prioritization, scheduling, etc.

7. What We Believe
• You Should Move Apps to PCF
• Plan Just Enough to Start
• Define Hard Goals and Measure Results
• Start With “One Thing”
• Automate Everything You Can
• Build Skills by Pairing and Doing
• Let Real Work Inform Strategy

8. Start
© Copyright 2018 Pivotal Software, Inc. All rights reserved.

9. What You’ll Need
YOUR PCF
PRODUCT
TEAM
MOTIVATED
BU
App Developers with
Domain Knowledge
An Initial Idea of
Migration Candidates
Empowered PCF
Platform Team
Aligned with BUs
ORGANIZATIONAL COMMITMENT
LIST OF APPLICATION CANDIDATES
GOOD PEOPLE
A motivated business unit with leadership committed to
Cloud and a willingness to invest time and money in
transformation.
Start with apps built <7 years ago using tech supported
by PCF (ex. JEE) that are actively being used, updated and
maintained
A small team of people that understand candidate
applications and made available to work on the initiative
in a dedicated way

10. Fundamentally Speaking
Getting apps to run on PCF is easy. Policy, regulation, manual process, organization and politics is hard. Tackling these things can take
time so let’s start right away. Let’s really dig into the path to prod and define the value stream. Identify the manual process and
bottlenecks. Figure out how we measure near-term success. Do it with working code.
Identify a
small set of
apps
Define a
Funnel to
make
decisions
Baseline the
Path to prod
Fire a tracer bullet to validate assumptions and push on path to prod constraints

11. Technical Filter
Type (ex. COTS, ISV), Suitability Factors, etc.
Application Portfolio
Business Filter
Criticality, Risk Tolerance, Change Frequency, etc.
Prioritized Backlog
App Tx Iterative Process
App Patterns PCF
App
Measurement & Learning
Select top
app in
migration
backlog
Continued
iteration
Create / update patterns, provide
feedback to enhance filtering and
backlog velocity
Application
Transformation
Funnel
Use of tooling and templates to
quickly make effective candidate
selection, constantly prioritize
work and continuously share
feedback to accelerate future
efforts

12. Funneling Decision Tree
PAS
Triage
PKS
Triage
PAS App
Queue
Wave
Candidate
Filter
Apply Business
Filters
Apply
Technical
Filters
No
PAS Candidate
PKSCandidate
Yes
Business
Score
Technical
Score
Matrix
Prioritization
Apply Human and
Organizational
Factors
Application
Wave Selected
Deprioritized apps re-queued
Iterate through funnel to produce multiple waves as needed

13. Technical Triage:
App Foundry
Automated suitability
assessment and decisioning
framework.
Currently a closed beta,
targeting GA this fall.
Upload binary or map
to source control Parsers for most common
languages (Java, .NET, PHP,
Ruby, etc.)
Extensible rules (100s
available currently)
UI dashboard to help
triage decisioning

14. Sample: Path to Production
Division of a Very Large Banking Customer
65 Steps consisting of 45 days of wait and 180
days of process time for a total cost, per new
application, of $150,000.
● Workshop to define the basic process baseline
● Break down the larger steps into detail
○ Steps
○ Who is involved
○ Time required
○ Dependencies
○ Average cost
● Flag areas of potential automation
● Identify the full duration of time and cost
● Take “1” app and run through the process
○ Validate / invalidate assumptions
○ Try to automate in low-risk way
● Use as roadmap for subsequent steps

15. Scale
© Copyright 2018 Pivotal Software, Inc. All rights reserved.

16. Building Blocks of an At Scale Program
Measurement
Quantify Success
● OKR and KPI
● Business Impact
● Framework for
Governance
Internal Consulting Function
FTE Leaders - Pivotal - Qualified SI
Skills
Power the Engine
● Boot Camp Training
● Knowledge Base
● Mob Programming
● Pair Programming
Funnel
Assess and Prioritize
● Business value
● Technical Suitability
● SNAP Analysis
● App Roadmap
Buckets
Document the Learning
● Defined Archetypes
● Cookbook
● Recipes
● Patterns
Process
Measure and Automate
● Value Streaming
● Pairing / Agile
● Incremental Wins
● CI/CD, QA. etc.

17. Pivotal’s App Tx Iterative Process
• Portfolio level goals
definition
• Cloud suitability
assessment and
education
• Define OKRs
• Discuss timeline,
staffing, risk,
dependencies,
etc.
• One-week iterations
• Hands-on code within 2-3 days
• 1s to 10s of apps moved in 1s of
weeks
• Working code used to inform a
cookbook of patterns
Product Backlog
(Pivotal Tracker)
Boris
Event
Storming
OKRs
Slice
Analysis
Snap /
SnapE
Patterns
ScopingDiscovery
Ongoing Delivery Cycle
We deliver working code via
replatformed apps and modernized
slices that prove out patterns
Value
Stream
We work on a fixed timeline and spin
this wheel many times, using the
techniques as necessary
Fixed Timeline Engagement
Supported by a Paired Team
Want to know more?
Search for “Tools to Slay the Fire Breathing Monoliths”
For a 1 hour deep dive on YouTube

18. Working Code Informs Your Cookbook
We accelerate team velocity using a
“cookbook” filled with recipes written by
developers as new patterns for
transformation and legacy interoperation
are discovered through hands-on work.
Recipes are written in Git
markdown. The Cookbook is a
PCF site, includes search and is
assembled using a CI pipeline

19. TDA AppTx FY19Q1
Expanding Scale
ENABLEMENT
TEAMS
BU - A
BU-LEVEL DEV
TEAMS
BU - B BU - C
Move toward parallel execution
● BU move toward autonomy
● Use a common funnel template,
calibrated by each BU
● Enablement teams provide approach,
tooling, support to BU through pairing
● Dev teams enable next wave dev teams
through pairing / cell division
● Tune the funnel
● Migrate subsequent waves of apps
GOVERNANCE AND STANDARDS

20. Notional Timeline, Progression and Staffing
Educate and Drive OTJ
Enablement While
Delivering Results
START
Define OKRs, Establish
Funnel, Publish
Cookbook, Show Wins
Ramp-Up
Replatforming, Learn,
Adjust and Oversee
INGRAIN
Define and Deliver
Incremental
Modernization
Program(s)
Multiple Teams
Running at High
Velocity
SCALE
Critical Mass of Apps
Running With Full
Automation and High
Security
Pivotal teams enable, pair,
kickstart and oversee
SI Partner(s) use
templates, deliver
expert staffing and
drive scale
Customer people as they
ramp skills and execute using
new models
STAFFING
3 +/- MONTHS 6 +/- MONTHS 12+ MONTHS

21. Succeed
© Copyright 2018 Pivotal Software, Inc. All rights reserved.

22. Recent Customer Overview
“We've been through a lot of service engagements, and by far we've had the
best experience with you guys at Pivotal. You guys are professional and you
really know your stuff.” - Product Owner @ Top 3 US Wireless Carrier

23. Commercial Division of a Top-5 Insurer
SCOPING AND SUITABILITY INCEPTION AND SNAP ANALYSIS TEN, 1-WEEK ITERATIONS OF EFFORT
● 10 Apps Running in PCF (as 15 MVPs)
● Cookbook of 50 Cloud App Recipes
● 13 Developers Trained on XP / TDD
● Increased Test Coverage & Use of Standard CI Pipelines
● Established Cloud Migration COE Using the “Pivotal Way”

24. App Transformation
Team Room onsite at a
Midwest Customer
Simple Objectives for a
5M+ LOC Modernization
Initiative
Event Storming for
Modernization of a $1b
Revenue System
Cookbook of Cloud Native
Recipes Informed by
Working Code

25. Scalability
500K Internet Facing
Users
(Go-Live in July)
300 Initial
App Instances
2 Data Centers using
vSphere in Active-Active
deployment
Security
21 Concourse Pipelines
for automation of
patches and upgrades.
23 CVEs fixed by Pivotal
in 2018 and delivered as
part of PCF
0 Information Risk
Mgmt. issues to address
Skills
6 Devs + 2 PMs
8-week App Tx
expanding to
60* Customer
Developers
5 Platform Operators
trained during a 4-week
Platform Dojo
1 Platform Team
Stability
0 minutes downtime for
running Apps in Prod &
Dev. PCF environments
1 Major intra-day
upgrade to PCF 2.1 with
0 downtime
Consistent response
times < 12ms
Speed
90x
Faster application
release cycles
0 midnight monthly
weekend outages for
App releases
3 hrs to complete a
major version PCF
upgrade
Outcomes (Inside of 90 Days) with Go-Live in August
Savings: Faster Time-to-Market + Enabler to moving Apps to the Cloud
Sustainability: Platform Dojo + App Tx + Balanced Account Team + SMEs

26. Cloud Migration Velocity Powered by Pivotal
1st project; started a
“migrate to PCF” initiative
within Business Unit “A”
1st project complete; 10 existing
apps moved into 15 on PCF
850
AIs
1400
AIs
1500
AIs
An ambitious, multi-year App
Modernization initiative starts
7000
AIs
Ramped from 250 to 1000+ logical
applications running on PCF from
June of 2016 to June of 2017
250
AIs
First project in Business Unit B to launch new product
(while modernizing APIs that underpin it)
600
AIs
Project starts to modernize core system
that spans new customer acquisition ->
renewal (large revenue system)
2300
AIs
Short, 1mo Project to Move
Set of 50 API Services to PCF
Major BU “A” (first adopter advantage)
IT Business Services
International
Hosting
IT
Major BU “B”

27. We are a team of Solution Architects and
Strategists that jumpstart Application
Transformation initiatives to quickly show
measured wins. We use simple tools, start small
and scale fast to redefine current systems and
achieve cloud native speed, resiliency and
economics.
WE ARE PIVOTAL APP TX

28. Buy This. Must Attend. Register Today. Do It.Download This.
Shameless Plugs for New, Great, And Related Things

29. Recap…
1
Many of Your Apps
Will Run on Pivotal
Cloud Foundry
Start by
Replatforming and
Modernize Where
it Makes Sense
Use Real Work to
Inform Strategy on
Your Cloud Native
Journey
2 3