Crayon Pharmaceuticals B2B/B2C Implementation Project Plan
VerifiedAdded on  2025/08/26
|22
|3227
|120
AI Summary
Desklib provides solved assignments and past papers to help students succeed.

Project Management
Assessment 1
Assessment 1
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Contents
Executive Summary...............................................................................................................................3
Introduction...........................................................................................................................................4
Project Requirement and Project Constraints (Functional as well as non – functional)........................5
Stakeholder analysis Matrix...................................................................................................................7
Communication plan and Matrix...........................................................................................................9
Risk Assessment and Matrix................................................................................................................10
Work Breakdown Structure.................................................................................................................11
Gantt chart..........................................................................................................................................13
Network Diagram................................................................................................................................14
Project Deployment.............................................................................................................................15
Project Signoff.....................................................................................................................................18
Post – Project Review and Recommendation......................................................................................19
Conclusion...........................................................................................................................................20
References...........................................................................................................................................21
Executive Summary...............................................................................................................................3
Introduction...........................................................................................................................................4
Project Requirement and Project Constraints (Functional as well as non – functional)........................5
Stakeholder analysis Matrix...................................................................................................................7
Communication plan and Matrix...........................................................................................................9
Risk Assessment and Matrix................................................................................................................10
Work Breakdown Structure.................................................................................................................11
Gantt chart..........................................................................................................................................13
Network Diagram................................................................................................................................14
Project Deployment.............................................................................................................................15
Project Signoff.....................................................................................................................................18
Post – Project Review and Recommendation......................................................................................19
Conclusion...........................................................................................................................................20
References...........................................................................................................................................21

Executive Summary
Project Management is the strategy or planning of the whole project which is conducted to achieve
the objective and specific goals of the process. It is done so that the whole process and the activities
can be successfully completed without any damage or delay. It is also done to estimate the cost,
duration, requirements, resources required, stakeholders and etc so that project can follow the
guideline and work according to it. The five main stages of PM are initiation, planning, execution,
monitoring and closure. The following assignment aims at conducting the project management
assignment and planning of the given scenario. It helps to identify the various different phases of the
project life cycle. It conducts communication matrix, risk assessment and matrix and stakeholder
analysis. The major activity done in this assignment are defining the scope and objective, estimating
time, cost and quality of the project, making Gantt chart network diagram and WBS, project
deployment plan, project signoff with the various set of recommendation.
Project Management is the strategy or planning of the whole project which is conducted to achieve
the objective and specific goals of the process. It is done so that the whole process and the activities
can be successfully completed without any damage or delay. It is also done to estimate the cost,
duration, requirements, resources required, stakeholders and etc so that project can follow the
guideline and work according to it. The five main stages of PM are initiation, planning, execution,
monitoring and closure. The following assignment aims at conducting the project management
assignment and planning of the given scenario. It helps to identify the various different phases of the
project life cycle. It conducts communication matrix, risk assessment and matrix and stakeholder
analysis. The major activity done in this assignment are defining the scope and objective, estimating
time, cost and quality of the project, making Gantt chart network diagram and WBS, project
deployment plan, project signoff with the various set of recommendation.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Introduction
The intended assignment is to conduct Project Management Planning for Crayon Pharmaceuticals. It
is the manufacturing organisation which aims at selling the product globally. Besides this, it also
sales the raw materials and composition to other pharmaceutical companies so that they can
transform their business. Now the company has decided to implement a Business to Business and
Business to Customer Solution including Siebel CRM, Supply Chain Management, Payroll, Human
Resource Management, SAP Order to Customer and Logistics. And hence the below-mentioned
report is the project management planning which is required to implement the solution. The
company also recruit various members to make this implementation a successful one.
Title – The title for the project is B2B, B2C implementation.
Goal – The goal of this project is to successfully implement the customer solution.
Objective – The objective which is carried out with this project is to make an efficient and effective
solution so that it helps to solve the various problems which are faced by the organisation to
transform their business.
Start and End data - As expected the project is going to start from the 9 September 2019 and more
than 6 months will be required to implement this project.
The intended assignment is to conduct Project Management Planning for Crayon Pharmaceuticals. It
is the manufacturing organisation which aims at selling the product globally. Besides this, it also
sales the raw materials and composition to other pharmaceutical companies so that they can
transform their business. Now the company has decided to implement a Business to Business and
Business to Customer Solution including Siebel CRM, Supply Chain Management, Payroll, Human
Resource Management, SAP Order to Customer and Logistics. And hence the below-mentioned
report is the project management planning which is required to implement the solution. The
company also recruit various members to make this implementation a successful one.
Title – The title for the project is B2B, B2C implementation.
Goal – The goal of this project is to successfully implement the customer solution.
Objective – The objective which is carried out with this project is to make an efficient and effective
solution so that it helps to solve the various problems which are faced by the organisation to
transform their business.
Start and End data - As expected the project is going to start from the 9 September 2019 and more
than 6 months will be required to implement this project.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Project Requirement and Project Constraints (Functional as well as non –
functional)
Project Scope – The following project plan is made for the Crayon Pharmaceuticals, but it can be
followed by any company which wish to implement the SAP solutions and other B2B, B2C and O2O
services.
Time Estimation – The expected time period of the (Meredith, et.al, 2017) whole project is
estimated to be around 8 – 10 months as the implementation is considered to change the whole
business processes.
Cost and Quality - With the solution provided that the SAP solution will cost around $ 30,000 - $
40,000 and around solution will give a sum of $ 50,000. The Quality of the solution depends on the
software and services one opts for.
Stakeholder Roles and responsibilities - The crayon recruited many new members for implementing
the new solutions and hence the given below are the major stakeholder in the process.
Table 1: Stakeholder name
Program Director Adam Cunningham
Program Manager Jake Black
Project Manager Tom Weilding and Paul McKenna
CEO of Crayon Crayon’s CEO
CIO of Crayon Crayon’s
Retail, Supply, Logistics, Customer Services and HR Team members
General Manager GM for the above-mentioned team.
Functional Requirement – The functional requirement of the system is described as follows –
 Management of the order – The system must manage all orders effectively and efficiently.
 Confirmation of order – It performs the task of confirming the order
 Verification of order – when once the (Schwalbe, 2015) item is ordered, it must perform the
