Project Management Plan for Crayon Pharmaceuticals
VerifiedAdded on  2025/09/06
|22
|2770
|340
AI Summary
Desklib provides solved assignments and past papers to help students succeed.

Project Management
Assessment Item – 1
Student name:
Student Id:
Assessment Item – 1
Student name:
Student Id:
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Summary
The management and organization of the activities in the project are known as Project
Management. For successfully conducting any project, it very essential to carefully plan
everything including resource, cost, time, budget, stakeholders and etc, so that no glitch
occurs on completion of the project. Project management helps in setting the objective of the
project and finds a different action plan to implement that goal. It functions in following five
levels: definition, planning, implementation, maintenance and closure. Using the discipline of
project management helps in increasing the efficiency of the product, improve quality and
increase productivity. In the following report, various aspects of Project Management are
carried out in the given scenario. Before starting any project, it is very important to identify
its functional as well as a non-functional requirement. Next, the report conducts an analysis
of stakeholder matrix, risk matrix, Communication matrix, WBS, Gantt chart, network
diagram, deployment of the project, project Signoff and suggestions.
The management and organization of the activities in the project are known as Project
Management. For successfully conducting any project, it very essential to carefully plan
everything including resource, cost, time, budget, stakeholders and etc, so that no glitch
occurs on completion of the project. Project management helps in setting the objective of the
project and finds a different action plan to implement that goal. It functions in following five
levels: definition, planning, implementation, maintenance and closure. Using the discipline of
project management helps in increasing the efficiency of the product, improve quality and
increase productivity. In the following report, various aspects of Project Management are
carried out in the given scenario. Before starting any project, it is very important to identify
its functional as well as a non-functional requirement. Next, the report conducts an analysis
of stakeholder matrix, risk matrix, Communication matrix, WBS, Gantt chart, network
diagram, deployment of the project, project Signoff and suggestions.

