Faculty of Information Technology

Semester 1, 2017

FIT5057 – Project Management

ASSIGNMENT: Section 1, Section 2, Presentation

(Project teams of 4 only)

‘Medibank Melbourne Marathon’ Project Report

Weighting: 60%
Due date: Section 1: due in week 4 In tutorials (4 marks)
Section 2: due in week 11 Friday 19th May (44 marks)
Project team deliverables Week 11 Friday 19th May (12 marks)
(includes confidential peer reviews handed to your tutor)
Submitting assignments: Section 2 must be electronically submitted by the due date
Page Length: 50 pages
Reference count: Minimum 10
Working strategy: Work together in project teams of 4

1. Aim
To produce a clearly articulated and well developed set of key deliverable documents for either a
mobile marathon running and/or walking training application, or a marathon running and/or walking
team website.

2. Learning outcomes
• critically, analyse evaluate and transform information to complete a range of activities that are
required in a typical project

• analyse, generate and transmit solutions to a range of project requirements

• transmit knowledge, skills and ideas to others to support the project requirements.

• apply knowledge and skills to demonstrate well-developed judgement, adaptability and

responsibility as a practitioner of a project

• ability to communicate appropriately in a team environment in order to successfully collaborate

with peers to deliver project deliverables.

Assignment1/Developed by Dr Foster
19/12/2016
 2
FIT5057 _Assignment 1_Semester 1, 2017
3. The case background
http://melbournemarathon.com.au/
Medibank Melbourne Marathon Festival is an institution and starts on the 15 October 2017. The
42.195 km run over the traditional marathon distance is the main race within the annual Melbourne
Marathon Festival. The race celebrated its 30th birthday in 2007 with a new course which featured the
Melbourne Cricket Ground (MCG) as both the starting point and finishing point. The Melbourne
Marathon has had nine different major sponsors in its 35 years.
Since moving the course to a finish inside the MCG In 2007, the Melbourne Marathon has regained its
status as the premier marathon in Australia. In 2013 the race was the largest marathon in Australian
history both in terms of entries (8066) and finishers (6820). There were 123 women who ran in the
first event in 1978. In 2013, there were 2004 female finishers, including 18 women breaking three
hours. More than 11,000 runners took part in Melbourne’s half marathon event last year and close to
10,000 runners entered the 10km event, swelling overall race entries to just over 34,000. Note: In
2017, the Medibank Melbourne Marathon doubled as the Australian Marathon Championships.

4. Instructions
There are a variety of events being held and these can be found at:
http://melbournemarathon.com.au/events/
Option 1 – Mobile application: Your team is tasked with developing a mobile running and/or walking
training app for any one of the five events: 42.195km Marathon, 21.1km Half Marathon, 10km Run,
ASICS 5.7km run, ASICS 3km Walk.

The mobile application should be designed to be downloaded onto any suitable hand held android
device. It should be cloud based so that all applications for the event can obtain all the data about the
run and/or walk.

For the mobile app to be functional it should run in the cloud and be able to:

capture all details about the runner/walker; their gender, age, years of running/walking, and
any other items of interest your team deem necessary. Remember the runner/walker should be
able to opt in or out of this section for privacy and confidentiality reasons.

For usefulness the mobile app should include:

a. a training program daily, weekly and monthly prior to the race itself – your team will need to
conduct research to establish the most important approaches to running/walking for beginners as
well as intermediates and advanced – these should be included in your app
b. A communication strategy for posting and receiving information
c. Health component – identifying hydration levels etc
d. record the kilometres the person has ran or walked daily, weekly and cumulatively
e. speed of the walker/runner each moment, daily and cumulatively
f. upload weekly/monthly information for runners/walkers via an e-newsletter
g. English translation option for international entrants
h. Any other detailed piece of information deemed necessary; for example help functionality,
security issues that need to be addressed from a cloud based perspective etc

Developed by Dr Sue Foster 02/02/2017

 3
FIT5057 _Assignment 1_Semester 1, 2017

Option 2: Team website: Your team is tasked with developing a marathon running and/or walking
team website for any one of the five events: 42.195km Marathon, 21.1km Half Marathon, 10km Run,
ASICS 5.7km run, ASICS 3km Walk.
Your website should include the following taken from:
http://melbournemarathon.com.au/events/marathon/

a. Communication strategy with each team member

b. Training strategy – including approach to hydration (research is needed here)
c. Event information:
I. Registration Entry fees ie early bird and early bird cut-off date
II. Race pack distribution and race pack inclusions
III. Course map
IV. Information for Slow course, pacers etc
V. Preferred starts
VI. Drink stations
VII. Prize money
VIII. Spartans
d. Any other information. This information must be relevant to the team website.

