DevOps 
DevOps: A Culture Transformation, 
More than Technology 
Andi Mann 
CA Technologies 
VP of Strategic Solutions, Office of the CTO 
DOT04S @andimann #CAWorld
Abstract 
DevOps is not a new technology or a product. 
It's an approach or culture of SW development 
that seeks stability and performance at the 
same time that it speeds software deliveries to 
the business. We will discuss this cultural shift 
where development teams have to accept the 
feedback of operations teams and the 
operations team should be ready to accept 
frequent updates to the SW that it's running. 
Andi 
Mann 
CA Technologies 
VP of Strategic 
Solutions, 
Office of the CTO 
2 © 2014 CA. ALL RIGHTS RESERVED.
Agenda 
DEVOPS CULTURAL CONCEPTS 
PEOPLE AND SKILLS 
ORGANIZATIONAL STRUCTURES 
PROCESS CHANGE 
FOSTERING COLLABORATION 
NEXT STEPS – WHERE TO START 
1 
2 
3 
4 
5 
6 
3 © 2014 CA. ALL RIGHTS RESERVED.
DevOps Cultural Concepts
Does Any of This Sound Familiar? 
Speed, Quality and Cost Problems Across Software Lifecycles 
DEVELOPERS 
I spend 70% of my time waiting 
INFRASTRUCTURE OWNERS 
I don’t have spare capacity 
5 © 2014 CA. ALL RIGHTS RESERVED. 
TESTERS 
Our test systems are not realistic 
LEVEL 1 OPS 
I don’t know who to escalate to 
APPS SUPPORT 
I’m constantly fighting fires 
LOB EXEC 
What is IT doing? 
I need new apps now!!
“DevOps isn’t something you can buy -- 
it’s something you have to do, and you 
have to do it yourself.” 
John Michelsen, CTO, CA Technologies 
DevOps 101: Why DevOps Matters to Large Enterprises, http://blogs.ca.com/2014/01/27/devops-101-why-devops-matters-to-large-enterprises/ 
6 © 2014 CA. ALL RIGHTS RESERVED.
cul·ture noun ˈkəl-chər 
2. 
A particular society that 
has its own beliefs, ways of 
life, art, etc. 
What is culture? 
CULTURE IS AN OUTPUT, NOT AN INPUT 
7 © 2014 CA. ALL RIGHTS RESERVED. 
3. 
A way of thinking, 
behaving, or working that 
exists in a place or 
organization (such as a 
business) 
1. 
The beliefs, customs, arts, 
etc., of a particular society, 
group, place or time 
Mirriam-Webster, http://www.merriam-webster.com/dictionary/culture
But what does DevOps actually mean? 
METHODS FOR IMPROVING 
COMMUNICATION INTEGRATION COLLABORATION 
BETWEEN DEV AND OPS 
8 © 2014 CA. ALL RIGHTS RESERVED.
Culture is not about building another silo. 
Dev DevOps Ops 
(… although a ‘DevOps team’ can work) 
9 © 2014 CA. ALL RIGHTS RESERVED.
Culture is not about a bounded ‘DevOps project’. 
No DevOps DevOps!! DevOps is Done! 
(… although a ‘DevOps Project’ can help) 
10 © 2014 CA. ALL RIGHTS RESERVED.
Culture is not about buying a new technology. 
(… although technology can play a part) 
11 © 2014 CA. ALL RIGHTS RESERVED.
DevOps Culture – Patterns and Anti-patterns 
“Design for 
Failure” 
“Agile for 
Infrastructure” 
12 © 2014 CA. ALL RIGHTS RESERVED. 
“Continuous 
Everything” 
“Agile, Lean, 
Scrum, Kanban, 
Extreme” 
“Wall of 
Confusion” 
“Willful 
Ignorance” 
“Tribal 
knowledge” 
“Two-Pizza 
teams” 
“Test-Driven 
Development 
“Empathy” 
“Systems 
Thinking” 
“Collaboration & 
Communication” 
“Technology 
“Roll forward” silos”
People and Skills
DevOps Starts With People 
BREAKING DOWN BARRIERS BETWEEN TEAMS – AND EMPIRES 
NEW ROLES, NEW TITLES, NEW (AND SHARED) RESPONSIBILITIES 
CAPTURING AND CONVERTING TRIBAL KNOWLEDGE 
ENSURING FOCUS ON BUSINESS SERVICE, NOT TECHNOLOGY 
BUILDING TRUST – IN EACH OTHER, IN TECHNOLOGY, IN PROCESS 
14 © 2014 CA. ALL RIGHTS RESERVED.
Which of the following is your organization likely to 
invest in over the next year as part of your 
implementation of DevOps? 
1% 
51% 
51% 
Hiring new resources with necessary skills 
Engaging a consulting firm with DevOps… 
Redesigning processes 
Training for development and… 
Changing organizational structure 
New tools 
Source: DevOps: The Worst-Kept Secret to Winning in the Application Economy, Vanson Bourne (commissioned by CA Technologies), 
http://rewrite.ca.com/us/articles/devops/research-report--devops-the-worst-kept-secret-to-winning-in-the-application-economy.aspx 
15 © 2014 CA. ALL RIGHTS RESERVED. 
30% 
40% 
46% 
63% 
None
What knowledge/skills do you need most to 
successfully implement a DevOps approach? 
Knowledge of business strategies 
Knowledge of business processes 
Inter-team communications 
Process re-engineering skills 
People skills/collaboration 
Project management skills 
Programming or scripting skills 
16 © 2014 CA. ALL RIGHTS RESERVED. 
19% 
24% 
33% 
30% 
30% 
36% 
42% 
47% 
Quality assurance and testing skills 
TechInsights Report: What Smart Businesses Know About DevOps, Vanson Bourne (commissioned by CA Technologies), 
https://www.ca.com/us/register/forms/collateral/techinsights-report-what-smart-businesses-know-about-devops.aspx
Seven Habits Of Highly Effective DevOps 
ESTABLISH TRUST AND TRANSPARENCY BETWEEN DEV. AND OPS. 
SEE EVERYTHING THROUGH THE EYES OF THE CUSTOMER. 
STREAMLINE YOUR APPLICATION DELIVERY PIPELINE. 
ADOPT A LOOSELY COUPLED SERVICE-ORIENTED ARCHITECTURE. 
REWARD SOLUTION SIMPLICITY AND RELIABILITY. 
1 
2 
3 
4 
5 
ADOPT AND 6 IMPROVE HOW YOU USE CUSTOMER EXPERIENCE DATA. 
7 DEV. AND OPS NEED TO WALK IN THE OTHER’S SHOES. 
Source: Forrester Research, Inc., ‘The Seven Habits Of Highly Effective DevOps’, October 2, 2014 
17 © 2014 CA. ALL RIGHTS RESERVED.
Organizational Structures
What is the most important component 
of a DevOps approach? 
4% 
32% 
IT automation 
Agile development 
Collaborative teaming 
Service virtualisation 
Continuous release cycles 
Accelerated app testing 
Aligned dev & ops processes 
TechInsights Report: What Smart Businesses Know About DevOps, Vanson Bourne (commissioned by CA Technologies), 
https://www.ca.com/us/register/forms/collateral/techinsights-report-what-smart-businesses-know-about-devops.aspx 
19 © 2014 CA. ALL RIGHTS RESERVED. 
25% 
32% 
45% 
42% 
47% 
52% 
Pre-prod performance testing
Web-scale Org – ‘Loosely-coupled’ Development Teams 
CA CA 
PO PO PO PO PO 
Chapter Chapter 
Squad 
Tribe 
PO PO PO 
SO SO 
SO SO 
SO 
Squad Squad Squad 
20 © 2014 CA. ALL RIGHTS RESERVED. 
Tribe 
Squad Squad Squad Squad 
Guild 
Guild 
Chapter 
Chapter 
SO 
SO SO 
Source: Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds, Henrik Kniberg & Anders Ivarsson, https://dl.dropbox.com/u/1018963/Articles/SpotifyScaling.pdf
Web-Scale Org – Ops as a Support Team for Dev 
PO 
SO 
DEV SQUAD 
PO 
SO 
DEV SQUAD 
PO 
SO 
OPS SQUAD 
Source: Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds, Henrik Kniberg & Anders Ivarsson, https://dl.dropbox.com/u/1018963/Articles/SpotifyScaling.pdf 
21 © 2014 CA. ALL RIGHTS RESERVED.
Gaming Company Organization(s) 
“Boss-free Since 1996” 
Source: Valve Handbook For New Employees, http://media.steampowered.com/apps/valve/Valve_Handbook_LowRes.pdf 
22 © 2014 CA. ALL RIGHTS RESERVED. 
Noob 
DEVELOPERS 
HEAD WRITER 
DEVELOPERS 
DEVELOPERS DEVELOPERS DEVELOPERS
Banking Org 
Independent Teams, Shared Tools & Processes 
IT OPERATIONS APPLICATION DEVELOPMENT 
APP PERFORMANCE & 
PROBLEM RESOLUTION 
23 © 2014 CA. ALL RIGHTS RESERVED. 
APPLICATION ROLLOUT 
& LIFECYCLE 
Service Delivery 
Infrastructure 
Network 
Change Management 
Other Teams… 
Development 
Testing 
Technical Service 
Management 
Solution Design 
Other Teams… 
Ops Functional Tools 
Shared Tools and Process 
Dev Functional Tools
COE Model - With Federated Members 
Core 
Community 
Communication 
Licenses 
Program 
Management 
24 © 2014 CA. ALL RIGHTS RESERVED. 
Internal training and 
competency building 
Delivery / 
staffing 
Best practices and 
knowledge base 
Asset creation and 
maintenance 
Framework 
Blueprints 
Sales 
(Engage and scope) 
Marketing 
(Awareness and brown 
bags) 
Value 
measurement 
Internal support 
Integrated 
project plans 
Cloud 
Project assistance 
Admin / IT 
Technical SMEs 
Change Agent 
Upgrades 
Human 
Factor 
Version control 
Federation
Process Change
DevOps Requires Fundamental Change To Process 
COLLABORATION BETWEEN DEVELOPMENT AND OPERATIONS 
IMPROVING AND AUTOMATING HANDOFFS BETWEEN SILOS 
REMOVING CONSTRAINTS AND OPENING UP BOTTLENECKS 
IMPROVING THE FLOW OF CODE FROM IDEATION TO DELIVERY 
CREATING FEEDBACK LOOPS AT EVERY STAGE 
26 © 2014 CA. ALL RIGHTS RESERVED.
What is the most important component 
of a DevOps approach? 
4% 
32% 
IT automation 
Agile development 
Collaborative teaming 
Service virtualisation 
Continuous release cycles 
Accelerated app testing 
Aligned dev & ops processes 
TechInsights Report: What Smart Businesses Know About DevOps, Vanson Bourne (commissioned by CA Technologies), 
https://www.ca.com/us/register/forms/collateral/techinsights-report-what-smart-businesses-know-about-devops.aspx 
27 © 2014 CA. ALL RIGHTS RESERVED. 
25% 
32% 
45% 
42% 
47% 
52% 
Pre-prod performance testing
Agile development – Deliver real requirements, faster. 
Backlog 
items 
28 © 2014 CA. ALL RIGHTS RESERVED. 
Potentially 
shippable product 
increment (MVP) 
Product backlog 
client prioritizes 
Sprint 
backlog 
1-4 weeks 
24 
hours
Bring ops (and others) into agile methodology. 
Backlog 
items 
29 © 2014 CA. ALL RIGHTS RESERVED. 
Potentially 
shippable product 
increment (MVP) 
Product backlog 
client prioritizes 
Sprint 
backlog 
1-4 weeks 
24 
hours
Stepping Stone to Agile - ‘Agile-fall’ 
30 © 2014 CA. ALL RIGHTS RESERVED.
Continuous Release Process – Release Automation 
Source Model 
Promote Deploy Target 
31 © 2014 CA. ALL RIGHTS RESERVED. 
Onto on-premises, 
hosted, or 
cloud infrastructure 
To a continuous delivery/release 
automation system 
From existing 
build/continuous 
integration
Accelerate Application Testing – From Serial Testing … 
Data Center 
Systems 
Middleware 
Services 
32 © 2014 CA. ALL RIGHTS RESERVED. 
Cloud 
Services 
Partner 
Services 
Your new app! 
Enterprise 
Storage 
Distributed 
Systems 
“I can’t test or QA anything until I have access to everything!”
Accelerate Application Testing – To Parallel Testing 
Data Center 
Systems 
Middleware 
Services 
33 © 2014 CA. ALL RIGHTS RESERVED. 
Cloud 
Services 
Partner 
Services 
Your new app! 
Enterprise 
Storage 
Distributed 
Systems 
Test and QA against virtual services – faster, better, safer
Fostering Collaboration
Some Ideas To Go On With ... 
FAMILIARIZATION 
Paintball, brownbags, LAN 
games… 
CO-LOCATION 
Face-to-face, real time, 
real people 
35 © 2014 CA. ALL RIGHTS RESERVED. 
GEO ALIGNMENT 
Local issues, smaller teams, 
business-focused 
SECONDMENT 
Walk a mile in another 
man’s moccasins 
EVENT HOSTING 
Share problems with peers 
and colleagues
Collaborative Teaming at Valve 
Source: Valve Handbook For New Employees, http://media.steampowered.com/apps/valve/Valve_Handbook_LowRes.pdf 
36 © 2014 CA. ALL RIGHTS RESERVED.
Collaborative Teaming At Citrix 
Source: South Florida Business Journal, A look inside Citrix's shared workspace offices – slideshow, http://www.bizjournals.com/southflorida/blog/2013/12/a-look-inside-citrix-shared-workspace. 
html?s=image_gallery 
37 © 2014 CA. ALL RIGHTS RESERVED.
Collaborative Teaming At Centurylink 
Team rooms, organized 
by function 
Desks suited to pairing Built-in collaboration spaces 
Spaces for “spikes” 
Meeting rooms of all shapes 
and sizes – few cubes 
Source: DevOps Gets Physical (Office Space), CenturyLink, http://www.centurylinkcloud.com/blog/full/devops-gets-physical-office-space 
38 © 2014 CA. ALL RIGHTS RESERVED. 
Large Projection Space 
Open lunch room (complete with catered lunches)
Next Steps – Where to Start
Where To Start Your DevOps Transformation? 
40 © 2014 CA. ALL RIGHTS RESERVED. 
Evaluate new tech 
to support DevOps 
Evaluate new 
processes to 
support DevOps 
Try it in a small part 
of the org, a new 
project, or 
skunkworks 
Improve education, 
communications, 
and cross-skilling 
Re-evaluate and 
rebuild your service 
delivery cycle
Start With The Goals In Mind 
Why Are You Implementing/Considering DevOps? 
16% 
Improve dev-ops collaboration 
Faster application delivery 
Cross-platform deployments 
Improve customer experience 
Mobile device support 
Cloud-based applications 
Increasingly complex hybrid IT 
41 © 2014 CA. ALL RIGHTS RESERVED. 
31% 
28% 
41% 
39% 
35% 
41% 
47% 
Cost reduction 
TechInsights Report: What Smart Businesses Know About DevOps, Vanson Bourne (commissioned by CA Technologies), https://www.ca.com/us/register/forms/collateral/techinsights-report-what- 
smart-businesses-know-about-devops.aspx
Andi Mann 
VP Strategic Solutions, Office of the CTO 
Andi.Mann@ca.com 
@AndiMann, @cainc 
slideshare.net/CAinc 
linkedin.com/in/AndiMann, linkedin.com/company/ca-technologies 
ca.com
For More Information 
Insert appropriate screenshot and text overlay 
from following “More Info Graphics” slide here; 
DevOps 
ensure it links to correct page 
To learn more about DevOps, please visit: 
http://bit.ly/1wbjjqX
For Informational Purposes Only 
Terms of this Presentation 
© 2014 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. 
This presentation provided at CA World 2014 is intended for information purposes only and does not form any type of warranty. 
Some of the specific slides with customer references relate to customer's specific use and experience of CA products and solutions so actual 
results may vary. 
44 © 2014 CA. ALL RIGHTS RESERVED.

