DELIVER Go/No-Go Decision The steering committee and/or customer executive sponsor (or delegate) should sign off that they agree we will go live, under what conditions, and when. This should be documented with acknowledgement from the customer. Defined Outcomes Purpose ❏ Criteria for Go Decision Documented: Clear documentation of the specific criteria that must be met for the project to proceed. The purpose of the Go/No-Go meeting to launch a project on ❏ Decision Agreement: Formal agreement on the Go/No-Go decision, Salesforce is to evaluate the project's readiness for deployment by including any conditions or contingencies, documented by all reviewing key milestones, testing results, stakeholder approvals, and stakeholders. potential risks. This meeting ensures that all necessary criteria and ❏ Readiness Assessment: Confirmation that all project components, including testing, training, and data migration, are complete and prerequisites are met, and that the team is aligned on the project's satisfactory. current status and next steps. ❏ Risk Evaluation: Thorough evaluation and mitigation plans for any identified risks or potential issues that could impact the project. Additionally, it includes the establishment of rollback plans to address ❏ Rollback Plan: Detailed and approved rollback plan outlining steps to any issues that may arise post-launch, ensuring a structured and revert changes in case of post-launch issues. secure approach to reverting changes if needed, thus safeguarding Salesforce Adoption Dashboards ❏ Stakeholder Alignment: Ensured alignment and commitment from all relevant stakeholders, confirming their support and readiness for system integrity and business continuity. the launch. Best Practice Go/No-Go Checklist Sample Template Tools & Templates