Introduction to Concurrent Change Management
Concurrent Change Management (CCM) in Pega Customer Decision Hub™ enhances traditional change management. CCM enables multiple teams to work simultaneously on different initiatives. This approach improves speed and coordination while maintaining uninterrupted operations.
Concurrent Change Management
Transcript
This video provides an overview of Concurrent Change Management (CCM).
Concurrent Change Management (CCM) is a feature of Pega Customer Decision Hub. CCM is a significant enhancement over traditional change management systems, enabling multiple teams to work on different initiatives simultaneously, without disrupting ongoing work.
By enabling parallel progress, CCM helps organizations operate at the speed of business demands while maintaining control and coordination.
CCM is powered by two core features: Release Vehicles and Just-in-Time Rule Generation, or ‘JIT Gen.’
The key innovation lies in release vehicles, which group related changes for coordinated testing and deployment. This approach augments the conventional revision-based system and provides greater flexibility and control.
CCM introduces a fundamental shift in how rules are generated. With Just-in-Time Rule Generation, rules are created only when needed for deployment or testing, not during the initial change process.
This delayed generation allows flexible reordering of changes and prevents merge conflicts.
CCM involves two key roles:
- The Release Manager, who creates and manages release vehicles, plans release cycles, and ensures timely progression of changes.
- The Test Manager, who validates changes in dedicated environments and approves or rejects release vehicles based on business requirements.
You have reached the end of this video. What have you learned?
- Concurrent Change Management (CCM) enables multiple teams to work on different initiatives simultaneously, without disrupting each other.
- CCM is powered by release vehicles and Just-in-Time Rule Generation.
Traditional Versus Concurrent Change Management
The following table describes the key distinctions between CCM and traditional change management:
|
Aspect |
Standard Revision |
Concurrent Change Management |
|
Work Model |
Sequential: Changes wait for current release to finish. |
Parallel: Multiple teams work simultaneously on different releases. |
|
Release Flexibility |
Rigid: All changes are bound to one revision schedule. |
Flexible: Each release vehicle follows its own schedule. |
|
Rule Generation |
Immediate: upon completion of a change request. |
Just-in-Time: Generated together for a release vehicle. |
|
Branch Structure |
Single: Single revision management for a revision. |
Multiple: Independent branches for each release vehicle. |
|
Testing |
Limited: Limited to Business Operations environment. |
Extensive: Extensive testing in UAT environment. |
|
Deployment |
Complete: Entire changes in a revision deploy together. |
Selective: Each release vehicle can deploy independently. |
|
Change Request Mobility |
Static: Change requests cannot move between revisions. |
Active: Change requests can be moved between release vehicles. |
|
Reopening Change requests |
Not supported: Not supported once completed. |
Supported: Supported if not yet deployed. |
This Topic is available in the following Module:
¿Quiere ayudarnos a mejorar este contenido?