5. Key Deliverables for option 1 and 2:

For both options your team will need to provide a range of key deliverable documents:
Due Dates for Deliverable Mark allocation for Project team
each Section each section documentation
deliverable
Section 1 1.1 A team project plan outlining the schedule for 4 marks No project team
Week 4 delivering the assignment by the team for documentation
Friday 24 March completion by Friday 19 May - end of week 11.

Section 2 2.1 Stakeholder analysis* 44 marks Project Team

Due by Friday Must link to the case study documentation is
19 May 1. An explanation identifies the influence and required
interest of various stakeholders
You will be 2. A stakeholder analysis in the form of a table
expected to must demonstrate the importance of the
provide progress stakeholder to the project and include a
draft documents strategy for engaging stakeholders
to your tutor
3. Communication Plan: create a
each week
communication plan for your team and
starting in week
6 with the stakeholders
Stakeholder
analysis
Draft document 2.2 Scope management plan *
provided to your In your scope management plan you will be
tutor in week 7 required to:
1. Collect scope requirements
2. Define the scope
3. Create the WBS baseline document
4. Verify scope
5. Control scope – create a change control
process

Draft document 2.3 Develop a Schedule baseline*

provided to your 1. Schedule demonstrates the project’s
tutor in week 8 proposed milestones, activities and deliverables
with start and finish dates

Developed by Dr Sue Foster 02/02/2017

 4
FIT5057 _Assignment 1_Semester 1, 2017
2. Displayed in the form of a Gantt chart and
includes tasks and activities

Draft document 2.4 Network diagram activity on node*

provided to your 1. Plan and develop a basic network diagram
tutor in week 9 with legend showing duration and
constraints
2. Activities and task dependencies are
displayed in a logical sequence with logical
relationships

Draft document 2.5 Cost management plan*

provided to your 1. An appropriate costing method must be
tutor in week 10 used in the plan (cost estimate table)
2.Explanation clearly outlines why the particular
cost method was chosen
4. The cost estimates must be appropriate for
the project
5. Costs must be correctly labelled

NB: Remember this is a baseline budget only it is

not expected that the budget costs are totally
accurate

2.6 Develop a risk register*

1. Describe the importance of identifying a risk
register
2.six risks are provided
3. A suitably structured risk matrix is used
4. Risk matrix ranks risk according to severity
5. Include risk mitigation/control strategies
appropriate for each risk
6. Risk monitoring methods are provided
7. A suitable numerical or colour coding to
identify the severity and likelihood
8. A legend explains 7. above

2.7 Presentation of the value of the project

Due by Friday Project team deliverables covering section 2 12 marks NB: progressive
19th May – Includes confidential individual peer reviews (see requests from your
page 5 of this assignment) tutor to view these
can be expected
*All section 2 deliverables require a set of assumptions to gain full marks

Developed by Dr Sue Foster 02/02/2017

 5
FIT5057 _Assignment 1_Semester 1, 2017
6. Project Team Deliverables (completed and handed in Week 11)
As part of delivering the overall assignment, group members are expected to work together as a
functioning project team. This collaboration requires certain deliverables to be completed and handed
in as part of the overall assignment requirements. These deliverables can be found in Moodle and
include:

1. Up to date team project plan for the team tasks for the life of the project
2. Agenda and minutes of EACH team meeting
3. Individual timesheets
4. Peer reviews (peer reviews are confidential and should be handed in separately by each team
member via email to your tutor – these will allow your tutors to evaluate how effective your
assignment team was in working together collaboratively – students will be marked according to
their contribution).

Team Project Plan: The project plan must be kept up to date. Any changes made to the team tasks
must be shown on the project plan. Your project supervisor (tutor) must be able to request and see an
updated project plan at any time. This is an up to date version of the original plan presented as Section
1 of the assignment in week 4.

Individual Timesheets: individual timesheets must be completed as per template provided on Moodle
for all team members. This is to ensure if there any issues or discrepancies between team tasks and
the project plan your project supervisor (tutor) can identify them.

Agenda and minutes of team meetings: Teams are expected to meet at least once a week and the
meeting outcomes are to be recorded in the template provided on moodle. Meetings are an
important way to identify how the team is functioning as a coherent whole.

Peer reviews (peer reviews are confidential): should be handed in separately – these
will allow your tutors to evaluate how effective your assignment team was in working together
collaboratively – you will be marked according to your contribution).

The deliverables (apart from the peer review) need to be completed and handed in in a progressive
manner. So when completing and submitting each Section (except Section 1) all meeting agendas,
minutes and individual timesheets that formed part of preparing the section should also be submitted.

Collaboration tool: You will be required to us an appropriate collaboration tool in your

