CT050-3-3-PRMGT-Project Management Page 1 of 10

CT050-3-3-PRMGT-Project Management
Incourse Assignment
Company : Innovative Wellbeing Pte. Ltd. (IW)
Project : Global Supply Chain Management Project (GSCMP)

I. Learning Outcomes

Explain the fundamentals of IT project management processes, lifecycle a typical

CLO1 Exam
IT project into manageable components (C5, PLO2)
Adhere a project management plan using the aims and objectives, deliverables, Group
CLO2 scope and appropriate standards through tools and techniques within processes of a Assignmen
typical IT project (A4, PLO8) t
Individual
Practise project management leadership to solve complexity in project using
CLO3 Assignmen
PMBOK standards (A5, PLO9)
t

II. The Scenario (A Case Study)

Innovative Wellbeing Pte. Ltd. (IW) 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 enhance its supply chain operations. The first wave
will be concentrated to South East Asia and the implementation will be deployed by local markets.

At present, markets located throughout South East Asia are using locally developed application to record
supply chain management activities information. The first-level support (L1) is being rendered by local IT
and second level (L2) is supported by the local application vendor.

Previously the cost for software support maintenance was managed locally within each market which has
resulted high in IT cost for both capital and operating expenses. Unfortunately, every market provides similar
support framework which has created duplication among markets within the South East Asia Region due to
decentralization of systems being used. Thus, by implementing this project, significant contribution such as
reduction in capital/operating expenses, centralized support from GITS, global governance and many more
value added are gained. Please refer to section VII, Table 1 for the list of departments directly and indirectly
involves in this project.

Due to the urgency for centralizing support and cost reduction, the project was scheduled to be
completed within duration of 6 months from the date of commencement. The project is named as
‘Global Supply Chain Management Project’ (GSCMP).

This is a critical and complex project which involves various department including subject matter
experts (SME(s)) from GITS. A Project Manager was hurriedly assigned from GITS-PMAC who has a
good working knowledge of the various regional office locations. The current Project Manager
portrays strong ‘global/regional project management’ and ‘technical’ skills. However, he lacks
leadership qualities and interpersonal skills.

Level 3 Asia Pacific University of Technology and Innovation January 2020

CT050-3-3-PRMGT-Project Management Page 2 of 10

In addition to a good project management practices, the following are some of the major critical success
factors (CSF) the Project Manager must comply for the success of the project:-

a) capable resources would be selected from any of the SME-departments as shown in the organisation
structure provided in section VII, Table 1
b) the current IT infrastructure must support this new system
c) the current system must be replaced in phases by GSCMP.
d) the cutover (transition from the current system to new centralised system) must be in parallel

(Note: Although the major milestones for the project are provided in section VIII, Table 2, Project
Manager is required to expand the detail activities/tasks for respective milestones if necessary.)

As the project progressed, it was meeting its ‘high-level’ milestones for the first two (2) months, and
with four (4) months left, it was now deemed as ‘failing to meet its target dates’, ‘not doing what it was
supposed to do’ and was ‘unreliable’. At this point also a few startling issues surfaced, as follows:

1. the steering committee (which consist of the board of directors, CEO and Senior Managers of the
organisation) do not recall of being presented the project feasibility study by the Project Sponsor or the
Project Manager to them.

2. the project approval was not formally documented. – no project charter, a document to formalize project

3. there is no evidence that a proper project management process was followed. – no proper methodology
followed

4. the PC and server hardware technical specifications were constantly being changed to suit new or added
requirements. -many scope changes

5. requirements keep coming in from users almost daily where the GITS-ADC Team Lead keeps on
accepting them without hesitation. -scope changes are incorporated

6. there was redundancy of work performed as the Work Breakdown Structure (WBS) was done separately
by each respective department and the Project Manager did not review and then consolidate those WBSs
into one holistic WBS. -redundant of scope of work

7. most of the team members have been focusing more on their daily operation support rather than tasks
being assigned by the Project Manager or their respective Team Lead. -people management issue and
task priority issues

8. tasks are performed without prioritising other dependent tasks. -time management

9. IT assets acquisition and spending were through PROC Manager with suppliers without going through a
proper tendering process. -no contract, no proper procurement process were followed

Level 3 Asia Pacific University of Technology and Innovation January 2020

CT050-3-3-PRMGT-Project Management Page 3 of 10

10. purchasing of IT assets without a proper tendering process has led to overrun by budget. -more cost in
buying IT assets

11. the testing plan was not developed yet. – no test cases – in terms app

12. there was not even a clear designated sponsor (or sponsors) for the project.

13. there was no clear project organisational structure to manage the project. -no proper org structure –
matrix, functional or projectized

