Introduction

Healthy Living Pte. Ltd. (HL) is one of the leading nutrition, health and wellness multinational
companies, based in Singapore with its global IT shared services known as Global IT Services
(GITS) located in Malaysia has embarked on a new project to its enhance supply chain
operations. The first wave will be concentrated to South East Asia and the implementation will
be deployed by markets.

Selected Methodology
There are different types of methodologies for the project management. Some of the
methodologies are Agile methodology, Scrum, Waterfall, RAD (Rapid Application Development)
and so on. To implement suitable methodology, there are some criteria for each methodology. In
Waterfall methodology, the requirements are fixed and the process is carried out step by step. In
Agile methodology, the change in requirements are adopted. RAD methodology is agile
approach. In this method, the system is developed within short period of time and this method
also adopted change in the requirement. Scrum is also agile approach to develop a product and it
uses frequent feedback and collaborative decision making.

Scrum is the empirical process in which the team members are actively involve in the process
and allows the team members to respond efficiently and effectively. In this method, the time and
cost are in an effort in order to control the requirement. It consists of different components like
sprint backlog, product backlog, and feedback cycle. After the preparation of sprint backlog, the
process is carried out. The product log consists of feature of the product or system. and after the
completion of the product the product is send to stakeholder for feedback. Scrum consists of
three roles, they are Product owner, Scrum master and Team. Product owner is the person who
have right to take decision related to product and work with team every day to provide guidance
related to product. Scrum master is the one who represent the team and the team is responsible
for the delivery of the product. [ CITATION Sli11 \l 1033 ]

Among different methodology, Scrum is suitable methodology for “Global Supply Chain
Management Project”. Before starting the development process, the sprint backlog and product
backlog is prepared by the help of stakeholder. So that, there is control on the requirement of
product and completed within fixed time and fixed cost. Product owner is present to provide the
proper guidance to team related to the product and Scrum master is the one who while take the
responsibility of the team. Each member of team is responsible for prepare a daily report about
the progress of committed tasks. The team are led by both Product Owner and Scrum Master. In
this methodology, there are daily meeting to assign the task and to check the progress of task. To
track the progress, task board is prepared which is divided into three parts i.e. To Do, Doing and
Done. Team call the stakeholder to check whether the product consists of all the features or not
and to provides the feedback after completion of each sprint. The feedback from stakeholder is
added to backlog by the Product Owner. And the team check out the task which is done well and
which need to be improved. In this way, the process is carried in order to complete “Global
Supply Chain Management Project”. [ CITATION Sli11 \l 1033 ]
Project Charter
Project Charter
Project Title Global Supply Chain Date of 14th Feb 2018
Management Project’ Authorizatio
(GSCMP). n
Project Start 14th Feb 2018 Project End 14th May 2018
Date Date
Key Schedule Milestones: Completion of first sprint or prototype within 4 to 5 weeks. And
the complete product by 14th May.
Budget Information: The budget for completion of this project is about $ 1 hundred thousand.

Project Manager Mahesh Prajapati, +977 9860749777,

mahesh.prajapati@lbef.study.edu.np
Project Objective
 To provides all functions which is found in typical supply chain management software
 To support centralized data warehouse with business intelligence.
 To cover function likes transportation management, order management, yard
management, etc.

Main Project Success Criteria: The  system  must meet  all  the  criteria  of requirement,  the

system   should   test   thoroughly,   and   be   completed   on   time.   The   primary   stakeholders   will

formally approve the project with certain advice.
Approach: To develop the scope statement along with work break down structure, and Gantt
chart which clearly show the tasks that should be complete in order to complete the project
within the time. After purchasing required software and to arrange every week meaning with
project team member and primary sponsor to discuss about progress.
Roles and Responsibilities: Sponsor
Project Manager: Manager
Subject Matter Experts(SME): Team Member
Tester: Team Member
Programmers: Team Member
Scope Management
Scope refers to all the work involved in creating the products of the project and the processes
used to create them. The main concerned for this scope management is to manage the project
scope and controlling what is and is not included in the project. To perform that, scope
management consists of different process which required to ensure that the project consists all
the work that are required and only the work required to complete the project successfully. Scope
management consists of different process like collect requirement, define scope, create WBS,
verify scope and control scope. There may be two types of scope i.e. Product scope and Project
scope. The product scope characterized the product and the project characterized the factors,
need that should require to deliver the product.[CITATION AGu \l 1033 ]

Scope Statement
The scope statement is agreement between the project team, the project sponsor and key
stakeholders. It includes relating the project to business objectives and defining the boundaries of
the project in multiple dimensions including approach, deliverables, milestones and budget. The
Scope Statement of “Global Supply Chain Management Project” was stated after the different
process. To find out the scope of the proposed system, the document was review. After that
brainstorming was done among team member in order to find out the correct scope.
The Scope statement of the proposed system are:
 The system consists of all the functions that are commonly found in every typical Supply
