Unit of competency details

Release 

Comments 

Release 1

This Unit first released with ICA11 Information and Communications Technology Training Package version 1.0

Element 

Performance Criteria 

Elements describe the essential outcomes of a unit of competency.

Performance criteria describe the performance needed to demonstrate achievement of the element. Where bold italicised text is used, further information is detailed in the required skills and knowledge section and the range statement. Assessment of performance is to be consistent with the evidence guide.

1. Manage project definition activities

1.1 Confirm organisational project governance policy and processes 

1.2 Confirm business problem or opportunity as well as project objectives

1.3 Develop project charter, including preliminary statement of project scope and obtain sign-off

1.4 Conduct a feasibility  study and prepare a business case as necessary

2. Undertake project planning

2.1 Plan information-gathering activities  to determine project requirements, constraints  and risks

2.2 Identify project partitioning on the basis of intended system development life cycle and risk

2.3 Prepare project work breakdown, schedule and budget

2.4 Compile project-management plan documents  as necessary to communicate the intended management strategy for the project and obtain sign-off

3. Establish the IT project team

3.1 Identify and select team members, including roles and responsibilities, based on project solution requirements

3.2 Determine training and support needs of team members

3.3 Establish project team values and agreed behavioural standards with team members

4. Manage project execution activities

4.1 Monitor delivery and acceptance of assigned project team work activities and manage individuals as necessary

4.2 Monitor and control the quality of project deliverables

4.3 Monitor and control project scope changes, risks and issues

4.4 Manage system testing and hand-over activities 

5. Coordinate project closure

5.1 Prepare IT support plans and maintenance or support documents 

5.2 Obtain final project sign-off

5.3 Conduct post-project review and document lessons learned

5.4 Review and update disaster recovery plan

5.5 Close project

Overview of assessment 

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

Evidence of the ability to:

• define, plan, execute and close a reasonably complex project to meet project requirements.

Context of and specific resources for assessment 

Assessment must ensure access to:

• real or appropriate simulated organisation with a desire to implement an IT project to address an identified problem, opportunity or unfulfilled legislative need
• 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:

• direct observation of the candidate carrying out project work
• verbal or written questioning to assess required knowledge and skills
• review of reports and implementation plans
• review 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.

Project governance policy and processes  may include:

• established roles and responsibilities for key project stakeholders
• mandated positions to be filled on various project-governance boards or committees, such as the project steering committee or quality-review board
• mandated project-management standard or development methodology for the organisation
• project portfolio prioritisation process or criteria
• project selection process or criteria.

Feasibility  in relation to IT solutions may refer to:

• economic
• operational
• technical.

Information-gathering activities  may include:

• interviews
• research related to existing documents, and similar or previous projects
• surveys
• workshops.

Constraints  may include:

• external or internal project dependencies
• limitations or standards that the project must adhere to:

• resources budget
• quality
• timeframe.

Project-management plan documents  may include:

• change control
• communications
• human resource
• procurement
• quality
• risk management
• training.

Hand-over activities  may include:

• communications to users and other stakeholders
• production system environment verification tests
• user training and documentation.

Maintenance or support documents  may include:

• additional tasks or changed responsibilities within the support team for ongoing support of the new system
• new policies and procedures and how these differ to current practices
• technical documents relating to the system:

• specifications
• system dependencies
• technical requirements.