diff_months: 13

Task 2 ICT Project Plan 2 Product Lifecycle Management System

Download Solution Now
Added on: 2024-11-21 06:00:17
Order Code: SA Student Parvinder Management Assignment(10_23_37964_857)
Question Task Id: 497620

Task 2 ICT Project Plan 2 Product Lifecycle Management System

Instructions to Learners:

This summative assessment can be completed in class or at any other convenient location.

Students are required to complete this task using digital tools and ensure to submit in an acceptable format, e.g. .docx, .pdf, .pptx, or as advised by your assessor.

Please use the following formatting guidelines to complete this assessment task:

Font Size: 12; Line Spacing: Double; Font Style: Times New Roman

Assessment activities can be completed either in real workplace environment or in a simulated environment such as your classroom. In both cases, appropriate evidence of the assessment activities must be provided.

Instruction to Assessors:

You must assess students assessment according to the provided Marking Criteria.

You must complete and record any evidence related to assessment activities including role-plays and presentations using appropriate forms which must be attached with student assessment submission.

You must provide students with detailed feedback within 10 working days from submission.Skills Assessment (Practical Tasks)

ASSESSOR NOTE

These instructions must be followed when assessing the student in this unit. The checklist on the following page is to be completed for each student. Please refer to separate mapping document for specific details relating to alignment of this task to the unit requirements.

This competency is to be assessed using standard and authorised work practices, safety requirements and environmental constraints.

Assessment of essential underpinning knowledge will usually be conducted in an off-site context.

Assessment is to comply with relevant regulatory or Australian standards' requirements.

Resource implications for assessment include:

an induction procedure and requirement

realistic tasks or simulated tasks covering the mandatory task requirements

relevant specifications and work instructions

tools and equipment appropriate to applying safe work practices

support materials appropriate to activity

workplace instructions relating to safe work practices and addressing hazards and emergencies

material safety data sheets

research resources, including industry related systems information.

Reasonable adjustments for people with disabilities must be made to assessment processes where required. This could include access to modified equipment and other physical resources, and the provision of appropriate assessment support.

What happens if your result is Not Yet Competent for one or more assessment tasks?

The assessment process is designed to answer the question has the participant satisfactorily demonstrated competence yet? If the answer is Not yet, then we work with you to see how we can get there.

In the case that one or more of your assessments has been marked NYC, your Trainer will provide you with the necessary feedback and guidance, in order for you to resubmit/redo your assessment task(s).

What if you disagree on the assessment outcome?

You can appeal against a decision made in regards to an assessment of your competency. An appeal should only be made if you have been assessed as Not Yet Competent against specific competency standards and you feel you have sufficient grounds to believe that you are entitled to be assessed as competent.

You must be able to adequately demonstrate that you have the skills and experience to be able to meet the requirements of the unit you are appealing against the assessment of.

You can request a form to make an appeal and submit it to your Trainer, the Course Coordinator, or an Administration Officer. The RTO will examine the appeal and you will be advised of the outcome within 14 days. Any additional information you wish to provide may be attached to the form.

What if I believe I am already competent before training?

If you believe you already have the knowledge and skills to be able to demonstrate competence in this unit, speak with your Trainer, as you may be able to apply for Recognition of Prior Learning (RPL).

Credit Transfer

Credit transfer is recognition for study you have already completed. To receive Credit Transfer, you must be enrolled in the relevant program. Credit Transfer can be granted if you provide the RTO with certified copies of your qualifications, a Statement of Attainment or a Statement of Results along with Credit Transfer Application Form. (For further information please visit Credit Transfer Policy)

Your organisation is preparing a project plan for to undertake the project for the Bureau of Meteorology as outlined in the attached scope of requirements. You have been tasked with developing and documenting logical processes and timelines to ensure that the project is delivered according to organisational and stakeholder expectations, and in order to do so, you must:

select methodologies

develop project schedules

develop project budgets

establish budgetary controls.

A full project plan, including sub-plans must be developed. Sub-plans can include:

