And before you close this label because you’re not working for the government, let me say that what you’ll deliver in this post will offer a good example of how large organizations could implement DevOps-organizations where some teams have to decide on things and documents have to be trailed before anyone can turn. That’s usually the case with many big enterprises. Bureaucracy and organization among teams are often what stop organizations from providing value at the particular right time.
But what does this completely have to do with DevOps and government? Well, DevOps is about if the value to someone that will advantage from the invention the organization is providing. It’s not just around helping organizations to rapidity up delivery and profit. Governments have a yearly reasonable, so profit might not be a big success in this case. Instead, they’re involved in a more social cause: educating human life. The software they produce could move someone’s life to the point of not receiving healthcare treatment. We’ll talk about that in a moment. The point is that we entirely depend on software now, so it’s not just a problem of profitability. It’s also a matter of providing life-enhancing value
Suggested read: DevOps key practices
Culture, Processes, and Architecture Are Too Rigid
Government agencies typically have serious silos. That’s because they frequently work with a waterfall model, and each stage represents a dissimilar group. And it’s not just that. They usually have to deal with a series of contractors, and all of them use a different tool to communicate. This particularly relates to, say, a ticket system to report errors. As Conway’s Law says, “Any organization that designs a system (defined approximately) will produce a project whose collecting is a duplicate of the organization’s communication arrangement.” Communication is precisely one of the things that DevOps tries to progress.
Resistance to Change until It’s urgently Needed
Usually, bureaucratic shops resist changing culturally. Most of the time it’s because, in government, several people have loads of years in a similar job. Some might be scared to lose those jobs, and others just don’t see the need for change. For them, the work force is measured, but at least growth is being made. But what about when there’s an outside pressure-a political one that you can’t regulator? You might recollect when the launch of the healthcare.gov stage failed. Everybody had somewhat to say about what went mistaken and how they should have done things inversely.
Working With Bureaucracy in Small Batches
So, you’re in an environment where all little thing needs six levels of agreement. Do you want to use Jenkins? Great! You just requirement 15 committees to approve it over two years, and you’re virtuous! So how do you work with this? Startups can simply take the DevOps method because there are not various people who have to approve. But in government or large enterprises, that’s not the situation. Some time ago, I had the wrong impression about my boss and his moods about introducing somewhat new. I thought he didn’t like it when I’d invent or try innovative things. In reality, he was afraid of the steadiness and quality of our product. But then he encouraged me in a different way.
Rome Wasn’t Built in a Day
It will take time for certain organizations to accept DevOps. And we all can absorb about other industries that have needed to do things inversely. What worked for some might not work for you and vice versa? Particularly in software development, there will continuously be tradeoffs. The common of the difficulties in such bureaucratic industries concerns culture and procedure. It’s not about individuals, per se, nor is it almost technology stack or tools. I’ve had problems with my friends when coordinating where to go to dinner.
Also read: DevOps model and practices
Imagine how complex it can be with the government, where there are so several people and features to take into attention. There will always be resistance to change. We humans don’t like it. Even in our personal lives, we try to avoid it. Alteration seldom comes until you need it or you’re required into it. So instead of trying to avoid it, let’s hold it. So yes, DevOps is possible in government agencies.
And if it’s probably in this area, probabilities are that it’s likely everywhere else. The secret is in the strategy we choose to introduce these types of changes into complex organizations.