Original blog 《Comment on monitoring report on the first day of system launch by colleaguesProject E was launched last week. Project colleague P insisted that the E system launch monitoring report should be sent to the owners and project teams every day.
After one week's observation, I found that the project team had made continuous improvements in submitting the online use Report, which is worthy of praise. Our company is currently evaluating cmmi3. In fact, CMMI advocates this continuous improvement.
From the weekly report, we can see the improvement details of the project team's online use report:
- In the body of the email, the system E's tracking and monitoring information is classified and introduced. As the report is sent to the owner's business side, the owner's IT department, and relevant company leaders, it is copied to all members of the project team, therefore, we put the statistical monitoring data of the business class at the beginning, and put the statistical monitoring data of the IT class at the end;
- All statistical monitoring and analysis data will be shown after the introduction. You can refer to the attachment for details to meet the reading needs of personnel at different levels. For owners who are concerned about the business, you can only read the business section. Owners and colleagues at the leadership can only read the introduction to understand the situation. Direct leaders can monitor the overall quality through the attachment details when needed;
- In terms of business statistics, the data analysis features a multi-dimensional experience by collecting statistics on the number of visits, including classification statistics, regional statistics, and functional statistics, points out problems in use and possible problems in promotion, and asks the owners to improve their work through data;
- In terms of IT system statistics, we can analyze the operating system, middleware, database, and application logs, and propose precautions for maintenance by the owner's IT team; instead of simply listing data, we try to analyze statistics and draw conclusions from the data.
- Maintains service records with complete record elements, from information such as record time, recorder, problem submission time, organization, respondent, contact information, problem type, degree of emergency, Problem description, handling status, resolution, and notification, maintains complete records of each service;
After praising the project team, we hope that the project will be complete in terms of maintaining service records for last week's improvements, and complete all service records in the QQ, telephone service, and service system dispatch orders, do not miss out, so that after continuous service, you can analyze the service and reflect the value of the maintenance service to the user, and require more owner resources to be invested.
