Major, significant, and minor changes are all considered normal changes and require case-by-case approval for implementation. Standard changes have the smallest scope and lowest impact of any change and are therefore pre-approved as a matter of policy. They meet the following essential criteria: Routine with low risk. Frequently performed. Easy to implement. Simple to back out. Well documented. Do not require case-by-case review. Pre-budgeted. Involved a material change to a CI. As noted above, provisioning falls under the category of a standard change. A comparison of the steps in processing normal and standard changes is pictured in Table 2. Table 2. Comparison of Normal and Standard Change Processes Normal Changes Standard Changes Configurations are Baselining is not baselined for normal needed for standard changes changes Normal and standard changes require formal requesting, logging, and tracking. Normal changes are Classification is classified on a defined for standard basis. changes Normal changes are Standard changes approved on a are pre-approved. Normal changes Standard changes require individual are effectively development and and testing. tested. Normal and standard changes are released according to established release policies and procedures. Normal and standard changes are validated and reviewed according to established validation and post-implementation review policies and procedures.
Major, significant, and minor changes are all considered normal changes and require case-by-case approval for implementation. Standard changes have the smallest scope and lowest impact of any change and are therefore pre-approved as a matter of policy. They meet the following essential criteria: Routine with low risk. Frequently performed. Easy to implement. Simple to back out. Well documented. Do not require case-by-case review. Pre-budgeted. Involved a material change to a CI. As noted above, provisioning falls under the category of a standard change. A comparison of the steps in processing normal and standard changes is pictured in Table 2. Table 2. Comparison of Normal and Standard Change Processes Normal Changes Standard Changes Configurations are baselined for normal changes Baselining is not needed for standard changes Normal and standard changes require formal requesting, logging, and tracking. Normal changes are classified on a basis. Classification is for standard changes Normal changes are approved on a Standard changes are pre-approved. Normal changes require individual development and testing. Standard changes are effectively and tested. Normal and standard changes are released according to established release policies and procedures. Normal and standard changes are validated and reviewed according to established validation and post-implementation review policies and procedures. defined
Using%20Standard%20Changes%20to%20Improve%20Provisioning.docx