Enabling Processes

Recommendations

Info

Build, Acquire and Implement 150 : ENABLING PROCESSES BAI06 Process Practices, Inputs/Outputs and Activities Management Practice Inputs Outputs BAI06.01 Evaluate, prioritise and authorise From Description Description To change requests. Evaluate all requests for change to determine the impact on business processes and IT services, and to assess BAI03.05 Integrated and configured solution components Impact assessments Internal whether change will adversely affect the operational DSS02.03 Approved service requests Approved requests BAI07.01 environment and introduce unacceptable risk. Ensure for change that changes are logged, prioritised, categorised, assessed, authorised, planned and scheduled. DSS03.03 Proposed solutions to known errors DSS03.05 Identified sustainable solutions Change plan and schedule BAI07.01 DSS04.08 Approved changes to the plans DSS06.01 Root cause analyses and recommendations Activities 1. Use formal change requests to enable business process owners and IT to request changes to business process, infrastructure, systems or applications. Make sure that all such changes arise only through the change request management process. �� application software) and relate affected configuration items. 3. Prioritise all requested changes based on the business and technical requirements, resources required, and the legal, regulatory and contractual reasons for the requested change. 4. Plan and evaluate all requests in a structured fashion. Include an impact analysis on business process, infrastructure, systems and applications, business continuity plans (BCPs) and service providers to ensure that all affected components have been identified. Assess the likelihood of adversely affecting the operational environment and the risk of implementing the change. Consider security, legal, contractual and compliance implications of the requested change. Consider also inter-dependencies amongst changes. Involve business process owners in the assessment process, as appropriate. 5. Formally approve each change by business process owners, service managers and IT technical stakeholders, as appropriate. Changes that are low-risk and relatively frequent should be pre-approved as standard changes. 6. Plan and schedule all approved changes. 7. Consider the impact of contracted services providers (e.g., of outsourced business processing, infrastructure, application development and shared services) on the change management process, including integration of organisational change management processes with change management processes of service providers and the impact on contractual terms and SLAs. Management Practice Inputs Outputs BAI06.02 Manage emergency changes. From Description Description To Carefully manage emergency changes to minimise further incidents and make sure the change is controlled �� are appropriately assessed and authorised after the change. Post-implementation review of emergency changes Internal Activities 1. Ensure that a documented procedure exists to declare, assess, give preliminary approval, authorise after the change and record an emergency change. �� 3. Monitor all emergency changes, and conduct post-implementation reviews involving all concerned parties. The review should consider and initiate corrective actions based on root causes such as problems with business process, application system development and maintenance, development and test environments, documentation and manuals, and data integrity. 4. Define what constitutes an emergency change. Personal Copy of: Mr. Dong Hong Wang
BAI06 Process Practices, Inputs/Outputs and Activities (cont.) CHAPTER 5 COBIT 5 PROCESS REFERENCE GUIDE CONTENTS Management Practice Inputs Outputs BAI06.03 Track and report change status. Maintain a tracking and reporting system to document �� and in-process changes, and complete changes. Make certain that approved changes are implemented as planned. From Description Description To BAI03.09 Record of all approved and applied change requests Change request status reports BAI01.06 BAI10.03 Activities �� 2. Implement change status reports with performance metrics to enable management review and monitoring of both the detailed status of changes and the overall state (e.g., aged analysis of change requests). Ensure that status reports form an audit trail so changes can subsequently be tracked from inception to eventual disposition. 3. Monitor open changes to ensure that all approved changes are closed in a timely fashion, depending on priority. 4. Maintain a tracking and reporting system for all change requests. Management Practice Inputs Outputs BAI06.04 Close and document the changes. From Description Description To Whenever changes are implemented, update Change documentation Internal accordingly the solution and user documentation and the procedures affected by the change. Activities 1. Include changes to documentation (e.g., business and IT operational procedures, business continuity and disaster recovery documentation, configuration information, application documentation, help screens, and training materials) within the change management procedure as an integral part of the change. 2. Define an appropriate retention period for change documentation and pre- and post-change system and user documentation. �� BAI06 Related Guidance Related Standard Detailed Reference �� 9.2 Change management �� 13. Change Management Personal Copy of: Mr. Dong Hong Wang 151 Build, Acquire and Implement
Page 1 and 2:
Enabling Processes Personal Copy of
Page 3 and 4:
ACKNOWLEDGEMENTS ISACA wishes to re
Page 5 and 6:
ACKNOWLEDGEMENTS (CONT.) ACKNOWLEDG
Page 7 and 8:
TABLE OF CONTENTS TABLE OF CONTENTS
Page 9 and 10:
LIST OF FIGURES LIST OF FIGURES Fig
Page 11 and 12:
CHAPTER 1 INTRODUCTION CHAPTER 1 IN
Page 13 and 14:
CHAPTER 2. THE GOALS CASCADE AND ME
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
CHAPTER 3 THE COBIT 5 PROCESS MODEL
Page 21 and 22:
Enabler Performance Management CHAP
Page 23 and 24:
CHAPTER 4 THE COBIT 5 PROCESS REFER
Page 25 and 26:
CHAPTER 5 COBIT 5 PROCESS REFERENCE
Page 27 and 28:
Generic Guidance for Processes CHAP
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
EDM02 Process Practices, Inputs/Out
Page 39 and 40:
Page 41 and 42:
EDM03 Process Practices, Inputs/Out
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
APO01 Process Practices, Inputs/Out
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
APO04 Manage Innovation (cont.) CHA
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100: CHAPTER 5 COBIT 5 PROCESS REFERENCE
Page 103 and 104: APO11 Process Practices, Inputs/Out
Page 113 and 114: APO13 Manage Security Process Descr
Page 123 and 124: BAI01 Process Practices, Inputs/Out
Page 149: CHAPTER 5 COBIT 5 PROCESS REFERENCE
Page 179 and 180: DSS02 Process Practices, Inputs/Out
Page 195 and 196: DSS05 Process Practices, Inputs/Out
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
MEA01 Process Practices, Inputs/Out
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
APPENDIX A MAPPING BETWEEN COBIT 5
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
APPENDIX B DETAILED MAPPING ENTERPR
Page 227 and 228:
APPENDIX C DETAILED MAPPING IT-RELA
Page 229 and 230:
Deliver, Service and Support Monito
show all

Enabling Processes

Create successful ePaper yourself

Delete template?

Save as template?