PRMGT Assignment Question Marking Scheme
PRMGT Assignment Question Marking Scheme
CT050-3-3-PRMGT-Project Management
Incourse Assignment
Company : Innovative Wellbeing Pte. Ltd. (IW)
Project : Global Supply Chain Management Project (GSCMP)
I. Learning Outcomes
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 decentralisation 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 centralising 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.
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.
3. there is no evidence that a proper project management process was followed.
4. the PC and server hardware technical specifications were constantly being changed to suit new or added
requirements.
5. requirements keep coming in from users almost daily where the GITS-ADC Team Lead keeps on accepting
them without hesitation.
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.
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.
8. tasks are performed without prioritising other dependent tasks.
9. IT assets acquisition and spending were through PROC Manager with suppliers without going through a
proper tendering process.
10. purchasing of IT assets without a proper tendering process has led to overrun by budget.
11. the testing plan was not developed yet.
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.
14. the Project Manager’s authority was constantly overridden by the department head /managers.
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.
17. the risks associated with the project, although documented, had no detailed action plans and were not
categorised in terms of impact or severity.
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.
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:
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.
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.
V. Assessment Details
The main contents should cover a detailed group discussion on processes, tools and techniques as
follows:
a) Comparative Analysis
PMBOK
PRINCE2
AGILE
b) Project Charter
BOSCARD
Milestones
c) Stakeholder Register
d) Project Kick-off
Meeting Agenda
Breakdown of marks:
a) Aligning Projects Process Groups with Business Strategies – 25%
Comparative Analysis – Establishing the appropriateness level of different project management
standards
Project Charter – Connecting the ideas to the case study therefore fulfilling business needs and
objective
b) Initiating Projects – 25%
Project Kick-off – Meeting agenda required and a brief explanation of how this is crucial to initiate
projects
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 – 50% (SUBMISSION – WEEK 12)
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 according to the project lifecycle
Breakdown of marks:
a) PMBOK Standards – 25%
Proposed tools are according to PM standards and explaining the reliability of the solutions proposed
b) Planning, Executing, Monitoring & Controlling and Closing Projects – 25%
Solutions provided from identified issues are covered accordingly within these processes and to
ensure more than one process is covered
This assignment is worth 40% (20% - Individual & 20% - Group) of the final grade. Assignment will be
handed-out by Week 2 and to be handed-in by Week 6 & Week 12.
The criteria below detail the areas, which will be taken into account when the assignment is marked:
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.
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
CT050-3-3-PRMGT-Project Management
Incourse Assignment – Marking Scheme
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
Assignment
typical IT project (A4, PLO8)
Practise project management leadership to solve complexity in project using Individual
CLO3
PMBOK standards (A5, PLO9) Assignment