Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
11
The Coming Donkey Apocalypse
Day of the Donkey
Cloud, continuous delivery, and DevOps
…government edition
September, 20...
2
Conclusions
 Organizations are craving faster, more agile IT that creates better
product
– Government is seeking to imp...
3
 @cote – Director, Technical Marketing
at Pivotal for Pivotal Cloud Foundry
 Former industry analyst at 451
Research a...
44
Fear of
nerds
55
“Silicon Valley is
coming….
We are going to
work hard to make
our services as
seamless and
competitive as
theirs.”
-Jam...
6
Only 25% of
respondents felt that
their companies were
innovating in agile ways.
Source: Institute for the Future study,...
7
THE DEVOPS WILL SAVE US!
88
“We estimate that, by 2018, 90
percent of I&O organizations
attempting to use DevOps without
specifically addressing th...
99
Saving the
donkeys
10
Know your equestrian metaphors
Unicorns
• Flys around in clouds
doing magic
• Streams things &
doesn’t seem to need
mon...
11
Clipart from Gerd Altmann.
12
Clipart from Gerd Altmann.
13
Source: "Strategy, not Technology, Drives Digital Transformation," 2015 Digital Business Global Executive Study and Res...
1414© Copyright 2015 Pivotal. All rights reserved.Columbus Renaissance hotel, 3rd floor. See also Plumbing: Design and Ins...
15
Bad meatware spoils IT
Failure to change
the operational
model
31%
Doing too little
19%
Failure to change
the funding m...
1616
Getting to
DevOps
17
Goals that lead to DevOps
1. Delivering software that runs on the Internet (mobile, web,
etc.)
2. The pipeline is the f...
18
The word defines itself…
(1.)
DevOps is the practice of operations
and development engineers
participating together in ...
19
What developers do, simplified
Requirements
Design Code Build Verify Check-in
Team
Build
Update
Code
Note: “Screwing ar...
20
Developer flow, complexified
“Coding” is a very small part
21
DevOps == continuous delivery
(More or less)
Build Test/Verify
Package
repository
Version
Control
Infrastructure
Platfo...
2222
How’s it
going?
23
Things are improving, but we need accelerants
DIY
36%
CI
Products
28%
Other
8%
None
28%
What build automaton or CI/CD t...
24
It’s not much of an IT department, but I’m sorta
attached to it…
2525
Cheering up
donkeys
26
Simplifying “cloud native”
Source: Casey West’s cloud native piece in O’Reilly Radar, August 2015. See also Wikibon’s r...
27
Cloud native can be reduced to three technology layers, plus
“culture”
Source: slides in this section based on “Pattern...
28
The Cloud Native Platform, simplified
Applications
Runtimes
Infrastructure
Contract
Contract
Culture
Key transformation...
29
Management creates the game
 Leading change
management
 Setting, communicating,
tracking goals
 Dramatic organizatio...
30
Portfolio management balancing resources, creating time for
innovation
Source: “A Value Framework that Works for Transf...
31
The emerging cloud native organization model
Innovation: Plan, design, develop and
test business capabilities as deploy...
3232
Thanks!
@cote | cote@pivotal.io
“We are uncovering better
ways of developing software
by doing it and helping others
...
33
Further reading
Leading the
Transformation
(2015)
Excellent overview
of goals and
management
tactics for doing
Agile an...
Upcoming SlideShare
Loading in …5
×

Day of the Donkey with cloud platform interlude, government edition

1,342 views

Published on

Recording: https://www.youtube.com/watch?v=Cj_EPfwzVYE

For an upcoming presentation to some government CIOs.

Published in: Technology
  • Be the first to comment