project team. This must be agreed to with your supervisor (tutor) and ensure you include your
tutor.

Tools: Microsoft Project (in labs and downloadable)

Project management for Google Apps – smartsheet (free)
Google Docs

Resources:
http://melbournemarathon.com.au/
http://melbournemarathon.com.au/events/

Developed by Dr Sue Foster 02/02/2017

 6
FIT5057 _Assignment 1_Semester 1, 2017

7. Minimum Structure and format of the report for Section 2 only:

1. Title Page

2. Exec Summary
No more than 2/3rds of a page.
The executive summary should provide an overview of the report outcomes
https://www.griffith.edu.au/__data/assets/pdf_file/0003/320178/writing-an-executive-
summary.pdf

3. Table of contents page

4. Structure of the report – must include:

Headings
Major headings in initial capitals 14 point Arial consecutively numbered
2nd level headings in 12 point Arial bold – consecutively numbered
3rd level headings 12 point font, bold italics – consecutively numbered
Headings should include the following BUT must follow the structure of the report:
Introduction:
Purpose of the report
Historical Background to the case company
Scope of the report

Headers and Footers

Page Number
Assignment Group Name
Unit code and Name
Date

Document Body
Use default margins
All text in 12 point times roman
Single spaced
Use bullets for lists
Each deliverable should be numbered according to the numbering provided ie
o Section 1 = 1.1 Team Project Plan
o Section 2 = 2.1 Stakeholder analysis etc

Overall Summary
An overall summary of the report is provided

Developed by Dr Sue Foster 02/02/2017

 7
FIT5057 _Assignment 1_Semester 1, 2017

8. References
Citations should be in APA style. This involves references to Smith (1979) or to a publication (Smith,
1979). Multiple authors (three or more) are referred to in the body of the text only as Anderson et
al. (1982). Multiple publications by the same author within the same year are differentiated as Jones
(1983a, 1983b). Where the author is unknown, or is an organisation, an appropriate surname or
organisation name or acronym is used, e.g. (OECD 1985, BCS 1980).

Project Management: A Systems Approach to Planning, Scheduling, and Controlling, by Harold Kerzner,
2013, 11th Edition, John Wiley & Sons, Australia.
Project Management: A Systems Approach to Planning, Scheduling, and Controlling, by Harold Kerzner,
2009, 10th Edition, John Wiley & Sons, Australia.
Project Management Workbook and PMP/CAPM Exam Study Guide, Harold Kerzner and Frank P.
Saladis, 11th Edition 2013, John Wiley.
A Guide to the Project Management Body of Knowledge, PMBOK 5th Edition. 2013. Project Management
Institute. (Available as an e-book)
Schwalbe, K. (2016) Information Technology Project Management (8th Edn), Cengage Learning.
ISBN 13 978 1 285 45234 0
Kathy Schwalbe Information Technology Project Management, , 8th Edition, 2016.
Kathy Schwalbe Information Technology Project Management, , 6th Edition, 2010.
Bentley, C. Prince 2: A Practical Handbook, 2nd Edition, 2002 Butterworth Heinemann.
Kerzner, H. (2014) Project Management - Best Practices: Achieving Global Excellence, 3rd Edition
Kerzner, H. (2013) Project management metrics, KPIs, and dashboards : a guide to measuring and
monitoring project performance. 2nd Edition. John Wiley & Sons. (Available as an e-book)
Kerzner, H. (2014) Project Recovery: Case Studies and Techniques for Overcoming Project Failure.
(Available as an e-book)
Tomanek, M., Cermak, R., & Smutny, Z. (2014). A Conceptual Framework for web Development Projects
Based on Project Management and Agile Development Principles. Proceedings Of The European
Conference On Management, Leadership & Governance, 550-558.
Link
http://ezproxy.lib.monash.edu.au/login?url=http://search.ebscohost.com/login.aspx?direct=true&db=bth&A
N=99239893&site=ehost-live&scope=site
Turner, J. R. 2015. The Handbook of Project based Management (2015) (4th Edn) Mc Graw Hill New York
- ISBN 0-07-707656-7
Project Definition Reports are addressed on page 296
Located at:
http://ebookinga.com/pdf/the-handbook-of-project-based-management-j-rodney-277171148.html

Developed by Dr Sue Foster 02/02/2017

 8
FIT5057 _Assignment 1_Semester 1, 2017

