ASSIGNMENT 2 - 30% & ASSIGNMENT 3 – 30%

PROJECT PROPOSAL (PROJECT CHARTER)

(2000 WORDS MAX)

INF30029 – Information Technology Project Management

Due date Tuesday 22 April 2020
Presentation Week Commencing: 18 May 2020

Overview

The case study for this assignment [Funky Energy] has been provided within the assignment folder in
Canvas.
The case study outlines a project which will be the basis for Assignments 2 and 3.

Students should undertake Assignments 2 & 3 in teams of 4 (Must obtain approval from unit convenor if
your group has more/less than 4 members). Please contact the convenor to confirm groups. Also refer to
the section below on group Assignment requirements.

Project Proposal Deliverables [the tasks]

You are to assume the role of the project manager.

For the purposes of this Assignment we will refer to the project management framework or the Project
Management Body of Knowledge [PMBOK].

In this Assignment you are to focus on the following PMBoK areas:

1. Project Scope Management, including but not exclusively:

a. Scope Statement
b. Work Breakdown Structure [WBS]
c. Include all Deliverables
d. Define a Change Management Process

2. Project Time Management, including but not exclusively:

a. Gantt Charts with reasonable Assumptions and relevant Milestones
b. Schedule Summary in Proposal
c. Detailed Schedule in Appendix

3. Project Cost Management, including but not exclusively:

a. Budget Summary in Proposal
b. Include Assumptions and Constraints
c. Detailed Budget in Appendix

4. Project Quality Management, including but not exclusively:

a. Quality Planning
b. Quality Assurance and Control Activities
c. Define Quality Standards and Metrics

5. Project Risk Management, including but not exclusively:

a. Risk Identification
b. Risk Register
c. Perform Qualitative Risk Analysis using Probability / Impact Matrix
d. Risk Mitigation

Page 1 of
 6. Project Procurement Management, including but not exclusively:
a. Processes to Support Project Procurement
b. Outsourcing [if appropriate]
c. Type(s) of Contract
d. Source Selection Criteria

7. Project Integration Management, including but not exclusively:

a. Development of the project proposal [Project Charter]
Notes:
1. Actual resources and costs will be determined by each student [who assumes the role of the project manager],
determining the number required to complete the project. In specifying the resources and costs you should
clearly state your justification, assumptions and limitations. Project teams have the opportunity to determine
resource salaries as their role of a project manager.
2. In developing your WBS and schedule you should ensure the project is completed on the required date.
3. You are required to use any suitable project management software to develop the WBS, schedule, and
budget. The project file MUST be embedded into your project proposal for verification.
4. As this is a unit allowing students to apply their learning, you are not to write a proposal simply describing what
a project proposal is about, but to actually produce a project proposal from the material supplied and
demonstrate your understanding of PMBoK©.

Submission Procedures

Your proposal is to be typewritten. The proposal should be written in clear, plain language, so that non-expert users can
easily understand it. The proposal must be properly constructed, it should contain all the necessary parts that a proposal
is required to have. Include all relevant documents and support materials [if required] in an appendix. All sources quoted
in your proposal should be correctly referenced and included in a Reference or Bibliography or both. Swinburne
University has adopted the “Harvard Referencing System”, it is therefore expected that you will also use this reference
system in your proposal.

Please ensure you also use the style guide provided on Canvas.

Notes:
1. The project proposal should be plausible, that is it should reflect the objectives from the case study.

On the front page of all Assignments submitted you must include:

 Full names and student ID’s
 Unit code, Assignment number, due date and % weighting
 Assignment name and a descriptive title of your chosen topic
 Signed declaration as worded below:
• I hold a copy of this Assignment that can be produced if the original is lost/damaged. To the best
of my belief, no part of this Assignment has been copied from any other student’s work or from any
other source except where due acknowledgement is made in the text. No part has been written for
me/us by any other person, except where such collaboration has been authorised by the lecturer
concerned.

Do not submit any Assignments by eMail to the tutor or convenor.