communications

human resource

organisational change

project implementation procurement quality

risk

scope

change control.

At a minimum, a project plan answers basic questions about the project:

Why? - What is the problem or value proposition addressed by the project? Why is it being sponsored?

What? - What is the work that will be performed on the project? What are the major products/deliverables?

Who? - Who will be involved and what will be their responsibilities within the project? How will they be organized?

When? - What is the project timeline and when will particularly meaningful points, referred to as milestones, be complete?

The project plan document may include the following sections:

Introduction: A high-level overview of the project.

Project Management Approach: The roles and authority of team members. It represents the executive summary of the Project Management Plan.

Project Scope: The scope statement from the Project charter should be used as a starting point with more details about what the project includes and what it does not include (In-Scope and Out-Of-Scope).

Milestone List: A list of the project Milestones (the stop points that helps evaluating the progress of the project). This list includes the milestone name, a description about the milestone, and the date expected.

Schedule Baseline and Work Breakdown Structure: WBS which consists of Work Packages and WBS Dictionary, which defines these work packages, as well as Schedule Baseline, which is the reference point for managing project progress, are included here.

Project Management Plans: This section contains all management plans of all project aspects.

Change Management Plan

Communication Management Plan

Cost Management Plan

Procurement Management Plan

Project Scope Management Plan

Schedule Management Plan

Quality Management Plan

Risk Management Plan

HR/Staffing Management Plan

Resource Calendar: Identify key resources needed for the project and their times and durations of need.

Cost Baseline: This section includes the budgeted total of each phase of the project and comments about the cost.

Quality Baseline: Acceptable levels of quality.

Sponsor Acceptance: Some space for the project sponsor to sign off the document.

ICTPMG613 Manage ICT Project Planning

Task 1- ICT Project Plan 1 Automated Payroll System with GPS Tracking and Image Capture

Submitted to - Submitted By-

Task 1 Scenarios

Your organisation is undertaking the development of a new software product - Automated payroll system with GPS tracking and image capture. You are required to develop a project plan for the development of the product. This automated payroll system doubles up as a web and Android application while the user will use the Android interface, the Admin (usually the HR) will use the web interface. The application will work something like this each employee is given an employee ID and password for accessing the app from their Android device. When an employee logs into the system from an Android device and immediately, the user image is captured. Then, the system sends the user image and their GPS location to the Admin. As long as the user stays logged into the system via an Android device, the GPS location will continue to be automatically updated and forwarded to the Admin every five minutes. When the user logs out, their image and GPS location are again sent to the Admin. This application allows Admins to keep track of employee attendance and payroll. The Admin creates employee profiles for each employee by entering all the relevant personal information (name, job position, qualification, etc.). They can also check the salary details and breakdown of the salary of each employee by entering the employee ID and date. Since the application is GPS-enabled, no employee can add proxy attendance. This enables the HRs to keep an accurate record of working days of individual employees and tweak their payroll accordingly.

Table of Contents

TOC o "1-3" h z u Introduction PAGEREF _Toc98770012 h 4Project Goals PAGEREF _Toc98770013 h 4CSF Impact on stakeholders PAGEREF _Toc98770014 h 4Project Deliverables PAGEREF _Toc98770015 h 4Project Schedule PAGEREF _Toc98770016 h 5Supporting Plans PAGEREF _Toc98770017 h 5Tools Utilised in Project Plan PAGEREF _Toc98770018 h 6

Introduction< Provide the Introduction of the Organization and Scenario provided to you, you might Paraphrase the Introduction information provided to you in your own words>

Project Goals<In project goals please mention and identify stakeholders in your project such as:- the project sponsors- the customer who receive the deliverables- the user of the project output- the project manager and project team

Mention the stakeholders needs and priorities, and create a goal based on the needs of the stakeholders>

CSF Impact on stakeholders

Explain the relationship between each group of the stakeholders and the identified CSF (Critical Success Factors)

Relationships STAKEHOLDER 1 STAKEHOLDER 2 STAKEHOLDER 3

