The clients perception is that what works in Test (CTE) would work in Production when deployed. But, often times that isn't the case as our CTE environment is never identical to what is in Prod environment for any of the customer's business aliases. And, very frequently - we end up giving burn in support to the production deployments to try and fix all failures that would have occurred.
So, it is important to have Devops manage the production deployments in GIODE.
And, we must obviously have three environments - Dev, Test and Prod.
All Implementation, PER and support changes should happen in Dev. There must be a mechanism to zip or group everything that is being deployed at any given point.
The zipped file should be the only source of change for Test. If things are found to be working as it did in Dev, only then then should be the CSR / Implementer be allowed by a set of people (Group) who approve the deployment to production via Change Plan on one or two days a week