John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/

Want to listen to other episodes? www.Federaltechpodcast.com

Once upon a time, requirements would be collected and a software team would write custom code and after a year or two, a solution would be released.

This seems like the Land of Oz.

Today's software developers grab code off the shelf, assemble it, and then deploy it. Then iteration after iteration must be evaluated and deployed in a world of constantly changing system requirements and cyber attacks.

Let us not forget testing must be included in each phase. There is functional testing, performance testing, checking for data integrity, mobile testing, and let us not forget user interface testing. In the federal world, consideration must be given to compliance. In the intelligence sphere, this is all taken up a notch.

Modern software development is a marathon with a constantly changing course and a never-ending finish line.

Today, we sat down with Adam Rosenbaum from Tricentis to examine the role of testing in this arduous process. He suggests that the custom part of coding prevalent years ago should be applied to automating testing.

This way, application testing can be automated using custom built-for-purpose solutions to verify functionality and performance. Adam Rosenbaum looks at a no code, low code approach to relieve some of the burden of excessive testing demands.

Two main benefits of automated testing are to be able to do several tests at once and that time can be used to free up developers for other human-based analytical work.

https://content.leadquizzes.com/lp/fk1JL_FgeQ

Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/

Want to listen to other episodes? www.Federaltechpodcast.com

FedRAMP was launched fourteen years ago; today we get an update on metrics and use cases to help companies considering certification.

James Leach has been immersed in the world of FedRAMP since the beginning. Today, he gives listeners insight on navigating the FedRAMP compliance process.

Commercial companies understand, in detail, the business problem they can solve. For some reason, when it comes to the federal government, they think they can "copy and paste" a business case and have it resonate.

When they apply, they may reference a single-threaded business case without federal business. Or they may promote an on-premises model and not include a cloud reference. Finally, organizations may dive into a hybrid cloud environment where it is a challenge to get sponsors.

First, one must do business with an agency and understand their requirements in detail; they will have different priorities from a regular "for profit" company. You will also need an agency to sponsor your application.

Once these basic hurdles are achieved, then one can begin to study cloud reference architecture. During the interview, James Leach gave several guidelines.

>> You need to understand FedRAMP more as a maturity model than a checklist for compliance.

>> You need to understand the controls but, more importantly, how the mandates are implemented.

Commercial companies can expend considerable resources to achieve FedRAMP certification, only to get frustrated in the end. FedRAMP is not a walk in the park and must be taken seriously.

Fun fact #1: 90% of software developed today comprises third-party apps.

Fun fact #2: 48% of organizations have over one hundred tools in the toolchain.

What could go wrong?

Today, we sat down with Ben Chicoski from CloudBees. He discusses the evolution of software development, emphasizing the importance of testing in the software delivery lifecycle.

CloudBees acquired Launchable to use AI to analyze test patterns and results to surface only important tests. He highlights that up to 80% of tests are unnecessary, consuming significant developer time.

CloudBees leverages AI and machine learning to optimize testing, reduce waste, and improve efficiency. The conversation also touches on the importance of continuous improvement, trustworthy pipelines, and the future challenges and opportunities in federal software development.

This discussion includes release orchestration and how it addresses the unintended consequences of increased development speed.

https://content.leadquizzes.com/lp/fk1JL_FgeQ

Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/

Want to listen to other episodes? www.Federaltechpodcast.com

Growth always brings challenges. In today's episode, we talk about how the DoD can manage the challenge of development in several aspects of identity management.

Like most federal agencies, the DoD has made a move to the hybrid cloud; this alone adds to the complexity of the identification process. However, in addition to the 1.3 million active-duty service members, they must contend with reserves, DoD civilians, veterans, and many more. Oh, did we mention mobile?

The official designation of the process of validating identity is called Identity Credentialing and Access Management, or ICAM.

During this interview, experts from Akamai suggest:

>> Consider applying AI/ML to help analyze identity data.

>>> Fast Identity Online (FIDO) FIDO standards exist, and one can consider applying FIDO to simplify identity.