CSF1 CSF2 CSF3 CSF4 Project Deliverables

<Identify the Critical Success Factors (CSF) - factors that must be present in order for the project to be successful and promote the organisations goals.>

Assigned To

Due Date

CSF1 CSF2 CSF3 CSF4 Project Schedule<Create a list of tasks (at least 10) that need to be carried out for each deliverable identified in the Project Deliverables. For each task determine the following:

The amount of effort (hours or days) required for completing the task

The resource who will carry out the task>

Supporting Plans<Create the following plan to support the project:

Human Resource Plan - Identify, by name, the individuals and organisations with a leading role in the project. For each, describe their roles and responsibilities on the project.

Next, specify the number and type of people needed to carry out the project. For each resource detail start dates, the estimated duration and the method you will use for obtaining them. Create a single sheet containing this information.

Communications Plan - Create a document showing who is to be kept informed about the project and how they will receive the information. The most common mechanism is a weekly or monthly status report, describing how the project is performing, milestones achieved and the work you've planned for the next period.

Risk Management Plan - Risk management is an important part of project management. Although often overlooked, it is important to identify as many risks to your project as possible and be prepared if something bad happens.

Here are some examples of common project risks:

Time and cost estimate too optimistic

Customer review and feedback cycle too slow

Unexpected budget cuts

Unclear roles and responsibilities

No stakeholder input obtained

Not clearly understanding stakeholder needs

Stakeholders changing requirements after the project has started

Stakeholders adding new requirements after the project has started

Poor communication resulting in misunderstandings, quality problems and rework

Lack of resource commitment

>

Tools Utilised in Project Plan<Create the following tools used in the project plan:

Work breakdown structure - As its name suggests, a work breakdown structure (WBS) is a project management tool that breaks down large projects into more manageable sections. It defines the projects deliverables and provides a visual decomposition of the projects scope. The WBS is created with the team first identifying the major deliverables, and then breaking those deliverables down into smaller, more digestible bits until they can be assigned as tasks to members of the team.

Network diagrams - A project management network diagram graphically represents the projects tasks and workflow. It lays out the projects schedule and sequence of activities, and uses boxes and arrows to connect work segments and illustrate the dependencies between tasks.

Gantt chart - A Gantt chart is a visual snapshot of the different project management activities on a timeline. A bar represents each activity, with the location and length of the bar signifying the start and end dates and duration of the activity. A quick glance at a Gantt chart will let you know right away the start and end dates of the entire project, what the projects activities are, each activitys start and end date, how long theyre scheduled for, and if there are any overlapping activities to be mindful of.>

ICTPMG613 Manage ICT Project Planning

Task 2 ICT Project Plan 2 Product Lifecycle Management System

807720393065PROJECT MANAGEMENT PLAN

Project name:

Table of Contents

TOC o "1-3" h z u 1. Introduction PAGEREF _Toc106698500 h 32. Project Management Approach PAGEREF _Toc106698501 h 33. Schedule Baseline PAGEREF _Toc106698502 h 34. Project Management Plan PAGEREF _Toc106698503 h 44.1. Communication Management Plan PAGEREF _Toc106698504 h 44.2. Cost Management Plan PAGEREF _Toc106698505 h 4a) Budgetary Assumptions PAGEREF _Toc106698506 h 4b) Project Budget Planning PAGEREF _Toc106698507 h 54.3. Sponsor Acceptance PAGEREF _Toc106698508 h 5Reference PAGEREF _Toc106698509 h 5

1. Introduction(Provide an overview of the project, and the purpose and objectives of the project management plan)

2. Project Management Approach(Here you need to discuss which approach you will choose for this project and why is the best option. e.g. Agile, waterfall, scrum, etc)

3. Schedule Baseline(Develop a project schedule using the milestone table provided. You will need to provide WBS and Gantt Chart from the milestone table)

3.1. Milestone Table

Milestone Description Date Resources Needed Responsibility