Contents
Summary....................................................................................................................................2
Introduction................................................................................................................................4
Requirements of the Project.......................................................................................................5
Stakeholder Analysis Matrix......................................................................................................7
Communication Matrix..............................................................................................................9
Risk Matrix...............................................................................................................................11
WBS.........................................................................................................................................12
Gantt chart................................................................................................................................14
Network Diagram.....................................................................................................................15
Project Deployment..................................................................................................................16
Project Signoff’........................................................................................................................18
Reviews and Suggestions.........................................................................................................19
Conclusion................................................................................................................................20
References................................................................................................................................21
Summary....................................................................................................................................2
Introduction................................................................................................................................4
Requirements of the Project.......................................................................................................5
Stakeholder Analysis Matrix......................................................................................................7
Communication Matrix..............................................................................................................9
Risk Matrix...............................................................................................................................11
WBS.........................................................................................................................................12
Gantt chart................................................................................................................................14
Network Diagram.....................................................................................................................15
Project Deployment..................................................................................................................16
Project Signoff’........................................................................................................................18
Reviews and Suggestions.........................................................................................................19
Conclusion................................................................................................................................20
References................................................................................................................................21
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Introduction
The following assessment task aims at conducting the Project management Planning and
present proposal for Crayon Pharmaceuticals. The company need project planning and
management for implementing new technologies and solution in the business. The main aim
of their implementation is to transform and expand its business. The company is the retail
seller of medicine and also supply chemical composition and raw materials. The company is
trying to enhance its B2B and B2C solution by including various solutions which are Payroll,
HRM, SAP O2C, Logistics, SCM and Siebel CRM. For successful completion of the project,
the company as recruited various members. The following report is the proposal and
document for project planning.
The following assessment task aims at conducting the Project management Planning and
present proposal for Crayon Pharmaceuticals. The company need project planning and
management for implementing new technologies and solution in the business. The main aim
of their implementation is to transform and expand its business. The company is the retail
seller of medicine and also supply chemical composition and raw materials. The company is
trying to enhance its B2B and B2C solution by including various solutions which are Payroll,
HRM, SAP O2C, Logistics, SCM and Siebel CRM. For successful completion of the project,
the company as recruited various members. The following report is the proposal and
document for project planning.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Requirements of the Project
Project Title - the selected title for the project is the Pursuit of B2C & B2B solutions.
Project Objective – The main purpose of the following project is to develop an efficient
system which carries out the operations of the business and make the processes quicker and
easier.
Project Scope – The system and solution are developed (White & Sholtes, 2016) for Crayon
Pharmaceuticals. The solution will help the organisation to transform the business and will
help the developer and employee to attain maximum productivity.
Expected completion Time – the project is intended to start from 24 September 2019 and
expected to finish within 10 – 11 months.
Expected Budget – the overall costing of the whole (Heinze, 2017) project is expected to be
in the range of $ 50,000 - $ 70,000. The software quality depends on the automated tool and
software used.
Stakeholder name and responsibilities – New members were recruited to implement the
solution. Adam Cunningham as the Program Director, Program Manager is Jake Black; two
project managers were appointed Tom Weilding and Paul McKenna. Other than that
stakeholder includes CEO of crayon, CIO of crayon, General Manager, Retail department,
Logistics department, Supply management, Customer service team and HR team.
Functional Requirement – The activities which will be performed by the system are as
follows:
ï‚· Store data related to medicines
ï‚· Prepare bills of the material order
ï‚· Search the details of the
ï‚· Login and logout process
ï‚· Documentation for using the system and solution
ï‚· Delete, update and modify the details
ï‚· Send alert and notification
ï‚· Confirmation and management of the orders
ï‚· Maintaining details of the customer
Non – Functional Requirement – The non- functional requirement of the following system
is as follows:
ï‚· Reliability - The system will restart if its suspects any malfunctioning. The system will be
protected from the passwords. It will also help in performing many tasks efficiently and
effectively.
Project Title - the selected title for the project is the Pursuit of B2C & B2B solutions.
Project Objective – The main purpose of the following project is to develop an efficient
system which carries out the operations of the business and make the processes quicker and
easier.
Project Scope – The system and solution are developed (White & Sholtes, 2016) for Crayon
Pharmaceuticals. The solution will help the organisation to transform the business and will
help the developer and employee to attain maximum productivity.
Expected completion Time – the project is intended to start from 24 September 2019 and
expected to finish within 10 – 11 months.
Expected Budget – the overall costing of the whole (Heinze, 2017) project is expected to be
in the range of $ 50,000 - $ 70,000. The software quality depends on the automated tool and
software used.
Stakeholder name and responsibilities – New members were recruited to implement the
solution. Adam Cunningham as the Program Director, Program Manager is Jake Black; two
project managers were appointed Tom Weilding and Paul McKenna. Other than that
stakeholder includes CEO of crayon, CIO of crayon, General Manager, Retail department,
Logistics department, Supply management, Customer service team and HR team.
Functional Requirement – The activities which will be performed by the system are as
follows:
ï‚· Store data related to medicines
ï‚· Prepare bills of the material order
ï‚· Search the details of the
ï‚· Login and logout process
ï‚· Documentation for using the system and solution
ï‚· Delete, update and modify the details
ï‚· Send alert and notification
ï‚· Confirmation and management of the orders
ï‚· Maintaining details of the customer
Non – Functional Requirement – The non- functional requirement of the following system
is as follows:
ï‚· Reliability - The system will restart if its suspects any malfunctioning. The system will be
protected from the passwords. It will also help in performing many tasks efficiently and
effectively.

 Usability – The system is developed keeping in mind both the new users and as well as
familiar user.
 Performance – The Solution implements in very little time which is less than 1.5 seconds.
 User Interface – the system should be very friendly and should be understood by the user.
 Operation – All the operations will be managed and controlled by the Program Director.
 Security – The system will be password encrypted and will use two authentication
security systems.
 Supportability – It will be supported by the windows and MAC operating system. The
successful implementation
 Implementation – The solutions are going to be implemented on the i3 processors with 8
GB RAM, 64-bit computer. The various language which will be needed to execute the
solution are as follows: MySQL, Netbeans, Java, HTML, CSS and JavaScript
familiar user.
 Performance – The Solution implements in very little time which is less than 1.5 seconds.
 User Interface – the system should be very friendly and should be understood by the user.
 Operation – All the operations will be managed and controlled by the Program Director.
 Security – The system will be password encrypted and will use two authentication
security systems.
 Supportability – It will be supported by the windows and MAC operating system. The
successful implementation
 Implementation – The solutions are going to be implemented on the i3 processors with 8
