Y DEPLO Deploy Solution Deploying a solution follows the processes and the roles and responsibilities described in a deployment plan signed off by the customer. Once the solution accessible in production for its user, the Customer will formally accept the deployment. How To Perform The deployment methods will vary based on the tools used, and it's assumed the Technical Architect (TA) and relevant team members are familiar with these specifics. Before deploying to Production, the TA should conduct several test deployments in a staging environment with customer team involvement to catch and address errors. This collaborative process helps the customer understand and contribute to the deployment runbooks. The Technical Architect (TA) and Solution Architect (SA) are responsible for maintaining the deployment workbook, ensuring the development team documents their work continuously during the Deliver and Deploy stages. Deployment must follow the Deployment Plan, including obtaining a "Go" decision, setting checkpoints, identifying dependencies, and arranging logistics like access to a "situation room" and after-hours site access should this be required. Deployment starts only with authorization from the Project/Program Manager (PM/PgM) on receipt from the customer project sponsor. If the deployment exceeds planned time, the TA must escalate to the PM/PgM for necessary adjustments. After completion, the TA informs the PM/PgM and key stakeholders per the Deployment Plan. A verification plan, created with the customer, uses components from the QA test plan to ensure consistent acceptance criteria and comprehensive test scripts for deployment verification (as described in the next chapter).