Examples of Documentation Impacted by Change Management
Summary
PDF p.391Various types of documentation are impacted by change management, including change requests, policies and procedures, system or process documentation, configuration management documentation, training materials, and incident response and recovery plans.
In plain words
Supplementary — not from your PDFChanges ripple through documentation: change requests (record details and approvals), policies and procedures (align with new processes), system or process documentation (architecture diagrams, flows, SOPs, manuals), configuration management records, training materials, and incident response and recovery plans.
Detailed explanation
PDF p.391-
Change Requests
- Purpose: Reflect details and status of changes.
- Updates: Include modifications or approvals during the change process.
-
Policies and Procedures
- Purpose: Ensure alignment with new processes, guidelines, or controls.
- Updates: Review and update as needed.
-
System or Process Documentation
- Purpose: Reflect changes to systems, applications, or processes.
- Updates: Update system architecture, diagrams, process flows, SOPs, or user manuals.
-
Configuration Management Documentation
- Purpose: Track changes to configuration items.
- Updates: Maintain accurate records of configurations.
-
Training Materials
- Purpose: Ensure employees are trained on changes.
- Updates: Review and update presentations, manuals, or learning modules.
-
Incident Response and Recovery Plans
- Purpose: Account for revised configurations, new dependencies, or recovery procedures.
- Updates: Ensure plans reflect changes.
Important terms
taken from the text above- Updates
- Include modifications or approvals during the change process.
Examples & real-world scenarios
Supplementary — not from your PDF- Updating an architecture diagram after a change.
- Revising an IR plan for new dependencies.
- Updating training materials for a new process.
Scenario
A change adds a new server, but the incident response plan still lists the old setup. Updating IR and recovery plans as part of the change keeps them accurate for the next incident.
Common mistakes
Supplementary — not from your PDF- Updating the system but not its documentation.
- Forgetting to revise incident response plans after changes.
Practical skills
Supplementary — not from your PDF- List documents that a change should update.
What I should remember
Key Points PDF p.391- Change Requests: Reflect change details and status.
- Policies and Procedures: Align with new processes.
- System Documentation: Update for changes.
- Configuration Management: Track configuration changes.
- Training Materials: Update for employee training.
- Incident Response Plans: Reflect revised configurations.