Copado Change Management (CCM)

Updated 7 days ago ​by Estela García

Copado Change Management  (CCM)  is an extension on top of the existing Copado feature set (CEE) and is designed to help customers to better manage the release management process of requirements from one or multiple sandboxes to production. It allows business users and developers to interact with User Stories and manage Projects following agile methodologies (Kanban, Scrum, Scrumban, etc.).

This license is restricted to User Story functionality where users assigned to this license will contribute to the deployment flow, and these users are allowed to perform deployments to all types of sandboxes. They simply interact with the User Stories, add metadata to their User Stories and in doing so contribute to the deployment pipeline.

License details: Copado Change Management is a user dependent license and includes all Copado Agile Delivery functionalities. It can be used with or without version control (Git), yet it requires Copado Branch Management Licenses to identify which orgs are connected and how between each other.

Roles / Users: Typical users assigned to this license type are Developers, Project Managers,  Business Users, Release Managers, Scrum Masters, Product Owners or Admins.

Features:

  • Keep your business context and associate Metadata and Git Metadata changes on User Stories.

  • Add commits to User Stories: Files within those commits will automatically be deployed when promoting the User Stories.

  • Add Manual, Data, Custom Setting, Deletion, Scrip or Callout Steps to a User Story to make sure also non-metadata steps are also completed before or after the deployment of a feature.

  • Promote: Select set of User Stories that are approved for promotion, and Copado will create 1 single deployment that combines all the changes automatically.

  • Back Promote User Stories to lower environments.

  • Validate User Stories.

  • Perform static code analysis per User Stories.

  • Run apex tests for User Stories

  • Run Compliance tests for User Stories

  • Set up Quality Gates with Salesforce configuration to provide release managers intel if a User Story is completed, approved, tested and ready to be released.

  • Increase collaboration between project team members, with e.g. business & developer tests aligned on a User Story context.

  • Overlap Awareness: Copado will detect potential conflicts when same metadata items are selected against multiple user stories.

  • Quick check for potential conflicts of specific metadata with other User Stories (only with git)

  • Integration with Rally / Agile Accelerator / Jira / VersionOne: import user stories from external providers.

  • Use Sprint wall and Work Manager dashboards with Backlog, Backburner, Sprints and other configurable panels.



How did we do?