GB RAM, 64-bit computer. The various language which will be needed to execute the
solution are as follows: MySQL, Netbeans, Java, HTML, CSS and JavaScript
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Stakeholder Analysis Matrix
Table 1: Stakeholder analysis
Name of
the
stakeholde
r
Power Legitim
acy
Import
ance/
Priorit
y (1 –
5) 1=
highest
, 5 =
Lowest
Interest
( 0- 5)
0=
lowest,
5 =
highest)
Impact Potential Constraint
s
Owner
CEO
High High 1 5 Mediu
m
Increased in
sales margin
and
productivity
Not funding
project, not
approving
agreements
CIO High High 1 4 Mediu
m
The
technicality
of the
solution is
achieved
Not
providing
basic details
Program
manager
High Medium 3 3 High Can achieve
successful
completion
of project
Lack in
managemen
t
Sponsor Mediu
m
High 2 3 High Funding
properly
Funding not
appropriate
Investors Mediu
m
Medium 3 3 High Investing in
sufficient
amount to
Insufficient
funding
Suppliers Low Medium 4 3 Mediu
m
Supplying all
the necessary
item on time
Irregular
supply of
items
Director
of the
program
Mediu
m
High 2 5 High Can achieve
successful
completion
of the project
Lack of
skills
Manager
1
High High 3 5 High Effective
Management
of whole
project
Lack in
skills and
leadership
quality
Manager
2
High High 3 5 High Effective
Management
of whole
project
Lack in
skills and
leadership
quality
Table 1: Stakeholder analysis
Name of
the
stakeholde
r
Power Legitim
acy
Import
ance/
Priorit
y (1 –
5) 1=
highest
, 5 =
Lowest
Interest
( 0- 5)
0=
lowest,
5 =
highest)
Impact Potential Constraint
s
Owner
CEO
High High 1 5 Mediu
m
Increased in
sales margin
and
productivity
Not funding
project, not
approving
agreements
CIO High High 1 4 Mediu
m
The
technicality
of the
solution is
achieved
Not
providing
basic details
Program
manager
High Medium 3 3 High Can achieve
successful
completion
of project
Lack in
managemen
t
Sponsor Mediu
m
High 2 3 High Funding
properly
Funding not
appropriate
Investors Mediu
m
Medium 3 3 High Investing in
sufficient
amount to
Insufficient
funding
Suppliers Low Medium 4 3 Mediu
m
Supplying all
the necessary
item on time
Irregular
supply of
items
Director
of the
program
Mediu
m
High 2 5 High Can achieve
successful
completion
of the project
Lack of
skills
Manager
1
High High 3 5 High Effective
Management
of whole
project
Lack in
skills and
leadership
quality
Manager
2
High High 3 5 High Effective
Management
of whole
project
Lack in
skills and
leadership
quality
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Producers
and
Retailers
Low
Medium
2 4 Mediu
m
Maximising
the sale and
manufacturin
g
Not
manufacturi
ng required
item
Distributo
r
Low Medium 4 3 Mediu
m
Maximising
the sale
Not
properly
distributing
items
Team
member
Low Low 4 2 High Working
properly and
putting
maximum
efforts
Not
working
properly
and
minimum
efforts
Logistics Low Medium 3 2 Low Delivering of
the item on
time
Delaying
the order
and
misplacing
of the order
Consumer Low Low 5 2 High Buying more
and more
items
Not buying
the product
and
presence of
alternative
and
Retailers
Low
Medium
2 4 Mediu
m
Maximising
the sale and
manufacturin
g
Not
manufacturi
ng required
item
Distributo
r
Low Medium 4 3 Mediu
m
Maximising
the sale
Not
properly
distributing
items
Team
member
Low Low 4 2 High Working
properly and
putting
maximum
efforts
Not
working
properly
and
minimum
efforts
Logistics Low Medium 3 2 Low Delivering of
the item on
time
Delaying
the order
and
misplacing
of the order
Consumer Low Low 5 2 High Buying more
and more
items
Not buying
the product
and
presence of
alternative

