Let’s finish with part 3 of 3 of the “usual suspects” for the technical deliverables in Salesforce discovery projects.

3. Environment Release Strategy

Purpose:

  • Understand the various sandboxes and their uses
  • Describe how functionality will be migrated from one sandbox to another and eventually to production

Usage:

  • Some sandboxes are specifically built for development while others are for proof of concepts (POCs) or testing
  • Align everyone on how to move functionality from one instance to another, i.e. continuous improvement/continuous delivery (CI/CD)
  • Plan for minimizing impact on the production instance

Required:

  • A list of sandboxes and their primary function
  • Technologies used to deploy and their promotion path
  • A description of the source code repository

Example:

 

3. Data Migration Strategy

Purpose:

  • An artifact which provides the details for the data migration approach
  • It should mention the tools and data elements to consider while importing data

Usage:

  • Plan to research and analyze the data required and not required
  • Determine the strategy for general data migration planning and data governance

Required:

  • Plan on how to approach and select data to be migrated
  • Details on how data will be mapped to the Salesforce object model
  • Rollout plan for when users can validate the data and which in sandbox
  • Deployment plan when the source systems are being actively used

Example:

The takeaway
Depending on the size and complexity of the project, not all of these deliverables will be necessary. Set them as a starting point in deciding which ones could be considered and make a final decision based on your context.

Category:
Salesforce