CCD Process Flow
CCD stands for Change Control for Deployments. There are two main process flows for deploying packages to Production:
Product/Project (Non-domain-based) Flow:
CCD tickets are initially raised by the respective team using SRN details. These are then approved by the Technical Leads (Mapped as CCD PRODUCT LEADS).
The Leads review the SRN and request approval from the Testing team. The queue is mapped to the individual Test lead of the Product/Project.
Once the test lead approves, the CCD moves to the Infosec team's queue for review and approval.
After approval by the Infosec team (one of the resources mapped to CCD INFOSEC Groups), the tickets move to the Delivery Manager of the particular Product (mapped as CCD DELIVERY MANAGER).
The Delivery Manager routes the request to Release Management for Release Audit. The Release Management team (CCD RELEASE MANAGEMENT) approves and routes it to the Delivery Head (CCD DELIVERY HEAD) for the particular Product for deployment.
CCD will be addressed by the GIT team (CCD DEPLOYMENT), either by themselves or by routing it to CCD TECH SUPPORT or CCD DATABASE team for deployment steps.
Finally, once the CCD is deployed, the GIT team will move it to the Post-Monitoring queue. After 5 days, the CCD automatically moves to the archive.
Project Vertical-based Flow
CCD tickets are initially raised by the respective team with SRN details. These are to be approved by the Technical Leads (Mapped as CCD PROJECT LEADS). Since leads are shared across projects, all project leads will be listed as part of the CCD Project leads, and respective leads should review & approve. This also applies to the Testing & Delivery Manager.
The Leads review the SRN and request approval from the Testing team. The queue is mapped to the individual Test lead of the Product/Project.
Once the test lead approves, the CCD goes to the queue of the QA & Operations team for review & approval.
Once the QA team (CCD QUALITY ASSURANCE) approves the CCD, it moves to the Operations team (CCD OPERATIONS) for approval and gets routed to the Delivery Manager.
The Delivery Manager routes the request to Release Management for Release Audit. The Release Management team (CCD RELEASE MANAGEMENT) approves and routes it to the Delivery Head (CCD DELIVERY HEAD) for the particular Product for deployment.
CCD will be addressed by the GIT team (CCD DEPLOYMENT), either by themselves or by routing it to CCD TECH SUPPORT or the CCD DATABASE team for deployment steps.
Finally, once the CCD is deployed, the GIT team will move it to the Post-Monitoring queue. After 5 days, the CCD automatically moves to the archive.