| |
 |
|
Phase I |
 |
| |
|
|
|
 |
|
Select team based upon the execution platform, operating systems, software environment, business environment, databases, etc. |
|
| |
|
|
|
|
|
Obtain thorough understanding of the business domain and a complete understanding of the application implementation. |
|
| |
|
|
|
|
|
Configure the right maintenance model along with a gradual knowledge transfer to the offshore maintenance team. |
|
| |
|
|
Phase II |
|
| |
|
|
|
|
|
Stabilize infrastructure and the support processes. |
|
| |
|
|
|
|
|
Obtain thorough understanding of the scope and complexity of technical and business issues. |
|
| |
|
|
|
|
|
Distribute work between client and offshore maintenance teams. |
|
| |
|
|
|
|
|
Provide training in the areas required to the maintenance team under the guidance of the onsite team. |
|
| |
|
|
|
|
|
Schedule workload and system analysis. |
|
| |
|
|
Phase III |
|
| |
|
|
|
|
|
Acquire complete knowledge of application execution environment, operational knowledge, business logic and structural/design knowledge. |
|
| |
|
|
|
|
|
Offshore maintenance team to perform most change request activities on its own, including help desk calls. |
|
| |
|
|
|
|
|
Client team to retain highly critical activities like change prioritization and version control. |
|
| |
|
|
Phase IV |
|
| |
|
|
|
|
|
Provide steady state support. |
|
| |
|
|
|
|
|
Assume entire maintenance operation, from versioning and end-user support, to help desk activities. |