Management software.
 The system which will helps to take a quick decision in managing inventory due to use of
business capabilities in system.
 The system covers transportation management, order management, yard management, labor
management and warehouse optimization.

Work Breakdown Structure

Work Breakdown Structure (WBS) is the process in which the main task is divided into sub task
so that it can be manage properly. The WBS for the proposed project is given below:
Task Name
1. Initiating
1.1 Assigning the project manager.
1.2 Identifying key stakeholders.
1.2.1 Primary Stakeholders
1.2.2 Secondary Stakeholders
1.2.3 Tertiary Stakeholders
1.2.4 Facilitating Stakeholders
1.3 Business Case
1.3.1 Introduction
1.3.2 Business Objectives
 1.3.3 Current Situation and Problem Statement
1.3.4 Preliminary Project Requirements
1.3.5 Budget Estimate
1.4 Project Charter
2. Project Plan
2.1 Scope statement.
2.1.1 Scope Planning
2.1.2 Scope Definition
2.1.3 Work breakdown structure (WBS).
2.1.4 Scope Verification
2.2 Time Management
2.2.1 Gantt Chart
2.2.2 Network Diagram
2.3 Cost Management
2.3.1 Cost Estimation
2.3.2 Budgeting
2.4 Quality Management
2.4.1Quality Planning
2.5 Human Resource Management
2.5.1 Human Resource Plan
2.6 Communication Management
2.6.1 Stakeholder Analysis
2.6.2 Communication Channel
2.7 Risk Management
2.7.1 Risk Management Process
2.7.2 Risk `Management Plan
2.7.3 Risk Analysis
2.7.4 Risk Response Plan
2.8 Procurement Management
2.8.1 Procurement Plan
2.9 Stakeholder Management
2.9.1 Stakeholder identification
2.9.2 Stakeholder Management Plan
3. Execution
3.1 Requirement Gathering
3.1.1 Document Review
3.1.2 Brain Storming
3.2 Data Refining
3.2.1 Stakeholder Identification
3.2.2 Primary Stakeholders
 3.2.3 Secondary Stakeholders
3.2.4 Tertiary Stakeholders
3.3 Preliminary Approval
3.4 Execution Change
3.4.1 Change Request
3.4.2 Change Request Approval
3.5 Business Approval
3.6 Functional & Technical Specification
Development
3.6.1 System Requirement Gathering
3.6.2 Technical Requirement
3.6.3 Software Requirement
3.7 Application Development
3.7.1 Design System
3.7.2 Coding
4 Project Monitoring and Controlling
4.1 Scope Verification and Change Control
4.2 Schedule Control
4.3 Cost Control
4.4 Quality Control
4.4.1 ADC Testing
4.4.2 IT Regression Testing
4.4.3 User Acceptance Test(UAT)
4.5 Performance Reporting
4.6 Risk Control
4.7 Contract Administration
4.8 Complete Monitoring and Controlling
Phase Review
5 Project Closing
5.1 Project Review Meeting
5.2 Lessons Learned Report
5.3 System Setup
Table 1: Work Breakdown Structure
Time Management
Time Management is the process to manage the time for the completion of project. In the time
management, activities are defined, make the sequence of activities, estimate resources for
activities, estimate the time for those activities and develop a schedule for completion of all task.
For each activities a group or a person is assigned as per the requirement of project. For the time
management of proposed system, firstly the activity is defined then those activities are scheduled
then tools and technique were selected to show the proper implementation of all activities. The
process is described below;

Define Activities

Defining the activities is the first phase of planning process in the time management. All
activities are listed that should be carried out through the development process of the system.
These activities are enlisted by the help of team members and the feedback provided by the key
stakeholder during the approval of project charter.

Scheduling

After the activities were defined then those activities are schedule in sequenced so that it will be
easier to find out the dependencies and precedence, as well as it helps in time estimation and
estimated the resources for the certain activities.

Tools and Techniques

After scheduling the activities in the sequence, the proper tools and technique are to be selected
in order to represent the task along with time estimation and resource estimation. Then
dependency of tasks was located then leads and lags were determined. That mean the relationship
between different tasks defined which is possible. After the dependencies and the relation
diagram were determined, the network diagram is scheduled. To show these dependences, and
relationship, Gantt chart was selected as a tool.
Cost Management

Gantt Chart
Network Diagram

Cost Management
Cost Estimating
Cost Budgeting

Quality Management
Quality Management Plan

Administrative Closure Procedure

Lesson Learned Report
References
fourth ed., n.d. A Guide To The Project Management Body of Knowledge. Fourth Edition ed.
Atlanda,USA: Project Management Institute, Inc..
Sliger, M., 2011. Agile Project management with Scrum. North America, Dallas,TX. Newtown
Square, PMI Global Congress 2011.