3.2. Work Breakdown Structure

(Discuss the purpose and objectives of Work Breakdown Structure and create WBS based on the milestone table)

3.3. Gantt Chart

(Discuss the purpose and objectives of Gantt Chart and create Gantt Chart based on the milestone table)

4. Project Management Plan4.1. Communication Management Plan(Discuss the purpose and objectives of the communication management plan)

Audience Message Delivery Method Delivery Frequency Communicator

4.2. Cost Management Plan(Discuss the purpose and objectives of the cost management plan)

a) Budgetary Assumptionsb) Project Budget PlanningProject Phase Resources Estimated Cost Contingencies and Tolerances Overheads

4.3. Sponsor AcceptanceSponsor Approval Signature Date

Project Manager Signature Date

Reference

Task 1 ICT Project Plan 1 - Automated payroll system with GPS tracking and image capture

Instructions to Learners:

This summative assessment can be completed in class or at any other convenient location.

Students are required to complete this task using digital tools and ensure to submit in an acceptable format, e.g. .docx, .pdf, .pptx, or as advised by your assessor.

Please use the following formatting guidelines to complete this assessment task:

Font Size: 12; Line Spacing: Double; Font Style: Times New Roman

Assessment activities can be completed either in real workplace environment or in a simulated environment such as your classroom. In both cases, appropriate evidence of the assessment activities must be provided.

Instruction to Assessors:

You must assess students assessment according to the provided Marking Criteria.

You must complete and record any evidence related to assessment activities including role-plays and presentations using appropriate forms which must be attached with student assessment submission.

You must provide students with detailed feedback within 10 working days from submission.Skills Assessment (Practical Tasks)

ASSESSOR NOTE

These instructions must be followed when assessing the student in this unit. The checklist on the following page is to be completed for each student. Please refer to separate mapping document for specific details relating to alignment of this task to the unit requirements.

This competency is to be assessed using standard and authorised work practices, safety requirements and environmental constraints.

Assessment of essential underpinning knowledge will usually be conducted in an off-site context.

Assessment is to comply with relevant regulatory or Australian standards' requirements.

Resource implications for assessment include:

an induction procedure and requirement

realistic tasks or simulated tasks covering the mandatory task requirements

relevant specifications and work instructions

tools and equipment appropriate to applying safe work practices

support materials appropriate to activity

workplace instructions relating to safe work practices and addressing hazards and emergencies

material safety data sheets

research resources, including industry related systems information.

Reasonable adjustments for people with disabilities must be made to assessment processes where required. This could include access to modified equipment and other physical resources, and the provision of appropriate assessment support.

What happens if your result is Not Yet Competent for one or more assessment tasks?

The assessment process is designed to answer the question has the participant satisfactorily demonstrated competence yet? If the answer is Not yet, then we work with you to see how we can get there.

In the case that one or more of your assessments has been marked NYC, your Trainer will provide you with the necessary feedback and guidance, in order for you to resubmit/redo your assessment task(s).

What if you disagree on the assessment outcome?

You can appeal against a decision made in regards to an assessment of your competency. An appeal should only be made if you have been assessed as Not Yet Competent against specific competency standards and you feel you have sufficient grounds to believe that you are entitled to be assessed as competent.

You must be able to adequately demonstrate that you have the skills and experience to be able to meet the requirements of the unit you are appealing against the assessment of.

You can request a form to make an appeal and submit it to your Trainer, the Course Coordinator, or an Administration Officer. The RTO will examine the appeal and you will be advised of the outcome within 14 days. Any additional information you wish to provide may be attached to the form.

What if I believe I am already competent before training?

If you believe you already have the knowledge and skills to be able to demonstrate competence in this unit, speak with your Trainer, as you may be able to apply for Recognition of Prior Learning (RPL).

Credit Transfer

Credit transfer is recognition for study you have already completed. To receive Credit Transfer, you must be enrolled in the relevant program. Credit Transfer can be granted if you provide the RTO with certified copies of your qualifications, a Statement of Attainment or a Statement of Results along with Credit Transfer Application Form. (For further information please visit Credit Transfer Policy)

