Formats and tools
- Unit Description
- Reconstruct the unit from the xml and display it as an HTML page.
- Assessment Tool
- an assessor resource that builds a framework for writing an assessment tool
- Assessment Template
- generate a spreadsheet for marking this unit in a classroom environment. Put student names in the top row and check them off as they demonstrate competenece for each of the unit's elements and performance criteria.
- Assessment Matrix
- a slightly different format than the assessment template. A spreadsheet with unit names, elements and performance criteria in separate columns. Put assessment names in column headings to track which performance criteria each one covers. Good for ensuring that you've covered every one of the performance criteria with your assessment instrument (all assessement tools together).
- Wiki Markup
- mark up the unit in a wiki markup codes, ready to copy and paste into a wiki page. The output will work in most wikis but is designed to work particularly well as a Wikiversity learning project.
- Evidence Guide
- create an evidence guide for workplace assessment and RPL applicants
- Competency Mapping Template
- Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners. A template for developing assessments for a unit, which will help you to create valid, fair and reliable assessments for the unit, ready to give to trainers and students
- Observation Checklist
- create an observation checklist for workplace assessment and RPL applicants. This is similar to the evidence guide above, but a little shorter and friendlier on your printer. You will also need to create a seperate Assessor Marking Guide for guidelines on gathering evidence and a list of key points for each activity observed using the unit's range statement, required skills and evidence required (see the unit's html page for details)
- Self Assessment Survey
- A form for students to assess thier current skill levels against each of the unit's performance criteria. Cut and paste into a web document or print and distribute in hard copy.
- Moodle Outcomes
- Create a csv file of the unit's performance criteria to import into a moodle course as outcomes, ready to associate with each of your assignments. Here's a quick 'how to' for importing these into moodle 2.x
- Registered Training Organisations
- Trying to find someone to train or assess you? This link lists all the RTOs that are currently registered to deliver ICASAS511A, 'Prioritise IT change requests'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Prioritise IT change requests' on fishpond.com.au. This online store has a huge range of books, pretty reasonable prices, free delivery in Australia *and* they give a small commission to ntisthis.com for every purchase, so go nuts :)
Elements and Performance Criteria
1. Classify and monitor change requests | 1.1 Receive and record change requests from the client or other sources 1.2 Classify and prioritise change requests according to business guidelines and service level agreements (SLAs) |
2. Determine priority settings | 2.1 Identify risks to business continuity and prioritise changes that reduce risks for implementation 2.2 Evaluate the costs and benefits of implementing changes against the current system 2.3 Examine the benefits and costs of how and when a change is made, including risks to business continuity 2.4 Schedule change analysis according to business down periods and periods of business-critical activities |
3. Develop change analysis work plan to develop and implement changes | 3.1 Analyse similar change requests that might be developed and implemented simultaneously 3.2 Determine impact to the system and organisation of methodology and timing of change 3.3 Notify the reason for the change to key stakeholders 3.4 Determine the resources necessary to carry out the change development, taking into account time and cost constraints 3.5 Develop a change plan based on change analysis 3.6 Review the change plan documentation to ensure it is completed according to system documentation standards 3.7 Forward the change plan to the appropriate person for consideration and decision |
4. Confirm change plan is complete and satisfies client | 4.1 Conduct feedback session with client groups to ensure change requirements are satisfactory 4.2 Complete follow-up work and make recommendations for changes in procedures or documentation |