Sandbox Design Strategies for Enterprise Implementations

In this session we will talk about sandbox design strategies for enterprise Implementations. It is inevitable to avoid Sandboxes in most enterprise implementations. As different teams work on different processes like testing, development, pre-release, and final rollout, it is essential to have a strong Sandbox strategy for a number of reasons ? parallel development (teams can work simultaneously, without halting any of their processes), shortened cycle times, reduce operational risks, increase productivity, efficiency and ultimately enhance the delivery.

In this session, you will learn industry best practices for effective Sandbox strategies.

1. Introduction to Sandbox
2. Types of Sandboxes
3. Sandbox Quotas
4. Agile Development Life Cycle
5. Typical Sandbox Use Cases
6. Deployment Flow
7. Different Sandbox Strategies

KEYNOTE

What is Sandbox?

1. Copy of your Salesforce Org/Production as a separate environment
2. Development, Testing, and Training.

 

Type of sandbox?

 

Sandbox - Key Features

1. Sandbox Templates: Pick a specific object and data to copy to your Full or Partial Copy sandbox
2. Sandbox Cloning: All Metadata - Copied to new sandbox, Same license type, Refresh a cloned sandbox from its source

 

Sandbox Allocations

Sandbox Types	Professional	Enterprise	Performance**	Unlimited
Developer	10	25	100	100
Developer Pro			5	5
Partial Copy		1	1	1
Full copy			1	1

 

Here is recording of session.

If you like this session please appreciate our speaker for his hard work over the weekend. His twitter handler is @SF_Guha (Please use #SalesforceApexHours tag).