DevOps: A Culture Transformation, More than Technology

  • 1.
    DevOps DevOps: ACulture Transformation, More than Technology Andi Mann CA Technologies VP of Strategic Solutions, Office of the CTO DOT04S @andimann #CAWorld
  • 2.
    Abstract DevOps isnot a new technology or a product. It's an approach or culture of SW development that seeks stability and performance at the same time that it speeds software deliveries to the business. We will discuss this cultural shift where development teams have to accept the feedback of operations teams and the operations team should be ready to accept frequent updates to the SW that it's running. Andi Mann CA Technologies VP of Strategic Solutions, Office of the CTO 2 © 2014 CA. ALL RIGHTS RESERVED.
  • 3.
    Agenda DEVOPS CULTURALCONCEPTS PEOPLE AND SKILLS ORGANIZATIONAL STRUCTURES PROCESS CHANGE FOSTERING COLLABORATION NEXT STEPS – WHERE TO START 1 2 3 4 5 6 3 © 2014 CA. ALL RIGHTS RESERVED.
  • 4.
  • 5.
    Does Any ofThis Sound Familiar? Speed, Quality and Cost Problems Across Software Lifecycles DEVELOPERS I spend 70% of my time waiting INFRASTRUCTURE OWNERS I don’t have spare capacity 5 © 2014 CA. ALL RIGHTS RESERVED. TESTERS Our test systems are not realistic LEVEL 1 OPS I don’t know who to escalate to APPS SUPPORT I’m constantly fighting fires LOB EXEC What is IT doing? I need new apps now!!
  • 6.
    “DevOps isn’t somethingyou can buy -- it’s something you have to do, and you have to do it yourself.” John Michelsen, CTO, CA Technologies DevOps 101: Why DevOps Matters to Large Enterprises, http://blogs.ca.com/2014/01/27/devops-101-why-devops-matters-to-large-enterprises/ 6 © 2014 CA. ALL RIGHTS RESERVED.
  • 7.
    cul·ture noun ˈkəl-chər 2. A particular society that has its own beliefs, ways of life, art, etc. What is culture? CULTURE IS AN OUTPUT, NOT AN INPUT 7 © 2014 CA. ALL RIGHTS RESERVED. 3. A way of thinking, behaving, or working that exists in a place or organization (such as a business) 1. The beliefs, customs, arts, etc., of a particular society, group, place or time Mirriam-Webster, http://www.merriam-webster.com/dictionary/culture
  • 8.
    But what doesDevOps actually mean? METHODS FOR IMPROVING COMMUNICATION INTEGRATION COLLABORATION BETWEEN DEV AND OPS 8 © 2014 CA. ALL RIGHTS RESERVED.
  • 9.
    Culture is notabout building another silo. Dev DevOps Ops (… although a ‘DevOps team’ can work) 9 © 2014 CA. ALL RIGHTS RESERVED.
  • 10.
    Culture is notabout a bounded ‘DevOps project’. No DevOps DevOps!! DevOps is Done! (… although a ‘DevOps Project’ can help) 10 © 2014 CA. ALL RIGHTS RESERVED.
  • 11.
    Culture is notabout buying a new technology. (… although technology can play a part) 11 © 2014 CA. ALL RIGHTS RESERVED.
  • 12.
    DevOps Culture –Patterns and Anti-patterns “Design for Failure” “Agile for Infrastructure” 12 © 2014 CA. ALL RIGHTS RESERVED. “Continuous Everything” “Agile, Lean, Scrum, Kanban, Extreme” “Wall of Confusion” “Willful Ignorance” “Tribal knowledge” “Two-Pizza teams” “Test-Driven Development “Empathy” “Systems Thinking” “Collaboration & Communication” “Technology “Roll forward” silos”
  • 13.
  • 14.
    DevOps Starts WithPeople BREAKING DOWN BARRIERS BETWEEN TEAMS – AND EMPIRES NEW ROLES, NEW TITLES, NEW (AND SHARED) RESPONSIBILITIES CAPTURING AND CONVERTING TRIBAL KNOWLEDGE ENSURING FOCUS ON BUSINESS SERVICE, NOT TECHNOLOGY BUILDING TRUST – IN EACH OTHER, IN TECHNOLOGY, IN PROCESS 14 © 2014 CA. ALL RIGHTS RESERVED.
  • 15.
    Which of thefollowing is your organization likely to invest in over the next year as part of your implementation of DevOps? 1% 51% 51% Hiring new resources with necessary skills Engaging a consulting firm with DevOps… Redesigning processes Training for development and… Changing organizational structure New tools Source: DevOps: The Worst-Kept Secret to Winning in the Application Economy, Vanson Bourne (commissioned by CA Technologies), http://rewrite.ca.com/us/articles/devops/research-report--devops-the-worst-kept-secret-to-winning-in-the-application-economy.aspx 15 © 2014 CA. ALL RIGHTS RESERVED. 30% 40% 46% 63% None
  • 16.
    What knowledge/skills doyou need most to successfully implement a DevOps approach? Knowledge of business strategies Knowledge of business processes Inter-team communications Process re-engineering skills People skills/collaboration Project management skills Programming or scripting skills 16 © 2014 CA. ALL RIGHTS RESERVED. 19% 24% 33% 30% 30% 36% 42% 47% Quality assurance and testing skills TechInsights Report: What Smart Businesses Know About DevOps, Vanson Bourne (commissioned by CA Technologies), https://www.ca.com/us/register/forms/collateral/techinsights-report-what-smart-businesses-know-about-devops.aspx
  • 17.
    Seven Habits OfHighly Effective DevOps ESTABLISH TRUST AND TRANSPARENCY BETWEEN DEV. AND OPS. SEE EVERYTHING THROUGH THE EYES OF THE CUSTOMER. STREAMLINE YOUR APPLICATION DELIVERY PIPELINE. ADOPT A LOOSELY COUPLED SERVICE-ORIENTED ARCHITECTURE. REWARD SOLUTION SIMPLICITY AND RELIABILITY. 1 2 3 4 5 ADOPT AND 6 IMPROVE HOW YOU USE CUSTOMER EXPERIENCE DATA. 7 DEV. AND OPS NEED TO WALK IN THE OTHER’S SHOES. Source: Forrester Research, Inc., ‘The Seven Habits Of Highly Effective DevOps’, October 2, 2014 17 © 2014 CA. ALL RIGHTS RESERVED.
  • 18.
  • 19.
    What is themost important component of a DevOps approach? 4% 32% IT automation Agile development Collaborative teaming Service virtualisation Continuous release cycles Accelerated app testing Aligned dev & ops processes TechInsights Report: What Smart Businesses Know About DevOps, Vanson Bourne (commissioned by CA Technologies), https://www.ca.com/us/register/forms/collateral/techinsights-report-what-smart-businesses-know-about-devops.aspx 19 © 2014 CA. ALL RIGHTS RESERVED. 25% 32% 45% 42% 47% 52% Pre-prod performance testing
  • 20.
    Web-scale Org –‘Loosely-coupled’ Development Teams CA CA PO PO PO PO PO Chapter Chapter Squad Tribe PO PO PO SO SO SO SO SO Squad Squad Squad 20 © 2014 CA. ALL RIGHTS RESERVED. Tribe Squad Squad Squad Squad Guild Guild Chapter Chapter SO SO SO Source: Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds, Henrik Kniberg & Anders Ivarsson, https://dl.dropbox.com/u/1018963/Articles/SpotifyScaling.pdf
  • 21.
    Web-Scale Org –Ops as a Support Team for Dev PO SO DEV SQUAD PO SO DEV SQUAD PO SO OPS SQUAD Source: Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds, Henrik Kniberg & Anders Ivarsson, https://dl.dropbox.com/u/1018963/Articles/SpotifyScaling.pdf 21 © 2014 CA. ALL RIGHTS RESERVED.
  • 22.
    Gaming Company Organization(s) “Boss-free Since 1996” Source: Valve Handbook For New Employees, http://media.steampowered.com/apps/valve/Valve_Handbook_LowRes.pdf 22 © 2014 CA. ALL RIGHTS RESERVED. Noob DEVELOPERS HEAD WRITER DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS
  • 23.
    Banking Org IndependentTeams, Shared Tools & Processes IT OPERATIONS APPLICATION DEVELOPMENT APP PERFORMANCE & PROBLEM RESOLUTION 23 © 2014 CA. ALL RIGHTS RESERVED. APPLICATION ROLLOUT & LIFECYCLE Service Delivery Infrastructure Network Change Management Other Teams… Development Testing Technical Service Management Solution Design Other Teams… Ops Functional Tools Shared Tools and Process Dev Functional Tools
  • 24.
    COE Model -With Federated Members Core Community Communication Licenses Program Management 24 © 2014 CA. ALL RIGHTS RESERVED. Internal training and competency building Delivery / staffing Best practices and knowledge base Asset creation and maintenance Framework Blueprints Sales (Engage and scope) Marketing (Awareness and brown bags) Value measurement Internal support Integrated project plans Cloud Project assistance Admin / IT Technical SMEs Change Agent Upgrades Human Factor Version control Federation
  • 25.
  • 26.
    DevOps Requires FundamentalChange To Process COLLABORATION BETWEEN DEVELOPMENT AND OPERATIONS IMPROVING AND AUTOMATING HANDOFFS BETWEEN SILOS REMOVING CONSTRAINTS AND OPENING UP BOTTLENECKS IMPROVING THE FLOW OF CODE FROM IDEATION TO DELIVERY CREATING FEEDBACK LOOPS AT EVERY STAGE 26 © 2014 CA. ALL RIGHTS RESERVED.
  • 27.
    What is themost important component of a DevOps approach? 4% 32% IT automation Agile development Collaborative teaming Service virtualisation Continuous release cycles Accelerated app testing Aligned dev & ops processes TechInsights Report: What Smart Businesses Know About DevOps, Vanson Bourne (commissioned by CA Technologies), https://www.ca.com/us/register/forms/collateral/techinsights-report-what-smart-businesses-know-about-devops.aspx 27 © 2014 CA. ALL RIGHTS RESERVED. 25% 32% 45% 42% 47% 52% Pre-prod performance testing
  • 28.
    Agile development –Deliver real requirements, faster. Backlog items 28 © 2014 CA. ALL RIGHTS RESERVED. Potentially shippable product increment (MVP) Product backlog client prioritizes Sprint backlog 1-4 weeks 24 hours
  • 29.
    Bring ops (andothers) into agile methodology. Backlog items 29 © 2014 CA. ALL RIGHTS RESERVED. Potentially shippable product increment (MVP) Product backlog client prioritizes Sprint backlog 1-4 weeks 24 hours
  • 30.
    Stepping Stone toAgile - ‘Agile-fall’ 30 © 2014 CA. ALL RIGHTS RESERVED.
  • 31.
    Continuous Release Process– Release Automation Source Model Promote Deploy Target 31 © 2014 CA. ALL RIGHTS RESERVED. Onto on-premises, hosted, or cloud infrastructure To a continuous delivery/release automation system From existing build/continuous integration
  • 32.
    Accelerate Application Testing– From Serial Testing … Data Center Systems Middleware Services 32 © 2014 CA. ALL RIGHTS RESERVED. Cloud Services Partner Services Your new app! Enterprise Storage Distributed Systems “I can’t test or QA anything until I have access to everything!”
  • 33.
    Accelerate Application Testing– To Parallel Testing Data Center Systems Middleware Services 33 © 2014 CA. ALL RIGHTS RESERVED. Cloud Services Partner Services Your new app! Enterprise Storage Distributed Systems Test and QA against virtual services – faster, better, safer
  • 34.
  • 35.
    Some Ideas ToGo On With ... FAMILIARIZATION Paintball, brownbags, LAN games… CO-LOCATION Face-to-face, real time, real people 35 © 2014 CA. ALL RIGHTS RESERVED. GEO ALIGNMENT Local issues, smaller teams, business-focused SECONDMENT Walk a mile in another man’s moccasins EVENT HOSTING Share problems with peers and colleagues
  • 36.
    Collaborative Teaming atValve Source: Valve Handbook For New Employees, http://media.steampowered.com/apps/valve/Valve_Handbook_LowRes.pdf 36 © 2014 CA. ALL RIGHTS RESERVED.
  • 37.
    Collaborative Teaming AtCitrix Source: South Florida Business Journal, A look inside Citrix's shared workspace offices – slideshow, http://www.bizjournals.com/southflorida/blog/2013/12/a-look-inside-citrix-shared-workspace. html?s=image_gallery 37 © 2014 CA. ALL RIGHTS RESERVED.
  • 38.
    Collaborative Teaming AtCenturylink Team rooms, organized by function Desks suited to pairing Built-in collaboration spaces Spaces for “spikes” Meeting rooms of all shapes and sizes – few cubes Source: DevOps Gets Physical (Office Space), CenturyLink, http://www.centurylinkcloud.com/blog/full/devops-gets-physical-office-space 38 © 2014 CA. ALL RIGHTS RESERVED. Large Projection Space Open lunch room (complete with catered lunches)
  • 39.
    Next Steps –Where to Start
  • 40.
    Where To StartYour DevOps Transformation? 40 © 2014 CA. ALL RIGHTS RESERVED. Evaluate new tech to support DevOps Evaluate new processes to support DevOps Try it in a small part of the org, a new project, or skunkworks Improve education, communications, and cross-skilling Re-evaluate and rebuild your service delivery cycle
  • 41.
    Start With TheGoals In Mind Why Are You Implementing/Considering DevOps? 16% Improve dev-ops collaboration Faster application delivery Cross-platform deployments Improve customer experience Mobile device support Cloud-based applications Increasingly complex hybrid IT 41 © 2014 CA. ALL RIGHTS RESERVED. 31% 28% 41% 39% 35% 41% 47% Cost reduction TechInsights Report: What Smart Businesses Know About DevOps, Vanson Bourne (commissioned by CA Technologies), https://www.ca.com/us/register/forms/collateral/techinsights-report-what- smart-businesses-know-about-devops.aspx
  • 42.
    Andi Mann VPStrategic Solutions, Office of the CTO Andi.Mann@ca.com @AndiMann, @cainc slideshare.net/CAinc linkedin.com/in/AndiMann, linkedin.com/company/ca-technologies ca.com
  • 43.
    For More Information Insert appropriate screenshot and text overlay from following “More Info Graphics” slide here; DevOps ensure it links to correct page To learn more about DevOps, please visit: http://bit.ly/1wbjjqX
  • 44.
    For Informational PurposesOnly Terms of this Presentation © 2014 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. This presentation provided at CA World 2014 is intended for information purposes only and does not form any type of warranty. Some of the specific slides with customer references relate to customer's specific use and experience of CA products and solutions so actual results may vary. 44 © 2014 CA. ALL RIGHTS RESERVED.