The Applications Handbook.pdf - Nexus Technologies Inc.

RUN: Maintaining the Responsive Live Application ■ 77
means testing and validating the overall business
process, as we described in the previous chapter, not
just the underlying applications and subsystems.
6. As you implement the change, test it against its new,
updated requirements. You can return it to production
when you’ve verified that it still functions, performs,
and is secure enough to meet the needs of the business.
7. Before moving to production, evaluate and compare the
deployment of the change with all other changes
moving to production to avoid collision and impact to
production. Generally, require an authorization to move
to production before deployment.
Change with the Times: Automating
Change Management
Many handoffs occur in the application change-management
process, and each is fraught with peril. Even minor miscommunication
may keep a critical change out of the next release.
Automating the handoffs assures that the information
exchanged is accurate and timely. A change request that originates
from the service desk should automatically update the
demand-management system and should trigger notification
of the appropriate team members to review change requests.
If the change is approved, the management system should trigger
updates to the requirements management or defect management
systems that initiate the workflow to expedite the
change activities.
Following and automating application change management
processes helps lower costs while reducing the risks and
impact to the business. It helps meet compliance requirements
and provides better visibility into what needs to be delivered
so you’re using finite IT resources effectively to meet the needs
of the business.