Already a member? Sign In.
Need help? Our Trial Membership program will get you help on any IT project you're working on. You'll get access to our research, tools, advice and project help.
Change Execution Management
Changes to an application must be executed and rolled out to the user base in a controlled way that maximizes the change’s success and minimizes disruption to the business. This process is known as change execution management.
This stage of application maintenance includes four iterative steps:
- Build the Change
- Test the New Version
- Release the New Version
- Monitor Maintenance Changes
When you have completed these four steps, the requested changes will have been completed, documented, and delivered to stakeholders. Since this process can be used again and again, be sure to use the tools provided to identify areas for improvement for the next iteration.
Bundle 3 of 3
|FastTrack Activity||Execution Management FastTrack|
|Design, Develop, and Code the Change||
Functional Specifications Template
Work Breakdown Structure
|Build the Release and Gain Final Approval||
Release Inclusion Request and Approval
Release Configuration Record
|Test the Changes to Be Implemented||
Testing Method Selection Tool
Test Strategy Template
Use Case and Test Case Matrix
Functional Test Plan Template
|Analyze and Review Test Results||Test Tracking and Resolution Report|
|Document Version, Configuration and Release Control||Version Control Worksheet|
|Plan and Communicate Version Release to Users||
Release Rollout Communication Plan
Release Rollout Stakeholders Meeting Agenda
Release Approval Checklist
|Review Maintenance Change Costs and Performance||Release Post-Implementation Review|