Matrix42 Core Delivery: Change Management Practices in Matrix42 Core Deliveries
Matrix42 Core Delivery: Change Management Practices in Matrix42 Core Deliveries
Introduction
This change management guideline has been designed to facilitate a successful and effective Matrix42 Core delivery. The goal of this document is to offer you practical guidance on managing changes effectively, ensuring that your project remains on course, aligned with your goals, and free from budget and timeline uncertainties. We prioritize transparency and collaboration in the change management practices.
Reporting and Resolving Test Findings and Change Requests
Change request can be created directly, or they can originate from test findings.
Change requests not associated with specific test cases
- Select the Create new button in the header bar
- Type Delivery item for filtering the results
- Select Delivery Item from the list
- Write a brief name that summarizes the change request clearly
- Write a comprehensive description, including steps of the desired behavior and screenshots.
- Set the Item type as Delivery change proposal
- Add attachments if necessary
- Write a description of the background of the request in the field What is the backgound for this request?
- Describe the suggested change in the field What is the suggested change?
- Save the datacard



The Efecte delivery team will review the change request. You can also link Change requests to test cases if necessary.
Implementation of Change Requests
In situations necessitating change requests, it's important to note that these will be put into action only after:
a) The delivery team has provided a comprehensive work estimate.
b) Both you and the Efecte delivery team have mutually accepted the change request.
c) The initial Matrix42 Core delivery has been successfully concluded.
We appreciate your understanding of this approach, which is designed to ensure the efficiency and effectiveness of the Matrix42 Core delivery process.
Table of Contents