In enterprise management, few enterprises report on the quality of a completed project. However, the quality report is crucial to improving the working level and production capability of a project team, at the same time, the accumulation of enterprise management experience is also very important.
Quality reports mainly include productive analysis, quality analysis and corresponding improvement strategies.
Productive analysis: In the long-term production process of an enterprise, accumulate and analyze the desired workload of the software production process level, analyze the scheduled working hours and actual working hours of the project implementation, and draw a conclusion about whether the workload is consistent with the productive work.
For example, the production of a page is 1md.
Slow emergency troubleshooting
Quality Analysis: It mainly analyzes the quality of bugs in system testing and acceptance testing. The quality analysis conclusions mainly include the causes of bugs (excluding human factors), bug handling timeliness, and so on.
Corresponding strategy: This article mainly proposes an organization-level Avoidance Method Based on the negative conclusions drawn from the productive analysis and quality analysis.
Appendix: An example of a quality report
Quality Report |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project name: XX System |
|
|
|
|
|
|
|
|
|
Period: Mm DD, xxxx ~ Mm dd, xxxx |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project, generative, quality list |
|
|
|
|
|
|
|
|
|
|
Engineering |
Product Category |
Scheduled job count (MD) |
Actual job count (MD) |
QA count |
Number of demand changes |
Number of system test bugs |
Acceptance bug count |
Bug density (pieces/kloc )) |
|
|
Investigation |
Investigation Report |
1 |
1 |
2 |
1 |
|
|
|
|
|
Development |
APP code modification |
0.5 |
0.5 |
0 |
0 |
|
|
|
|
|
Unit test plan preparation |
Unit Test Plan |
1 |
1 |
0 |
0 |
|
|
|
|
|
Unit Test Plan Review |
- |
0.5 |
0.5 |
0 |
0 |
|
|
|
|
|
Unit test implementation |
Unit Test report |
3 |
3 |
0 |
0 |
|
|
|
|
|
Unit Test Report Review |
- |
1.5 |
1.5 |
0 |
0 |
|
|
|
|
|
System Test Plan Compilation |
System Test Plan |
2 |
2 |
0 |
0 |
|
|
|
|
|
System Test Plan Review |
- |
1 |
1 |
0 |
0 |
|
|
|
|
|
System test implementation |
System Test report |
1 |
1 |
0 |
0 |
2 |
|
|
|
|
System Test Report Review |
- |
1 |
1 |
0 |
0 |
|
|
|
|
|
Total |
|
12.5 |
12.5 |
2 |
1 |
2 |
1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Productive analysis: |
|
|
|
|
|
|
|
|
|
|
1. Slow modification of emergency problems |
|
|
|
|
|
|
|
|
|
2. Insufficient personnel considerations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quality Analysis: |
|
|
|
|
|
|
|
|
|
|
1. Timely reporting of System bugs |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Policy: |
|
|
|
|
|
|
|
|
|
|
|
1. Increase the unit test coverage rate of the system. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|