Akamai has worked with both Defense and Civilian agencies to enable technologies like CAC/PIV and YUBIkey. Further, their well-known enterprise access management gives them the ability to protect web applications as well as mobile devices.

Many organizations are tasked with managing millions of individuals. Very few are associated with capabilities that can have as serious consequences as the DoD.

Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/

Want to listen to other episodes? www.Federaltechpodcast.com

When you watch a spy movie you get the impression that the federal government's intelligence agencies have unlimited funds for intelligence, satellites, and anything else that sounds mysterious.

Well, today's interview will reinforce the concept that every federal agency has a limited budget. Money is allocated to buy test tubes at NIH or purchase intelligence data.

There may be situations where federal agencies may not be able to access information from the dark web, or they may get overwhelmed with the volume of data produced on any given day.

Today, we sat down with McDaniel Wicker to talk about how Babel Street is positioned to provide reliable data to federal agencies.

Babel Street began with a focus on foreign language knowledge acquisition. During the interview, McDaniel shared how Babel Street has grown into a service that can provide a wide range of information for various clients.

McDaniel's company has the technology to sift through information in a wide variety of languages to understand sentiment. As a result, they are positioned to do expensive, original research or even just confirm suspicious activity for an agency.

Listen to the interview to get a better perspective on how the federal government can leverage artificial intelligence and multiple sources to provide timely information that can result in responsible decisions.

Want to make the most out of your next podcast appearance? https://content.leadquizzes.com/lp/fk1JL_FgeQ

Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/

Want to listen to other episodes? www.Federaltechpodcast.com

According to the MIT Technology Review, the federal government has over 26,000 websites. What good is it if citizens cannot access the information they require?

Today, we have Angela Mercado from RELI Group discuss User Experience (UX) and User Interface (UI) for federal websites.

One of the many impacts of COVID was American citizens were trying to get information from federal websites and were frustrated. As a result, in December of 2021 the White House issued Executive Order 14058, which had an emphasis on improving user experience for federal web sites.

Angela Mercado likes to focus on the phrase "Human Centered Design." This means to gather as much data from users as one and to seek to optimize their experience.

During the interview she reviews heat maps, surveys, Net Promoter Score, and a myriad of tools to diagnose a faltering website. The goal is to reduce user frustration, have their commercial website experience like a federal website, give the user a seamless experience and to take advantage of automation and Artificial Intelligence to accomplish these tasks.

For example, AI tools can be used to scan federal websites to determine if they follow accessibility standards.

She gives listeners a great overview of the UI/UX work done by the GSA as a proponent of improved user experience for federal websites.

Want to make the most out of your next podcast appearance?

Want to make the most out of your next podcast appearance? https://content.leadquizzes.com/lp/fk1JL_FgeQ

Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/

Want to listen to other episodes? www.Federaltechpodcast.com

Every software developer knows about the meeting in February 2011 at a skiing lodge in Utah. Seventeen people met to produce the "Agile Software Manifesto."

Large software projects were falling left and right. This was a group of experienced developers who thought interaction and flexibility were keys to producing complex code effectively.

They introduce concepts like iteration and technical debt to the general audience.

Twenty- three years later we see a distortion of these concepts in the federal government's approach to software development. They may launch an application quickly and suboptimal, and then expect to iterate.

However, this process has been distorted to a point where 70% of the federal IT budget is spent on this "iteration" under the guise of Operations and Maintenance.

Today, we sat down with Sonny Hashimi, the Head of Global Sector for Unquirky. He has experience in the commercial world as well as the federal government. His last federal title was Commissioner, Federal Acquisition Service for the GSA.

He has seen this flawed software development strategy from many angles. He suggests that proprietary software should be replaced by open-source methods that will allow for rapid change in code.

That way, patches, and changes in direction of application development can be accomplished in a timely manner. This change would free up millions of dollars to accomplish improvements in federal systems.

Listen to hear his diagnosis of the problem and the options he provides.

