Copado Change Management

Copado Change Management is an extension on top of the existing Copado feature set.  Copado Change Management (CCM) is designed to help customers better manage the release management process of requirements from one or multiple sandboxes to production.

Copado Change Management is included with the Enterprise Edition and available as an add-on license.

Change Management entities

Projects

A project is a proposed or planned undertaking of changes that are to be made in Salesforce.

Sprints

A sprint (or iteration) is the basic unit of development in Scrum. The sprint is a "time boxed" effort, which means that it is restricted to a specific duration. The duration is fixed in advance for each sprint and is normally between one week and one month, although two weeks is typical.

User Stories

A user story is one or more sentences in the everyday language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function.  The User Stories allows Salesforce change requirements to be added and linked to the new/changed metadata components that will later be deployed.

Epics

A large user story that awaits decomposition into smaller stories prior to implementation.  Epics are typically stories that are far off on the development horizon, usually lower priority items. When an epic story works its way up the backlog, it is usually decomposed into smaller stories.

Test Script

A test script is a list of pre-defined steps that a user must follow in order to test the specifications of a system.

Test Runs

A test run is the execution of a test script in a chosen environment by a particular user.

Deployment Flows

A deployment flow is a uni-directional flow for which metadata should be migrated. For example a deployment flow might specify that deployments must pass from a Dev sandbox Staging Sandbox  UAT Sandbox before finally passing to Production.  A deployment flow connection (the flow between two Salesforce Environments) can only have 1 destination Environment, but multiple source environments.  E.g Dev 1 Sandbox and Dev 2 Sandbox may both have “Staging Sandbox” set as their destination Environment. A flow must have 1 source environment and one destination environment. If “one side” of the connection is removed, the flow connection is deleted.

Promotions

As user stories are worked on, Metadata may be added to the user story. Once a user story is ready for deployment, the user story can be flagged as, “Ready for Promotion”.  This means that the User Story may be deployed from one environment to the next as defined by the project’s deployment flow.  A promotion is therefore a deployment of multiple user stories from one or to another, following a designated deployment flow.