verification process.
 Selling of raw materials and composition – It provides the raw material and chemical
composition to other pharmaceutical companies.
 Administration – It is managing the whole task and activities of the system.
 Maintaining customer relation – the system helps in providing better services and
maintaining good relation with the customer
 supply chain management – It looks after the various approaches to initiate and apply supply
management
Non – Functional Requirement – The non-functional requirement of the system are listed as below
 Security of data – It is the most important requirement which should be explicitly used when
implementing a new solution.
functional)
Project Scope – The following project plan is made for the Crayon Pharmaceuticals, but it can be
followed by any company which wish to implement the SAP solutions and other B2B, B2C and O2O
services.
Time Estimation – The expected time period of the (Meredith, et.al, 2017) whole project is
estimated to be around 8 – 10 months as the implementation is considered to change the whole
business processes.
Cost and Quality - With the solution provided that the SAP solution will cost around $ 30,000 - $
40,000 and around solution will give a sum of $ 50,000. The Quality of the solution depends on the
software and services one opts for.
Stakeholder Roles and responsibilities - The crayon recruited many new members for implementing
the new solutions and hence the given below are the major stakeholder in the process.
Table 1: Stakeholder name
Program Director Adam Cunningham
Program Manager Jake Black
Project Manager Tom Weilding and Paul McKenna
CEO of Crayon Crayon’s CEO
CIO of Crayon Crayon’s
Retail, Supply, Logistics, Customer Services and HR Team members
General Manager GM for the above-mentioned team.
Functional Requirement – The functional requirement of the system is described as follows –
 Management of the order – The system must manage all orders effectively and efficiently.
 Confirmation of order – It performs the task of confirming the order
 Verification of order – when once the (Schwalbe, 2015) item is ordered, it must perform the
verification process.
 Selling of raw materials and composition – It provides the raw material and chemical
composition to other pharmaceutical companies.
 Administration – It is managing the whole task and activities of the system.
 Maintaining customer relation – the system helps in providing better services and
maintaining good relation with the customer
 supply chain management – It looks after the various approaches to initiate and apply supply
management
Non – Functional Requirement – The non-functional requirement of the system are listed as below
 Security of data – It is the most important requirement which should be explicitly used when
implementing a new solution.

 Flexible Application – It must have the ability to integrate with other applications like
databases, SQL and etc.
 Requirements of the software – It is important to understand the version of the browser in
which it will get implemented.
 Quality of service – It must have the quality in providing the services they are offering.
 Service level Agreement – It includes the time of application, turn- around time and
response time so that downtime can be (Boyle, 2017) reduced.
 Time of implementation – It is the ability of the application and solution implemented to run
