Hello guys;
My actual situation is:
We have been testing phase; (Unit test; Integral Test; System Test; Acceptance Test).
So in each test; we have a tester team; this team is mix between technician & Functional testers);
When Functional test the system and they find some error; they send this error to technical team for to fix this.

How I can to implement Change Management process for to improvement my actual process ?

usually the first step is to try and identify your pains. What problems do you currently experience that force you to look for improvement?

The procedures in dev and test environment are likely to be somewhat different from those for prod. As former software developer I understand the importance of keeping both test and dev environments 'clean' and up to date, thus requiring certain level of control over changes happening to these environment to maintain their functionality.
However, you also need to minimize process overhead and to be able to propagate your changes rather quickly from one env't to another.

Again, it is hard to suggest anything concrete with information available. As I said, start by documenting what the issues are. Then it should become clearer what your change process, or a variation of such, should be for the non-production environments.

The main goal of CM is to mitigate risks to the PRODUCTION enviroment. You should focus less on what happends in dev and UAT. But you will require proof of successful testing from UAT (pre-prod) in order for you to mitigate any risk of implementing a change into Prod. But dev is where the developers play.

To add to others' points. You need to make sure that you have very precise and well controlled procedures for transitioning from development to production environment in terms of support.

One of the projects I am working on now has that very problem. There is no clear differentiation between when test stops and production begins, i.e. when Incident and Change management, Service desk and configuration management become the governing forces for newly developed applications.

Tests stops when Testing Center of Excellence or UAT group says testing is complete per project. Then, a signoff by stakeholders are required to move the deliverable into production along with approval from the CAB.

You must control test and live environments to ensure consistency between the two. If you don't, a successful test in the test environment may cause chaos in a live environment that isn't in step with your test environment.