PROJECT MANAGEMENT

(CT050-3-3-PRMGT)
GROUP ASSIGNMENT

GROUP MEMBER

LIYA DAYANA BINTI ISMAIL (TP043725)

NORMAHANIM BINTI ABU HASSAN (TP043719)
RAJA NURUL NASUHA BINTI RAJA AZMAN SHAH (TP043721)
AHMAD ZHILAL FARASGALI (TP044401)

LECTURER’S NAME
MR. KAMALANATHAN SHANMUGAM

HAND-OUT DATE
WEEK 2
HAND-IN DATE
WEEK 6
Table of Content
Introduction
In this research, the students have done research on managing project. The case study for this
research is on one of the leading nutrition, health and wellness multinational, Innovative
Wellbeigh Pte.Ltd that based in Singapore. The project that the students will manage named
as Global Supply Chain Management Project, GSCMP which the duration to complete it is
about six months. Two months already gone and with the four months left, it is failing to meet
the target finished date and failing to do what it supposed to do. The students will act as the
project development team that will identify the appropriate processes, tools and technique to
ensure the project can be manage well such as creating the project charter, the project
management methodology, the stakeholder register and done the meeting kick off before
starting GSCMP.
1.0 Comparative Analysis
PMBOK
A foundation upon which
organization can build
methodologies, policies,
Definitio
procedure, rules, tools and management that focus
n which driven by
technique and life cycle
phases needed to practice
project management
It acts as a guide and
standard for managing
projects in various
Purpose
industries that emphasize
on the processes, tools,
technique and good
practices.
PMBOK mainly emphasis
on initialisation, planning,
execution, control or
Emphasis
monitoring and closing
the project to achieve the
objective of the business
and project.
PMBOK is a knowledge-
Approac
based approach.
h
Focus PMBOK more focus on
PRINCE2
Process-based method
for effective project
on the business
justification.
For the project to
continues to be align
with the business
objectives as it looks in
various perspective by
considering risk,
business case, roles,
stages and others.
PRINCE2 focus on
break down the project
into subcategories,
themes and principle to
make it more
controllable and
manageable.
It is a process-based
approach for project
management.
PRINCE2 focus on Agile focus on delivery
AGILE
Set of management
practices that mainly
focus on software
development project
customer requirement
and continuous
changes
It is a practice for
organization to carry
out software or project
development and
respond to any
changes.
Agile emphasis on
using adaptive
approach for the
software or project
development.
Agile more to people-
based approach rather
than process-based
approach.

the activity which it
describes the activities
required to complete the
project.
PMBOK is plan driven
Key
that drive the project to
driven
be align with the business the project.
objective.
PMBOK does not
Principle contain any official
principles to lead to
project’s success.
In PMBOK, it contents
ten knowledge areas, 49
Contents processes, 132 tools,
technique referenced and
project manager role and
the required skills.
In PMBOK, it focusses
PM Role on the project manager
role and interpersonal
skills.
Table 1: Shows the comparison between PMBOK, PRINCE2 and Agile
delivery the project in the product that high
high quality, meet the quality, meet the
requirement align with customer requirement
the business and customer can request
objectives. changes to the product.
PRINCE2 is business
Customer requirement
case driven that drives
driven being implement
in the project.
This methodology is
There are 12 principle
based on 7 principle
stated by Agile Manifesto
which become the
for project development
foundation of this
success.
methodology to run.
Contain seven
It only stated the 12
processes, 41 activities
principle of agile in the
40 tools and
agile manifesto.
techniques referenced.
Each agile methodology
It focusses on the
defined its own role
project management
involve with the project
team roles.
development.
Critical Analysis

Based on the table above, PMBOK shows that its emphasis on guiding the project manager in
initialisation, planning, execution, control or monitoring and closing the project to achieve
the objective of the business and project [ CITATION Pro173 \l 17417 ]. Meanwhile,
PRINCE2 mainly focus on break down the project into sub task to make it easier manageable
and controllable for the project management team to handle it [ CITATION ILX191 \l
17417 ].. Agile emphasize on adapt the changes in the uncertain environment, customer
feedback and increase the business productivity which can increase the satisfaction of the
customers [ CITATION Den16 \l 17417 ]. In PMBOK, it highlights the project manager role
and skills rather than other members of project management team. Agile and PRINCE2 share
some similarities which both of it is methodology that tell what to do, how to do and others
which is more prescriptive than PMBOK. From the table, it can be concluded that there are
some strength and weakness can be seen in those three project management methods.
PMBOK strength is in the content, it provides wide range of helpful knowledge areas, tools
and technique for the project manager to handle any types of project. In total, there are 132
tools and technique described in the content of PMBOK. For example, in the schedule
management knowledge area list about 33 tools and techniques can be used to handle any
scheduling issue [CITATION Pro171 \l 17417 ].