on time.
 Back – up and recovery – The application must exhibit the data back – up capabilities which
can be recovered at the time of the crash.
databases, SQL and etc.
 Requirements of the software – It is important to understand the version of the browser in
which it will get implemented.
 Quality of service – It must have the quality in providing the services they are offering.
 Service level Agreement – It includes the time of application, turn- around time and
response time so that downtime can be (Boyle, 2017) reduced.
 Time of implementation – It is the ability of the application and solution implemented to run
on time.
 Back – up and recovery – The application must exhibit the data back – up capabilities which
can be recovered at the time of the crash.
⊘ 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 2 : Stakeholder Analysis
Stakehold
er name
Pow
er
(0 –
5)
Interes
t
(0 – 5)
Impac
t
(High,
Mediu
m,
Low)
Influenc
e
(High,
Medium
, Low)
What is
important
to the
stakeholde
r
How could
stakeholder
contribute to
the project
How could
stakehold
er block
the project
CEO of
crayon
4 5 High Medium Providing
necessary
informatio
n
By agreeing
and
approving
the project
plan
By not
approving
and
signing
document
CIO of
crayon
4 5 High Medium Providing
necessary
informatio
n and
backgroun
d details
By agreeing
and
approving
the project
plan
By not
approving
and
signing
document
Program
director
5 4 High High Making
decision
and
directing
program
manger
Communicat
e with the
program
manager,
project
managers to
discuss
decision and
policies.
By taking
wrong
decision
Program
manager
5 4 High High Implementi
ng and
taking
decisions
and
directions
By making
good
strategies
and
communicati
ng with the
Mangers
By
misleading
the
planning
Project
manager 1
5 5 High High Taking
action and
directing
team and
planning
the whole
team
Should guide
the whole
team and
maintain
communicati
on with each
team
member
By
delaying
the project
and not
making
proper
communic
ation
Project
Manager
2
5 5 High High Taking
action and
directing
Should guide
the whole
team and
By
delaying
the project
Table 2 : Stakeholder Analysis
Stakehold
er name
Pow
er
(0 –
5)
Interes
t
(0 – 5)
Impac
t
(High,
Mediu
m,
Low)
Influenc
e
(High,
Medium
, Low)
What is
important
to the
stakeholde
r
How could
stakeholder
contribute to
the project
How could
stakehold
er block
the project
CEO of
crayon
4 5 High Medium Providing
necessary
informatio
n
By agreeing
and
approving
the project
plan
By not
approving
and
signing
document
CIO of
crayon
4 5 High Medium Providing
necessary
informatio
n and
backgroun
d details
By agreeing
and
approving
the project
plan
By not
approving
and
signing
document
Program
director
5 4 High High Making
decision
and
directing
program
manger
Communicat
e with the
program
manager,
project
managers to
discuss
decision and
policies.
By taking
wrong
decision
Program
manager
5 4 High High Implementi
ng and
taking
decisions
and
directions
By making
good
strategies
and
communicati
ng with the
Mangers
By
misleading
the
planning
Project
manager 1
5 5 High High Taking
action and
directing
team and
planning
the whole
team
Should guide
the whole
team and
maintain
communicati
on with each
team
member
By
delaying
the project
and not
making
proper
communic
ation
Project
Manager
2
5 5 High High Taking
action and
directing
Should guide
the whole
team and
By
delaying
the project
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

team and
planning
the whole
team
maintain
communicati
on with each
team
member
and not
making
proper
communic
ation
General
manager
2 3 mediu
m
Medium Managing
the whole
team
Manage the
working of
whole teams
Complaini
ng about
the
decisions
and
Customer
Services
manager
1 2 Low High Maximising
the quality
of the
service
Work
efficiently to
support
implementati
on
By giving
wrong
advice to
the
customer
Logistic
team
1 2 Low High Providing
good
logistic
services
Work
efficiently to
support
implementati
on
By
delaying
the project
and going
on strike
HR 0 3 Low High Maintainin
g Human
resource in
company
Work
efficiently to
support
implementati
on
By
providing
wrong
details
Supply
managem
ent team
1 4 Low High Efficient
Supply
chain
manageme
nt
Work
efficiently to
support
implementati
on
By creating
a mess in
the
process
Retail
team
1 4 Low High Maximising
the
production
Work
efficiently to
support
implementati
on
By not
selling the
product
planning
the whole
team
maintain
communicati
on with each
team
member
and not
making
proper
communic
ation
General
manager
2 3 mediu
m
Medium Managing
the whole
team
Manage the
working of
whole teams
Complaini
ng about
the
decisions
and
Customer
Services
manager
1 2 Low High Maximising
the quality
of the
service
Work
efficiently to
support
implementati
on
By giving
wrong
advice to
the
customer
Logistic
team
1 2 Low High Providing
good
logistic
services
Work
efficiently to
support
implementati
on
By
delaying
the project
and going
on strike
HR 0 3 Low High Maintainin
g Human
resource in
company
Work
efficiently to
support
implementati
on
By
providing
wrong
details
Supply
managem
ent team
1 4 Low High Efficient
Supply
chain
manageme
nt
Work
efficiently to
support
implementati
on
By creating
a mess in
the
process
Retail
team
1 4 Low High Maximising
the
production
Work
efficiently to
support
implementati
on
By not
selling the
product

