The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Prepare for system implementation
|
|
Review relevant project and system development documentation Completed |
Evidence:
|
Consider organisational culture as part of an implementation risk analysis Completed |
Evidence:
|
Identify implementation options and constraints and select a preferred approach in consultation with stakeholders Completed |
Evidence:
|
Develop a detailed implementation plan and a high-level training plan and obtain sign-off Completed |
Evidence:
|
Ensure the creation of system-user documentation and obtain sign-off Completed |
Evidence:
|
Ensure the preparation of operations documentation and obtain sign-off Completed |
Evidence:
|
Manage organisational change
|
|
Communicate relevant information about the pending change through appropriate channels Completed |
Evidence:
|
Establish necessary support structures Completed |
Evidence:
|
Coordinate release management
|
|
Establish and confirm release management roles and responsibilities, including those of the release manager Completed |
Evidence:
|
Determine release configuration items, including any production system software, hardware and capacity changes required and compile a request for change Completed |
Evidence:
|
Ensure the creation of required test environment Completed |
Evidence:
|
Establish ongoing monitoring procedure to cover the post-release warranty period Completed |
Evidence:
|
Undertake data conversion activities if needed Completed |
Evidence:
|
Manage acceptance testing
|
|
Review results of system test and ensure acceptance test entry criteria are met Completed |
Evidence:
|
Ensure test environment and IT configuration management processes meet solution requirements and organisational standards Completed |
Evidence:
|
Ensure acceptance testing is performed and results are collated Completed |
Evidence:
|
Ensure test results meet acceptance test exit criteria and obtain sign-off Completed |
Evidence:
|
Manage user training
|
|
Undertake training needs analysis Completed |
Evidence:
|
Review high-level training plan and schedule and add detailed activities as necessary Completed |
Evidence:
|
Ensure training materials are prepared and user training is conducted Completed |
Evidence:
|
Release system to production
|
|
Develop an hour by hour action plan or checklist for release activities Completed |
Evidence:
|
Create a rollback strategy and plan to guide rollback of changes if required Completed |
Evidence:
|
Prepare appropriate communication to inform users of possible interruption to service due to the release Completed |
Evidence:
|
Manage the installation of the new release into production and ensure performance of operational verification tests and rollback changes if necessary Completed |
Evidence:
|
Review and update service level agreements (SLAs) and disaster recovery plan Completed |
Evidence:
|