Please enable JavaScript.

Coggle requires JavaScript to display documents.

9 by 4 (RELEASE MANAGEMENT (Planning a release involves: (• Agree to the…

- - - - typically consist of several problem fixes and enhancements to the service :shallow_pan_of_food:
  - - - Suitable contingency plans may also be developed, if it is not completely restorable. :arrow_backward:
  - - - (e.g., the phasing over time and by geographical location, business unit and customers)
  - - - contain a SIGNIFICANT change or addition of NEW FUNCTIONALITY
        
        supersedes all
        preceding minor upgrades.
        
        Grouping together several changes facilitates more comprehensive testing and planned user training.
        
        predefined timetable for
        implementing major releases throughout the year
        
        Smaller organizations may have only one release during the year or numerous releases if the organization is quickly growing.
    - - normally containing SMALL ENHANCEMENTS AND FIXES A
        
        supersedes all preceding emergency
        fixes
        
        generally used to fix small reliability or functionality problems that cannot wait until the next major release
        
        release process should be followed for the preparation and
        implementation of minor releases
        
        less time because the development, testing and implementation activities do not require as much time as major releases do.
    - - fixes that require implementation as quickly as possible to prevent significant user downtime to business-critical functions
        
        Depending upon the required urgency of the release, limited testing and release management activities are executed prior to implementation
        
        changes should be avoided whenever
        possible because they increase the risk of errors being introduced
    - - contains only those items that have undergone changes since the last release.
- - - - simple steps, such as performing backups :file_folder:and testing patches on non-critical systems prior to installations
- - - - from the test environment,
        
        test environment consists of development and
        maintenance occur, by quality assurance (QA) environment
        thorough testing occurs by production environment
  - - - methods are aimed at minimizing the adverse impact of any probable incidents triggered by change that may arise :red_flag:
        
        achieved by formalizing and documenting the process of change request, authorization, testing, implementation and communication to the users.
  - - - rollback plan is developed to back out the changes, if necessary :left_right_arrow:
- - - - network, systems and applications :signal_strength::computer: :iphone:
    - - • Execute and monitor scheduled jobs. :alarm_clock:
      - • Facilitate timely backup. # :file_folder:
      - • Monitor unauthorized access and use of sensitive data. :silhouette:
      - • Monitor and review the extent of adherence to IS operations procedures as established by IS and business management. :mag_right: :eyes: :memo:
      - • Participate in tests of disaster recovery plans (DRPs). :black_square_for_stop:
      - • Monitor the performance, capacity, availability and failure of information resources. :label: :bookmark_tabs:
      - • Facilitate troubleshooting and incident handling. :recycle: