Typical examples from the computer and network environments are patches to software products, installation of new operating systems, upgrades to network routing tables, or changes to the electrical power systems supporting such infrastructure.
Afterwards, a risk category should ideally be assigned to the proposed change: high-, moderate-, or low-risk.
[3][9][10] If not addressed in the plan/scope, the desire for a backout plan should be expressed, particularly for high-risk changes that have significant worst-case scenarios.
This allows the delivery team an opportunity to design and make incremental changes, with unit and/or regression testing.
In rare cases where the solution can't be tested, special consideration should be made towards the change/implementation window.
[3] Following implementation, the team may also carry out a post-implementation review, which would take place at another stakeholder meeting or during project closing procedures.
[3] In a good manufacturing practice regulated industry, the topic is frequently encountered by its users.
[16] From the information technology perspective for clinical trials, it has been guided by another U.S. Food and Drug Administration document.