Communication Matrix
Table 2: Communication matrix
Name of
the
stakeholder
Frequency Format Goal Timings Owner Communication
type
Owner
CEO
Monthly Email, To update
about the
progress of
the project
At the
beginning
of the
project
Program
Manager
Status of report
CIO Monthly Email, In-
person
To discuss
and review
technical
problems
and
solution
At the
beginning
of the
project
Program
Manager
Progress report
Program
manager
Weekly Conference Discuss On
induction
Program
Director
Project Progress
and status report
Sponsor Once in 6
month
Face to face To discuss
the cost
and budget
of the
project
Project
Start
Project
Manager
Steering Board
meet up
Investors Once in 6
month
In-person,
email, call
To discuss
the cost
and budget
of the
project
Project
Start
Project
Manager
Steering Board
meet up
Suppliers weekly On-call To
introduce
the project
During the
project
Project
Manager
Weekly status
report
Director of
the
program
Daily Conference
meeting
Review
and status
of the
project
Ongoing
process
Program
Manager
Team meeting
Manager 1 Daily Conference
meeting
Detailed
progress
report
An
ongoing
process,
during the
whole
project
Program
Director
Task progress
update, project
review
Manager 2 Daily Conference
meeting
Detailed
progress
An
ongoing
Program
Director
Task progress
update, project
Table 2: Communication matrix
Name of
the
stakeholder
Frequency Format Goal Timings Owner Communication
type
Owner
CEO
Monthly Email, To update
about the
progress of
the project
At the
beginning
of the
project
Program
Manager
Status of report
CIO Monthly Email, In-
person
To discuss
and review
technical
problems
and
solution
At the
beginning
of the
project
Program
Manager
Progress report
Program
manager
Weekly Conference Discuss On
induction
Program
Director
Project Progress
and status report
Sponsor Once in 6
month
Face to face To discuss
the cost
and budget
of the
project
Project
Start
Project
Manager
Steering Board
meet up
Investors Once in 6
month
In-person,
email, call
To discuss
the cost
and budget
of the
project
Project
Start
Project
Manager
Steering Board
meet up
Suppliers weekly On-call To
introduce
the project
During the
project
Project
Manager
Weekly status
report
Director of
the
program
Daily Conference
meeting
Review
and status
of the
project
Ongoing
process
Program
Manager
Team meeting
Manager 1 Daily Conference
meeting
Detailed
progress
report
An
ongoing
process,
during the
whole
project
Program
Director
Task progress
update, project
review
Manager 2 Daily Conference
meeting
Detailed
progress
An
ongoing
Program
Director
Task progress
update, project
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

report process,
during the
whole
project
review
Producers
and
Retailers
In every 6
month
On-call,
email
To
introduce
the project
Project
Manager
Steering board
meet up
Distributor In every 3
month
Email,
telephonic
conversatio
n
To discuss
the
distribution
plan
Project
End
Program
Director
Project team
meeting
Team
member
2 -3 times
per week
In-person,
face to face
conversatio
n
Task
reviews
and report
During the
project
Project
manager
Progress and
update review
Logistics At project
ending
In-person To discuss
the
delivery of
the item
After the
project
Project
Manager
Progress status
HR Weekly Email To
maintain
the human
assets
Once in
project
Project
manager
Kick-off
meeting
General
manager
Weekly Email, in
person
To update
the project
and team
On
induction
Project
Manager
Kick-off
meeting and
status report
during the
whole
project
review
Producers
and
Retailers
In every 6
month
On-call,
To
introduce
the project
Project
Manager
Steering board
meet up
Distributor In every 3
month
Email,
telephonic
conversatio
n
To discuss
the
distribution
plan
Project
End
Program
Director
Project team
meeting
Team
member
2 -3 times
per week
In-person,
face to face
conversatio
n
Task
reviews
and report
During the
project
Project
manager
Progress and
update review
Logistics At project
ending
In-person To discuss
the
delivery of
the item
After the
project
Project
Manager
Progress status
HR Weekly Email To
maintain
the human
assets
Once in
project
Project
manager
Kick-off
meeting
General
manager
Weekly Email, in
person
To update
the project
and team
On
induction
Project
Manager
Kick-off
meeting and
status report
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Risk Matrix
Table 3: Risk Assessment
Risk assessment Matrix
Consequences
Cost and time Technical
and human
errors
Safety and
financial
risk
Communi
cation and
unskilled
labour
Insufficient
resources
Catastrophic (5) Major(4) Moderate
(3)
Minor(2) Insignifica
nt (1)
Likelihood
Almost Certain
(5)
Very High Very high Very high High Medium
Likely (4) Very High Very High High High Medium
Possible (3) Very High High High Medium Low
Unlikely (2) High Medium Medium Low Low
Rare (1) Medium Low Low Low Low
Table 3: Risk Assessment
Risk assessment Matrix
Consequences
Cost and time Technical
and human
errors
Safety and
financial
risk
Communi
cation and
unskilled
labour
Insufficient
resources
Catastrophic (5) Major(4) Moderate
(3)
Minor(2) Insignifica
nt (1)
Likelihood
Almost Certain
(5)
Very High Very high Very high High Medium
Likely (4) Very High Very High High High Medium
Possible (3) Very High High High Medium Low
Unlikely (2) High Medium Medium Low Low
Rare (1) Medium Low Low Low Low

