What are the steps to execute engineering change management processes?

1 Identify the need for change

The first step is to identify the need for change, which can arise from various sources, such as customer feedback, design errors, regulatory requirements, or market trends. The need for change should be clearly defined and justified, and the impact of the change on the project scope, schedule, budget, and quality should be assessed. The need for change should be documented and communicated to the relevant stakeholders for approval.

2 Analyze the change request

The second step is to analyze the change request, which is a formal document that describes the proposed change, the rationale, the benefits, and the risks. The change request should be evaluated by a cross-functional team of experts, who can provide technical, operational, and business insights. The team should consider the feasibility, desirability, and viability of the change, and identify the resources, activities, and deliverables required to implement the change. The team should also estimate the cost, time, and quality implications of the change, and compare them with the baseline plan.

3 Decide on the change

The third step is to decide on the change, which involves reviewing the analysis and recommendations from the team, and approving or rejecting the change request. The decision should be based on the criteria and priorities established by the project sponsor, the customer, and other key stakeholders. The decision should be documented and communicated to all the parties involved in the project, and the change request should be updated accordingly.

4 Implement the change

The fourth step is to implement the change, which involves executing the tasks and deliverables defined in the change request, and monitoring and controlling the progress and performance of the change. The implementation should follow the best practices and standards of engineering management, such as project management, risk management, quality management, and configuration management. The implementation should also involve regular communication and coordination with the stakeholders, and reporting and documentation of the results and outcomes of the change.

5 Verify and validate the change

The fifth step is to verify and validate the change, which involves checking and testing the change to ensure that it meets the requirements and specifications, and that it delivers the expected value and benefits. The verification and validation should use appropriate methods and tools, such as inspections, reviews, audits, simulations, or prototypes. The verification and validation should also involve feedback and acceptance from the customer and other stakeholders, and documentation and closure of the change request.

6 Learn from the change

The sixth step is to learn from the change, which involves capturing and analyzing the lessons learned from the change process, and identifying the best practices, improvements, and opportunities for future changes. The learning should also involve sharing and disseminating the knowledge and experience gained from the change, and updating and maintaining the project records, documents, and assets. The learning should also involve celebrating and rewarding the achievements and contributions of the team and the stakeholders involved in the change.