Experience summary of project implementation over the years

2007 to 2010 I have participated in more than 10 customer service system project implementation of the work, these projects short time has a month, a long two years, the amount of less than hundreds of thousands of, more than a few billion, the number of two or three people, more than hundred people, I in these projects, some of the participation in the whole process, some participated in the part, Because I do the project is the implementation of the middle and late deployment, system cutting, legacy problem processing, system to dimension, such as research, analysis, coding, testing and other matters are not within the scope of my responsibility, especially for several years to participate in the implementation of the project experience to write, for reference.

Some of the major projects involved are:
1.2007 A central database upgrade project, including the upgrade of minicomputer, AIX, Oracle, minicomputer from P660 to P570, AIX from 5.1 to 5.3, Oracle from 8.1.7 OPS to 9.2.0.8 RAC.
2. More than 2007 years of media customer service projects, mainly the implementation of database and application software deployment, System commissioning, problem processing.
3. More than 2009 years in the city of the process of transformation projects, mainly the implementation of application software deployment.
4. The NGCC project in more than 2010 centers, including hardware, software, network, database and other parts.
The above projects in my duties are mainly the database installation, application software deployment installation, script loading, data import, configuration file modification, System commissioning, fault location processing, customer test acceptance, system formal cutting, legacy problem processing, system to dimension and other work.

Personal Summary of the      project:
1. Regardless of the size of the project, it is important to open a project mobilization before commencement, to allow all participants in the project to understand the nature of the project, objectives, scope, time, the responsibilities of each person in the project, the time of the work, The phase of the project, such as the near degree of logistics.
2. Project implementation in strict accordance with the project schedule, each stage of the work should be as far as possible to budget, to avoid the occurrence of accidents caused by project delays.
3. In the Division of labor with the user, all the need for customer coordination to promote things, all let customers do.
4. All software functions are strictly based on the software specification, and the temporary request of the user is handled by the project manager, and the others are strictly forbidden to reply casually.
5. All things on both sides are handled by the interface person, do not bypass the interface person and directly handle.
6. The system test is strictly based on the test manual, and for other situations appearing in the test, the test work should not be prevented from continuing.
7. Test to have test scale, range, degree, not due to some problems and unlimited testing.
8. To develop detailed hardware, software, network, database acceptance standards, based on standards, can not casually sloppy.
9. Each person is required to inform each day of his/her work progress, difficulties encountered, resources needed, suggestions and comments, and progress of the project.
10. For large projects to be in batches, phased cut, each cut to develop a detailed cutting plan (detailed standard is what: is specific to each command line), each involved in the responsibility of cutting personnel (main operator, technical support person, coordinator, test person, inspection person, computer room security personnel, After cutting the attendant), cut the failure of the reverse program, cut the 24 hours after the high volume of traffic to the system impact contingency plans.
11. After each batch is cut, the cutting will be summarized and analyzed for the next cut to lay a good foundation until the entire system cut-off completed.
12. To inform customers in advance, after the completion of the cut-off after the relevant personnel to gradually evacuate the cutting site.
13. When the relevant personnel evacuate the cut-off site, to surrender their own possession of all resources, strictly prohibited to take away or dispose of arbitrarily.
14. After the cut-off problem has been addressed to a certain extent, it must be transferred from the project stage to the maintenance phase, and the project cannot never end.
15. To work out the principle of dealing with legacy issues that have been approved by both parties, it is not possible to delay the signing of the project acceptance report because some issues have not been addressed.
16. After the completion of the project, the software version, manuals, maintenance manuals, upgrade manuals and other manuals and documents must also be transferred synchronously.
17. After the project is completed, temporary data in the test, temporary tools installed, other things that affect system performance and security must be thoroughly cleaned up, and the system is strictly forbidden to leave the back door.

The above is my participation in the project of some experience, write out to learn from, the shortcomings of the hope forgive me.

Http://blog.sina.com.cn/s/blog_668aae780101h5bz.html

Experience summary of project implementation over the years