9. Learning Criteria
Course Masters degree PM
Learning
Outcomes(CLO)
CLO1 Analyse critically a business problem, Understand and be able to apply the
design IT solutions for such problems and theories and concepts of project
assess their effectiveness. management
CLO2 Engage in business information systems Analyse requirements for the
practice to a level of depth and management of given projects,
sophistication consistent with senior identify theory and methods
professional practice. applicable to their management of
given projects, apply these and
identify ethical, cultural and legal
context and issues that impact on
this.
CLO3 Demonstrate professional social, ethical Develop and apply innovative
and communication skills in an industry strategies and processes in project
setting, and manage ambiguity and management
complexity in real-world settings.
CLO4 Communicate findings and the rationale of Communicate effectively with all
design solutions to the full range of stakeholders
stakeholders.
CLO5 Review, analyse, consolidate, and
synthesise information in order to
respond to project management
issues;

Developed by Dr Sue Foster 02/02/2017

 9
FIT5057 _Assignment 1_Semester 1, 2017

10. Marking Criteria

Project teams should be aware that the final assignment mark will reflect the marking criteria
shown below. Please note a more stringent and comprehensive marking guide will be followed
by your tutors.

HD A comprehensive coverage of the topic

80-100 Excellent structure – easy to follow, headings used effectively
This is an Excellent supporting evidence and critical assessment, clear explanations,
outstanding flow from one point to the next in logical sequence
assignment Higher level considerations
Sound and useful strategies and/or issues provided supported by evidence
References correctly cited in body of text and in list
References include a variety of sources: journal, texts, book chapters and
whitepapers - no more than 5 references should come from
APPROPRIATE internet* sources
Excellent grammar, spelling, neatly and consistently presented in line with
the business case structure provided in the assignment.
D A very good coverage of the topic with a good level of supporting evidence;
70-79 critical assessment evident, reasonably clear explanations, logical
sequencing used
Some additional considerations offered
Good use of strategies and/or issues provided, supported by evidence
References used correctly in body and in list
Good grammar, minimum spelling errors, neatly presented and presented
in line with the business case structure provided in the assignment.
C A reasonable coverage of the topic with some level of supporting evidence.
60-69 Critical assessment may be demonstrated but is limited in its scope.
Fair to moderate explanations. Sequencing in some logical style.
Some link to strategies and/or issues offered with supporting evidence
(references) but little indepth knowledge displayed.
Referencing used correctly throughout and correspond to the reference list.
Reasonable grammar and spelling, neatly presented and followed the
structure.
P A basic coverage of the topic, all questions answered but little indepth
50-59 knowledge demonstrated indicating lack of reading.
Poor logical sequencing.
Little or no critical analysis attempted. Headings limited.
Some grammatical and spelling errors – basic presentation
Referencing limited or inappropriate reference sources
Referencing style incorrect or inappropriate
References listed do not correspond to those shown in the report.
NP Insufficient coverage of the topic or the content did not cover the topic.
<49 No evidence of additional reading.
This is a very Absence of critical analysis.
poor Poorly organised and displayed.
assignment Less than acceptable grammar and spelling.
Insufficient and incorrect referencing
* Internet referencing are those references that are identified solely through the internet – these are not classified
as e-journals. Internet sources need to be assessed carefully. White papers are an accepted resource but again
the depth of information contained within should provide value and should come from a trusted internet source. For
example, Gartner, IBM, SAP, Forrester. If unsure email either myself or your tutors for clarification.
Computerworld, Newsweek and other assorted magazines are not acceptable reference material for this type of
academic paper.

Developed by Dr Sue Foster 02/02/2017

 10
FIT5057 _Assignment 1_Semester 1, 2017

11. Referencing: Please Note:

If you DO NOT reference in the body but have an extensive reference list at the back of your
assignment, the assignment will not be marked and will be sent back for you to complete.

1 Acknowledgment of sources
IT plagiarism policy: each time you complete any assessment, please refer to and make
yourself familiar with the most current information regarding acknowledgement of sources,
plagiarism and academic conduct contained in the FIT Policy website.
http://www.infotech.monash.edu.au/resources/student/assignments/policies.html

2. Assignments
2.1 Standards for presentation – Style Guide
All printed assignment work must be word processed and meet the standards set out in the
assignment. Refer to the following URL for writing assignments and for referencing styles:
http://intranet.monash.edu.au/infotech/resources/students/style-guide/index.html

2.2 Assignment submission procedure: all assignments must include an appropriate signed
CaSIT assignment cover page. Located at:
http://www.infotech.monash.edu.au/resources/student/assignments/

2.3 Extensions
This is a group assignment. If one member should fall ill and is not able to complete their
task(s) on time, this should not delay the assignment past its due date; therefore the other
team members will be expected to complete the assignment by the due date. Please DO
NOT contact your tutors or myself requesting an extension.
However, should you apply for an extension prior to the due date, then all applications for
extensions must be made in writing to your lecturer. Medical certificates or other
supporting documentation are required.

Developed by Dr Sue Foster 02/02/2017