Policy 7230A - Department of Administration

5.1.3.3 Provide Implementation Documentation
To ensure that changes are executed in a controlled manner, formal
documentation that outlines roles, responsibilities and required tasks
must be created and vetted by all stakeholders (see section 6.3.1 of
these Non-Mandatory Procedures).
5.1.3.4 Execute Controlled Test of the Change
Where appropriate test and development facilities exist, the change
should be executed in this environment to validate the plan and
identify any gaps:
• Configure the test environment to mimic the to be changed
production environment as much as possible including up and
down stream dependent systems.
• Execute the implementation in the controlled environment,
noting any deficiencies with the set plan.
• Update the plan as required reflecting lessons learned from
the test implementation.
5.1.3.5 Implement the Change per the Plan
Execute the change according to the outlined and vetted plan:
• Implement tasks and communications as outlined in the plan.
• Escalate where implementation errors or plan deficiencies are
noted.
• Upon completion of change update the Systems Inventory
(see section 5.1.1 of these Non-Mandatory Procedures).
5.1.3.6 Perform Post-Implementation Validation and Review
Once the change is finished, all systems impacted must be verified as
appropriately functional and a post-implementation review
completed:
• Validate that the implementation has achieved the required
change and has not yielded any unexpected results.
• Perform a post implementation review to identify any lessons
learned and to debrief staff around any deficiencies in the
plan that had to be addressed during the implementation.
5.2. Systems Protection
No applicable Non-Mandatory Procedures.
15