ITEC841 Project Management: MS Project and Case Study, Semester 1 2019

This document presents a comprehensive solution to a project management assignment, focusing on the application of MS Project to a case study. The solution includes a detailed task breakdown with durations, predecessors, and resource allocation, culminating in a project schedule and network diagram. It identifies the critical path, calculates slack times for various activities, and provides a spending analysis, including total project expenditure and weekly cash flow projections. The solution also addresses resource management, pinpointing peak usage periods for designers and programmers. Part B delves into risk management, identifying potential risks such as external attacks, data loss, and scope creep, along with corresponding treatment strategies. Finally, it discusses the suitability of MS Project for baseline project plan development and offers advice on structuring the project for effective use of the software. Desklib is a platform where students can find a wide array of study resources including similar assignments and past papers.

Running Head: PROJECT MANAGEMENT
ITEC841: Project Management
Name of the Student
Name of the University

1PROJECT MANAGEMENT
Part A
Answer to Question 1
Task Name Duration Start Finish Predecessors Resource Names
ABC Development
Company Project
27 wks Mon 4/8/19
Fri
10/11/19
Task 1 1 wk Mon 4/8/19 Fri 4/12/19
Designer[300%],
Programmer[300%]
Task 2 2 wks
Mon
4/15/19
Fri 4/26/19 1
Designer,
Programmer
Task 3 1 wk
Mon
4/15/19
Fri 4/19/19 1 Programmer
Task 4 2 wks
Mon
4/15/19
Fri 4/26/19 1 Designer
Task 5 2 wks
Mon
4/15/19
Fri 4/26/19 1
Designer,
Programmer[200%]
Task 6 3 wks
Mon
4/29/19
Fri 5/17/19 2
Designer,
Programmer
Task 7 7 wks Mon Fri 7/5/19 3,6 Designer[200%]

2PROJECT MANAGEMENT
5/20/19
Task 8 2 wks
Mon
4/29/19
Fri 5/10/19 4 Programmer
Task 9 4 wks
Mon
4/29/19
Fri 5/24/19 5 Programmer
Task 10 6 wks
Mon
4/29/19
Fri 6/7/19 5 Designer
Task 11 1 wk Mon 7/8/19 Fri 7/12/19 7,8 Programmer[200%]
Task 12 1 wk
Mon
5/27/19
Fri 5/31/19 9
Designer,
Programmer
Task 13 3 wks
Mon
6/10/19
Fri 6/28/19 10
Designer[200%],
Programmer
Task 14 2 wks
Mon
7/15/19
Fri 7/26/19 11 Programmer[200%]
Task 15 3 wks Mon 6/3/19 Fri 6/21/19 12 Designer
Task 16 4 wks Mon 7/1/19 Fri 7/26/19 13
Designer,
Programmer
Task 17 3 wks Mon Fri 8/16/19 14 Designer[200%]

3PROJECT MANAGEMENT
7/29/19
Task 18 5 wks
Mon
7/29/19
Fri 8/30/19 16 Programmer
Task 19 4 wks Mon 9/2/19 Fri 9/27/19 15,18
Designer,
Programmer
Task 20 2 wks
Mon
9/30/19
Fri 10/11/19 17,19
Designer,
Programmer
Answer to Question 2
The critical path is Task 1  Task 5  Task 10  Task 13  Task 16  Task 18  Task
19  Task 20.
Figure 1: Network Diagram of th Project
(Source: Created by Author)

4PROJECT MANAGEMENT
Answer to Question 3
The finish date of the Project is 11th October 2019.
Answer to Question 4
The activities are listed as follows.
Activity Free Slack Duration
Task 3 4 weeks
Task 8 8 weeks
Task 15 10 weeks
Task 17 6 weeks
Answer to Question 5
The spending is listed as follows.
Activity Spending
Task 1 $24,000
Task 5 $22,400
Task 8 $6,400
Task 12 $8,000
Task 19 $32,000
Answer to Question 6
The total project expenditure is $419,200.
Answer to Question 7
The cash flow for each week is as follows.

5PROJECT MANAGEMENT
Week Cash Flow ($)
Week 1 24000
Week 2 27200
Week 3 24000
Week 4 19200
Week 5 19200
Week 6 16000
Week 7 17600
Week 8 22400
Week 9 19200
Week 10 27200
Week 11 27200
Week 12 22400
Week 13 17600
Week 14 14400
Answer to Question 8
The peak usage of D is 40 hours and the peak usage of P is 32 hours.
The peak usage of D occurs in June 10-16 and June 17-23.
The peak usage of P occurs in April 15-21.

6PROJECT MANAGEMENT
Part B
Answer to Question 1
The risks are identified as shown in the following table.
Sources Problems Consequences Treatments
External attacks External agents like
hacks might break into
the electronic health
record
The attacks may result
in stealing and misusing
personal information of
the patients
Use strong firewall and
restrict database access
in the health record
system
Change in Data The database cannot
update itself
automatically
Inaccurate information
may remain stored
The data has to be
manually updated at a
constant basis
Data Loss During migration from
paper document to
EHR, some important
information may be
destroyed or lost
Valuable patient
diagnosis data can be
destroyed resulting in
wrong treatment
Keep a spare copy of
paper documents for
verification while
downloading data from
EHR
Patients The patients may not
trust the EHR
Patients will not agree
to use the EHR for
keeping medical records
Promote the use of EHR
and assure patients that
the data will be
completely safe
Additional and
unwanted costs
The implementation of
EHR may result in
various unwanted costs
Budget overshoot Ensure there is
sufficient funding
before proceeding with

7PROJECT MANAGEMENT
the project
Project scope Scope creep and lack of
control during project
Schedule overshoot Prepare appropriate
project plan before
proceeding with the
project
Answer to Question 2
The baseline project plan for this project cannot be ideally developed using MS Project
because there are several different branches of the project that act differently and do not have
dependencies with each other. MS Project can only develop a baseline project plan when the
activities are continues and linked with each other.
The advice to David Worthington is to divide the total project into different sub-projects
can be treated as separate projects. Accordingly, MS Project can be used to develop baseline
project plan for the projects separately.

8PROJECT MANAGEMENT
Bibliography
Binder, J., 2016. Global project management: communication, collaboration and management
across borders. Routledge.
Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach.
Routledge.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.