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.

1. 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 sqeinfo@sqe.com www.sqe.com

2. 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 oneman 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.

3. Implementing DevOps…
and Actually Making it Stick!
ADC East 2013
Alex Papadimoulis
@apapadimoulis

5. 10 PRINT "ALEX IS COOL"
20 GOTO 10

6. _________
_...._
.|
|.'
'-.
__
.' |_
.'```'.
'.
.:--.'. .'
|
/ |
|'--. .-| |
|
|
|
`" __ | |
| | ' |
/
.
.'.''| |
| |
|
|`'-.-'
.'
/ /
| |_ | '.
|
| '-....-'`
._, '/ |
/' .'
'.
`--' `"
`'-' '-----------'
____ ____ ____ ___ _ _ _ ____ ____ ____
[__ | | |___ | | | | |__| |__/ |___
___] |__| |
| |_|_| | | | |___

10. • Approval Flag of "DUP"
• Attach "DUPVFY" instead of “DUPCHK"

11. function flagForApproval(code) {
if (code == "DUP") {
attachSupplemental("DUPCHK");
}
}

12. function flagForApproval(code) {
if (code == "DUP") {
attachSupplemental("DUPCHKVFY");
}
}

13. You did what!?

15. •
•
•
•
•
•
•
•
•
Estimation
Internal Prioritization
Prioritization Review
Approach Write-up
Approach Review & Approval
Implementation Write-up
Implementation Review & Approval
Prioritization Evaluation
Code Assignment

17. 53 More Steps!

18. There has to be a better way.

20. Extreme!!~!1!

27. “Agile”

28. Agile Principles
1. Smaller Changes
2. Sooner

30. Sooner

36. There has to be a better way.

37. Dev
Ops

38. SCM
Integration
Testing
QA
Production

39. DevOps
1. Increased Collaboration
2. Automation

40. QA
Dev Ops
Mgmt
SCM
Integration
Testing
QA
Production

41. QA
Mgmt
Dev
Ops

56. Identify
Step 1

57. Policies

58. People

59. People

60. Assess
Step 2

61. Champions

62. Anti-Champions

63. Adversaries

64. Opponent

65. Skeptic

66. Expert

67. Frantic

68. Tinkerer

69. Hoarder

70. Align
Step 3

71. Aha!

72. Enable

73. Politics

74. Execute
Step 4

75. Prioritize
I. Development Structure
II. Build Automation
III. Deployment Automation
IV. Process Automation
V. Infrastructure Automation

76. Incremental Change

77. Group by Group

78. Failure Happens

79. Summary
1. Identify
2. Assess
3. Align
4. Execute

81. Focus on Business Value
Alex Papadimoulis