QUICK START GUIDE
- There are two is one main Change Management process flows used when flow used when creating Change Requests (CRs) in lower and upper environments: Parent/Child CRs and Normal CRs.
- Use CRs for application deployments to a Production environment and for infrastructure and environmental changes within the HCQIS environment.
- The majority of these infrastructure requests are initiated by the Infrastructure contractor.
Types of Change Requests:
Parent CRs are the PI level changes encompassing the scope of each increment as defined by the release cycle. That parent represents all work planned within a PI. There is one Parent Change associated with each PI.
Child CR changes represent the specific deployments within the iterations that make up the PI. There are many Child Changes associated with a single Parent Change.
Parent CR: - Program Increment 13 (objectives for PI attached)
Child CR: Iteration 13.2 1. XXX deployment
Normal CRs follow the same process as Parent CRs. They are intended more for organizations that do not follow a Lean-Agile software development process.
Change the XXX domain name from hcqis.org to cms.gov
Emergency CRs (ECR)
ECRs are used to resolve outages or for emergency deployments and require the same level of approvals as CRs.
Delete Duplicate Facilities
Other types of CRs:
For any other requests that are intended to make changes to any environment, the organization that is requesting the change will typically open the CR.
Patching, upgrades, configuration changes (performance tuning, memory, account management, space increase, time out value, connections increase, etc..), restarts, security remediation, password updates, monitoring setup, decommissioning requests and break fixes.