implementing devops and making it stick
DESCRIPTION
If you’ve ever been involved in promoting cultural change within an organization, you may have experienced something even more disheartening than flat-out rejection—a full rollback of hard-won cultural change followed by a decade-long resentment of anyone remotely associated with the implementation. This has happened at countless organizations with agile, with SOA, with virtualization—and it’s starting to happen with DevOps. How can such a simple idea that’s been so successful at so many organizations become such a resounding failure at others? It’s not the organization, and it’s certainly not DevOps. The problem lies in the implementation, and ultimately, with its promoters and champions. Alex Papadimoulis discusses what this "DevOps thing" is all about, goes over the technical and organizational strategies for a successful long-term DevOps implementation, shares a few big failures at big companies, and covers the common and not-so-common pitfalls when promoting this type of cultural change.TRANSCRIPT
�
AT2 Concurrent�Session�11/14/2013�10:15�AM�
�����
"Implementing DevOps and Making It Stick"
���
Presented by:
Alex Papadimoulis Inedo
��������
Brought�to�you�by:��
��
340�Corporate�Way,�Suite�300,�Orange�Park,�FL�32073�888Ͳ268Ͳ8770�ͼ�904Ͳ278Ͳ0524�ͼ�[email protected]�ͼ�www.sqe.com
Alex Papadimoulis Inedo
Alex Papadimoulis is a speaker and writer who's passionate about looking beyond the code to build great software. Through the years, he’s served in many different roles (from developer to executive), in different industries (from healthcare to manufacturing), at a variety of companies (from a one-man shop to a megabank). He’s seen his share of successful projects and failures—undoubtedly contributing to some. Alex believes failure is a powerful lesson and founded The Daily WTF, a site which chronicles bad code and other failures in IT. Alex recently founded Inedo, a company that builds software tools to help organizations effectively and responsibly implement agile software delivery and DevOps methodologies.
Implementing DevOps… and Actually Making it Stick!
ADC East 2013 Alex Papadimoulis
@apapadimoulis
10 PRINT "ALEX IS COOL"
20 GOTO 10
_________ _...._ .| \ |.' '-. __ .' |_ \ .'```'. '. .:--.'. .' \ | \ \ / | \ |'--. .-| | | | | `" __ | | | | ' | \ / . .'.''| | | | | |\`'-.-' .' / / | |_ | '. | | '-....-'` \ \._,\ '/ | /' .' '. `--' `" `'-' '-----------' ____ ____ ____ ___ _ _ _ ____ ____ ____ [__ | | |___ | | | | |__| |__/ |___ ___] |__| | | |_|_| | | | \ |___
• Approval Flag of "DUP"
• Attach "DUPVFY" instead of “DUPCHK"
function flagForApproval(code) { if (code == "DUP") { attachSupplemental("DUPCHK"); } }
function flagForApproval(code) { if (code == "DUP") { attachSupplemental("DUPCHKVFY"); } }
You did what!?
• Estimation • Internal Prioritization • Prioritization Review • Approach Write-up • Approach Review & Approval • Implementation Write-up • Implementation Review & Approval • Prioritization Evaluation • Code Assignment
53 More Steps!
There has to be a better way.
Extreme!!~!1!
“Agile”
Agile Principles
1. Smaller Changes
2. Sooner
Sooner
There has to be a better way.
Dev Ops
SCM Integration Testing QA Production
DevOps
1. Increased Collaboration
2. Automation
SCM Integration Testing QA Production Dev Ops QA
Mgmt
QA
Dev
Ops
Mgmt
Identify
Step 1
Policies
People
People
Assess
Step 2
Champions
Anti-Champions
Adversaries
Opponent
Skeptic
Expert
Frantic
Tinkerer
Hoarder
Align
Step 3
Aha!
Enable
Politics
Execute
Step 4
Prioritize I. Development Structure
II. Build Automation
III. Deployment Automation
IV. Process Automation
V. Infrastructure Automation
Incremental Change
Group by Group
Failure Happens
Summary
1. Identify
2. Assess
3. Align
4. Execute
Focus on Business Value
Alex Papadimoulis