DevOps in government – real deal or house of cards?
For budget-strapped agencies, Lean is the best way to start a successful DevOps journey.
It’s good to hear that the DevOps movement is gaining momentum within the public-sector. While it’s not exactly new, a few agencies have adopted the principles or dipped their toes in the water.
The adoption challenge, as is usually the case for government departments, can’t easily be associated with a single word – be that culture, technology or process – it’s often a combination of many things, including perhaps the toughest nut to crack – budget.
Busting budgets and failing fast
Like it or not, government agencies have to deal with shrinking IT budgets; it’s the one constant and agencies are under increased scrutiny to ensure money is spent wisely. Unlike private sector companies who can justify mega IT spending as the means to increase market share or make more profit, government agencies can only think in terms citizen-centric service improvement, which given the overarching political context might not be a top priority.
Even when budget is available, the track record in IT delivery hasn’t been great. For example, if we believe numbers from the Standish Group, just over 94 percent of all large government IT projects (2003-2012) have been over budget, behind schedule, fallen short of user expectations, or had to be abandoned completely.
So with a 6 percent chance of success, it’s perhaps not surprising that the DevOps-style mantra of “failing fast” hasn’t taken full hold in government. After all, who wants to be in front of a Congressional committee when software services go really wrong? That’s never going to be fun and it certainly won’t be “blameless”.
Upside too great to ignore
But the potential for DevOps, with its focus on collaboration to continuously deliver enhanced software services, is huge. Especially when we consider that approximately $90 billion is spent on government IT in the U.S., yet according to a Meritalk survey only 13% of IT managers claimed they could develop and deploy new applications as fast as their agency mission requires.
So for government agencies focused on budget, probably the best place to start DevOps is to focus on the Lean elements that underpin much of the thinking.
This involves agencies identifying all elements of “waste” that incur greater cost and negatively impact delivery. To this end, and before any investment is made in tools, highly mature government agencies will carefully examine the entire end-to-end software delivery cycle and remove any cultural, process or technology-related elements that add no value.
The intention of course is to increase speed and quality, but a very important “byproduct” for the budget-constrained agency is cost reduction.
Lean: it’s not just for manufacturing anymore
Traditionally associated with manufacturing, many wasteful practices outlined in Lean thinking are applicable to government IT. These may include:
More and more organizations and government agencies are realizing the benefits of adopting DevOps. For the private sector this nets out to increased profit, but in the public sector it’s far more profound.
High performance government IT enabled with DevOps means delivering software that helps the sick, supports the vulnerable and educates our children.
As government agencies begin a process of determining what wasteful practices impede these goals, they’ll not only drive cost efficiencies, but also start delivering more high-quality digital services needed to improve our society.