14. the Project Manager’s authority was constantly overridden by the department head /managers. – 2 bosses
syndrome – depend on the project org struc

15. technical skills were especially lacking in the network and security areas.

16. there were no monitoring reports to review as none were prepared and formally documented. -no progress
report of the project to track the project

17. the risks associated with the project, although documented, had no detailed action plans and were not
categorised in terms of impact or severity. – no risk assessment map to identify possible risk factors

18. the hardware and software delivery were still being negotiated with some potential vendors while there
were only four (4) months to complete the project. – managing task on time, procurement

Level 3 Asia Pacific University of Technology and Innovation January 2020

 CT050-3-3-PRMGT-Project Management Page 4 of 10

III. Assignment Requirements

As the project is failing and needs to be recovered, you should start by looking into a proper project
management practices with the appropriate processes, tools and techniques.

Besides, the steering committee decided to replace the current Project Manager. As a group of five (5)
members in this group assignment, assuming they have appointed one of you to be the new Project
Manager, and now you are to look at all the 18 issues above (section II) and resolve them using the ten
(10) project management knowledge areas:

1. Project Integration Management

2. Project Scope Management
3. Project Time Management
4. Project Cost Management
5. Project Quality Management
6. Project Human Resource Management
7. Project Communication Management
8. Project Risk Management
9. Project Procurement Management
10. Project Stakeholder Management

Your team should aim to make your report interesting and engaging, without losing sight of the fact that the
organisation is seeking a professional approach to the problems. All analysis should thoroughly illustrate and
document the pressing need to recover a failing project. Avoid theoretical discussions. Apply the theories to
solve the problems.

Assumptions can be made to assist in ascertaining the solutions, but they must not impair the decision made
on the scope and delivery of the project. – Budget, do costing to come up proper budget, assume budget

IV. Assignment Instructions

As part of a team (maximum of five (5) individuals per group), a single report must be submitted to senior
management. The report should be a formally written document, the contents of which should not exceed
6,000 words (1,000 – group total and 1,000 x 5 – individual), excluding abstracts, tables, appendices, etc.
An electronic copy should also be submitted with the report.

Level 3 Asia Pacific University of Technology and Innovation January 2020

CT050-3-3-PRMGT-Project Management Page 5 of 10

V. Assessment Details

1. A GROUP based report of 1000 words (SUBMISSION – WEEK 7)

This is the part of the report that details your project management awareness of how project
management practices with the appropriate processes, tools and techniques, once introduced, will be
able to manage the project well.

The main contents should cover a detailed group discussion on processes, tools and techniques as
follows:
a) Comparative Analysis
 PMBOK | PRINCE2 | AGILE – compare and contrast in table(bullet form) + further elaborate
the bullet point in documentation
Pmbok derived based on knowledge areas – 10
Prince2 – process oriented rather than knowledge area
b) Project Charter – a document to formalize project
 BOSCARD
 Milestones – key task
c) Stakeholder Register 6-7 people, people who directly or indirectly affected by the project
d) Project Kick-off – what, when, how is discussed and the importance of KO
 Meeting Agenda

Breakdown of Criteria:
a) Aligning Projects Process Groups with Business Strategies
o Comparative Analysis – Establishing the appropriateness level of different project
management standards
o Project Charter – Connecting the ideas to the case study therefore fulfilling business needs and
objective
b) Initiating Projects
o Project Kick-off – Meeting agenda required and a brief explanation of how to initiate projects
o Stakeholder Register – Provides an extensive list with all possible stakeholders and their roles
while relating to their significance in the project kick-off meeting

2. An INDIVIDUAL based report of 1,000 words each (SUBMISSION – WEEK 13)

A detailed discussion on processes, tools and techniques by each member of the group on the mapped
issues segregated amongst each team member as follows:
a) Appropriate mapping of issues to the solutions identified
b) Relation to the case study is crucial.
c) Three selected issues MUST be from at least TWO different Process Groups
d) Each selected issue MUST have proposed solutions from TWO Knowledge Areas

Breakdown of Criteria:
a) PMBOK Standards
o Identify 3 Project Issues from Case Study (Unique to each member of the team) and identify
Tools & Techniques that can resolve the respective project issues
o Map the Tools & Techniques to respective process groups and knowledge areas of PMBOK
Standard
o Analyse and justify your selections of Tools and Techniques

Level 3 Asia Pacific University of Technology and Innovation January 2020

 CT050-3-3-PRMGT-Project Management Page 6 of 10

b) Tools & Techniques Samples

o Provide sample of the tools & techniques selected for each issue addressed which should
relate to the assignment case study. Empty templates are NOT accepted and DO NOT just
copy and paste off the internet.

