Fundamentals of Project

Management (PMGT 701-104)

By: Man Dinh Trac and Lalit

Bhartola
For: Prof. Tayfun Akkus
Fourth Party Logistics- Trading Solutions
Corporation
December 2,

Contents
Introduction Business Case
Work Breakdown Structure (WBS)
Project Stakeholder Management
Project Scope Management
Project Schedule Management
Project Cost Management
Project Quality Management
Project Human Resources Management
Project Communication Management
Project Risk Management

 Background:

Business Case

Trading Solutions Corp. provides consulting solutions using its vast network of

global network and system for supply chain management, custom clearance,
forwarders, transportation, insurance and risk management.

Objectives: To help customers reduce 10% shipping cost, 5% inventory cost and
17% fixed cost.

Budget: $9.5 million incurred (mostly project members salaries and training cost)
Roles and Responsibilities:Name

Position

Project Role

Contact Information

Brian

Share Holder

Project Sponsor

brian@trading solution.ca

Ji Sung

Project Manager

Project Manager

jisun@trading solution.ca

Lalit

Team leader

Hardware

lalit@trading solution.ca

Mandinh

Team leader

Software

mandinh@trading solution.ca

Park

Team leader

Testing

park@trading solution.ca

WBS

Management

Project Scope Management

Product Description

Project Deliverables
User Acceptance Criteria
Boundaries/ Exceptions
Constraints
Assumptions

Project Schedule Management

Gantt Chart

Project Cost Management

Project Quality Management

45

40

Defects

Number
of Defect

Percentage of
Defect

System Slow

15

32%

Error in Log In
Inaccuracy in
System
Internet Issue

10

21%

4%

20

43%

Total

47

100%

35

30

25

20

15

10

Number of defect
Percentage of Defect

Project Quality Management

Project Human Resources Management

Project Communication Management

Stakeholders

Document Name

Document
Format

Contact Person

Project Manager

Kick-off meeting

Hard copy

Ji Sung

Project Manager

Closing Report

Hard copy

Ji Sung

Project Manager

Monthly Status Report

Hard copy

Ji Sung

Hardware Team Leader

Bi-weekly Status Report

Hard copy

Lalit

Software Team Leader

Bi-weekly Status Report

Hard copy

Mandinh

Testing Team Leader

Bi-weekly Status Report

Hard copy

Park

Hardware Team members

Weekly Status Report

Hard copy

Sr. Executive

End of the Week

Software Team members

Weekly updated
Software implementation
plan

E-mail

Sr. Executive

End of the Week

Testing Team members

Weekly updated Training

and Testing plan

Hard copy

Sr. Executive

End of the Week

Due Date
End of First week
of project
At the end of the
project
At the beginning
of the month
End of the
Bi-Weekly
End of the
Bi-Weekly
End of the
Bi-Weekly

Project Risks Management

No

R1

Rank

Risk

Description

HR risk

Risk occurred due to

the inability to find the
skillful employees to
work with the new
system

System
R2

R3

R4

Protection
risk

Risk occurred when the

customer's system is not
highly protected from
virus and easily be
violated the privacy and
confidentiality of the
company.

Software risk

Risks occurred when

the current system of
customer is not
compatible with the
new software.

Hardware
risk

Risks occurred when

customers' current
computers cannot
support to operate the
new software.

Category

People

Root Cause

Triggers

The customer
It's harder to train
organization can't hire
and may delay the
the right person for the
process of the project.
training

Technology

Customers system is
weak in technology.

The project team

didn't recognize the
situation beforehand.

Technology

The current system is

too old and not up-todate.

The software team

didnt recognize the
problem.

Technology

The hardware system

is too old and not upto-date.

The project team

didn't recognize the
situation beforehand.

Project Risks Management

No

Potential Responses

R1

Be more patient in training, providing

more detailed information and willing
to answer each and every question the
customer has; may put extra effort in
training.

R2

It's important to check carefully before

installing the new software whether the
customer's current system is fully
Project Manager
protected. Double check on the current
system before installing the new
software.

Project Manager

Software team
leader

R3

R4

Risk Owner

Check and test the trial before actually

installing the new software on the
current computer.

Hardware team
leader.

Probability

High

High

Medium

Medium

Impact

Status

High

Will have a formal meeting to

explain the issue with the
customer

High

In case of the risk actually

happens, meet with customers
to inform them about the issue
and discuss for solution.

Medium

In case of the risk actually

happens, meet with customers
to inform them about the issue
and discuss for solution.

Medium

In case of the risk actually

happens, meet with customers
to inform them about the issue
and discuss for solution.

Thank
you!