Section 12.112 Documenting Changes

Question 1

Documenting Changes

Answer 1

Documenting changes provides a clear history of the what, when, and why for
accountability and future reference

Question 2

Version Control

Answer 2

■ Tracks and manages changes in documents, software, and other files

■ Allows multiple users to collaborate and revert to previous versions when
needed

■ Ensures changes do not create chaos and helps track project evolution

■ Preserves past iterations and ensures continuity and stability

Question 3

Proper Documentation

Answer 3

All accompanying documentation should be updated when implementing a change

■ Updates should reflect the implementation of the change, from minor configurations to major network overhauls

Question 4

Continuous Improvement

Answer 4

■ After implementing a change, evaluate the process and its success

■ Identify issues and revise policies and procedures to prevent recurrence

■ Emphasises iterative process improvement to ensure smoother future changes

■ Learn from past mistakes for better change management practices

Question 5

Key elements of proper documentation

Answer 5

● Updating diagrams to provide a visual representation of system architecture

● Revising policies and procedures to address issues or improvements

● Updating change requests and trouble tickets to reflect successful completion

Proper documentation is critical for clarity and accountability

Question 6

Importance of Records

Answer 6

■ Change requests and trouble tickets help create a clear timeline of change
actions

■ Inform stakeholders and provide a record of change history for future reference

■ Records are essential for communication and accountability in change management