VI. Assignment Assessment Criteria

The criteria below detail the areas, which will be taken into account when the assignment is marked:

1. Distinction assignments exhibit comprehensive research with detailed evidence.

 High level of analysis performed, exceptional and thorough knowledge and understanding displayed
with regard to application. This includes analysis and evaluation of facts followed by results of
evaluation.
 Documentation presented in a professional manner, following proper sequencing and flow. Displayed
evidence of critical appraisal.
2. Credit assignments demonstrate adequate research conducted with fair detail of evidence presented.
 Moderate level of understanding, analysis and knowledge displayed.
 Some level of relevance included in terms of application.
 Moderate level of analysis and evaluation of facts followed by results comparison. Good level of
documentation presented.
 Some level of reflection was evident in the documentation.
 Moderate level of critical appraisal.
3. Pass assignments show low level research conducted.
 Some evidence of research displayed.
 Basic level of understanding and knowledge analysis displayed.
 Satisfactory level of documentation.
 No evaluation and analysis of facts, no results comparison performed Satisfactory or low level of
reflection displayed.
 No level of critical appraisal demonstrated.
4. You are expected to clearly state any assumptions you make, and support statements and theories by
referencing to appropriate sources.

Attention will be paid to:

 Critical evaluation and discussion. Issues will be dealt with deeper and on an analytical plane, based on
good research - with industry examples, data projections and commentaries.
 Balanced researched materials. Appropriate and different sources which must include sufficient
academic research, not just secondary research from URLs
 Proper referencing and citation. Harvard Referencing is a must. Citation must include, apart from the
normal details, the page number from where the issue for discussion has been taken. (Refer to Handbook
for penalty on plagiarism)

Level 3 Asia Pacific University of Technology and Innovation January 2020

CT050-3-3-PRMGT-Project Management Page 7 of 10

Level 3 Asia Pacific University of Technology and Innovation January 2020

 CT050-3-3-PRMGT-Project Management Page 8 of 10

VII. Global IT Services & Local Market Organisation Structure

To indicate the extent of the project resources and team construction, the table below indicates the
organisation structure for IW local market and Global IT Services.

Support Unit SME-Department Abbreviation SME Responsibility

GITS Communication & Network CNN Provides network services for Local IT/Market
Provide governance for IT security for application
GITS IT Security ITSEC
development, software and hardware

Provide develop application and provide

GITS Application Development Center ADC
application Governance and Intellectual Property.
GITS Project Management Centre PMAC Provide Project Managers to manages projects
Global Provide governance for IT operations, which
GITS IT Operations ITO includes supporting local markets and its business
operations.
Center of Excellence – Enterprise
GITS CoE-ERP Provide L2 Support for CoE-ERP
Resources Planning
Center of Excellence – Customer
GITS CoE-CRM Provide L2 Support for CoE-CRM
Relationship Management
Center of Excellence – Supply CoE-Supply
GITS Provide L2 Support for CoE-SCS
Chain Services Chain Services
Market IT Dept IT IT Manager, Executive #1, Executive #1
MKTG Manager, Executive #1, Executive #2,
Market Marketing Dept MKTG
Executive #3, Sales Rep x 30,
FIN Manager, Executive #1, Executive #2,
Local Market Finance Dept FIN
Clerk#1, Cashier #1
Market Human Resources Dept HR HR Manager, Executive #1, Executive #2
Market Communication Affairs COMM COMM Manager
Market Procurement PROC PROC Manager, Officer x2
Table 1: IW Organisation Structure

VIII. List of activity from previous project implementation from other markets

Immediate
No Major Milestones Estimated predecessor
activity
1 Requirements Gathering 33 0
2 Preliminary Approval 19 0
3 Change Request, CR Approval 10 2
4 Business Approval 6 2
5 Functional & Technical Specification Development 12 1
6 Application Development 52 5
7 ADC Testing 7 5
8 IT Regression Testing 5 6,7
9 User Acceptance Test (UAT) 27 7,8
10 System setup (in Production environment) 1 9
Total Project Cost (in USD) $280,000
Table 2: List of Major Milestones

Level 3 Asia Pacific University of Technology and Innovation January 2020

CT050-3-3-PRMGT-Project Management Page 9 of 10

CT050-3-3-PRMGT-Project Management
Incourse Assignment – Marking Scheme
This assignment is worth 40% (20% - Group & 20% - Individual) of the final grade. Assignment will
be handed-out by Week 2 and to be handed-in by Week 7 (Group) & Week 13 (Individual).