PRINCE2 advantage to the project management is it can be tailored and implement in any
types of projects that not limited to project scale, organization geography or culture, risk and
others. Agile main key strength by implementing into project, the project management team
can get immediate feedback from the clients as they always need to engage with the customer
to ensure satisfactory and meet their requirement. In weakness perspective, PMBOK
weakness is it mainly focus on project manager which it does not put any guidance for the
project management team responsibilities that might become difficulty for the team to handle
the project even they have a good project manager. For PRINCE2, it does not cover any
leadership and people management skills as it states the role of project management team
only which it may rise issues of lack of skills in doing the project. Agile does not emphasise
on documentation which it is the main weakness of Agile. This is because they too much
focus in development and the documentation tends to get side-tracked that make it difficult
for any new member join to keep up with the other team speed.
2.0 PROJECT CHARTER
2.1 Project Background

Project Name: Global Supply Chain Management (GSCMP)

Project Description

Innovative Wellbeing Pte. Ltd. (IW) is a company based in Singapore and it is one of the
leading nutrition, health and wellness multinational companies. Its global IT shared services
known as Global IT Services (GITS) located in Malaysia. This company has embarked on a
new project which is called ‘Global Supply Chain Management’ (GSCMP) as a way to
enhance its supply chain operations. This project can contribute to the company in reducing
its capital or operating expenses, centralizing support from GITS, global governance and so
on. This effort will be done in order to encounter the problems that the company face which
are high IT cost for both capital and operating expenses, duplication created among South
East Asia markets and the current project manager lacks of leadership qualities and
interpersonal skills.

2.2 Aim and Objectives

2.2.1 AIM
To enhance the company’s supply chain operations by reducing its capital or operating
expenses, centralizing support from GITS, global governance and so on.
2.2.2 OBJECTIVES
 To reduce IT cost for both capital and operating expenses.
 To avoid data redundancy created by ensuring synchronization operation among
markets within the South East Asia Region.
 To avoid decentralisation of systems being used.
 To improve global governance by centralizing support from Global IT Services
(GITS).
 To complete the project within the duration that has been set.
 To ensure that the cutover is successful.
 To maximize profit and minimize waste.
2.3 High-level Scope

Scope-In Scope-Out
Focus on reducing the IT cost, capital
and operational expenses.
Focus on synchronizing operation
among the South East Asia markets.
Focus with developing mobile The development of web based
application only. application.

2.4 Constraints and Assumptions

2.4.1 CONSTRAINTS
The potential constraints of the project is as listed below :-

 The time constraint of the project as the duration is just 6 months with only 4 months
left.
 The cost budget cannot be exceeded as the economy of the company is bad.
 Project Manager is lack of leadership skill and interpersonal skills.
 Restriction on the types of vendors’ equipment that can be used.
 Staffs attitude towards change.
 Project sponsors must be find within the time frame.
 Network
 facilities
2.4.2 ASSUMPTIONS
 Assume that the milestones will be achieve according to its schedule.
 Assume that not all project budget is used by the previous project manager.
 Assume that the team members are highly motivated from the start of the project.
 Assume that not all vendors’ equipment is restricted to be used.
 Assume that staffs are highly motivated and eager towards change.
 Assume that the designated sponsor is identified as soon as possible.
 Assume the project is able to fit in with the current business industry.

2.5 High-level Risk

The potential risks of the system as listed below:-

  As there are no sponsor identified within the time frame, the potential risk is the project
might not be completed within the time frame.
 As cost budget cannot be exceeded, the potential risk is the products might not be the
highest quality.
 As project manager is lack of leadership skill and interpersonal skills, the potential risk
is the team members might not do their tasks within the time frame and this could affect
the project end date.
 As some types of vendors’ equipment are restricted to be used, the potential risk is late
placed orders and internal procurement challenges.
 As staffs are resist to change, the potential risk is the absenteeism rate might be higher
than usual, project delays and productivity declines.

2.6 Deliverables

 Conduct workshop for the staffs and end-users training.

 Proposing organization chart.
 Finalizing budget.
 Finalizing job descriptions.

2.7 Roles and Responsibility

ROLES AND RESPONSIBILITY

No. Name Role Responsibility
1. Normahanim Project Manager The one who is responsible for making
decisions that benefit the project.
Individual who manages the project and
responsible for the successful initiation,
planning, design, execution, monitoring
and closing of the project.
2. Liya Dayana Risk Manager The one who is responsible to perform a
risk assessment by analysing current
risk, predict the risk and find the
solution to overcome the risk.
3. Raja Nurul Nasuha Human Resource The one who oversees the human
resource department and ensure the
 Manager tasks being carried out by the HR team.
