NTISthis.com

Evidence Guide: ICAPMG602A - Manage IT project initiation

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

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

 

ICAPMG602A - Manage IT project initiation

What evidence can you provide to prove your understanding of each of the following citeria?

Define project

  1. Define business problems and initial scope
  2. Identify key stakeholders and analyse stakeholder needs
  3. Define project constraints
Define business problems and initial scope

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify key stakeholders and analyse stakeholder needs

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define project constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop project business case and feasibility

  1. Identify project objectives and benefits
  2. Identify and select feasible IT solutions
  3. Develop and present the business case or feasibility study
  4. Obtain appropriate sign-off
Identify project objectives and benefits

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and select feasible IT solutions

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop and present the business case or feasibility study

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Obtain appropriate sign-off

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Select project approach

  1. Identify project core technology areas
  2. Identify solution approach requirements
  3. Negotiate project outcomes
Identify project core technology areas

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify solution approach requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Negotiate project outcomes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish the IT project team

  1. Identify and select team members
  2. Establish team member roles and responsibilities
  3. Develop a cohesive technical team
  4. Train and support team members
Identify and select team members

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish team member roles and responsibilities

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop a cohesive technical team

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Train and support team members

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

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:

produce a comprehensive business case and project implementation approach that takes into account core technology limitations and project constraints

establish and work in a cohesive project team.

Context of and specific resources for assessment

Assessment must ensure access to:

appropriate learning and assessment support when required

modified equipment for people with special needs

real or appropriate simulated organisation with a desire to implement an IT project to address an identified problem, opportunity or unfulfilled legislative need.

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.

Note: The preferred assessment method is through a workplace project or through a simulated medium to large enterprise workplace.

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.

Required Skills and Knowledge

Required skills

analytical skills to determine current system deficiencies and new system objectives

communication skills to gather stakeholder needs and liaise with senior enterprise management

literacy skills to present options and recommendations in reports

numeracy skills to develop cost-benefit analyses

planning and organisational skills to:

meet project timeframes and produce required deliverables

mentor and coach team members and resolve conflict

problem-solving skills to negotiate with stakeholders and senior enterprise management to ensure expected project outcomes are achievable

research skills to identify solution alternatives.

Required knowledge

characteristics of leadership and technical teams

consultation and communication techniques, styles and strategies, including interviewing techniques

estimation and cost-analysis techniques

how to establish technical teams and determine stages of team development

objectives and benefits analysis

organisational values, policies and processes

performance management and project team appraisal methods

processes for monitoring team and own performance

project cash flow and budgeting

range of project-management methods and tools and how they apply in a formal project -management methodology

self-awareness

systems analysis and modelling techniques

team roles and delegation within a multi-project methodology context

technology solution models and frameworks.

Range Statement

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.

Business problems may include:

deficiencies in the current business process

deficiencies or identified problems with current systems or IT infrastructure

legislative mandated system changes

opportunities identified as part of the strategic or operational planning processes.

Stakeholder needs may include:

expectations related to agreed project outcomes

project constraints

project objectives based on business problems

solution requirements based on project objectives.

Project constraints may include:

external or internal project dependencies

limitations or standards that the project must adhere to, such as timeframe, budget resources and quality

organisational policies or procedures, including mandated project management and systems development methodologies.

Feasibility may relate to:

economic

operational

technical.

Core technology areas may include:

database-dependent implementations

process-oriented implementations

software implementations:

C

C++

COBOL or other third generation languages

Java

Visual Basic

systems and network architectures:

client or server

legacy mainframe

mid-range

web-oriented solution architectures.