Application maintenance has basic software development principles at its core. However, a full-blown development approach is often inappropriate for changes and enhancements requiring limited effort. Focus on the important steps – functional requirements and impact analysis before making the code change. Regardless of the size and scope of the change requested, some planning must take place to ensure the final result meets business expectations. 

Use Info-Tech’s OptimizeIT core Functional Specifications Template to describe the business requirements and functional elements the change must deliver. Use OptimizeIT’s advanced Work Breakdown Structure Template to help identify specific activities and plan resources to ensure successful change completion.

For some organizations, once a change has been made, it is ready to be tested and released into the production environment. Other organizations will bundle a change with other changes into a scheduled release – release management. This process creates a package of changes that can be tested and released together. 

The first two tools used in formal release management are the advanced Release Inclusion Request and the Release Configuration Record. The first is used by developers to define what changes have been made and need to be released into production. The latter is used by the release manager to confirm what will actually appear in a given release and to track the release’s status.

Testing is all about confirming that intended results have been, and will continue to be achieved going forward. Developing a clear test plan that identifies the types of testing to be carried out and the goals of each type is essential. 

First, use Info-Tech’s OptimizeIT advanced Testing Method Selection Tool to determine which testing types are of highest priority based on the quality of existing application development processes and overall impact of the change on the business. Next, use the advanced Test Strategy Template and Use Case and Test Case Matrix, as well as the core Functional Test Plan Template, to plan specific test scenarios and document your overall testing approach. 

Closing out testing activities is one of the final steps before rolling out a change. The effectiveness of this stage of a change activity or project can have a significant impact on the team’s ability to bring changes in on time, with quality. 

Use OptimizeIT’s core Test Tracking and Resolution Report tool to document problems found and how they were resolved. The information tracked here will be important during last-mile progress communication with change stakeholders.

All changes that have been made must be clearly documented across a range of information repositories. This is the final opportunity to ensure that no detail that can affect the ongoing health of the release has been overlooked. 

Take advantage of OptimizeIT’s core Version Control Worksheet in order to document all changes that have gone into the current version of the affected application. At this point, also be sure to update your existing Forward Schedule of Changes Template with new information about the status of the release.

Making a change without proper communication can result in end-user confusion and ultimate failure of the change that was supposed to make things better. End users and all stakeholders of the requested changes must be kept in the loop to minimize risk and maximize success.

Start the communication process by drafting a Release Rollout Communication Plan. This advanced planning tool will help you organize the key messages and communication channels required to get the word out about the change. Also plan a Release Rollout Stakeholders Meeting to address final concerns and achieve final buy-in for the change rollout – Info-Tech has provided an advanced-level meeting agenda for this purpose. At this meeting you can use OptimizeIT’s Release Approval Checklist to make sure all release prerequisites have been effectively addressed.

Measuring the success of the change is the final step in the maintenance lifecycle. OptimizeIT offers an advanced Release Post-Implementation Review tool to help you assess the success of project-scale application changes and recommend changes to existing processes. .

Application maintenance has basic software development principles at its core. However, a full-blown development approach is often inappropriate for changes and enhancements requiring limited effort. Focus on the important steps – functional requirements and impact analysis before making the code change. Regardless of the size and scope of the change requested, some planning must take place to ensure the final result meets business expectations. 

Use Info-Tech’s OptimizeIT core Functional Specifications Template to describe the business requirements and functional elements the change must deliver. Use OptimizeIT’s advanced Work Breakdown Structure Template to help identify specific activities and plan resources to ensure successful change completion.

For some organizations, once a change has been made, it is ready to be tested and released into the production environment. Other organizations will bundle a change with other changes into a scheduled release – release management. This process creates a package of changes that can be tested and released together. 

The first two tools used in formal release management are the advanced Release Inclusion Request and the Release Configuration Record. The first is used by developers to define what changes have been made and need to be released into production. The latter is used by the release manager to confirm what will actually appear in a given release and to track the release’s status.

Testing is all about confirming that intended results have been, and will continue to be achieved going forward. Developing a clear test plan that identifies the types of testing to be carried out and the goals of each type is essential. 

First, use Info-Tech’s OptimizeIT advanced Testing Method Selection Tool to determine which testing types are of highest priority based on the quality of existing application development processes and overall impact of the change on the business. Next, use the advanced Test Strategy Template and Use Case and Test Case Matrix, as well as the core Functional Test Plan Template, to plan specific test scenarios and document your overall testing approach. 

Closing out testing activities is one of the final steps before rolling out a change. The effectiveness of this stage of a change activity or project can have a significant impact on the team’s ability to bring changes in on time, with quality. 

Use OptimizeIT’s core Test Tracking and Resolution Report tool to document problems found and how they were resolved. The information tracked here will be important during last-mile progress communication with change stakeholders.

All changes that have been made must be clearly documented across a range of information repositories. This is the final opportunity to ensure that no detail that can affect the ongoing health of the release has been overlooked. 

Take advantage of OptimizeIT’s core Version Control Worksheet in order to document all changes that have gone into the current version of the affected application. At this point, also be sure to update your existing Forward Schedule of Changes Template with new information about the status of the release.

Making a change without proper communication can result in end-user confusion and ultimate failure of the change that was supposed to make things better. End users and all stakeholders of the requested changes must be kept in the loop to minimize risk and maximize success.

Start the communication process by drafting a Release Rollout Communication Plan. This advanced planning tool will help you organize the key messages and communication channels required to get the word out about the change. Also plan a Release Rollout Stakeholders Meeting to address final concerns and achieve final buy-in for the change rollout – Info-Tech has provided an advanced-level meeting agenda for this purpose. At this meeting you can use OptimizeIT’s Release Approval Checklist to make sure all release prerequisites have been effectively addressed.

Measuring the success of the change is the final step in the maintenance lifecycle. OptimizeIT offers an advanced Release Post-Implementation Review tool to help you assess the success of project-scale application changes and recommend changes to existing processes. .