Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.
Required skills
analytical skills to identify implementation risks, risk mitigations and contingency plans
communication skills to:
communicate plans and status to stakeholders
coordinate training, run implementation workshops and presentations
negotiate implementation priorities and manage stakeholder expectations
literacy skills to develop documentation, recommendations and reports
planning skills to develop implementation, testing and training plans.
Required knowledge
methods and techniques of configuration management
organisational policies and standards relating to IT configuration management, e.g. an IT infrastructure library (ITIL)
business analysis, processes and techniques
project management and systems development, as well as potential risks associated with implementation activities
structure and implications of disaster recovery plans and SLAs.
The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.
Project and system development documentation may include: | planned project schedule tasks and milestones project and organisational assumptions and constraints project-management plan documents, such as quality plan, acceptance plan, implementation plan, and training plan system specification or vendor product specifications in the case of a procured solution. |
Implementation plan may include: | cut-over activities data conversion. |
Relevant information may include: | background and business need and strategy for the change new policies and procedures and how these differ to current practices planned implementation schedule, including milestones, such as: data conversion new system cut-over recognition of staff who contributed to the project in any special way roles and responsibilities within the implementation, and for ongoing operation of the new system. |
Appropriate channels may include: | help desk organisation intranet regular departmental team meetings, including informal discussion and feedback specific training courses staff newsletters or wall posters workshops and staff briefing sessions. |
Support structures may include: | checklists or frequently asked question (FAQ) guides help desk identified change leaders. |
Release manager may include: | project manager specialist release manager systems administration manager systems development manager other nominated technical IT manager given the specific responsibility of managing the release of system changes into the IT production environment. |
Configuration items refer to: | exact list of the items, including version designations that make up the configuration of the system changes at the time of the release. |
Configuration management processes refer to: | processes and procedures developed to control system changes and maintain the integrity of IT systems. |
Training needs analysis refers to: | activity undertaken to identify the extent of training needed to ensure staff can effectively operate in the new or changed system environment. |
Rollback strategy: | refers to strategy or plan to facilitate the act of reverting the production system to its earlier stable state, in response to an unsuccessful release, such as a new system failing operational verification tests usually includes creation of a backup of the production system or relevant system components. |
Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.
Observation Checklist