Prioritize changes is an acceptable as a short-term strategy. However, more complex changes cannot be deferred indefinitely and need to be managed effectively, particularly if being introduced by multiple development initiatives. Care also needs to be taken that individual projects do not manipulate risk assessments to suit their own development timetable. Coordinated release management across projects and systems is a suitable strategy to employ in a complicated, dynamic system environment. Under this option, changes are packaged into releases that are implemented according to a predetermined schedule. Determining what changes are included in a release can be done in accordance with business and technical priorities. With release management, the emphasis is on coordinating changes stemming from multiple sources that impact multiple interconnected systems. This approach should lower technical risk and reduce the potential for system outage. Automating code movement is good practice. However, it does not address the fundamental issue of coordinating concurrent changes from multiple sources that impact multiple systems. Deferring changes to customer systems is not as comprehensive an approach as coordinated release management. The external usage environment could be a consideration when packaging changes into a release and scheduling release implementation. While there may be reasons to implement changes during quieter business periods (or at least to avoid known high-stress periods such as holidays), at other times there may be business imperatives for implementing customer system changes as quickly as possible.