Project Proposal – Group Presentation

Assessment of the presentation will be based on:

Content of the presentation. The presentation should include/demonstrate the following:

 Project Management Plan (includes Project Background, Objectives, Key Constraints/Assumptions, Deliverables,
Team Structure, Change Management as well as Project Schedule, Budget, Risks and Procurement)

Presentation style
 The presentation should be to professional standards suitable for senior managers or an industry interest group.

 Participation
All group members must participate in the 12 minutes presentation and demonstrate your effort to answer
questions from audience (if any)

*Marks will be deducted (at a rate of 1% per minute) for presentations that exceed the 12 minutes limit.

Assignment Procedures for Group Work

1. Assignment task 2 & 3 will be undertaken as a team assignment in groups of 4. The choice of operating mode will be
left to the students, although where the group mode is preferred, the team as a whole will be responsible for its day-
to-day operation and management. Where working in team mode is chosen, you should work with the same group
members in both assignments.
2. When the relevant decisions on team have been made, work space for groups will be made available on Canvas if
required. Other than this, however, management of the team will be the responsibility of the students concerned. In
the group space, the features/tools [e.g., discussion board, chat room, file exchange, email, blogs, etc.] available
within the group area.
3. The requirements and marking criteria for the Assignment will remain the same, whether submissions come from
individuals or groups. The assignment marking guide has been provided on the last page of this Assignment
Specification.
4. Where working in project teams, only one submission [on behalf of all members of the team] is required. Please
ensure that the full name and student number of every group member are provided as part of the submission.
5. It is anticipated that each member of the project team will receive equal marks. Depending on the results of the peer
assessment form [provided on Canvas], the final mark may be distributed unevenly across the team depending on
level of participation, preparation and scholarly academic contributions to the assignment.

Warnings!

1. It is expected that your proposal be of acceptable content and structure as this is an undergraduate unit.
2. You will not pass if you do not comply with the assignment requirements.
3. The work you submit must be your team’s work only and nobody else’s.
4. You MUST submit the proposal by using Canvas.
5. Don’t forget to keep a backup. If your assignment goes astray, whether your fault or ours, you will be required to re-
produce it.
6. Late submission of assignments may result in a lower grade for the assignment in terms of the Swinburne Assignment
guidelines as suggested in the unit outline.
Marking Criteria (Project Proposal)

Very Good Good Satisfactory Unsatisfactory

Introduction and 4 to >3.2
Objective of the Project Provide a very detailed
Plan (4%) overview of the
organisation.
Clearly outline the
objectives of the project
Project Integration 13 to >10.4
Management (13%) Provide a very detailed
project charter with all
elements (see Schwalbe,
K. (2016) IT Project
Management, 8th Edition,
p.157)
Project Scope 11 to >8.8
Management (11%) Product Description:
Correctly describe the
solution used to address the
problems / opportunities.
Deliverable: Correctly
identify the relevant major
deliverables of the project.
Scope Statement: Include a
detailed and relevant
description on product
scope description, product
user acceptance criteria,
project boundaries,
constraints and
assumptions.
3.2 to >2.8
Provide a detailed
overview of the
organisation.
Outline most of the
objectives of the project
10.4 to >9.1
Provide a detailed project
charter with most of the
elements (see Schwalbe,
K. (2016) IT Project
Management, 8th Edition,
p.157)
8.8 to >7.7
Product Description:
Correctly describe the
solution used to address
most of the problems /
opportunities.
Deliverable: Identify some
relevant major deliverables
of the project?
Scope Statement: Include a
general description on
product scope description,
product user acceptance
criteria, project boundaries,
constraints and
assumptions.
2.8 to >2
Provide a general
overview of the
organisation.
Outline some objectives of
the project
9.1 to >6.5
Provide a project charter
with some of the elements
(see Schwalbe, K. (2016)
IT Project Management,
8th Edition, p.157)
7.7 to >5.5
Product Description:
Describe the solution used
to address some problems /
opportunities.
Deliverable: Identify a few
relevant major deliverables
of the project?
Scope Statement: Include a
description on product
scope description / product
user acceptance criteria /
project boundaries /
constraints / assumptions.
Some of the components
are missing.
2 to 0
Inappropriate / No overview
is provided.
Incorrect / No objective of
the project is provided
6.5 to 0
Provide a very brief project
charter with only a few
elements; or no project
charter is provided.
5.5 to 0
Not / Poorly describe the
product description / scope
statement / scope change
management process.
Not / Poorly identify the
Deliverable.
WBS: Provide a WB but
most of the works are
missing and are not logically
divided.

