How to implement a Customization?
Once the Customization Opportunity is identified, either the Developer of the Developer Lead should write a Specification Document with all the changes to be made to the Migration Tool. This document must contain a detailed description of the changes required, samples of code (both in the source language and target language) and other technical information required by the VBUC Product Team to make the change. Once this technical document is ready, it is separated in individual issues that are raised to the Product Testing Coordinator.
In Product Testing, the issue is reproduced and registered in the Product Backlog where issues are prioritized by the Product Team Lead.
The Product Team Lead then designates a member of the Product Team who will be in charge of implementing the customizations. The Product Engineer must coordinate all actions with the Developer in charge of the customization.
Once customizations are ready they must be tested by the Product Testing Team. If expected behavior is not the one intended the requirement, it goes back to the Product Backlog. If it meets the expected behavior, a new release of code is available to be used by the team performing the migration project.