Presentado por Nic Cheneweth en SGCE 2015

1. PRAGMATIC
DEVOPS
the what, why, and how
1

2. 2
http://bit.ly/gsmamobileeconomy
Within 5 years, mobile infrastructure and technology will be 5% of GDP.
Large majorities of consumers in the 13-country sample would
forgo most offline media before losing their mobile Internet
access. Two-thirds or more would give up chocolate and alcohol.
More than half are willing to forgo coffee and movies.
http://on.bcg.com/1MVG4VD
The Boston Consulting Group, Feb 2015

3. 3
http://bit.ly/1H5RO9F
“In Mexico, 40% of individuals 18-34 will used advanced mobile device this year”
“Latin America is the fastest growing smart phone market”
http://cnb.cx/1LaBdSb
This smartphone market is booming (Hint: Not China)
Feb 2015 • Arjun Kharpal

4. 4
http://on.wsj.com/1IVOUSs
“software is eating the world”
MARC ANDREESSEN
“Regardless of industry your company is now a software company, and
pretending that it’s not spells serious peril…That leads to an increasingly urgent
and overarching mandate: Your company must, using software and technology,
become as responsive and agile as your customers.”
David Kirkpatrick
Now Every Company Is A Software Company
http://onforb.es/1Lsks63

5. 5
“The average lifespan of a company listed in the S&P 500 index of
leading US companies has decreased by more than 50 years in the
last century, from 67 years in the 1920s to just 15 years today,
according to Professor Richard Foster from Yale University.”
http://bbc.in/1BKMlTP

6. 6
“Please select the statement that most closely aligns with
how your company decides which products are built.”
Source: A commissioned study conducted by Forrester Consulting
on behalf of ThoughtWorks, September 2012
Committee decides from potential options
Financial Modeling
Opinion of person with highest salary
Product portfolio approach
No systematic approach

7. 7
How effective are we at deciding?
Kohavi “online experimentation at Microsoft”
http://bit.ly/OnlineExperimentation
2/3 of all the ideas to improve expand software have either no effect or a negative effect
80% of the time we are wrong about what the customer wants.
Web Analytics:Experimentation and Testing primer, Kaushik

8. 8
need for agility

9. 9
Common Process

10. 10
Common Process

11. 11
Resilience,
security,
scalability,
deployability,
testability are
architectural
concerns

12. 12
Definition of Devops
What we really need to do is be able to build, and operate
systems that are resilient, secure, and capable of rapid
change at scale. Hence
a cross-functional community of practice dedicated to the study of building, evolving
and repidly changaeing secure, resilient systems at scale - Jez
movement, focused on how we build and operate high velocity organizations, born from the experi

13. 13
Turns out this is hard
Over in Dev - describe
while in Ops - describe
If herein lies the potential for IT alignment trap

14. IT Spending
Less Effective Highly Effective
Less
Aligned
Alignment
Highly
Aligned
Efficacy
+13
-14
“Alignment Trap”
+0
-2
“Maintenance Zone”
-6
+35
“IT Enabled Growth”
-15
+11
“Well-Oiled IT”
3-Year Sales Compound
Annual Growth Rate
“Avoiding the Alignment Trap in IT,” David Shpilberg, MIT Sloan Management Review Magazine, Fall 2007.

15. 15
Key IT Performance Indicators
Lead time for changes
Release Frequency
Time to restore service
Change fail rate
http://bit.ly/2014-devops-report

16. 16
image mgmt [packer, docker]
configuration mgmt [chef, puppet, ansible]
deployment automation [Go, Jenkins]
across LB, DNS, Security, Monitoring

17. 17
“Cease dependence on mass
inspection to achieve quality.
Improve the process and
build quality into the product
in the first place”
W. Edward Deming

18. 18
Top predictors of IT Performance
peer-reviewed change approval process
version control everything
proactive monitoring
high trust organizational culture
win-win relationship between dev and ops
http://bit.ly/2014-devops-report

19. 19
Sometimes you need a blank template.

20. 20
so in summary
• every company is a software company
• it is difficult to predicte the impact of features and changes
• so we need the ability to rapidly test and alter course based on feedback
• which requires software defined infrastructure
• close partnership between development and operations

21. 21
leave you with this

22. 22
As leaders
• cross-functional teams, spirit cooperation
• share risk
• experiement in novel ways to find solutions
• Use failures as an opportunity to learn not place blame

23. For questions or suggestions:For questions or suggestions:
GRACIAS