Assessor Resource

ICASAD603A
Plan and monitor business analysis activities in an IT environment

Assessment tool

Version 1.0
Issue Date: April 2024


This unit applies to senior business analysts in medium to large organisations who ensure business analysis activities for a particular business analysis effort are properly initiated, planned and managed.

Their job roles combine high-level management, business and technical skills necessary to manage complex analysis efforts within the information and communications technology (ICT) industry, often as part of business critical IT projects.

This unit describes the performance outcomes, skills and knowledge required to establish and manage IT business analysis activities in a medium to large organisation.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)

Prerequisites

Not applicable.


Employability Skills

This unit contains employability skills.




Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to:

plan and monitor business analysis activities, including determining an approach and processes that are appropriate to the circumstances

determine business analysis deliverables, tasks and estimates

determine metrics that will be used for monitoring business analysis work.

Context of and specific resources for assessment

Assessment must ensure access to:

documentation, including appropriate policies, current business analysis practices, tools and legislation

appropriate learning and assessment support when required

modified equipment for people with special needs.

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:

evaluation of a simulated or workplace project in a medium to large enterprise

direct observation of the candidate carrying out business analysis work

verbal or written questioning to assess required knowledge and skills

review of reports and plans prepared for the projects

evaluation of a portfolio of the project work undertaken.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, where appropriate.

Assessment processes and techniques must be culturally appropriate, and suitable to the communication skill level, language, literacy and numeracy capacity of the candidate and the work being performed.

Indigenous people and other people from a non-English speaking background may need additional support.

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.


Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)


Assessment Tasks

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 review organisational and technical business solutions

communication skills to:

conduct focus groups and requirements workshops

conduct research, interviews and liaise with stakeholders

planning and organisational skills to:

develop mitigation strategies

manage an analysis project

manage risk and implement contingency plans

problem-solving and analytical skills to brainstorm requirements and approaches

technical writing skills to develop requirements documents and specifications

technical skills to develop models of systems, processes and solutions.

Required knowledge

business-analysis process, procedures and techniques

project management process, procedures and techniques

risk management strategies

technology and technology solution patterns.

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.

Initiative may include:

feasibility studies

new software development (in-house)

organisational change

outsourced new software development

process improvement

software maintenance or enhancement

software package selection.

Approach defines:

approach will also determine how the planning process is performed

deliverables

life cycle

templates and tasks that should be included.

Appropriate stakeholders may include:

customer, domain SME, end user or supplier

implementation SME

regulator or other stakeholder with legal or governance authority over the solution or the process used to develop it

project manager

tester

sponsor.

Business activities may include:

analysis techniques

frequency of stakeholder interactions

project deliverables

project risk

project timeframe

team roles

other elements of the business-analysis process.

Influence may include:

influence on the project

influence in the organisation

influence needed to ensure success of the particular project

influence with other stakeholders.

Authority may relate to:

approving the deliverables

approving the requirements process that will be used

inspecting and approving the requirements

requesting and approving changes

reviewing and approving the traceability structure

vetoing proposed requirements or solutions (individually or in a group).

Stakeholder needs and constraints to communication may include:

communication approach for the stakeholder

how best to communicate requirements conclusions or packages, including authority level (sign-off authority, veto authority or review only)

physical location or time zone of the stakeholders

time and resource availability constraints

what types of communications will be required, such as status, anomalies, issues and their resolution, risks, meeting results and action items

what types of requirements will be elicited, such as business, stakeholder, solution, or transition; high level versus detailed and how best to elicit them.

Requirements repository may include:

diagrams and models

requirements management tools and applications

whiteboards

word-processing documents

wikis

any other method of recording information that allows requirements to be single-sourced and available to stakeholders for as long as they are needed.

Relevant factors may include:

complexity of the domain

number of views of requirements that will be produced

potential impacts from risk

costs and benefits involved.

Requirements attributes may include:

absolute reference via a unique numeric (preferred) or textual identifier

author of the requirement

cost

complexity

ownership

priority

risks associated with meeting or not meeting the requirements

source of the requirement

stability

status

urgency

resource assignment

revision number

traced-from and traced-to.

Appropriate format may include:

verbal

presentation

writing.

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

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Establish organisational process needs and objectives that apply to the initiative and if necessary define the requirements that the process must meet 
Review existing organisational standards, including standards, guidelines and processes relating to the current initiative 
Tailor approach to the needs of a specific business analysis initiative, according to organisational standards if required 
Engage with the appropriate stakeholders to determine how the work will be completed 
Plan the execution of business activities 
Recognise stakeholders who may be affected by the business need or a new solution 
Assess stakeholder attitudes toward and influence over the initiative 
Decide which stakeholders will have authority over business analysis activities 
Instigate regular reviews to identify new stakeholders or changed positions as clarity of business needs evolve 
Decide the type of project or initiative and the business analysis deliverables 
Determine the scope of work for business analysis activities 
Approve which activities the business analyst will perform and when 
Develop estimates for business analysis work 
Determine how best to receive, distribute, access, update and escalate information from project stakeholders 
Decide how best to communicate with each stakeholder according to stakeholder needs and constraints to communication 
Establish a requirements repository for storing requirements, including those under development, those under review, and approved requirements 
Assess the need and process for requirements traceability based on relevant factors 
Conclude which requirements attributes will be captured 
Determine the process for requirements change management 
Determine which metrics will be used to measure the work performed by the business analyst 
Report performance in an appropriate format based on the needs of the project 
Assess performance measures to determine where problems may be occurring in executing business analysis activities 
Identify preventative or corrective actions as required 

Forms

Assessment Cover Sheet

ICASAD603A - Plan and monitor business analysis activities in an IT environment
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:


Assessment Record Sheet

ICASAD603A - Plan and monitor business analysis activities in an IT environment

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: