Project and Operations Management
VerifiedAdded on 2023/06/12
|28
|3251
|254
AI Summary
The report discusses the project management plan for developing a new Smartphone for Samsung. It covers project purpose, description, scope statement, deliverables, milestones, schedule, budget, quality plan, and risk register.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: PROJECT AND OPERATIONS MANAGEMENT
Project and Operations Management
Name of the student
Nam of the university
Author note
Project and Operations Management
Name of the student
Nam of the university
Author note
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
1PROJECT AND OPERATIONS MANAGEMENT
Executive Summary
The project had aimed of developing a new Smartphone for the organization named Samsung.
The company would use their innovation and technological proficiency in developing gadgets
that provide them with cost leadership n the market. It can be concluded from the report that an
effective project management plan had been developed to build a Smartphone that would be
superior to the products in the market. The risk factors and the quality control measures had been
defined and Samsung would have to follow this method to successfully develop the product.
However, agile methodology is a contingency plan which should be used when there is too much
deviation from the original specification of the stakeholders.
Executive Summary
The project had aimed of developing a new Smartphone for the organization named Samsung.
The company would use their innovation and technological proficiency in developing gadgets
that provide them with cost leadership n the market. It can be concluded from the report that an
effective project management plan had been developed to build a Smartphone that would be
superior to the products in the market. The risk factors and the quality control measures had been
defined and Samsung would have to follow this method to successfully develop the product.
However, agile methodology is a contingency plan which should be used when there is too much
deviation from the original specification of the stakeholders.
2PROJECT AND OPERATIONS MANAGEMENT
Table of Contents
Project purpose................................................................................................................................3
Project description...........................................................................................................................3
Project scope Statement...................................................................................................................3
Project deliverables..........................................................................................................................4
Project milestones............................................................................................................................5
Project schedule...............................................................................................................................6
Gantt chart.....................................................................................................................................11
Network diagram...........................................................................................................................12
Work break down structure...........................................................................................................13
Project budget................................................................................................................................14
Quality plan...................................................................................................................................20
Risk register...................................................................................................................................21
Conclusion.....................................................................................................................................24
References and Bibliography.........................................................................................................25
Table of Contents
Project purpose................................................................................................................................3
Project description...........................................................................................................................3
Project scope Statement...................................................................................................................3
Project deliverables..........................................................................................................................4
Project milestones............................................................................................................................5
Project schedule...............................................................................................................................6
Gantt chart.....................................................................................................................................11
Network diagram...........................................................................................................................12
Work break down structure...........................................................................................................13
Project budget................................................................................................................................14
Quality plan...................................................................................................................................20
Risk register...................................................................................................................................21
Conclusion.....................................................................................................................................24
References and Bibliography.........................................................................................................25
3PROJECT AND OPERATIONS MANAGEMENT
Project purpose
The project is aimed at developing a new Smartphone for the organization named
Samsung. The company will use their innovation and technological proficiency in developing
gadgets that provide them with cost leadership n the market.
Project description
Samsung is the market leader in terms of their cost leadership and they have provided the
consumers with smartphones at affordable prices by keeping the features same as that of the
other major companies in the market (News.samsung.com 2018). The market of smart phone has
become more and more saturated and in order to maintain their competitive advantage in the
market the organization is launching another innovative product which will increase their short
term sales and provide them with competitive advantage. This project will consist of developing
a product far superior to that of the products already in the market.
Project scope Statement
The project scope statement consists of the various factors such as project objective,
constraints, assumptions, requirements, deliverables, milestone and schedule (Harrison and Lock
2017). The project scope statement will define all these factors and in this current project a
project plan will be developed for developing a new smart phone for Samsung.
Project Objectives
The project objectives are as follows:
Developing an innovative product to gain advantage in the market
Project purpose
The project is aimed at developing a new Smartphone for the organization named
Samsung. The company will use their innovation and technological proficiency in developing
gadgets that provide them with cost leadership n the market.
Project description
Samsung is the market leader in terms of their cost leadership and they have provided the
consumers with smartphones at affordable prices by keeping the features same as that of the
other major companies in the market (News.samsung.com 2018). The market of smart phone has
become more and more saturated and in order to maintain their competitive advantage in the
market the organization is launching another innovative product which will increase their short
term sales and provide them with competitive advantage. This project will consist of developing
a product far superior to that of the products already in the market.
Project scope Statement
The project scope statement consists of the various factors such as project objective,
constraints, assumptions, requirements, deliverables, milestone and schedule (Harrison and Lock
2017). The project scope statement will define all these factors and in this current project a
project plan will be developed for developing a new smart phone for Samsung.
Project Objectives
The project objectives are as follows:
Developing an innovative product to gain advantage in the market
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
4PROJECT AND OPERATIONS MANAGEMENT
Market the product
Testing and launching of the product
Project Assumptions
The assumptions made in the project are as follows:
The CEO, board and the other stakeholder have approved the project
The different departments have been made aware of the project and its purpose
Project constraint
The time and budget of the project is a big constraint as Samsung uses cost leadership so
developing economies of scale is important in this project. Therefore, the project will have to
make sure that unnecessary over allocation of resources have to be avoided especially while
executing the non critical tasks in the study.
Project deliverables
The outputs of the different phases of the project are known as project deliverables and
defining project deliverables are essential to understand the variation in the results achieved in
each stage (Maylor, Turner and Murray-Webster 2015). The project deliverables in the current
project are listed below:
Task Name Duration Start Finish
Samsung Smartphone product
development
598 days Mon 5/21/18 Wed 9/2/20
Market the product
Testing and launching of the product
Project Assumptions
The assumptions made in the project are as follows:
The CEO, board and the other stakeholder have approved the project
The different departments have been made aware of the project and its purpose
Project constraint
The time and budget of the project is a big constraint as Samsung uses cost leadership so
developing economies of scale is important in this project. Therefore, the project will have to
make sure that unnecessary over allocation of resources have to be avoided especially while
executing the non critical tasks in the study.
Project deliverables
The outputs of the different phases of the project are known as project deliverables and
defining project deliverables are essential to understand the variation in the results achieved in
each stage (Maylor, Turner and Murray-Webster 2015). The project deliverables in the current
project are listed below:
Task Name Duration Start Finish
Samsung Smartphone product
development
598 days Mon 5/21/18 Wed 9/2/20
5PROJECT AND OPERATIONS MANAGEMENT
1.0 Product planning and
concept
73 days Mon 5/21/18 Wed 8/29/18
2.0 Requirement analysis 184 days Thu 8/30/18 Tue 5/14/19
3.0 Production development
Stage
70 days Wed 5/15/19 Tue 8/20/19
4.0 Testing phase 61 days Wed 8/21/19 Wed 11/13/19
5.0 Product launch 120 days Thu 11/14/19 Wed 4/29/20
6.0 Product Monitoring 90 days Thu 4/30/20 Wed 9/2/20
Table 1
Project milestones
The progress of the project is defined by milestones and the tasks having zero duration on
the timeline signifies the end of an important phase (Binder 2016). The project deliverables for
the current have been listed and presented below:
Task Name Duration Start Finish
1.6 Milestone 1: Project Charter
Developed
0 days Wed 8/29/18 Wed 8/29/18
2.8 Milestone 2: Functional
requirement approved
0 days Tue 5/14/19 Tue 5/14/19
1.0 Product planning and
concept
73 days Mon 5/21/18 Wed 8/29/18
2.0 Requirement analysis 184 days Thu 8/30/18 Tue 5/14/19
3.0 Production development
Stage
70 days Wed 5/15/19 Tue 8/20/19
4.0 Testing phase 61 days Wed 8/21/19 Wed 11/13/19
5.0 Product launch 120 days Thu 11/14/19 Wed 4/29/20
6.0 Product Monitoring 90 days Thu 4/30/20 Wed 9/2/20
Table 1
Project milestones
The progress of the project is defined by milestones and the tasks having zero duration on
the timeline signifies the end of an important phase (Binder 2016). The project deliverables for
the current have been listed and presented below:
Task Name Duration Start Finish
1.6 Milestone 1: Project Charter
Developed
0 days Wed 8/29/18 Wed 8/29/18
2.8 Milestone 2: Functional
requirement approved
0 days Tue 5/14/19 Tue 5/14/19
6PROJECT AND OPERATIONS MANAGEMENT
3.4 Milestone 3: Smartphone
developed
0 days Tue 8/20/19 Tue 8/20/19
4.4 Milestone 4: Product Testing
completed
0 days Wed 11/13/19 Wed 11/13/19
5.3 Milestone 5: Product
launched
0 days Wed 4/29/20 Wed 4/29/20
6.4 Milestone 6: Product
monitored
0 days Wed 9/2/20 Wed 9/2/20
Table 2
Project schedule
The project will depict the different tasks that will be performed in successful execution
of the project (Heldman 2018). In table 3, the project schedule shows that duration, the start date
and finish date of each of the tasks. The project schedule is the structured way of identifying the
work that has to be done and the optimal time period for cost reduction. The overall timestamp
for this project is 598 days which is almost two years and the project will start at 20th May, 2018
to 2nd September, 2020. However, as 20th is a Sunday, the official schedule has been prepared
from 21st May so the project schedule has been developed taking all the holidays into account.
There are only three tasks in the project that are non critical and rest of the tasks in the project
are critical task. Therefore, if Samsung wants to reduce the cost the time span will increase as
both are interdependent and inversely proportional to each other.
3.4 Milestone 3: Smartphone
developed
0 days Tue 8/20/19 Tue 8/20/19
4.4 Milestone 4: Product Testing
completed
0 days Wed 11/13/19 Wed 11/13/19
5.3 Milestone 5: Product
launched
0 days Wed 4/29/20 Wed 4/29/20
6.4 Milestone 6: Product
monitored
0 days Wed 9/2/20 Wed 9/2/20
Table 2
Project schedule
The project will depict the different tasks that will be performed in successful execution
of the project (Heldman 2018). In table 3, the project schedule shows that duration, the start date
and finish date of each of the tasks. The project schedule is the structured way of identifying the
work that has to be done and the optimal time period for cost reduction. The overall timestamp
for this project is 598 days which is almost two years and the project will start at 20th May, 2018
to 2nd September, 2020. However, as 20th is a Sunday, the official schedule has been prepared
from 21st May so the project schedule has been developed taking all the holidays into account.
There are only three tasks in the project that are non critical and rest of the tasks in the project
are critical task. Therefore, if Samsung wants to reduce the cost the time span will increase as
both are interdependent and inversely proportional to each other.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
7PROJECT AND OPERATIONS MANAGEMENT
Task Name Duration Start Finish
Task Name Duration Start Finish
8PROJECT AND OPERATIONS MANAGEMENT
Samsung Smartphone product
development
598 days Mon 5/21/18 Wed 9/2/20
1.0 Product planning and
concept
73 days Mon 5/21/18 Wed 8/29/18
1.1 Identifying the Specification 30 days Mon 5/21/18 Fri 6/29/18
1.2 Meeting with the stakeholders 7 days Mon 7/2/18 Tue 7/10/18
1.3 Amendment of the primary
document
5 days Wed 7/11/18 Tue 7/17/18
1.4 Product design developed 30 days Wed 7/18/18 Tue 8/28/18
1.5 Documentation Deployment 1 day Wed 8/29/18 Wed 8/29/18
1.6 Milestone 1: Project Charter
Developed
0 days Wed 8/29/18 Wed 8/29/18
2.0 Requirement analysis 184 days Thu 8/30/18 Tue 5/14/19
2.1 Software requirement
identification
30 days Thu 8/30/18 Wed 10/10/18
2.2 Hardware requirements 45 days Thu 8/30/18 Wed 10/31/18
2.3 functional requirement
analysis
60 days Thu 11/1/18 Wed 1/23/19
Samsung Smartphone product
development
598 days Mon 5/21/18 Wed 9/2/20
1.0 Product planning and
concept
73 days Mon 5/21/18 Wed 8/29/18
1.1 Identifying the Specification 30 days Mon 5/21/18 Fri 6/29/18
1.2 Meeting with the stakeholders 7 days Mon 7/2/18 Tue 7/10/18
1.3 Amendment of the primary
document
5 days Wed 7/11/18 Tue 7/17/18
1.4 Product design developed 30 days Wed 7/18/18 Tue 8/28/18
1.5 Documentation Deployment 1 day Wed 8/29/18 Wed 8/29/18
1.6 Milestone 1: Project Charter
Developed
0 days Wed 8/29/18 Wed 8/29/18
2.0 Requirement analysis 184 days Thu 8/30/18 Tue 5/14/19
2.1 Software requirement
identification
30 days Thu 8/30/18 Wed 10/10/18
2.2 Hardware requirements 45 days Thu 8/30/18 Wed 10/31/18
2.3 functional requirement
analysis
60 days Thu 11/1/18 Wed 1/23/19
9PROJECT AND OPERATIONS MANAGEMENT
2.4 Initial Design 65 days Thu 1/24/19 Wed 4/24/19
2.5 Board meeting 5 days Thu 4/25/19 Wed 5/1/19
2.6 Modifications noted 7 days Thu 5/2/19 Fri 5/10/19
2.7 Dispatch for approval 2 days Mon 5/13/19 Tue 5/14/19
2.8 Milestone 2: Functional
requirement approved
0 days Tue 5/14/19 Tue 5/14/19
3.0 Production development
Stage
70 days Wed 5/15/19 Tue 8/20/19
3.1 integrate the product
requirements
45 days Wed 5/15/19 Tue 7/16/19
3.2 Develop product 68 days Wed 5/15/19 Fri 8/16/19
3.3 Dispatch for product testing 2 days Mon 8/19/19 Tue 8/20/19
3.4 Milestone 3: Smartphone
developed
0 days Tue 8/20/19 Tue 8/20/19
4.0 Testing phase 61 days Wed 8/21/19 Wed 11/13/19
4.1 Product sample prototypes
given to employees
40 days Wed 8/21/19 Tue 10/15/19
4.2 Collecting feedback from 7 days Wed 10/16/19 Thu 10/24/19
2.4 Initial Design 65 days Thu 1/24/19 Wed 4/24/19
2.5 Board meeting 5 days Thu 4/25/19 Wed 5/1/19
2.6 Modifications noted 7 days Thu 5/2/19 Fri 5/10/19
2.7 Dispatch for approval 2 days Mon 5/13/19 Tue 5/14/19
2.8 Milestone 2: Functional
requirement approved
0 days Tue 5/14/19 Tue 5/14/19
3.0 Production development
Stage
70 days Wed 5/15/19 Tue 8/20/19
3.1 integrate the product
requirements
45 days Wed 5/15/19 Tue 7/16/19
3.2 Develop product 68 days Wed 5/15/19 Fri 8/16/19
3.3 Dispatch for product testing 2 days Mon 8/19/19 Tue 8/20/19
3.4 Milestone 3: Smartphone
developed
0 days Tue 8/20/19 Tue 8/20/19
4.0 Testing phase 61 days Wed 8/21/19 Wed 11/13/19
4.1 Product sample prototypes
given to employees
40 days Wed 8/21/19 Tue 10/15/19
4.2 Collecting feedback from 7 days Wed 10/16/19 Thu 10/24/19
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
10PROJECT AND OPERATIONS MANAGEMENT
employees
4.3 Sent the product for changes 14 days Fri 10/25/19 Wed 11/13/19
4.4 Milestone 4: Product Testing
completed
0 days Wed 11/13/19 Wed 11/13/19
5.0 Product launch 120 days Thu 11/14/19 Wed 4/29/20
5.1 Develop digital and
Traditional promotional campaign
30 days Thu 11/14/19 Wed 12/25/19
5.2 Market the product 90 days Thu 12/26/19 Wed 4/29/20
5.3 Milestone 5: Product launched 0 days Wed 4/29/20 Wed 4/29/20
6.0 Product Monitoring 90 days Thu 4/30/20 Wed 9/2/20
6.1 Evaluate the marketing
campaign
60 days Thu 4/30/20 Wed 7/22/20
6.2 Examine the product success 28 days Thu 4/30/20 Mon 6/8/20
6.3 Note the drawbacks for
Second phase
30 days Thu 7/23/20 Wed 9/2/20
6.4 Milestone 6: Product
monitored
0 days Wed 9/2/20 Wed 9/2/20
Table 3
employees
4.3 Sent the product for changes 14 days Fri 10/25/19 Wed 11/13/19
4.4 Milestone 4: Product Testing
completed
0 days Wed 11/13/19 Wed 11/13/19
5.0 Product launch 120 days Thu 11/14/19 Wed 4/29/20
5.1 Develop digital and
Traditional promotional campaign
30 days Thu 11/14/19 Wed 12/25/19
5.2 Market the product 90 days Thu 12/26/19 Wed 4/29/20
5.3 Milestone 5: Product launched 0 days Wed 4/29/20 Wed 4/29/20
6.0 Product Monitoring 90 days Thu 4/30/20 Wed 9/2/20
6.1 Evaluate the marketing
campaign
60 days Thu 4/30/20 Wed 7/22/20
6.2 Examine the product success 28 days Thu 4/30/20 Mon 6/8/20
6.3 Note the drawbacks for
Second phase
30 days Thu 7/23/20 Wed 9/2/20
6.4 Milestone 6: Product
monitored
0 days Wed 9/2/20 Wed 9/2/20
Table 3
11PROJECT AND OPERATIONS MANAGEMENT
PROJECT AND OPERATIONS MANAGEMENT 12
Gantt chart
Gantt chart
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
PROJECT AND OPERATIONS MANAGEMENT 13
Network diagram
Network diagram
PROJECT AND OPERATIONS MANAGEMENT 14
Work break down structure
Samsung Smartphone
product development
1.0 Product planning and
concept
1.1 Identifying the
Specfication
1.2 Meeting with the
stakeholders
1.3 Amendment of
the primary
document
1.4 Product design
developed
1.5 Documentation
Deployment
1.6 Milestone 1:
Project Charter
Developed
2.0 Requirement analysis
2.1 Softw are
requirement
identification
2.2 Hardware
requirements
2.3 functional
requirement analysis
2.4 Initial Design
2.5 Board meeting
2.6 Modifications
noted
2.7 Dispatch for
approval
2.8 Milestone 2:
Functional
requirement
approved
3.0 Production
development Stage
3.1 integrate the
product
requirements
3.2 Develop product
3.3 Dispatch for
product testing
3.4 Milestone 3:
Smartphone
developed
4.0 Testing phase
4.1 Product sample
prototypes given to
employees
4.2 Collecting
feedback from
employees
4.3 Sent the product
for changes
4.4 Milestone 4:
Product Testing
completed
5.0 Product launch
5.1 Develop digital
and Traditional
promotional
campaign
5.2 Market the
product
5.3 Milestone 5:
Product launched 6.0 Product Monitoring
6.1 Evaluate the
marketing campaign
6.2 Examine the
product success
6.3 Note the
drawbacks for
Second phase
6.4 Milestone 6:
Product monitored
Work break down structure
Samsung Smartphone
product development
1.0 Product planning and
concept
1.1 Identifying the
Specfication
1.2 Meeting with the
stakeholders
1.3 Amendment of
the primary
document
1.4 Product design
developed
1.5 Documentation
Deployment
1.6 Milestone 1:
Project Charter
Developed
2.0 Requirement analysis
2.1 Softw are
requirement
identification
2.2 Hardware
requirements
2.3 functional
requirement analysis
2.4 Initial Design
2.5 Board meeting
2.6 Modifications
noted
2.7 Dispatch for
approval
2.8 Milestone 2:
Functional
requirement
approved
3.0 Production
development Stage
3.1 integrate the
product
requirements
3.2 Develop product
3.3 Dispatch for
product testing
3.4 Milestone 3:
Smartphone
developed
4.0 Testing phase
4.1 Product sample
prototypes given to
employees
4.2 Collecting
feedback from
employees
4.3 Sent the product
for changes
4.4 Milestone 4:
Product Testing
completed
5.0 Product launch
5.1 Develop digital
and Traditional
promotional
campaign
5.2 Market the
product
5.3 Milestone 5:
Product launched 6.0 Product Monitoring
6.1 Evaluate the
marketing campaign
6.2 Examine the
product success
6.3 Note the
drawbacks for
Second phase
6.4 Milestone 6:
Product monitored
15PROJECT AND OPERATIONS MANAGEMENT
Project budget
The project will define the overall budget and the cost of each of the tasks. This is a
forecasted budget and the company will have to make sure to follow this as this is the optimal
budget for the next two years (Ochieng et al. 2018). The budget will increase if the resource
allocation is increased but there will be significant reduction in time. On the contrary, the budget
can be decreased by increasing the time span of the project. The table 4 shows that forecasted
budget for developing a smart phone for Samsung.
Task Name Resource Names Cost
Samsung Smartphone
product development
$421,504.00
1.0 Product planning and
concept
$50,736.00
1.1 Identifying the
Specification
Electronics and Communication engineer,
Instrumentation engineer, Project Manager,
Software developer
$22,080.00
1.2 Meeting with the
stakeholders
CEO, Finance manager, Human resource
Manager, Marketing manager, Project
Manager
$19,600.00
1.3 Amendment of the
primary document
Electronics and Communication engineer,
Instrumentation engineer, Software
$1,280.00
Project budget
The project will define the overall budget and the cost of each of the tasks. This is a
forecasted budget and the company will have to make sure to follow this as this is the optimal
budget for the next two years (Ochieng et al. 2018). The budget will increase if the resource
allocation is increased but there will be significant reduction in time. On the contrary, the budget
can be decreased by increasing the time span of the project. The table 4 shows that forecasted
budget for developing a smart phone for Samsung.
Task Name Resource Names Cost
Samsung Smartphone
product development
$421,504.00
1.0 Product planning and
concept
$50,736.00
1.1 Identifying the
Specification
Electronics and Communication engineer,
Instrumentation engineer, Project Manager,
Software developer
$22,080.00
1.2 Meeting with the
stakeholders
CEO, Finance manager, Human resource
Manager, Marketing manager, Project
Manager
$19,600.00
1.3 Amendment of the
primary document
Electronics and Communication engineer,
Instrumentation engineer, Software
$1,280.00
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
16PROJECT AND OPERATIONS MANAGEMENT
developer
1.4 Product design
developed
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$7,680.00
1.5 Documentation
Deployment
Instrumentation engineer $96.00
1.6 Milestone 1: Project
Charter Developed
$0.00
2.0 Requirement analysis $93,104.00
2.1 Software requirement
identification
Software developer $1,920.00
2.2 Hardware requirements
Electronics and Communication engineer,
Instrumentation engineer
$8,640.00
2.3 functional requirement
analysis
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$15,360.00
2.4 Initial Design
Electronics and Communication engineer,
Instrumentation engineer, Project Manager,
Software developer
$47,840.00
developer
1.4 Product design
developed
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$7,680.00
1.5 Documentation
Deployment
Instrumentation engineer $96.00
1.6 Milestone 1: Project
Charter Developed
$0.00
2.0 Requirement analysis $93,104.00
2.1 Software requirement
identification
Software developer $1,920.00
2.2 Hardware requirements
Electronics and Communication engineer,
Instrumentation engineer
$8,640.00
2.3 functional requirement
analysis
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$15,360.00
2.4 Initial Design
Electronics and Communication engineer,
Instrumentation engineer, Project Manager,
Software developer
$47,840.00
17PROJECT AND OPERATIONS MANAGEMENT
2.5 Board meeting
CEO, Finance manager, Human resource
Manager, Marketing manager, Project
Manager
$14,000.00
2.6 Modifications noted
Electronics and Communication engineer,
Instrumentation engineer, Project Manager,
Software developer
$5,152.00
2.7 Dispatch for approval Electronics and Communication engineer $192.00
2.8 Milestone 2: Functional
requirement approved
$0.00
3.0 Production
development Stage
$29,888.00
3.1 integrate the product
requirements
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$11,520.00
3.2 Develop product
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$17,408.00
3.3 Dispatch for product
testing
Project Manager $960.00
2.5 Board meeting
CEO, Finance manager, Human resource
Manager, Marketing manager, Project
Manager
$14,000.00
2.6 Modifications noted
Electronics and Communication engineer,
Instrumentation engineer, Project Manager,
Software developer
$5,152.00
2.7 Dispatch for approval Electronics and Communication engineer $192.00
2.8 Milestone 2: Functional
requirement approved
$0.00
3.0 Production
development Stage
$29,888.00
3.1 integrate the product
requirements
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$11,520.00
3.2 Develop product
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$17,408.00
3.3 Dispatch for product
testing
Project Manager $960.00
18PROJECT AND OPERATIONS MANAGEMENT
3.4 Milestone 3:
Smartphone developed
$0.00
4.0 Testing phase $37,536.00
4.1 Product sample
prototypes given to
employees
Human resource Manager, Project Manager $28,800.00
4.2 Collecting feedback
from employees
Electronics and Communication engineer,
Instrumentation engineer, Project Manager,
Software developer
$5,152.00
4.3 Sent the product for
changes
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$3,584.00
4.4 Milestone 4: Product
Testing completed
$0.00
5.0 Product launch $76,800.00
5.1 Develop digital and
Traditional promotional
campaign
Finance manager, Marketing manager $26,400.00
5.2 Market the product Marketing manager $50,400.00
3.4 Milestone 3:
Smartphone developed
$0.00
4.0 Testing phase $37,536.00
4.1 Product sample
prototypes given to
employees
Human resource Manager, Project Manager $28,800.00
4.2 Collecting feedback
from employees
Electronics and Communication engineer,
Instrumentation engineer, Project Manager,
Software developer
$5,152.00
4.3 Sent the product for
changes
Electronics and Communication engineer,
Instrumentation engineer, Software
developer
$3,584.00
4.4 Milestone 4: Product
Testing completed
$0.00
5.0 Product launch $76,800.00
5.1 Develop digital and
Traditional promotional
campaign
Finance manager, Marketing manager $26,400.00
5.2 Market the product Marketing manager $50,400.00
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
19PROJECT AND OPERATIONS MANAGEMENT
5.3 Milestone 5: Product
launched
$0.00
6.0 Product Monitoring $133,440.00
6.1 Evaluate the marketing
campaign
CEO, Marketing manager $105,600.00
6.2 Examine the product
success
Project Manager $13,440.00
6.3 Note the drawbacks for
Second phase
Project Manager $14,400.00
6.4 Milestone 6: Product
monitored
$0.00
Table 4
Resource table
The forecasted resource table shows the cost of each of the resources that will be used
along with the total number of hours they are required to work. The work has already been
divided according to the project requirements and table 5 describes the resources, their costs and
the hours of working.
Name Start Finish Cost Remaining
5.3 Milestone 5: Product
launched
$0.00
6.0 Product Monitoring $133,440.00
6.1 Evaluate the marketing
campaign
CEO, Marketing manager $105,600.00
6.2 Examine the product
success
Project Manager $13,440.00
6.3 Note the drawbacks for
Second phase
Project Manager $14,400.00
6.4 Milestone 6: Product
monitored
$0.00
Table 4
Resource table
The forecasted resource table shows the cost of each of the resources that will be used
along with the total number of hours they are required to work. The work has already been
divided according to the project requirements and table 5 describes the resources, their costs and
the hours of working.
Name Start Finish Cost Remaining
20PROJECT AND OPERATIONS MANAGEMENT
Work
Project Manager Mon 5/21/18 Wed 9/2/20 $106,080.00 1,768 hrs
Software developer Mon 5/21/18 Wed
11/13/19
$23,104.00 2,888 hrs
Instrumentation engineer Mon 5/21/18 Wed
11/13/19
$36,192.00 3,016 hrs
Electronics and
Communication engineer
Mon 5/21/18 Wed
11/13/19
$36,288.00 3,024 hrs
Human resource Manager Mon 7/2/18 Tue 10/15/19 $12,480.00 416 hrs
Finance manager Mon 7/2/18 Wed
12/25/19
$13,440.00 336 hrs
CEO Mon 7/2/18 Wed 7/22/20 $86,400.00 576 hrs
Marketing manager Mon 7/2/18 Wed 7/22/20 $107,520.00 1,536 hrs
Table 5
Project Manager
Software developer
Instrumentation engineer
Electonics and Communication engineer
Human resource Manager
Finance manager
CEO
Marketing manager
$0.00
$20,000.00
$40,000.00
$60,000.00
$80,000.00
$100,000.00
$120,000.00
Cost Variance
Graph 1
Work
Project Manager Mon 5/21/18 Wed 9/2/20 $106,080.00 1,768 hrs
Software developer Mon 5/21/18 Wed
11/13/19
$23,104.00 2,888 hrs
Instrumentation engineer Mon 5/21/18 Wed
11/13/19
$36,192.00 3,016 hrs
Electronics and
Communication engineer
Mon 5/21/18 Wed
11/13/19
$36,288.00 3,024 hrs
Human resource Manager Mon 7/2/18 Tue 10/15/19 $12,480.00 416 hrs
Finance manager Mon 7/2/18 Wed
12/25/19
$13,440.00 336 hrs
CEO Mon 7/2/18 Wed 7/22/20 $86,400.00 576 hrs
Marketing manager Mon 7/2/18 Wed 7/22/20 $107,520.00 1,536 hrs
Table 5
Project Manager
Software developer
Instrumentation engineer
Electonics and Communication engineer
Human resource Manager
Finance manager
CEO
Marketing manager
$0.00
$20,000.00
$40,000.00
$60,000.00
$80,000.00
$100,000.00
$120,000.00
Cost Variance
Graph 1
21PROJECT AND OPERATIONS MANAGEMENT
Quality plan
Policy/Directive/Standard/etc Reference Comment
Cost Benefit Analysis Project plan The cost benefit analysis will
evaluate the total cost and total
benefit obtained from each of the
phases which will enable the
organization to understand the
project feasibility and make
changes accordingly.
Cost of quality Metrics of quality The project manager will define the
standards outputs of each of the
phases and tasks so that the product
quality can be maintained.
Table 6 : (Nicholas and Steyn 2017)
Quality plan
Policy/Directive/Standard/etc Reference Comment
Cost Benefit Analysis Project plan The cost benefit analysis will
evaluate the total cost and total
benefit obtained from each of the
phases which will enable the
organization to understand the
project feasibility and make
changes accordingly.
Cost of quality Metrics of quality The project manager will define the
standards outputs of each of the
phases and tasks so that the product
quality can be maintained.
Table 6 : (Nicholas and Steyn 2017)
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
22PROJECT AND OPERATIONS MANAGEMENT
Risk register
Type of
risk
Risk Description Probability Impact Risk reduction
Strategy
Contingency
Plan
High Medium Low Performance Cost Time
Internal Scope creep The deviation
from the actual
result is one of
the common
risk factors in
projects which
results in the
change of
requirements in
of the project.
The project
deliverables will
have to closely
The project
manager cn use
agile
methodology
instead of the
waterfall method
which will enable
to reduce the cost
and develop
product at each
phases.
Risk register
Type of
risk
Risk Description Probability Impact Risk reduction
Strategy
Contingency
Plan
High Medium Low Performance Cost Time
Internal Scope creep The deviation
from the actual
result is one of
the common
risk factors in
projects which
results in the
change of
requirements in
of the project.
The project
deliverables will
have to closely
The project
manager cn use
agile
methodology
instead of the
waterfall method
which will enable
to reduce the cost
and develop
product at each
phases.
23PROJECT AND OPERATIONS MANAGEMENT
monitored and
measured in
order to avoid
changes in
requirement
after phase 2 of
the project
External Change in
market prices of
components
The
organization
should develop
better
relationship
with suppliers
and buy the
widely used
components in
bulk to avoid
this.
The organization
can develop a
vertical
integration
process for
manufacturing the
component
themselves.
monitored and
measured in
order to avoid
changes in
requirement
after phase 2 of
the project
External Change in
market prices of
components
The
organization
should develop
better
relationship
with suppliers
and buy the
widely used
components in
bulk to avoid
this.
The organization
can develop a
vertical
integration
process for
manufacturing the
component
themselves.
24PROJECT AND OPERATIONS MANAGEMENT
Internal Time delay in
getting approval
for project
initiation
Developing an
effective
communication
plan and
holding frequent
meetings will be
an effective way
of reducing this
risk factor.
The project team
should set include
buffer time in
each of the tasks
to avoid the actual
delay.
Table 7: (Turkulainen et al. 2015)
Internal Time delay in
getting approval
for project
initiation
Developing an
effective
communication
plan and
holding frequent
meetings will be
an effective way
of reducing this
risk factor.
The project team
should set include
buffer time in
each of the tasks
to avoid the actual
delay.
Table 7: (Turkulainen et al. 2015)
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
25PROJECT AND OPERATIONS MANAGEMENT
Conclusion
Thus, it can be concluded from the report that an effective project management plan has
been developed to build a Smartphone that is superior to the products in the market. The risk
factors and the quality control measures have been defined in the study and Samsung will have to
follow this method to successfully develop the product. However, agile methodology is a
contingency plan which should be used when there is too much deviation from the original
specification of the stakeholders.
Conclusion
Thus, it can be concluded from the report that an effective project management plan has
been developed to build a Smartphone that is superior to the products in the market. The risk
factors and the quality control measures have been defined in the study and Samsung will have to
follow this method to successfully develop the product. However, agile methodology is a
contingency plan which should be used when there is too much deviation from the original
specification of the stakeholders.
26PROJECT AND OPERATIONS MANAGEMENT
References and Bibliography
Binder, J., 2016. Global project management: communication, collaboration and management
across borders. Routledge.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management.
Project Management Institute.
Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach.
Routledge.
Heldman, K., 2018. PMP: project management professional exam study guide. John Wiley &
Sons.
Hitt, M.A., Xu, K. and Carnes, C.M., 2016. Resource based theory in operations management
research. Journal of Operations Management, 41, pp.77-94.
Holweg, M., Davies, J., De Meyer, A. and Schmenner, R., 2018. Process Theory: The Principles
of Operations Management. Oxford University Press.
Mahadevan, B., 2015. Operations management: Theory and practice. Pearson Education India.
Maylor, H., Turner, N. and Murray-Webster, R., 2015. “It worked for manufacturing…!”:
Operations strategy in project-based operations. International Journal of Project
Management, 33(1), pp.103-115.
News.samsung.com 2018. SAMSUNG NEWSROOM. [online] News.samsung.com. Available at:
https://news.samsung.com/global/ [Accessed 29 Apr. 2018].
References and Bibliography
Binder, J., 2016. Global project management: communication, collaboration and management
across borders. Routledge.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management.
Project Management Institute.
Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach.
Routledge.
Heldman, K., 2018. PMP: project management professional exam study guide. John Wiley &
Sons.
Hitt, M.A., Xu, K. and Carnes, C.M., 2016. Resource based theory in operations management
research. Journal of Operations Management, 41, pp.77-94.
Holweg, M., Davies, J., De Meyer, A. and Schmenner, R., 2018. Process Theory: The Principles
of Operations Management. Oxford University Press.
Mahadevan, B., 2015. Operations management: Theory and practice. Pearson Education India.
Maylor, H., Turner, N. and Murray-Webster, R., 2015. “It worked for manufacturing…!”:
Operations strategy in project-based operations. International Journal of Project
Management, 33(1), pp.103-115.
News.samsung.com 2018. SAMSUNG NEWSROOM. [online] News.samsung.com. Available at:
https://news.samsung.com/global/ [Accessed 29 Apr. 2018].
27PROJECT AND OPERATIONS MANAGEMENT
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and
technology. Taylor & Francis.
Ochieng, E.G., Ovbagbedia, O.O., Zuofa, T., Abdulai, R., Matipa, W., Ruan, X. and Oledinma,
A., 2018. Utilising a systematic knowledge management based system to optimise project
management operations in oil and gas organisations. Information Technology & People, 31(2),
pp.527-556.
Turkulainen, V., Ruuska, I., Brady, T. and Artto, K., 2015. Managing project-to-project and
project-to-organization interfaces in programs: Organizational integration in a global operations
expansion program. International Journal of Project Management, 33(4), pp.816-827.
Vaughan, P. and Parker, D., 2015. Project-based change management body of knowledge:
integrated intervention. In European Operations Management Association (EurOMA)(pp. 1-10).
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and
technology. Taylor & Francis.
Ochieng, E.G., Ovbagbedia, O.O., Zuofa, T., Abdulai, R., Matipa, W., Ruan, X. and Oledinma,
A., 2018. Utilising a systematic knowledge management based system to optimise project
management operations in oil and gas organisations. Information Technology & People, 31(2),
pp.527-556.
Turkulainen, V., Ruuska, I., Brady, T. and Artto, K., 2015. Managing project-to-project and
project-to-organization interfaces in programs: Organizational integration in a global operations
expansion program. International Journal of Project Management, 33(4), pp.816-827.
Vaughan, P. and Parker, D., 2015. Project-based change management body of knowledge:
integrated intervention. In European Operations Management Association (EurOMA)(pp. 1-10).
1 out of 28
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
© 2024 | Zucol Services PVT LTD | All rights reserved.