When I joined Rally Software in 2006, the concept of agile software development was still relatively progressive, even though the Agile Manifesto had been published in 2001. Today, aside from debating the merits of one instantiation of agile practices over another, few would question the benefits or why most software-driven organizations are in some phase of implementation.
One of the key benefits of agile is bringing the right features to market faster. But accelerating time to market is only possible if you’re able to effectively deploy software to operations at the same pace that development is shipping code. In some high-performance organizations, teams deploy software multiple times per day – Amazon announced during a presentation at Velocity Conference 2011 that it releases to production every 11.6 seconds. It’s no surprise that DevOps practices are now firmly in the spotlight for SaaS vendors who count on uptime to generate revenue, and Enterprise IT operations teams that defend SLAs with the business.
Ultimately, it’s impossible to realize the benefits of agile development without effective DevOps practices. And the ROI of DevOps is more obvious and easily measured than agile, because it’s closer to the customer. No matter how much software gets built, if the customer can’t access it reliably, the business loses money – whether via revenue disruption or internal funding cuts. CA Technologies recently published a study that found “between 17% and 23% improvement in key business metrics such as revenue, time-to-market and new customer acquisition” for organizations that have adopted DevOps practices.
Agile and DevOps have followed similar evolutions by first addressing the necessary technical tools and practices before eventually looking to the human side of the problem. For DevOps teams, continuous integration, virtualization and automation have become table stakes, but effective DevOps collaboration tools remain elusive. We seem to expect on-call engineers to continue bearing the burden of operational fire drills, at all hours, without sufficient access to the information and team members they need to solve the problem.
This is why VictorOps was created: to help DevOps teams expedite time-to-resolution and improve their quality of life. Regardless of time of day or connected device, VictorOps provides:
As Forrester states in its September 2013 report The Seven Habits of Highly Effective DevOps, “one of the barriers to effective DevOps is past reliance on personal heroics, a cultural value that many organizations unwittingly reward and so cement in place behaviors that stand in the way of systematic improvement.”
For DevOps to achieve mainstream success the teams responsible for its implementation will need tools that bring balance and a sustainable pace to their work lives.