WBS: Provide a correct WBS: Provide a WBS. The

WBS. The WBS should
include all of the works
require in a project. The
works are divided into
logical parts.
Scope Change
Management Process:
Provide a very detailed
process that describes how
a scope may be changed.
WBS: Provide a WBS. The
WBS should include most
of the works require in a
project. Most of the works
are divided into logical
parts.
Scope Change
Management Process:
Provide a process that
describes how a scope may
be changed.
WBS should include some
works require in a project.
Some of the works are
divided into logical parts.
Scope Change
Management Process:
Provide a partial process
that describes how a scope
may be changed.
Project Time 11 to >8.8
Management (11%) Creation of the Project
Schedule (Gantt Chart).
Do they include reasonable
assumptions?
Is the project schedule and
precedence’s of the tasks
properly though out?
Do they schedule anything
out of place (e.g. a
deliverable on Dec. 25)?
Does the estimate
accurately reflect the actual
work they are doing?
Milestones:
Have the correct and
relevant milestones
8.8 to >7.7
Creation of the Project
Schedule (Gantt Chart).
Does the project schedule
and the estimate reflect the
actual work they were
doing?
Milestones:
Have the correct and
relevant milestones
Narrative of the phases: Do
they give some rationale as
to how they divided the
project into phases?
Task Description:
Do they describe each task
that needs to be done?
7.7 to >5.5
Creation of the Project
Schedule (Gantt Chart).
Does the project
schedule and the
estimate reflected some
of the work they are
doing?
Narrative of the phases:
DO they give rationale as to
how they divided the
project into phases?
Task Description:
Do they describe some of
the tasks that need to be
done?
5.5 to 0
No clear Creation of the
Project Schedule (Gantt
Chart).
The estimate does not
reflect some of the work
they are doing?
Narrative of the phases: No
clear rationale as to how
they divided the project into
phases?
Task Description:
Does not describe the tasks
that need to be done?

Narrative of the phases: Do

they give clear rationale as
to how they divided the
project into phases?

Task Description:
Do they describe accurately
each task that needs to be
done?
Project Cost 11 to >8.8
Management (11%) All the components of A
FULLY COSTED PROJECT
are presented
Do they consider all
components?
Correctness of the estimate:
The estimates are correct
and they have supporting
data on this
Are the computations,
assumptions and
constraints correct?
Project Quality 11 to >8.8
Management (11%) Establish clear goals,
processes, and
responsibilities required to
implement effective quality
management functions for
the project.
8.8 to >7.7
Some of the components of
A FULLY COSTED
PROJECT are
presented
Do they consider some of
components?
Correctness of the estimate:
The estimates are correct
and they have some
supporting data on this
Some of the computations,
assumptions and
constraints are correct.
8.8 to >7.7
Establish some goals,
processes, and
responsibilities required to
implement effective quality
management functions for
the project.
7.7 to >5.5
Part of the components of A
PARTIALLY COSTED
PROJECT are presented?
Correctness of the estimate:
Part of the estimates are
correct; insufficient
supporting data on this is
provided
Part of computations,
assumptions and
constraints are correct
7.7 to >5.5
Some processes required to
implement effective quality
management functions for
the project.
Quality is planned.
5.5 to 0
Does not provide
components of expenses
Estimate is not correct
Unclear and incorrect
computations, assumptions
and constraints
5.5 to 0
No clear goals, processes
and responsibilities.
Incomplete management
plan