Individual who plans, organizes and
control the activities and actions of HR
department.
4. Ahmad Farasgali Procurement The one who chooses the suppliers and
Manager negotiate with the vendors. Procurement
manager also handles all purchasing of
the goods.
5. Ari Staprans Leff Finance Manager The one who manages the transaction
occurs during the project and looking
for cost-reduction opportunities.
6. Corbyn Besson IT Manager The one who manages information
technology and computer systems used
in the project. Individual who controls
and evaluates IT and electronic data
operations.
7. Shawn Mendes System Test The one who build and lead the testing
Manager team. Individual who applies the
appropriate test measurements and
metrics in the product and the testing
team.
2.8 Milestones
2.9 High-level Budget

Cost (RM) Task Name

10,000.00 Initiation Process
30,000.00 Planning Process
200,000.00 Execution Process
20,000.00 Control Process
10,000.00 Closing Process

2.10 Team Operating Principle and Critical Success Factor

2.10.1 CRITICAL SUCCESS FACTOR
The critical success factors for this project is as listed below:-

 Capable resources would be selected from any of the SME-departments.

 The current IT infrastructure must support this new system.
 The current system must be replaced in phases by GSCMP.
 The cutover (transition from the current system to new centralised system) must be
in parallel.

2.10.2 TEAM OPERATING PRINCIPLE

The team should follow certain guidelines as listed below in order to ensure the project is
successful:-

 The team should be productive while working.

 The team should have a good team working by helping one another.
 The team should avoid absenteeism.
 The team members must respect others’ point of view while discussing in meeting.
 The team members must give cooperation and help the project manager in
conducting the project.
2.11 Signature

Therefore, we are authorizing to commence the project.

_________________________ _________________________

Siti Sarah Maidin Normahanim Abu Hassan

(Project Sponsor) (Project Manager)

Date: Date:
3.0 Stakeholder Register

Name Position Internal/ Project Contact

External Role Information
Normahanim Project Manager Internal Top management Normahanim
@gmail.com
Raja Nurul Human Resource Internal functional Rajanasuha@
Nasuha Manager managers gmail.com

Ahmad Farasgali Procurement Internal functional afarasgali@g

Manager managers mail.com
Liya Dayana Risk Manager Internal functional Liyadayana
managers @yahoo.com
Ari Staprans Leff Financial Manager Internal functional Arileff@yaho
managers o.com
Siti Sarah Maidin Project sponsor Internal The sponsor sitisarah@gm
ail.com
4.0 Kick-off Meeting

Global Supply Chain Management Project

Kick-off Meeting

1 Dec 2019

Meeting Objectives:

1. To get the overview of the whole project

2. To get a good start for the project establishment by introducing the key stakeholders
3. To review project goals and risks managements
4. To discuss future plans for the project

Attendees:

 CEO
 Project Manager
 Project Sponsor
 Risk Manager
 Human resource Manager
 Procurement Manager
 Finance Manager
 IT Manager
 System Test Manager
 Project Team Members

Meeting Agenda:
2:00 pm – 2:10 pm Meeting Opening Project Manager
 Review the meeting objectives and the
agenda of the meeting
Team Introduction All Attendees
 Introduce name, role and organization
represented
 Identify the responsibilities and
 contributions for each person
2:10 pm – 2:50 pm Review Project Charter Project Manager
 Review project background and
objectives
 Discuss team organization, funding, risk
managements, project scopes and others.
2:50 pm – 3:00 pm Clarify Roles and Responsibilities Project Manager/
 Project Manager, team leaders, All Attendees
stakeholders
 Review and discuss project guiding
principles
3:00 pm – 3:15 pm Determine Team Communication All Attendees
 Discuss how team will communicate
(meeting platform, frequency of meeting,
meeting attendees and others)
3:15 pm – 3:30 pm Break
3:30 pm – 4:50 pm Develop Project Schedule Project Manager/
 Review and classify requirements to High- All Attendees
and Low-level requirements
 Team leaders identify high level tasks to
be integrated into the project schedule
4:50 pm – 6:00 pm Meeting Close Project Manager
 Ensure the meeting met with the and All Attendees
objectives

List of Action Items from Meeting:

Action Item Assigned To Due Date
 Develop budget allocation for the project Finance Manager 12 Dec 2019
 Get the functional and non-functional IT Manager 12 Dec 2019
requirements for the project
  Decide the possible hardware and software
for the system implementation
 Decide few possible suppliers to be discussed
Procurement Manager 12 Dec 2019
on next meeting
 Identify the possible risk responses that can
Risk Manager 12 Dec 2019
be implemented during project development

Date and time of next meeting: 14 Dec 2019 (2:00 pm – 6:00 pm)
Conclusion

As for conclusion, this assignment really helps the students to have a better
understanding about the project management because the students do analysis, discussion and
brainstorming for the study case that is given by the lecturer. Besides that, the students can
gain new knowledge and experience when doing this assignment. This is because this
assignment allows the students for hands-on experience on project management practices
which the knowledges can be used for their future workplace. This assignment also ensures
that the students to have a clear vision on everything that have been taught by the lecturer in
the class.
References