Communication plan and Matrix
Table 3: Communication Matrix
Stakeholder
name
Communication Purpose Medium Frequency Owner
CEO of crayon Project Kick-off
meeting
To introduce
the goal and
objective of
the project
In-person
meeting
Start of the
project, once a
month
Program
Director
CIO of crayon Project Kick-off
meeting
To introduce
the goal and
objective of
the project
In-person
meeting
Start of the
project, once a
month
Program
Director
Program
director
Project team
meeting
Review status Round table
conference
Once a week Program
Director
Program
manager
Project team
meeting
Review status
and discuss
another
action
In-person,
round table
Thrice a week Project
Director
Project
manager 1
Status Report Review status
and discuss
another
action
Conference
call, round
table
discussion
Daily Program
manager and
program
director
Project
Manager 2
Status Report Review status
and discuss
another
action
Conference
call, round
table
discussion
Daily Program
manager and
program
director
General
manager
Status meeting To check the
status
Email weekly Project
manager
Customer
Services
manager
Update meeting Take update Email,
telephone
weekly General
Manager
Logistic team Progress
Review
Take Update Email,
telephone
Monthly General
Manager
HR Status report Take update Email,
telephone
Weekly General
Manager
Supply
management
team
Progress review Take Update Email,
telephone
weekly General
Manager
Retail team Progress review Take update Email,
telephone
Daily General
Manager
Table 3: Communication Matrix
Stakeholder
name
Communication Purpose Medium Frequency Owner
CEO of crayon Project Kick-off
meeting
To introduce
the goal and
objective of
the project
In-person
meeting
Start of the
project, once a
month
Program
Director
CIO of crayon Project Kick-off
meeting
To introduce
the goal and
objective of
the project
In-person
meeting
Start of the
project, once a
month
Program
Director
Program
director
Project team
meeting
Review status Round table
conference
Once a week Program
Director
Program
manager
Project team
meeting
Review status
and discuss
another
action
In-person,
round table
Thrice a week Project
Director
Project
manager 1
Status Report Review status
and discuss
another
action
Conference
call, round
table
discussion
Daily Program
manager and
program
director
Project
Manager 2
Status Report Review status
and discuss
another
action
Conference
call, round
table
discussion
Daily Program
manager and
program
director
General
manager
Status meeting To check the
status
Email weekly Project
manager
Customer
Services
manager
Update meeting Take update Email,
telephone
weekly General
Manager
Logistic team Progress
Review
Take Update Email,
telephone
Monthly General
Manager
HR Status report Take update Email,
telephone
Weekly General
Manager
Supply
management
team
Progress review Take Update Email,
telephone
weekly General
Manager
Retail team Progress review Take update Email,
telephone
Daily General
Manager
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Risk Assessment and Matrix
Table 4 : Risk Assessment and matrix
Risk matrix Likelihood
Type of risk Probability of
occurrence (0 –
100 %)
Unlikely
( High,
moderate,
low
Possible
( High, moderate,
low )
Likely
( High, moderate,
low )
Cost 70 % Moderate High Moderate
Time delay 90 % low High High
Communication 80 % Low Moderate High
Insufficient resources 65 % Moderate Low High
Financial risk 60 % High High High
Operational risk 80 % High High High
Ethics and Moral 20 % High Low Low
Man power 10 % Low Moderate High
System Crash 30 % low Low Low
Lack of skilled person 40 % Low Moderate Low
Table 4 : Risk Assessment and matrix
Risk matrix Likelihood
Type of risk Probability of
occurrence (0 –
100 %)
Unlikely
( High,
moderate,
low
Possible
( High, moderate,
low )
Likely
( High, moderate,
low )
Cost 70 % Moderate High Moderate
Time delay 90 % low High High
Communication 80 % Low Moderate High
Insufficient resources 65 % Moderate Low High
Financial risk 60 % High High High
Operational risk 80 % High High High
Ethics and Moral 20 % High Low Low
Man power 10 % Low Moderate High
System Crash 30 % low Low Low
Lack of skilled person 40 % Low Moderate Low

Work Breakdown Structure
Work Break down Structure is used to break (Slovic, et.al, 2016) the whole project process in the
different subsets which are shown in the below figure. It shows start date as well as end date of
project
Table 5: WBS Table
Task Name Duration Start Finish
B2B, B2C and O2C
implementation 197 days Mon 09-09-
19
Tue 09-06-
20
Project Initiation 23 days Mon 09-09-
19
Wed 09-10-
19
Problem Analysis 3 days Mon 09-09-
19
Wed 11-09-
19
Research on the topic 10 days Thu 12-09-19 Wed 25-09-
19
Deciding different
solution to adopt 10 days Thu 26-09-19 Wed 09-10-
19
Milestone 0 days Wed 09-10-
19
Wed 09-10-
19
Project Planning 60 days Thu 10-10-19 Wed 01-01-
20
Defining scope, goal,
objective 15 days Thu 10-10-19 Wed 30-10-
19
Estimation of time
and cost 13 days Thu 31-10-19 Mon 18-11-
19
Identifying
stakeholder 12 days Tue 19-11-19 Wed 04-12-
19
Stakeholder analysis 7 days Thu 05-12-19 Fri 13-12-19
Gathering Resources 4 days Mon 16-12-
19 Thu 19-12-19
Collecting fund 9 days Fri 20-12-19 Wed 01-01-
20
Milestone 0 days Wed 01-01-
20
Wed 01-01-
20
Project execution 41 days Thu 02-01-20 Thu 27-02-20
Installing SAP O2C 4 days Thu 02-01-20 Tue 07-01-20
Installing Payroll 5 days Wed 08-01-
20 Tue 14-01-20
Installing Human
resource management 5 days Wed 15-01-
20 Tue 21-01-20
Installing Logistics 7 days Wed 22-01-
20 Thu 30-01-20
Installing Supply Chain
Management 5 days Fri 31-01-20 Thu 06-02-20
Installing Siebel CRM 5 days Fri 07-02-20 Thu 13-02-20
Work Break down Structure is used to break (Slovic, et.al, 2016) the whole project process in the
different subsets which are shown in the below figure. It shows start date as well as end date of
project
Table 5: WBS Table
Task Name Duration Start Finish
B2B, B2C and O2C
implementation 197 days Mon 09-09-
19
Tue 09-06-
20
Project Initiation 23 days Mon 09-09-
19
Wed 09-10-
19
Problem Analysis 3 days Mon 09-09-
19
Wed 11-09-
19
Research on the topic 10 days Thu 12-09-19 Wed 25-09-
19
Deciding different
solution to adopt 10 days Thu 26-09-19 Wed 09-10-
19
Milestone 0 days Wed 09-10-
19
Wed 09-10-
19
Project Planning 60 days Thu 10-10-19 Wed 01-01-
20
Defining scope, goal,
objective 15 days Thu 10-10-19 Wed 30-10-
19
Estimation of time
and cost 13 days Thu 31-10-19 Mon 18-11-
19
Identifying
stakeholder 12 days Tue 19-11-19 Wed 04-12-
19
Stakeholder analysis 7 days Thu 05-12-19 Fri 13-12-19
Gathering Resources 4 days Mon 16-12-
19 Thu 19-12-19
Collecting fund 9 days Fri 20-12-19 Wed 01-01-
20
Milestone 0 days Wed 01-01-
20
Wed 01-01-
20
Project execution 41 days Thu 02-01-20 Thu 27-02-20
Installing SAP O2C 4 days Thu 02-01-20 Tue 07-01-20
Installing Payroll 5 days Wed 08-01-
20 Tue 14-01-20
Installing Human
resource management 5 days Wed 15-01-
20 Tue 21-01-20
Installing Logistics 7 days Wed 22-01-
20 Thu 30-01-20
Installing Supply Chain
Management 5 days Fri 31-01-20 Thu 06-02-20
Installing Siebel CRM 5 days Fri 07-02-20 Thu 13-02-20
⊘ 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.