Ensure quality is planned. Ensure quality is planned. A few quality assurance

Define quality assurance
and control activities.
Define acceptable
quality standards and
metrics.
11 to >8.8
Define quality assurance
and control activities.
Define acceptable
quality standards and
metrics.
8.8 to >7.7
and control activities are
defined.
A few acceptable quality
standards are defined.
7.7 to >5.5 5.5 to 0
Project Risk Provide a risk register with
Management (11%) 6-8 top risks and include ID,
rank, name description,
category, root cause,
triggers and potential
responses for each risk
event.
Each risk event is
reasonably assessed using
Probability / Impact Matrix.
Reasonable and relevant
mitigation recommendations
are provided for each risk
event.
Project Procurement 11 to >8.8
Management (11%) Identify and describe clearly
the processes required to
support project
procurement.
Clearly identify and the
type(s) of contract and
source selection criteria
required in the project.
Provide substantial
justification for your choices.
Provide a detailed
discussion on whether to
outsource or buy or
make/perform products and
services required in this
project.
Professional Proposal 5 to >4
Presentation and Information is well
Referencing (5%) organized. With a strong
professional layout,
includes; Executive
Summary, Table of
Contents, Headers /
Footers, Appendices, etc.
Very well written and
with proper grammar /
punctuation throughout.
Referenced correctly
(Harvard) and cited
appropriately in the
body of the proposal.
Provide a risk register with
4-5 top risks and include
most of the components: ID,
rank, name description,
category, root cause,
triggers and potential
responses for each risk
event.
Most risk events are
assessed using Probability /
Impact Matrix.
Mitigation
recommendations are
provided for most of the risk
events.
8.8 to >7.7
Identify and describe the
processes required to
support project
procurement.
Identify the type(s) of
contract and source
selection criteria required in
the project. Provide
justification for your choices.
Provide a discussion on
whether to outsource or buy
or make/perform products
and services required in this
project.
4 to >3.5
Information is organised.
With a professional
layout, includes; Exec.
Summary, Table of
Contents, Appendices,
etc.
Well written and with
Proper grammar and
Punctuation.
Most referencing is correct
(Harvard) and cited
appropriately in the
body of the proposal.
Provide a risk register with
2-3 top risks and include
some of the components:
ID, rank, name description,
category, root cause,
triggers and potential
responses for each risk
event.
Most risk events are not
assessed using Probability /
Impact Matrix or assessed
incorrectly.
Mitigation
recommendations are not
provided for most of the risk
events.
7.7 to >5.5
Identify and briefly describe
the processes required to
support project
procurement.
Identify the type(s) of
contract and source
selection criteria required in
the project.
Provide a brief discussion
on whether to outsource or
buy or make/perform
products and services
required in this project.
3.5 to >2.5
Information is somewhat
organised, some
elements of layout or
length are incorrect.
Proper grammar and
Punctuation.
Mostly correct
referencing (Harvard) but
some problems with the
reference list.
No / Incomplete risk register
is provided or most of the
components in the register
are incorrect
No included Probability /
Impact Matrix and mitigation
recommendations
5.5 to 0
Poor / No identification and
description of the processes
required to support project
procurement.
No Identification of the
type(s) of contract and
source selection criteria
required in the project.
Poor / No discussion on
whether to outsource or buy
or make/perform products
and services required in this
project.
2.5 to 0
Information is not clearly
organised, Some
elements of layout or
length are incorrect.
Proper grammar and
Punctuation.
Not all material is correctly
acknowledged and some
problems with the reference
list.
 Marking Criteria (Presentation)

Marks Comment
Presentation Project Background, Objectives, Key /1
Contents Constraints/Assumptions, Deliverables,
Team Structure,
Change Management /1
Project Schedule /1
Project Budget /1
Project Risks /1
Project Procurement /1
Slide content easy to see and read /1
Grammar and spelling /1

Presentation Active participation /2

style and Voice clear and easy to understand /1
Participation Eye contact with your audience /1

Overtime (-1% per minute)