Manage BAU and project changes and revisions: Applications, Environments, and Processes

Description	Manage BAU and project changes and revisions: Applications, Environments, and Processes
Version as of	8.6
Application	Pega Customer Decision Hub
Capability/Industry Area	Change and Revision Management

Relationships between the environments

Typical deployment sequence

Business Operations (Marketing, Personalization, Banking) formally deploys once per week and may deploy several times during the week
- Business users develop and test in a Business development environment, and complete unit and simulation testing
  - All development done in Artifacts rulesets in Business Operating Environment
  - Package and store in RAP repository
  - RAP deployed to QA / UAT for testing
  - If testing passes, then RAP deployed to production
Project Dev formally deploys at end of Sprint
- IT developers develop and unit test in IT development environment
  - All development done in other than Artifacts rulesets
  - Package and store in RAP repository
  - RAP deployed to QA / UAT for testing
  - If testing passes, then RAP deployed to production
On a weekly basis (or as needed), Business Operations and Project Development teams meet and agree on updates of Artifacts RAPS to IT Dev and for non-Artifacts RAPS to Business Dev

BAU and Software Development Lifecycles

Application Environments