Day of the Donkey with cloud platform interlude, government edition

  1. 1. 11 The Coming Donkey Apocalypse Day of the Donkey Cloud, continuous delivery, and DevOps …government edition September, 2015 @cote Slides: http://cote.io/govtdonkey
  2. 2. 2 Conclusions  Organizations are craving faster, more agile IT that creates better product – Government is seeking to improve application quality & innovation speed, while escaping the quicksand of legacy IT commitments  Our would be hero: DevOps wins! Adoption is growing, going mainstream  But, we need to fix the meatware problems or it’ll be donkey carnage  Mainstream IT is failing – you can lead a donkey to water, but…  Helping the donkeys: 1. Cloud platforms lay the ground work for DevOps & CD speed 2. Management has a lot of homework – leading change, creating the game 3. Do portfolio management to work with legacy, make room for innovation
  3. 3. 3  @cote – Director, Technical Marketing at Pivotal for Pivotal Cloud Foundry  Former industry analyst at 451 Research and RedMonk  Corporate Strategy & M&A at Dell  Podcasts: cote.io/podcasts  FierceDevOps columnist  More: http://cote.io or cote@pivotal.io Hello!
  4. 4. 44 Fear of nerds
  5. 5. 55 “Silicon Valley is coming…. We are going to work hard to make our services as seamless and competitive as theirs.” -Jamie Dimon, CEO@JPMC, 2015 letter to shareholders
  6. 6. 6 Only 25% of respondents felt that their companies were innovating in agile ways. Source: Institute for the Future study, April 2015, n=3,600; “The Agile Advantage,” MeriTalk/Accenture, May 2015; Cutter Consortium, July 2015;. Organizations are held back by an IT agility gap What is your IT organization's role in business innovation? 87% of Feds say it takes too long to deploy new systems per requirements
  7. 7. 7 THE DEVOPS WILL SAVE US!
  8. 8. 88 “We estimate that, by 2018, 90 percent of I&O organizations attempting to use DevOps without specifically addressing their cultural foundations will fail.” - Ian Head, Gartner, April 2015 Source: “DevOps Will Evolve From a Niche to a Mainstream Strategy Employed by 25% of Global 2000 Organizations,” Gartner, March 2015.
  9. 9. 99 Saving the donkeys
  10. 10. 10 Know your equestrian metaphors Unicorns • Flys around in clouds doing magic • Streams things & doesn’t seem to need money • Gets most of the attention • Stuff of legend Sources: “Getting away from unicorn job descriptions”; “About Stranger”; out of stock t-shirt. See also, “Continuous Delivery Among the Donkeys,” Feb 2015. Donkey • Hard working beast of burden • Gets no respect • Has to do more with less • Most of us Horse, destrier class • Makes lots of money • Has (and needs) lots of resources • Ridden by kings - market makers
  11. 11. 11 Clipart from Gerd Altmann.
  12. 12. 12 Clipart from Gerd Altmann.
  13. 13. 13 Source: "Strategy, not Technology, Drives Digital Transformation," 2015 Digital Business Global Executive Study and Research Project, MIT Sloan Management Review & Deloitte University Press, July 2015. n=4,800,conducted in Fall of 2014. Government concerns from “The Agile Advantage,” MeriTalk/Accenture, May 2015 43% 33% 25% 25% 24% 22% 17% 16% 15% 10% 7% 3% 8% Too many competing priorities Lack of an overall strategy Security concerns Insufficient technical skills Lack of organizational agility Lack of management understanding Lack of entrepreneurial spirit, willingness to take risks Lack of collaborative, sharing culture No strong business case Lack of employee incentives None/no barriers exist Don’t know Other (please specify ) What barriers are impeding your organization from taking advantage of digital trends? (select up to three) Most problems are in the meatware Government concerns: • Security • Budget • Infrastructure complexity • Fear of change • Inflexible practices • Lack of collaboration
  14. 14. 1414© Copyright 2015 Pivotal. All rights reserved.Columbus Renaissance hotel, 3rd floor. See also Plumbing: Design and Installation.
  15. 15. 15 Bad meatware spoils IT Failure to change the operational model 31% Doing too little 19% Failure to change the funding model 13% Defending I&O and doing too much 11% Focusing on the wrong benefits 10% Using the wrong technologies 6% Nothing is wrong - It's great! 5% Something else 5% "What is going wrong with your private cloud?" Sources: “Problems Encountered by 95% of Private Clouds,” Gartner, Feb 2015. See also 451 commentary on cloud for net-new applications and survey data on cloud pain points.
  16. 16. 1616 Getting to DevOps
  17. 17. 17 Goals that lead to DevOps 1. Delivering software that runs on the Internet (mobile, web, etc.) 2. The pipeline is the factory, from concept, to code, to production 3. Faster turns, while maintaining quality, uptime, performance – Lean approach to entire process – Shorten time to customer value – Keep the site up, resilience vs. failure 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.
  18. 18. 18 The word defines itself… (1.) DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support. (2.) DevOps is also characterized by operations staff making use of many of the same techniques as developers for their systems work. Source: “What Is DevOps?,” The Agile Admin, Dec 2011.
  19. 19. 19 What developers do, simplified Requirements Design Code Build Verify Check-in Team Build Update Code Note: “Screwing around” not pictured ;)
  20. 20. 20 Developer flow, complexified “Coding” is a very small part
  21. 21. 21 DevOps == continuous delivery (More or less) Build Test/Verify Package repository Version Control Infrastructure Platform (IaaS, PaaS, VMs) Production Concerns (monitoring, scaling, etc.) Feedback Loop Specify Code Development CI/CD Ops
  22. 22. 2222 How’s it going?
  23. 23. 23 Things are improving, but we need accelerants DIY 36% CI Products 28% Other 8% None 28% What build automaton or CI/CD tools are you using? (451 Research study, 2014) Sources: 2014Q1 451 Research DevOps Study, n=201. In second study (n=300), 38% used “build and continuous integration tools”; "DZone's 2014 Guide to Continuous Delivery," n=500; The DZone Guide to Continuous Delivery, Vol. 2," Feb, 2015, n=900. 50% 18% 41% 8% Believe doing CD Doing textbook CD Use of CD is growing (DZone studies) 2015 2014
  24. 24. 24 It’s not much of an IT department, but I’m sorta attached to it…
  25. 25. 2525 Cheering up donkeys
  26. 26. 26 Simplifying “cloud native” Source: Casey West’s cloud native piece in O’Reilly Radar, August 2015. See also Wikibon’s recent report, "Technical Dive into Cloud Native Application Platforms," September, 2015.
  27. 27. 27 Cloud native can be reduced to three technology layers, plus “culture” Source: slides in this section based on “Patterns of Cloud Native Architecture,” Agile 2015. Cloud Native Platform 12 factor apps & Microservices Container Orchestration Infrastructure Automation Cloud Native Application Frameworks Cloud Native Runtime Platform Cloud Native Operations Cloud Native Empowered Culture
  28. 28. 28 The Cloud Native Platform, simplified Applications Runtimes Infrastructure Contract Contract Culture Key transformation effects: - Finishes “last mile” of continuous delivery - Addresses “day 2” problems – operations, upgrades, new releases, resilience. - “DevOps” teams are “top of stack” - “Platform operations” team maintain the lower levels and shared services - Government: reduce ATO from 9 months to days Source: ATO stat from GSA’s Diego Lapiduz at CF Summit 2015.
  29. 29. 29 Management creates the game  Leading change management  Setting, communicating, tracking goals  Dramatic organization change, gradually  E.g.: from autocrat to self- directed teams Sources: Leading the Transformation, 2015; “Management’s Job is orchestrating the ‘why,’” 2015; The Concise Executive Guide to Agile, 2010.
  30. 30. 30 Portfolio management balancing resources, creating time for innovation Source: “A Value Framework that Works for Transforming Your Application Portfolio,” June, 2015. Key transformation effects: - Reduce costs to run “legacy” systems - Free resources (time, money, attention) for “innovation” - Waste elimination: cloud platform automates infrastructure management & “paperwork”
  31. 31. 31 The emerging cloud native organization model Innovation: Plan, design, develop and test business capabilities as deployable artifactsProduction Apps: config, deployment, QA, monitoring, scaling App Platform: upgrade platform, capacity planning, service mgmt., scale platform Infra Platform: Rack and stack, networking, data storage, etc. ROLES Cross-Functional (Prod. Owner, Dev, QA) Application Operators Platform Operators Engineering (Storage, Security, Network, etc.) AREAS OF FOCUS Source: based on slide from Pivotal Cloud Foundry Solution team, discussions with GSA’s Diego Lapiduz.
  32. 32. 3232 Thanks! @cote | cote@pivotal.io “We are uncovering better ways of developing software by doing it and helping others do it.” - The Agile Manifesto, 2001 Slides: http://cote.io/govtdonkey
  33. 33. 33 Further reading Leading the Transformation (2015) Excellent overview of goals and management tactics for doing Agile and DevOps in larger organizations Migrating to Cloud- Native Application Architectures (2015) Motivations and methods for moving to microservices and cloud-native patterns. Free! Cloud Native Journey Series, by me - Overview: 3 types of journeys - Part 1: Greenfield Journey - Part 2: Legacy (coming soon) - Part 3: Transformation (coming soon)

×