Manejo gerencial de cambios

Table of Contents

1. Change Management Overview 3

2. Relationship Diagram 5

3. Change Management Operating Framework 6

4. Change Management Process Scope 10

5. Change Initiation 12

6. Business/Functional/Technology Assessment 17

7. Agilent Change Control Team (ACCT) 22

8. Release Management Policy & Guidelines 25

9. Schedule and Coordinate 30

10. Product Lifecycle(PLC) 33

11. Project Guidelines 45

12. Documentation Repository 46

13. Emergency Change Request 48

14. Communication Process 53

15. CM Escalations 54

16. Repeatable Change Requests Guidelines 56

17. Freeze Exception Process 57

18. Managing Risks 58

19. PLC Child Creation Guidelines 59

Appendix 1: Configuration Tools 60

Appendix 2: Document Repositories 61

Appendix3: Change Management Events & Schedules 63

Appendix 4: Change Review Meeting – TIPS 64

Appendix 5: Interfaces Linkages 65

Appendix 6: Effectiveness Reviews 69

Appendix 7: Roles & Responsibilities 71

Appendix 8: RASIC Chart 77

Appendix 9: Separation of duties (SOD) 80

Appendix 10: Priority Definitions 80

Appendix 11: Resources/Tools 82

Appendix 12: Terms & Definitions 83Appendix 13: Best Practices 86
1. Change Management Overview

Purpose:

The Enterprise Change management process provides a way to manage and control changes to the current business and technology environment. Change Management monitors changes to the ‘live’ environment from initiation through to implementation.

Management of Change Requests: “Management” of change requests means:
❑Evaluating the change for appropriateness, scope, ownership
❑ Authorizing the request
❑ Setting priorities for requests
❑ Scheduling resources needed to effect the change
❑ Assessing risks associated with requested changes
❑ Managing of Releases into the production environment

Control of Change Requests: The scope of controlling change includes
❑ Scheduling the appropriateresources to affect the change
❑ Ensuring that the changes will not have an adverse impact on the production environment
❑ Monitoring and tracking significant steps in the development and deployment of changes
❑ Ensuring the synchronization of production, development and test environments

Audience:

This document is used by Agilent teams involved in the support and development of changes to thecurrent production environment from both a business and technical perspective. This document should be used as a framework to setup a local change team and integrating into the enterprise change review team.

Compliance Expectation:

❑ Enterprise Change Management is a required process for Agilent.
❑ Required is defined as: Compliance is mandatory and subject to audit for allAgilent process users.
❑ All sub process, listed below, are required:
o Change Request Submittal
o Initial Assessment
o Approval/Prioritization
o Release Management
o Software Distribution
o Configuration Management
o Monitoring and Reporting
o
o Communication
❑ These are the deliverables of the change:o CR processing
o Impact assessment
o Change approval
o Schedule and coordinate change (release management)
o Checkpoints throughout the development lifecycle to ensure overall supportability and auditibility.
❑ The Process Owner for Change Management will perform a self-assessment audit in conjunction with the Solution Center, Service Lineand/or Business Change Managers/Coordinators on a quarterly basis to ensure key controls are in place and compliant.

Process Value:
❑ Increases stability of environment -- in the face of evolving customer requirements and technological upheavals, control and management of change in this process minimize the risk of unexpected results from introduction of a change to the production environment....