Change-advisory board

Returning to the podcast are IGES Corrections Advisory Committee experts, Rick Davis, Lina Yala, Jerry Breniger, and Krista Murray.

Together, the panel dives into how strong collaboration between the program team and Change Advisory Board can support a successful implementation, funding approaches that enable continuous improvement, and the importance of working closely with the solution providers to keep systems modern long after implementation.

Whether your agency is preparing for an OMS modernization effort or already navigating one, this episode offers plenty to consider.

Join the conversation and hear what these experts have learned about setting programs up for success today and into the future.

I am going to go back to being the moderator because Krista and Lynn and Jerry have definitely the hard part.

Answering questions is the hardest part of this whole podcast series.

So with that, Lynn, you brought up about the Change Advisory Board in a previous question.

Let me ask you this.

It is an operational governance framework that ensures changes are documented, rigorously tested, authorized, and auditable before they touch production.

At the center of this framework sits the Change Advisory Board.

The Change Advisory Board is a cross-functional governing body made up of technical leads, infrastructure engineers, security personnel, and business managers.

Their mission is not to rubber stamp requests.

It is to evaluate the operational risk, security implications, and business disruption of any proposed modification to the enterprise environment.

The change owner must execute the change in an isolated staging or pre-production environment that mirrors production.

They must present verifiable proof that the patch closed the targeted vulnerability without breaking core business logic.

Once the Change Advisory Board evaluates the impact analysis and test results, the change is scheduled within a designated maintenance window.