| Product Change Process | |||
| Execution item | content | Person in charge | Is it done |
| Change application | Applications for product change should include information such as the reason for the change, content of the change, scope of influence, etc. | Product manager, R&D personnel or other related personnel | |
| Change review | Change review meeting: Discuss the necessity, feasibility, scope of impact of changes, etc. | Product manager, R&D personnel, testers | |
| Change plan formulation | Based on the review results, a change plan is formulated, including the time, personnel, resources, etc. of the change. | ||
| Change implementation | Implement according to the change plan, including code modification, testing, release, etc. | ||
| Change verification | After the change is implemented, verification is required to ensure that the change achieves the expected effect and will not affect other functions. | ||
| Change ends | After the change verification is passed, record the change process and results for subsequent reference. | ||
Reason for change:
1. Improve the productperformance: In order to improve the performance and quality of the product, some improvements may be required, such as adding new features, improving the durability of the product, etc.
2. Adapt to market demand: Market demand is constantly changing. In order to meet consumer needs, some adjustments and improvements to the product may be required.
3. Cost savings: In order to reduce production costs, some improvements to the product may be required, such as using cheaper materials, simplifying production processes, etc.
4. Comply with regulations and standards: In order to comply with relevant regulations and standards, some improvements to the product may be required, such as increasing safety performance, reducing environmental pollution, etc.
5. Optimize product structure: In order to improve product maintainability and upgradeability, some optimization and improvement of the product structure may be required.
| department | Person in charge | Execution content | Finished time | Leader confirms the signature(Relevant personnel confirm the signature one by one, expressing their agreement to change the content and promise the parts and completion time they need to perform) |
| Business Department | Whether the customer needs to confirm, confirm the deadline | 2023.6.18 | ||
| storehouse | Whether it affects product shipment, whether it affects shipped products | 2023.6.19 | ||
| test | Verify to ensure that the changes achieve the expected results and will not affect other functions. | 2023.6.20 | Verify the standards | |
| technology | Update the system BOM, record the change process and results, and publish changes | 2023.6.21 | Changes have been recorded in the system, and the XX department can check and notify the production department | |
| Production | Rearrange production tasks and implement changes | 2023.6.22 | No production problems, can be shipped normally |