Chiemerie Chigozie Chibuzor

Change Management Change Management Plan Pickup Page 1 of 14 Change Management VERSION HISTORY Version Date # 1.0 01/15/2022 Revision Approved Approval Date By Date // // 01/20/2022 Reason Initial draft of the Change Management Plan 1.1 02/01/2022 // // 02/05/2022 Incorporated feedback from project team 1.2 03/10/2022 // // 03/15/2022 Added section on Training and Development 1.3 04/05/2022 // // 04/10/2022 Updated Appendices and added Risk Management section 1.4 05/20/2022 // // 05/25/2022 Clarified roles and responsibilities in Section 3 Page 2 of 14 Change Management TABLE OF CONTENTS 1 INTRODUCTION ................................................................................................................4 1.1 Purpose of The Change Management Plan ..............................................................4 2 CHANGE MANAGEMENT PROCESS .............................................................................4 2.1 Change Request Process Flow Requirements ..........................................................4 2.2 Change Request Form and Change Management Log .............................................5 2.3 Evaluating and Authorizing Change Requests ........................................................7 3 RESPONSIBILITIES ...........................................................................................................9 APPENDIX A: CHANGE MANAGEMENT PLAN APPROVAL ....................................... 10 APPENDIX B: REFERENCES .............................................................................................. 11 APPENDIX C: KEY TERMS................................................................................................. 12 APPENDIX D: CHANGE REQUEST FORM EXAMPLE .................................................. 13 APPENDIX E: CHANGE MANAGEMENT LOG TEMPLATE ......................................... 14 Page 3 of 14 Change Management INTRODUCTION 1.1 PURPOSE OF THE CHANGE MANAGEMENT PLAN The purpose of this Change Management Plan is to establish a systematic approach for managing changes in the development and deployment of the E-commerce Platform. It aims to minimize risks, ensure effective communication, and maintain control over changes to achieve successful project delivery. The plan is tailored to minimize disruptions, assess impact on functionality, and engage stakeholders for the successful implementation of changes in the project. CHANGE MANAGEMENT PROCESS The Change Management process establishes an orderly and effective procedure for tracking the submission, coordination, review, evaluation, categorization, and approval for release of all changes to the project’s baselines. 1.2 CHANGE REQUEST PROCESS FLOW REQUIREMENTS Step Description Request for Stakeholders or project team members initiate a change request, Change outlining details such as the reasons for the change and potential benefits. Register & The change management team registers the request and conducts a Evaluate the preliminary evaluation to assess completeness and alignment with Change organizational objectives. Evaluate & Send A detailed evaluation is performed, considering the impact on scope, Changes to the schedule, budget, and resources. The Change Review Committee Review receives a comprehensive report with recommendations. Committee Accept The Change Review Committee makes a decision to accept or reject the proposed change. If accepted, formal approval is granted, communicated to stakeholders, and the change status is updated. Update Plan & The project or implementation plan is updated to include the approved Implement change. The change is executed according to the updated plan, and communication channels inform stakeholders of the progress. Page 4 of 14 Change Management 1.3 CHANGE MANAGEMENT PROCESS FLOW Step Description Start End Prepared Proactive identification and assessment of Change Request Impact Impact potential effects of a proposed change. Analysis Analysis Review Impact Thorough review of the prepared impact Analysis analysis by the Change Control Board or Impact Analysis Approval Approval Impleme relevant stakeholders. Implement Execution of planned modifications or Change additions to the system, process, or product. Test Change Rigorous testing to validate the effectiveness ntation Implementation Testing Testing Post- and reliability of the implemented change. Review Comprehensive assessment of the overall impact and success of the implemented Impleme change, informing continuous improvement. ntation Review Page 5 of 14 Change Management Figure 1. Change Management Process Flows Page 6 of 14 Change Management 1.4 1.5 CHANGE REQUEST FORM AND CHANGE MANAGEMENT LOG Element Description Date - CR# CR-PICKUP-001 Title Payment Gateway Integration Description Integrate additional payment gateway for user convenience. Submitter Sarah CR Impact Payment Gateway Integration Module Payment Module Version 1.4 Priority High EVALUATING AND AUTHORIZING CHANGE REQUESTS Change requests are evaluated using the following priority criteria: Priority Description High Change requests critical to the success of the E-commerce Platform. Significant impact on objectives, timelines, or deliverables. Medium Change requests with a noticeable impact. Affects project timelines or deliverables to a moderate extent. Low Change requests with a relatively minor impact. Enhancements but not critical to immediate project success. Change requests are evaluated and assigned one or more of the following change types: Type Description Scope Changes affecting the overall scope of the Pickup project. Includes features, functionalities, and project goals. Time Changes impacting the project timeline, such as adjustments to deadlines, milestones, or development phases. Duration Changes affecting the overall duration of the Pickup project, including extensions or compressions of the timeline. Cost Changes influencing the financial resources allocated for the Ecommerce Platform project. Page 7 of 14 Change Management Resources Changes related to personnel, technology, and tools necessary for the development, testing, and deployment of the project. Deliverables Changes impacting tangible project outputs, such as software modules, documentation, or user-facing features. Product Changes affecting the end result or output of the Pickup project, including its core functionality and features. Processes Changes involving adjustments to project workflows, methodologies, or procedures during the development and deployment. Quality Changes impacting the level of excellence or adherence to predefined standards in the design and functionality of the platform Change requests are evaluated and assigned one of the following status types: Status Description Open Change requests entered or open but not yet approved or assigned. Work in Change requests approved, assigned, and work is progressing. Progress In Review Change requests where work is completed and in the final review prior to testing. Testing Change requests where work has been reviewed and is currently being tested. Closed Change requests where work is complete, has passed all tests, and updates have been released. Page 8 of 14 Change Management 3 RESPONSIBILITIES Role Project Name // Authority Description High Overall project oversight, strategic Manager decision-making, and alignment of changes with project goals. Business // Medium Analyst Evaluate changes from a business perspective, ensuring alignment with user requirements. Technical Lead // Medium Assess technical feasibility and impact of proposed changes on the Ecommerce Platform. System // High Architecture Review changes for alignment with system architecture, scalability, and long-term technical vision. Page 9 of 14 Change Management Appendix A: Change Management Plan Approval The undersigned acknowledge they have reviewed the Pickup Change Management Plan and agree with the approach it presents. Changes to this Change Management Plan will be coordinated with and approved by the undersigned or their designated representatives. Signature: Date: Title: Role: Signature: Date: Title: Role: Signature: Date: Title: Role: Page 10 of 14 Change Management Appendix B: References The following table summarizes the documents referenced in this document. Document Name & Description Location Change Management Detailed strategy for managing URL or Network path Plan v2.1 changes throughout the project where document is located Version lifecycle. Project Plan v1.0 Change Request Form Comprehensive plan outlining project URL or Network path objectives, milestones, and resources. where document is located A Change Request Form is a concise Click Here document proposing, justifying, and assessing project changes for approval and implementation. Change Log Template A Change Log Template is a structured document capturing details of project changes, including date, description, and impact, for effective tracking and communication. Page 11 of 14 Click Here Change Management Appendix C: Key Terms This table provides definitions for terms relevant to this document. Term Definition E-commerce An online platform that facilitates electronic transactions, allowing Platform users to explore, book, and pay for automotive services. Scope The extent of what the E-commerce Platform project will accomplish, including features, services, and goals. System The high-level design and structure of the E-commerce Platform, Architecture including components, modules, and their interactions. Gateway The incorporation of a payment gateway into the E-commerce Integration Platform, allowing secure and seamless processing of online transactions. Page 12 of 14 Change Management Appendix D: Change Request Form Example Complete template link is mentioned in the table in Appendix B. Page 13 of 14 Change Management Appendix E: Change Management Log Template Complete template link provided in the table of the Appendix B. Page 14 of 14