In the last post I talked about a DevOps maturity model – a simplified set of milestones you could strive for to make your organization more efficient and agile.
The question “what will DevOps do for me?” still remains.
For Industry influencers DevOps is the harbinger of the new Industrial Revolution, something that will fundamentally change how we think about IT and various roles within IT.
For practitioners, still struggling to take that first step, the big vision is enticing but it is the smaller, more tactical goal that needs to be accomplished first to showcase the viability of DevOps.
Pragmatic thinking demands we help isolate one, may be two issues that these organizations can achieve in few months to an year’s time. Here is what I have noticed working for most Enterprise IT organizations
First – automate deployments. An average developer may spend up to 200 hours trying to set up the environment and deploy her application while still developing the code. Most end up writing there own scripts to make the job easier and repeatable. If however, they have a tool, blessed and available from IT, it would help them focus on code rather than how to deploy and test it.
Second – improve communication between your dev and ops teams. While “communication” can mean many things, I specifically mean “handoffs” from dev to ops. Instead of just handing over the code, the dev will now provide instructions, steps, deployment scripts, testing scripts and even known issues and defects to ops. This makes the job of ops much easier. If there’s a problem, then instead of just logging a defect, ops will now provide environment definition, data and even the state of environment before and after the defect occurred. This simplifies dev’s job of debugging the problem and finding the root cause helping them fix it faster and permanently.
So if you are looking for quick wins – start with deployment automation and look to improve communication, specifically handoffs, between dev and ops teams.