I will cover how to re-orient the way you think about and, thus, use IT in your business. That is: strategy.
I will also cover some tangible, pragmatic tactics to get you started.
There is much more, but this will give you start and likely keep you busy enough for the next year or so.
Also, I will highlight examples and learnings of companies I’ve been studying who have been successful.
We believe that most every company needs to build great software.
Our lives (and, thus, our sustainable profit margins) can be improved with better software. Businesses are finally discovering this after decades of treating IT like lesser corporate citizen.
BBVA was early to this as well, like with the purchase of Simple.
“Banks need to take on Amazon and Google or die. The shift to digital requires a complete overhaul of banks technology...it is a matter of survival.” -Francisco Gonzalez, CEOFrancisco Gonzalez, CEO
At a very high-level, this is the secret.
You establish a system of working on smaller batches of software that deploys frequently, observes what works and doesn’t work, and then starts the cycle over again.
Manufacturers understand the value of this process, and we’re just know both understanding and creating the platforms in IT that we need to do this with software.
I study IT as my hobby. I know: I’m not a great conversationalist at parties ;)
At the moment, these are three areas that top the list in what to focus on for companies to become software defined businesses.
I will go over each of them, and provide both tactics for starting and examples of your peers who have been successful.
Much of the talk you hear about cloud, DevOps, and technology today comes from consumer-centric, young companies: green field development that often has the luxury of starting fresh.
Once they become successful, they get caught up in their “legacy,” but that takes awhile. In most enterprise situations, you’ve inherited “legacy” and are dealing with the web of IT from day one.
You’ll need a way to prioritize projects so that you solve urgent, timely problems, but still manage to create your future.
How do we see people doing that?
DevOps is complicated, there’s a lot of moving parts.
It’s a principals based methodology that results in all of these moving parts.
The principals are focusing on the end-to-end of the system, a lean approach that focuses on delivering customer value (and removing waste), and placing as much importance on development as operations, and vice-versa.
It’s likely more focused, yet disciplined than what you’re doing.
Example: Lockheed changing, all of our customers.
Lockheed: needed to accelerate application development, delivered as a modern app. Adopted Agile principals to advance.
CoreLogic: needed a unified platform to sort out their portfolio, too many different platforms. Now they have a DevOps team that ensures they standardize on use of that platform, using Pivotal Cloud Foundry in a multi-cloud setup.
For each of your applications, you’ll need to do these 12 things, if not more.
You can’t hope to do that manually, or with the human-driven processes of ITIL and ITSM that we currently have.
Warner: putting the software factory in place - 6 months to 6 weeks, $1.1m savings per app.
GE: using the platform for their industrial internet – example: wind-turbine cf-push.
Becoming a Software Defined Business
Software Defined Business
26 May 2015
@cote | firstname.lastname@example.org
Companies want to use software for competitive advantage
to achieving sustainable innovation to secure leadership
To do this, companies are focusing on building their software
Three tactics that are working for your peers:
1. Re-discovering Innovation-driven IT strategies
2. DevOps provides the process for how it’s done
3. Cloud platforms provide the foundation
@cote – Director, Technical Marketing
at Pivotal for Pivotal Cloud Foundry
Former industry analyst at 451
Research and RedMonk
Corporate Strategy & M&A at Dell
Former software developer
More: http://cote.io or email@example.com
“Silicon Valley is
We are going to work
hard to make our
services as seamless
and competitive as
-Jamie Dimon, CEO@JPMC,
2015 letter to shareholders
Source: 2015 letter to shareholders.
[DevOps + cloud] == continuous delivery
(More or less)
(IaaS, PaaS, VMs)
(monitoring, scaling, etc.)
Development CI/CD Ops
Three areas that are working
Enterprise IT is a victim of it’s own success
Make time to establish a strategic planning
mind-set in IT
Most of IT
Source: Cave men from Dare Obasanjo; James Clear on the Eisenhower Box.
Different approaches for different problems
Divide projects & code by:
1. Don’t touch/quarantine
2. Carefully integrate
Source: Cutter from Murry Cantor and Israel Gat, 2015. See Migrating to Cloud-native Applications book by Matt Stine.
E.g.: Explore/Exploit, bimodal IT, Cutter
model, stranglers and SOA-cum-
Tactic: choose your initial projects wisely
Mobile applications are an
Limit scope to ensure
Focus on business value,
time to market
Build small successes into
Learning from your peers:
Source: “Can You Put a Little Palo Alto Into an Insurer in Louisville?,” Wall Street Journal, April 28th, 2015; HumanaVitality promotional
video. See more at this "Humana Leads Charge for Digital Transformation In Louisville.” Also, see Cloud Foundry Summit 2015 session.
Source: “Getting Your Arms Around DevOps – DevOps Patterns and Practices,” Cameron Haight, Gartner, Oct 2014.
Goals that lead to DevOps
1. Customer-centric focus on software products – learning, design
2. The pipeline is the factory, from concept, to code, to production
3. Delivering software that runs on the Internet (mobile, web, etc.)
4. Faster turns, while maintaining quality, uptime, performance
– Lean approach to entire process
– Shorten time to customer value
– Keep the site up, resilience vs. failure
Tactic: combine Development & Operations
Sources: see The Practice of Cloud System Administration, chapter 8 for an in-depth definition and discussion. Also, see Damon Edward's 2012
piece "Use DevOps to Turn IT into a Strategic Weapon.” Also, The Phoenix Project for a story of DevOps in the style of The Goal.
DevOps is the evolution of Agile to include
• Gartner predicts 25%
penetration by 2016
• Requires an Agile
approach, often you
• End-to-end focus
Source: "Gartner Says By 2016, DevOps Will Evolve From a Niche to a Mainstream Strategy Employed by 25 Percent of Global 2000
Organizations,” Gartner, March 2015. See also the Lockheed Martin keynote and the CoreLogic talk at Cloud Foundry Summit 2015.
Learning from your peers:
When you’re successful, you’ll have too many
applications to support
100’s of critical
10,000’s of critical
12 ops needs for the cloud stack
1. Role-based access to
2. Run specified code on demand
3. Coordinate cross service
4. Securely and reliably connect
to the public Internet
5. Read and write persistent data
6. Add and remove resources
7. Record internal and external
8. Isolate failures to recover from
9. Monitor and measure
performance and health
10. Detect and determine failure
11. Running a cloud business
12. Resilience to work tomorrow
Source: adapted from “You are Going to Need a Platform, Operational Concerns of the Third Platform,” April 2015.
Delegating to the platform for infrastructure
frees you up to focus on business value
Learning from your peers:Learning from your peers:
Source: Warner Music Group talk from 2013 and interview on software factories; GE Software on Wind-turbines at Cloud Foundry Summit
Tactic: you’re gonna need a platform
Source: see more on our website.