This document discusses lessons learned about getting software to production. It introduces Mike, a student of deploying software easily, and covers configuration management, the roles of developers and operations staff, and why communication between the two is important. Typical project lifecycles are discussed along with common problems that arise when developers don't consider operational needs or when operations rejects changes too often. The document promotes establishing a simple, repeatable release process and provides reading recommendations on the topic.

1. Getting To Production
LESSONS LEARNED

2. Hi I am Mike!
• Worked in software for about 10 years
• Working for a news syndicate right now
• Student of Deploying Software the Easy Way
• Likes to work on things that do work for me.
• Mike.roth@mxrss.com

3. .

5. Terms
Configuration
Management
People
◦Developer
◦Operations

6. Configuration Management
Configuration management can be used to
maintain OS configuration files.[11] Example
systems include CFEngine, Bcfg2, Puppet,
and Chef. (cited from Wikipedia)
(http://en.wikipedia.org/wiki/Configuration
_management)

7. First the Developer
People who write code to solve problems, fix bugs
to solve problems, evolve process to solve
problems.
LOVES CHOAS
Usually Do not Understand the words Operational
consistency.
Problem in production, blames the environment.
Some will debug in Prod.

8. Now The Ops
May or May not write code, if they do they will use
high level scripting
Usually gets the call at 4am first.
Usually against change
Tries to keep the devs out of prod.
Favorite word is “NO” if you ask to send a build out
on a Friday at 5pm.

9. Typical Project Lifecycle
Idea
Specs
(Someti
mes)
Design
(Meetings
always
yay!)
CodingTesting
Release
Repeat!

10. Stop Me If You heard this one before…

14. Why This Topic?

17. Planning Always,
well sometimes,
never.

25. Flip The Switch

30. Who’s Fault?
It really doesn’t matter. The result is the same the
department has a sizeable failure and the company failed to
deliver to their customer.
Both need to be invested in each others success, both need
to have empathy for each others need.
Release needs to be a process that if it hurts do it more
often, not less.
A process so easy ANYONE CAN DO IT.

31. A Better Way

33. Communicate! Communica

40. Reading
Continuous Delivery – Jez
Humble
Move Build Script – My Blog
The Phoenix Project - Gene
Kim (Author), Kevin
Behr (Author), George
Spafford (Author)