5 Tips For Government IT Modernization - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Government // Enterprise Architecture
09:06 AM
Chris Steel
Chris Steel
Connect Directly

5 Tips For Government IT Modernization

Make sure you have a solid strategy to come in under budget and at scale.

Most Wasteful Government Tech Projects Of 2014
Most Wasteful Government Tech Projects Of 2014
(Click image for larger view and slideshow.)

Over the decades, agencies' application environments have evolved into daunting sets of complex and often interrelated combinations of commercial-off-the-shelf software and homegrown applications, along with terabytes of data. While these complex, siloed environments may initially inspire a "rip-and-replace" mentality, below are five simple tips that can guide government IT leaders on a path to cost-efficient and incremental IT modernization wins.

1. Know what you have in place by establishing an IT and enterprise architecture (EA) governance model.
Modernization considerations should begin with an understanding of what's currently in place within your IT environment. As agencies continue to consolidate, document, and clean up their data centers, proper governance can ensure that IT continues to meet the needs of stakeholders well into the future. Establishing a governance framework can ensure all IT changes are coordinated and communicated, requests for duplicate services are eliminated, licensing requirements are met, and solid architecture principles are followed. It is important to evolve enterprise architecture guidelines with change in mind. Proper EA tools will help with further auditability and historical record-keeping to understand who changed what, when, and why.

2. Prove technology fast and efficiently.
Proving out a new technology that the agency is considering should not take long. A vendor that suggests more than six weeks for its technology to demonstrate value within the agency's environment should raise a red flag and questions. A prove-out period should to be as efficient as possible, so planning ahead is a must, as well as ensuring that you know what metrics the "prove-out" will be tracked against. As an organization gains experience in the process of managing vendor proving phases, taking on bigger projects becomes easier.

(Source: PublicDomainPictures/Pixabay)
(Source: PublicDomainPictures/Pixabay)

[Be prepared: 7 Important Tech Regulatory Issues In 2015.]

3. Start small.
A greater number of government executives have grown weary of making significant IT investments before the target solution is proven out in their own environment with their own data. Agencies should not need to spend millions of dollars to get started. Most new technologies are great at scaling, so starting small makes more sense, not only to make sure things work in the agency's environment, but to set a strong foundation to scale up from there. By starting with one small project, organizations can tackle larger and more projects as lessons are learned.

4. Leverage subject-matter expertise from vendors.
There are many great integrators and resellers in the community, and they have important roles in the ecosystem. But vendors can also bring subject-matter experts who have been on the front lines of implementations that have and haven't been successful. These lessons learned are valuable intelligence that can help your agency adopt best practices. The key is to build a good level of trust with your vendor partners and demand integrity. Let it be known that everyone must stay committed to the success they agreed to at the start of any project.

5. Remember security.
Understanding the security requirements for every component in the agency's infrastructure is no longer just wishful thinking -- it's critical. Components with high security requirements should not be combined with low-security components. Ideally, agencies shouldn't stop at tracking network requirements; they should include storage encryption requirements, facility-location and ITAR considerations, and auditability. Utilizing solid EA tools to plan the lifecycle of components, ensuring all elements are within current support from OEMs, will ensure a safe foundation for modernization initiatives. Weak links within an environment can have a ripple effect on cyber security.

With budget constraints and continuous change being the new norm for government IT leaders, many are taking action by embracing new and more productive ways of helping their agencies achieve their respective missions. By following these five steps, government organizations are sure to be on the path to fostering long-term value and growth.

To meet obligations -- and avoid accusations of cover-up and incompetence -- federal agencies must get serious about digitizing records. Get the No Excuse For Missing Documents Tech Digest from InformationWeek Government today. (Free registration required.)

Chris Steel is Chief Solutions Architect for Software AG Government Solutions, a leading software provider for the US federal government, helping it integrate and dramatically enhance the speed and scalability of its IT systems. Steel has more than 20 years of experience in ... View Full Bio
We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
1/9/2015 | 11:45:46 AM
Re: Involvement of the users
I couldn't agree more that end-user involvement is the key to success in any software project, gvernment or commercial. Each of the tips above assume end-user involvement. For instance, when we talk about prove it fast, the audience we are proving to should be all the stakeholders, including the end-users. By starting small, you are able to get fucntionality all the way out to the end-user so that everyone involved can provide feedback. Often, little things end up dooming the project to failure. By starting small and proving out the technology all the way through to the end-users, those little things get resolved early or, if they can't be overcome, prevent the project from moving forward before too much time and too many resourcs are wassted.
User Rank: Ninja
12/29/2014 | 2:14:33 PM
Involvement of the users
From what I have seen in my experience with government projects is the fact that most government projects fail because there's little or no buy-in from the people who use the system. I think for a project to be successful, the input of the people has to be very important to create a sense of ownership in the new system. Without that, the project is doomed to fail.
User Rank: Ninja
12/26/2014 | 3:41:06 PM
Hello and welcome to 2010
LOL I think the feds ought to stop sweating the cloud/wasting billions, and, instead, focus on using an OS other than Windows 95.  
Data Science: How the Pandemic Has Affected 10 Popular Jobs
Cynthia Harvey, Freelance Journalist, InformationWeek,  9/9/2020
The Growing Security Priority for DevOps and Cloud Migration
Joao-Pierre S. Ruth, Senior Writer,  9/3/2020
Dark Side of AI: How to Make Artificial Intelligence Trustworthy
Guest Commentary, Guest Commentary,  9/15/2020
White Papers
Register for InformationWeek Newsletters
Current Issue
IT Automation Transforms Network Management
In this special report we will examine the layers of automation and orchestration in IT operations, and how they can provide high availability and greater scale for modern applications and business demands.
Flash Poll