After IT Business System for Global Companies, the overall outsourcing of the company gives our company, the maintenance of existing business systems is divided into several maintenance projects, and in order to adapt to customer company's business development and changes, develop new business The system and modification of existing systems are essential, and this part of the work is divided into development projects. This divided organizational structure is clear, the task is clear, suitable for project management, is a typical project-type organizational structure. The current question is how to manage the connection between two projects? After the business system developed by the development project group, go to the maintenance project group for maintenance, how to manage this process? The business system should have been officially run before the development project group is transferred to the maintenance project group, and it is required to develop project team maintenance for a while until the maintenance project group officially begins to maintain the business system.
When the development project group believes that the development project can end, when the business system can transfer to the maintenance project group, the MANAGER of the two project groups starts to contact coordination, and this handover process begins. This process is actually very simple, that is, the two sides review the handover conditions, as long as the maintenance project team believes that the current business system meets the handover conditions, the maintenance of the project group Manager signage, the service system is officially maintained by the maintenance project team.
Which conditional maintenance project groups can sign up agree that the business system is maintained by them?
First, customers, end users, and related operators are satisfied with the business system.
This is the most basic condition. If these people are not satisfied with this system, the system has not yet reached the user's request, and the customer has not received it, and there may be the next development and modification. Then this is still the continuation of the development project, in this case, the development project is not able to end, and the maintenance project team is more impossible to receive such a system to maintain.
Second, the guarantee system has stabilized.
The development project group needs to start training to maintain the project group to make the necessary business system knowledge. After the maintenance project group is finished, you can test the system to see if the system is stable. If the system has a big performance problem, the development project group also needs to resolve the project team before you can receive it.
Another condition is that all system problems have been resolved, including issues reported after the user use.
If the business system is officially run, if the user discovers the problem, it needs to be resolved within the time specified in SLA. All problems are tracked, these issues must have been resolved before the business system is officially handed over to the maintenance project group.
Finally, when the above conditions are met, the development project group needs to show the development and short-term maintenance of the business system to the maintenance project group and business unit. This allows the maintenance project group to fully understand the history of the business system.
In the process of transferring the business system from the development project group to the maintenance project group, the key activities include:
1. Maintaining the project team testing system to meet customer requirements, if necessary, implement monitoring of the system.
2. Development Project Group reports the system maintenance and modification history of the system.
3. After maintaining the project team, after the system is considered to be stable, the development project group began to do business systems to maintain the project group.
4. Update the business system's risk management documentation.
5. Update the SLA of the business system.
6. To determine the definition maintenance process with the business unit, including how to report, how to solve, what kind of problem is to be responsible.
7. Determine the cost of maintenance projects and the settlement method.
8. Develop project teams and maintenance project groups and business units to share business system development and experience and lessons in short-term maintenance.
9. The customer's satisfaction assessment of the business system.
When all the above work has been done, all the transfer conditions are also met, then the project group, the maintenance project group, and the business unit can sign together, the business system is officially maintained by the maintenance project group. Then this handover process is successful.