WBS
Table 4: Work Breakdown Structure
Task Name Duration Start Finish
implementation of B2C & B2B 204 days Tue 24-09-
19 Fri 03-07-20
The initial stage of PM 9 days Tue 24-09-
19 Fri 04-10-19
Identification of issue 4 days Tue 24-09-
19 Fri 27-09-19
Research and analysis of the
solution 5 days Mon 30-09-
19 Fri 04-10-19
Milestone 0 days Fri 04-10-19 Fri 04-10-19
Planning of the project 29 days Mon 07-10-
19
Thu 14-11-
19
Identification of purpose, goal,
objective 4 days Mon 07-10-
19
Thu 10-10-
19
Identification of functional
requirements 5 days Fri 11-10-19 Thu 17-10-
19
Identification of non - functional
requirements 5 days Fri 18-10-19 Thu 24-10-
19
Cost and budget evaluation 10 days Fri 25-10-19 Thu 07-11-
19
Stakeholder analysis 5 days Fri 08-11-19 Thu 14-11-
19
Milestone 0 days Thu 14-11-
19
Thu 14-11-
19
Implementation phase 105 days Fri 15-11-19 Thu 09-04-
20
SAP installation 15 days Fri 15-11-19 Thu 05-12-
19
SCM installation 15 days Fri 06-12-19 Thu 26-12-
19
CRM installation 15 days Fri 27-12-19 Thu 16-01-
20
Payroll Installation 20 days Fri 17-01-20 Thu 13-02-
20
HRM Installation 20 days Fri 14-02-20 Thu 12-03-
20
Logistics Installation 20 days Fri 13-03-20 Thu 09-04-
20
Milestone 0 days Thu 09-04- Thu 09-04-
Table 4: Work Breakdown Structure
Task Name Duration Start Finish
implementation of B2C & B2B 204 days Tue 24-09-
19 Fri 03-07-20
The initial stage of PM 9 days Tue 24-09-
19 Fri 04-10-19
Identification of issue 4 days Tue 24-09-
19 Fri 27-09-19
Research and analysis of the
solution 5 days Mon 30-09-
19 Fri 04-10-19
Milestone 0 days Fri 04-10-19 Fri 04-10-19
Planning of the project 29 days Mon 07-10-
19
Thu 14-11-
19
Identification of purpose, goal,
objective 4 days Mon 07-10-
19
Thu 10-10-
19
Identification of functional
requirements 5 days Fri 11-10-19 Thu 17-10-
19
Identification of non - functional
requirements 5 days Fri 18-10-19 Thu 24-10-
19
Cost and budget evaluation 10 days Fri 25-10-19 Thu 07-11-
19
Stakeholder analysis 5 days Fri 08-11-19 Thu 14-11-
19
Milestone 0 days Thu 14-11-
19
Thu 14-11-
19
Implementation phase 105 days Fri 15-11-19 Thu 09-04-
20
SAP installation 15 days Fri 15-11-19 Thu 05-12-
19
SCM installation 15 days Fri 06-12-19 Thu 26-12-
19
CRM installation 15 days Fri 27-12-19 Thu 16-01-
20
Payroll Installation 20 days Fri 17-01-20 Thu 13-02-
20
HRM Installation 20 days Fri 14-02-20 Thu 12-03-
20
Logistics Installation 20 days Fri 13-03-20 Thu 09-04-
20
Milestone 0 days Thu 09-04- Thu 09-04-
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 22
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
 +13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.