Your organisation is undertaking the development of a new software product - Automated payroll system with GPS tracking and image capture. You are required to develop a project plan for the development of the product.

This automated payroll system doubles up as a web and Android application while the user will use the Android interface, the Admin (usually the HR) will use the web interface.

The application will work something like this each employee is given an employee ID and password for accessing the app from their Android device. When an employee logs into the system from an Android device and immediately, the user image is captured. Then, the system sends the user image and their GPS location to the Admin.

As long as the user stays logged into the system via an Android device, the GPS location will continue to be automatically updated and forwarded to the Admin every five minutes. When the user logs out, their image and GPS location are again sent to the Admin.

This application allows Admins to keep track of employee attendance and payroll. The Admin creates employee profiles for each employee by entering all the relevant personal information (name, job position, qualification, etc.). They can also check the salary details and breakdown of the salary of each employee by entering the employee ID and date.

Since the application is GPS-enabled, no employee can add proxy attendance. This enables the HRs to keep an accurate record of working days of individual employees and tweak their payroll accordingly.

Step 1: Project Goals

A project is successful when it has met the needs of the stakeholders. A stakeholder is anybody directly, or indirectly impacted by the project.

As a first step, it is important to identify the stakeholders in your project. It is not always easy to determine the stakeholders of a project, particularly those impacted indirectly. Examples of stakeholders are:

The project sponsor

The customer who receives the deliverables

The users of the project output

The project manager and project team

Once you understand who the stakeholders are, the next step is to find out their needs. The best way to do this is by conducting stakeholder interviews. Take time during the interviews to draw out the requirements that create real benefits. Sometimes stakeholders will talk about needs that aren't relevant and don't deliver benefits. These can be recorded and set as a low priority.

The next step, once you have conducted all the interviews and have a comprehensive list of needs is to prioritise them. From the prioritised list, create a set of easily measurable goals. A good technique for doing this is to review them against the SMART principle. This way, the achievement of the goal will be easy to identify.

Once you have established a clear set of goals, they should be recorded in the project plan. It can be useful also to include the needs and expectations of your stakeholders.

Now you have completed the most difficult part of the planning process; it's time to move on and look at the project deliverables.

Step 2: Project Deliverables

Using the goals you have defined in step 1, create a list of things the project needs to deliver to meet those goals. Specify when and how to deliver each item.

Add the deliverables to the project plan with an estimated delivery date. You will establish more accurate delivery dates during the scheduling phase, which is next.

Step 3: Project Schedule

Create a list of tasks that need to be carried out for each deliverable identified in step 2. For each task determine the following:

The amount of effort (hours or days) required for completing the task

The resource who will carry out the task

Once you have established the amount of effort for each task, you can work out the effort required for each deliverable, and an accurate delivery date. Update your deliverables section with the more precise delivery dates.

At this point in the planning, you could choose to use a software package such as Microsoft Project to create your project schedule. Alternatively, use one of the many free templates available. Input all of the deliverables, tasks, durations and the resources who will complete each task.

A common problem discovered at this point is when you have an imposed delivery deadline from the sponsor that is not realistic based on your estimates. If you discover this is the case, you must contact the sponsor immediately. The options you have in this situation are:

Renegotiate the deadline (project delay)

Employ additional resources (increased cost)

Reduce the scope of the project (less delivered)

Use the project schedule to justify pursuing one of these options.

Step 4: Supporting Plans

This section deals with the plans you should create as part of the planning process. These can be included directly in the plan.

Human Resource Plan

Identify, by name, the individuals and organisations with a leading role in the project. For each, describe their roles and responsibilities on the project.

Next, specify the number and type of people needed to carry out the project. For each resource detail start dates, the estimated duration and the method you will use for obtaining them.

Create a single sheet containing this information.

Communications Plan