https://content.leadquizzes.com/lp/fk1JL_FgeQ

Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/

Want to listen to other episodes? www.Federaltechpodcast.com

Forrester is well-known for conducting surveys with technology leaders and releasing conclusions. Today, we sat down with Sam Higgins, a Principal Analyst for Forrester, and looked at several studies he has participated in regarding the public sector and Artificial Intelligence.

We begin with some findings showing that 35% of global public sector organizations indicate an interest in implementing AI. Reduced cost, improved security, and automation are general benefits that have been reported.

This global view has been reinforced in the federal government with several programs including the AI test beds at the Department of Energy, Project Linchpin from the Army, and even the Air Force designating a Chief Data and AI Office.

During the interview, you will hear some surprising findings. One study shows that the responsibility for AI Strategy most often resides in the technology department, not official leadership.

Forrester is well-known for conducting surveys with technology leaders and releasing conclusions. Today, we sat down with Sam Higgins, a Principal Analyst for Forrester, and looked at several studies he has participated in regarding the public sector and Artificial Intelligence.

We begin with some findings showing that 35% of global public sector organizations indicate an interest in implementing AI. Reduced cost, improved security, and automation are general benefits that have been reported.

This global view has been reinforced in the federal government with several programs including the AI test beds at the Department of Energy, Project Linchpin from the Army, and even the Air Force designating a Chief Data and AI Office.

During the interview, you will hear some surprising findings. One study shows that the responsibility for AI Strategy most often resides in the technology department, not official leadership.

Want to make the most out of your next podcast appearance? https://content.leadquizzes.com/lp/fk1JL_FgeQ

Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/

Want to listen to other episodes? www.Federaltechpodcast.com

Our guest today is a grizzled veteran of the cyber wars. Chuck Herrin from F5 Networks has considerable experience in commercial and federal networks to see trends.

For example, years ago one could diagram a network easily. Today, we have complex systems that are bombarded with data. Virtual systems are allowing for databases to be created on the fly. Combine that with storage being split between in-house systems and many clouds, you get a situation difficult to understand.

Some hark back to 1970 when the Temptations released a song called "Ball of Confusion." Chuck has seen systems that can be appropriately titled a ball of confusion.

The solution? Understand your architecture. This way, you know all your endpoints and realize that the architecture is, in effect, your attack surface. From there, take a close look at your Application Program Interfaces.

Traditionally, one attack vector was the application itself. However, new cloud-based systems mean a process of distributed applications. As a result, the new attack point may be the API. We have a new term called a "leaky" API.

Chuck Herrin will share with listeners his experience and give you a deeper understanding of the role of protection of the API as part of a full orb strategy to protect vital federal data.

Want to make the most out of your next podcast appearance? https://content.leadquizzes.com/lp/fk1JL_FgeQ

Connect to John Gilroy on LinkedIn https://www.linkedin.com/in/john-gilroy/

Want to listen to other episodes? www.Federaltechpodcast.com

It seems like everyone is testing AI options; however, when it comes to technology like Quantum, people seem to shy away.

Today, we will attempt to clear up some of the questions listeners have about how to apply Quantum to federal problems.

Our guest Murray Thom has been working with Quantum for years. Further, his company, D-Wave, has been in business for 25 years, has two hundred patents, and employs over two hundred subject matter experts. So, D-Wave is not a startup without any proven record.

Murray sets the stage by setting up a contrast: classical computing compared to quantum computing. Traditional computers allow for a limited number of answers, while a quantum computer is not limited to the binary nature of the way we have been using computers.

Rather than diving into the philosophy and mathematics behind quantum, Murray looks at applications that can be boiled down to use cases.

If you look at the millions of containers that enter the United States each year, you can understand the complex nature of logistics. Effective use of quantum can allow for reduced fuel consumption, faster delivery times, and happier customers.

The federal government can apply this technology to areas like weather forecasting and even managing the 30,000 satellites that are projected to be circling the earth by 2030.