This vendor-written piece has been edited by Executive Networks Media to eliminate product promotion, but readers should note it will likely favour the submitter's approach.
In my last article, I provided a broad overview of DevOps of potential pitfalls and investment areas. In this second instalment, I share four practical business handles to help guide businesses in developing an effective DevOps strategy.
In August last year, Ryan Grepper set a new Kickstarter record for the most-funded campaign ever raising over US$10.3 million dollars. His project, The Coolest, is a tricked-out cooler with a built-in blender, speakers, and USB chargers.
In a recent interview, Grepper said that The Coolest wasn't an overnight success. Instead, his first round of funding on Kickstarter failed to raise his target of US$125,000. When asked what he did differently the second time round, he admitted that unlike his first launch, he simply took the time to plan when to launch the project. The old adage, "Fail to plan, plan to fail" comes to mind when hearing this story and still holds true today in the world of application creation and development where businesses are under pressure to deliver more frequently and faster than ever before. This is where planning for DevOps comes into play.
Planning for DevOps success
There's a lot of hype building around DevOps right now with industry pundits touting it as the "next great IT movement." Signs are pointing towards increasingly more businesses on the road to DevOps to streamline the development process by combining multiple steps into single, automated process. Our recent survey by analyst firm, Vanson Bourne, revealed that 81% of businesses in Asia Pacific and Japan already have or are planning to have a DevOps strategy.
However, DevOps is not an easy strategy to adopt to transform a business into an agile and nimble machine. In my experience as an application delivery consultant, I've worked with several businesses in their DevOps implementation through advising them on various best practices. Here are the four common areas that businesses can plan for on the road to DevOps to find fewer problems and more answers.
Sharing a common objective
In today's Application Economy, businesses are under increasing pressure to be agile and nimble to stay ahead. Traditionally, development teams and IT operations have worked in separate departments, striving to achieve different results while DevOps demands that all teams understand the shared, common goal.
However, a DevOps strategy in itself cannot be seen in isolation as a solution that would be the secret ingredient in changing businesses overnight. Instead, DevOps requires a far broader and impactful organisational change — one that is shared by a common goal and desired outcome. Sharing a common understanding of why the company is moving towards greater collaboration and the need for increased agility via DevOps will be key to an effective implementation.
Sign up for CIO Asia eNewsletters.