Organisations are realising that the rise of the DevOps philosophy may be the best way to address numerous competitive challenges that businesses face.
DevOps doesn’t just apply to start-ups and web operations. You can create a DevOps atmosphere in any organisation.
IT is changing
Organisations are realising that the rise of the DevOps philosophy may be the best way to address the competitive challenges that businesses face. It brings many benefits including the removal of silos to encourage collaborative working, continuous delivery, continuous feedback with process improvements in non-development environments, underpinning the infrastructure through the development lifecycle, automation, and improving quality and speed-to-market without jeopardising reliability, security or stability.
However, DevOps is not always easy for businesses to understand and implement. It may require a considerable change of culture, organisation style and roles, technology, processes and tools, making it challenging for some businesses to embrace. This is especially the case if your organisation has long relied upon rigid structures, processes and technical practices. DevOps, by contrast, is about adopting a mind-set.
Where do you begin?
As most businesses these days run on ITIL processes, this is a pretty good place to start. Despite the rumours, DevOps doesn’t mean the end of ITIL. DevOps should be seen as more of an evolution, a means of ITIL process improvement. By using ITIL processes as a basis for a DevOps initiative you can greatly simplify and focus your efforts. By using your ITIL processes as starting points for an analysis of potential benefits, a DevOps implementation is given greater focus. Identify pain points that could benefit from greater collaboration and automation. Prioritise them based on potential benefit and estimated effort.
Look at bringing in a trusted partner whose knowledge, experience and best practice approach will help you to exploit opportunities, avert threats and, together, enable you to plot your DevOps journey. You will benefit from assessing where you are today and where you want to go:
1) Current state analysis: develop a clear understanding of your business drivers, challenges, capabilities and ongoing initiatives related to DevOps. Build the business case. It will help you gain support of DevOps and alleviate any fear with this kind of change.
2) Future state vision: create a vision of DevOps maturity for your organisation through the lens of a SWOT analysis, whilst thinking about the business goals you want DevOps to help you achieve.
3) Transformation: develop an adoption roadmap and identify the short-term, mid-term, and long-term targets that will deliver quantifiable benefits to your organisation across teams, programs, applications and system portfolios. Start small with a specific workload and then widen out to bigger projects, demonstrating your successes along the way. You will also benefit from aligning your teams around the same goals and incentives.