Create a document showing who is to be kept informed about the project and how they will receive the information. The most common mechanism is a weekly or monthly status report, describing how the project is performing, milestones achieved and the work you've planned for the next period.

Risk Management Plan

Risk management is an important part of project management. Although often overlooked, it is important to identify as many risks to your project as possible and be prepared if something bad happens.

Here are some examples of common project risks:

Time and cost estimate too optimistic

Customer review and feedback cycle too slow

Unexpected budget cuts

Unclear roles and responsibilities

No stakeholder input obtained

Not clearly understanding stakeholder needs

Stakeholders changing requirements after the project has started

Stakeholders adding new requirements after the project has started

Poor communication resulting in misunderstandings, quality problems and rework

Lack of resource commitment

Risks can be tracked using a simple risk log. Add each risk you have identified to your risk log; write down what you will do in the event it occurs, and what you will do to prevent it from happening. Review your risk log on a regular basis, adding new risks as they occur during the life of the project. Remember, if you ignore risks, they don't go away.

In developing the project plan, a range of tools should be utilized such as:

Work breakdown structure

As its name suggests, a work breakdown structure (WBS) is a project management tool that breaks down large projects into more manageable sections. It defines the projects deliverables and provides a visual decomposition of the projects scope.

The WBS is created with the team first identifying the major deliverables, and then breaking those deliverables down into smaller, more digestible bits until they can be assigned as tasks to members of the team.

Network diagrams

A project management network diagram graphically represents the projects tasks and workflow. It lays out the projects schedule and sequence of activities, and uses boxes and arrows to connect work segments and illustrate the dependencies between tasks.

Gantt chart

A Gantt chart is a visual snapshot of the different project management activities on a timeline. A bar represents each activity, with the location and length of the bar signifying the start and end dates and duration of the activity.

A quick glance at a Gantt chart will let you know right away the start and end dates of the entire project, what the projects activities are, each activitys start and end date, how long theyre scheduled for, and if there are any overlapping activities to be mindful of.

Task 1 ICT Project Plan 1 Automated Payroll System with GPS Tracking and Image Capture

Guidelines:

Read through the Scenario given on Task 1 template document on Canvas (ICTPMG613 Task 1 Template.docx)

Resources:

Task 1 template document (ICTPMG613 Task 1 Template.docx)

Deliverables

Your document must include

Project Planning

Fill in the Task 1 template document based on the scenario provided in the template

Referencing

The Referencing style that we use is APA style. Please follow the link below for more information https://www.danford.edu.au/wp-content/uploads/2021/02/Guidelines-for-Referencing.pdf

Task 2 ICT Project Plan 2 Product Lifecycle Management System

Guidelines:Read through the Scenario given on Task 2 document on Canvas (Task 2.docx)

Resources:

Task 2 document (Task 2.docx)

Task 2 template document (ICTPMG613 Task 2 Template.docx)

Deliverables

Your document must include

Project Planning

Fill in the Task 2 template document based on the scenario provided in the Task 2 document

Referencing

The Referencing style that we use is APA style. Please follow the link below for more information https://www.danford.edu.au/wp-content/uploads/2021/02/Guidelines-for-Referencing.pdf

  • Uploaded By : Pooja Dhaka
  • Posted on : November 21st, 2024
  • Downloads : 0
  • Views : 194

Download Solution Now

Can't find what you're looking for?

Whatsapp Tap to ChatGet instant assistance

Choose a Plan

Premium

80 USD
  • All in Gold, plus:
  • 30-minute live one-to-one session with an expert
    • Understanding Marking Rubric
    • Understanding task requirements
    • Structuring & Formatting
    • Referencing & Citing
Most
Popular

Gold

30 50 USD
  • Get the Full Used Solution
    (Solution is already submitted and 100% plagiarised.
    Can only be used for reference purposes)
Save 33%

Silver

20 USD
  • Journals
  • Peer-Reviewed Articles
  • Books
  • Various other Data Sources – ProQuest, Informit, Scopus, Academic Search Complete, EBSCO, Exerpta Medica Database, and more