There are four main stages of software evolution – development, testing, deployment and monitoring. To ensure every application at your agency is secure, you must ingrain security in each cycle of development, no matter what process management approach your agency uses to create applications.
The federal government announced a new initiative on Friday that moves shared service missions into central offices to standardize purchasing.
Because governments have so many applications, platforms and servers, the security systems required to keep networks safe are abundant and diverse.
Agencies are looking for better approaches to data storage and backup. They are are shedding those complex, legacy multi-tiered solutions for simplified data management that still has physical support but is built for virtualized environments, and native cloud capabilities.
When Michael Sherwood, Director of Technology and Innovation for Las Vegas, assumed his role about three years ago, he was tasked with improving the city’s outlook for the future.
An agency’s decision to move to cloud can be complicated if an agency doesn’t quite understand the implications of cloud on everyday operations.
Changes include standing up an Office of Customer Experience, workforce reskilling, and using cloud and artificial intelligence to better serve the public.
Rather than ripping and replacing legacy systems, agencies are increasingly creating software applications to modernize their services.
Sometimes agencies lack the time or resources to fully phase out legacy IT systems. According to a March 27 audit from the Energy Department (DoE) Office of Inspector General (OIG), DoE was one of those agencies.
Technology goes beyond just the product; it’s also about the business value that the tech affords. Thus, the technology and business departments of an agency should work closely to make sure that there is overlap in their priorities.