GROUP
MARGINAL
COMPONENTS DISTINCTION CREDIT PASS FAIL
FAIL
(100%)
Comparative Analysis Very good in Good in Average in Poor in No appropriateness
establishing the Establishing the Establishing the Establishing the level of different
(25%) Establishing appropriateness appropriateness appropriateness appropriateness project
the appropriateness level of different level of different level of different level of different management
level of different project project project project standards included
project management management management
standards

Project Charter Well Good in Average in Poor Connecting Not connecting the
establishment of connecting the connecting the the ideas to the ideas to the case
(25%) Connecting the connecting the ideas to the case ideas to the case case study study
ideas to the case study ideas to the case study therefore study
therefore fulfilling study therefore fulfilling business
business needs and fulfilling business needs and
objective needs and objective
objective

Project Kick-off Provide very Good meeting General meeting Poor meeting No meeting agenda
clear meeting agenda developed agenda agenda developed or no
(25%) Meeting agenda required and sufficient developed and developed and brief explanation
agenda required and and a well brief explanation insufficient brief insufficient brief of how this is
a brief explanation of discussed of how this is explanation of explanation of crucial to initiate
how this is crucial to explanation of crucial to initiate how this is how this is the projects.
initiate projects how this is crucial the projects. crucial to initiate crucial to initiate
to initiate projects the projects. the projects.

Stakeholder Register Provides an Good list of all General list of all Poor list of all No extensive list
extensive list with possible possible possible provided with all
(25%) Provides an all possible stakeholders stakeholders stakeholders possible
extensive list with all stakeholders and created and their created and their created and their stakeholders and
possible stakeholders their roles while roles while roles while roles while their roles while
and their roles while relating to their relating to their relating to their relating to their relating to their
relating to their significance in significance in the significance in significance in significance in the
significance in the the project kick- project kick-off the project kick- project kick-off
project kick-off off meeting meeting off meeting meeting
meeting provided

TOTAL MARKS (100%)

Level 3 Asia Pacific University of Technology and Innovation January 2020

CT050-3-3-PRMGT-Project Management Page 10 of 10

INDIVIDUAL
MARGINAL
COMPONENTS DISTINCTION CREDIT PASS FAIL
FAIL
(100%)
Tool & Techniques Very good in Able to identify the Average in Poor in identifying No
Identification identifying the appropriateness in identifying the the appropriateness appropriateness
appropriateness tools & techniques, appropriateness in tools & in identifying the
(30%) Identifying in tools & some from different in tools & techniques and not tools &
the appropriate techniques from process techniques in much from different techniques in
Tools & different process groups/knowledge resolving the process resolving the
Techniques that groups and areas in resolving selected project groups/knowledge selected project
are able to resolve knowledge areas the selected project issues. areas in resolving issues.
respective project in resolving the issues. the selected project
issues. selected project issues.
issues.
Mapping to Well mapped the Good in mapping Average in Poor in mapping Not appropriately
Process Groups & Tools & the Tools & mapping the the Tools & mapped the Tools
Knowledge Areas Techniques to Techniques to Tools & Techniques to & Techniques to
respective respective process Techniques to respective process respective
process groups groups and respective groups and process groups
(10%) Mapping the and knowledge knowledge areas of process groups knowledge areas of and knowledge
selected Tools & areas of PMBOK PMBOK Standard and knowledge PMBOK Standard areas of PMBOK
Techniques to Standard areas of PMBOK Standard
respective process Standard
groups and
knowledge areas of
PMBOK Standard,
appropriately.
Justification Provided very Good analysis and Merely general Limited analysis No evidence or
clear analysis and justification in the analysis and and justification in poor analysis and
(30%) Analyse and justification in selections of Tools justification in the selections of justification done
justify the the selections of and Techniques the selections of Tools and in the selections
selections of Tools Tools and able to relate to Tools & Techniques and fail of Tools and
and Techniques to Techniques and address respective Techniques and to relate to address Techniques to
address respective very appropriate project issues. very little respective project address
project issues. in addressing relations to issues. respective project
respective project address issues.
issues. respective project
issues.
Samples Tools & Provided a clear Provided a good Provided a poor Provided weak Provided very
Techniques sample of the sample of the tools sample of the sample of the tools weak sample of
tools & & techniques tools & & techniques the tools &
(30%) Provide techniques selected for each techniques selected for each techniques
sample of the tools selected for each issue addressed selected for each issue addressed selected for each
& techniques issue addressed which relates to the issue addressed which relates to the issue addressed
selected for each which relates to assignment case which relates to assignment case which relates to
issue addressed the assignment study. the assignment study. the assignment
which should relate case study. case study. case study.
to the assignment
case study.
TOTAL MARKS (100%)

Level 3 Asia Pacific University of Technology and Innovation January 2020