POPP5013: Project Management - New Premium Soups Project Plan

This report details a project plan for the new product development of premium soups. It includes a project background, objectives, and deliverables within a six-month timeframe and a $25 million budget. The plan utilizes a project life cycle approach with five stages: initiation, conceptualization, planning, monitoring, and closure. Key components include a project charter, situational analysis using PESTLE, project scheduling with WBS and Gantt charts, risk and responsibility management, and a communication strategy. The PESTLE analysis identifies political, economic, social, technological, legal, and environmental factors influencing the project. The work breakdown structure (WBS) organizes the project into manageable tasks, while the Gantt chart schedules activities and timelines. The plan emphasizes adherence to time, budget, and quality constraints, with the final product delivered to senior management.

Project plan1
Project plan for new product development of premium soups
Submitted by
Affiliation
Supervisor’s name
Date of submission

Project plan2
Project background context
New product development is important in ensuring any business have a competitive edge in the
number and quality of the goods being offered in the market. ‘New product development entails
coming up with suitable, economic, and desirable plan of coming up with a product that meets
the market demand and customer satisfaction’ (Von Zedtwitz, 2014 p. 255-268). In marketing a
good product introduced to the market will depend on the new development process that was
achieved successfully by the project teams. The process requires proper planning and
organization through a suitable presentation. The sponsor contacted the business in order to draft
a project plan for a new development for a range of premium soups. The project plan
development and design process involves establishing suitable techniques, processes and
networks for enabling the organization to produce quality project that will meet consumer needs.
The new product development of the soups is intended to start in a period between may-August
2019. The period will provide a suitable time in which the product is estimated to perform well
in the market. The entire process of new product development is estimated to cost about $25
million during the start and launching of the product in the market. The amount of the budget
was agreed upon by the project sponsors and no exceeds will be desirable. Proper process and
techniques will be put in place in order the budget is utilized well and ensure accountability
measures are taken in consideration. Once the project is complete it is expected to meet the
constraints of time, budget and quality. Project constraints are important aspects in projects that
ensures that customers are satisfied with the final product. The final product will be delivered to
the senior management team representing the sponsorship of the project.
Project execution and delivery
‘The project team will apply project management techniques, methods and tools to ensure that
the project is delivered according to the required specifications and standards’ (McClory, Read &
Labib, 2017 p.1322-1335). The project management approach will be of that of the project life
cycle approach that will entail five stages from beginning to the end. The project plan will begin
with initiation of the idea, conceptualizing of the idea generated, planning, and monitoring and
project closure. The items presented in the project plan will include: a brief project charter,
situational analysis (PESTEL analysis), project scheduling (WBS, Gantt chart), risk management

Project plan3
(risk register), responsibility management (RACI), project communication (project management
strategy), and project closure. The brief project charter will entail the following outlined parts.
Project goal/objective: the goal of the project is to develop a new range of premium soups for a
period of 6 months.
Project deliverables: the main key deliverables of the projects will entail: generation of the idea,
researching on the product, development of a prototype, testing the prototype, trainings and
communications, launching of the products, and review of progress/performance.
Project budget: the budget will be done according to top down budget methodology based on the
estimated total amount breaking it down to sections. Allocation of costs will be based on the
market prices of inputs.
Project constraints: the project is intended to be done within the constraint of time, budget and
quality.
Project assumptions: the assumptions of the project is that there will be no major changes in
legislative framework or intense competition that will affect the project outcomes.
Project out- frame/in-frame: the project will be concern with only research, manufacturing,
marketing and development of the project. It will not concern itself with sourcing of resources to
support the project.
Acceptance criteria: the project sponsors will sign off on projects that will only meet their
required standards and specifications. This will take place at each phase or stage of the project
life cycle.
Situational analysis (PESTLE analysis)
Launching of the new product will involve carrying out a situational analysis through a
comprehensive research process. ‘The process of PESTLE analysis take place during the
conceptualization stage of a project idea’ (Jones, Lewis, Groomes & Adams, 2015 p.23-56). The
process involve gathering information regarding the project idea by analyzing the environment
components though the process of PESTLE analysis. The PESTLE analysis as illustrated in
(appendix I) shows analysis of the environment components on the basis of the project idea.

Project plan4
Some of the components that are shown and analyzed included: political, economic, social,
technology, legal, and environmental factors. The factors are used in planning process in
justifying the need of continuing the development and execution of the product. The analysis
showed that some of the factors directly affect the project delivery of the project as indicated in
(appendix I) the management did make mitigation measures and assumptions in order to address
some of the factors. Both these factors provide a positive and negative influence on the project
delivery and it will be worthwhile to review their general effect to the product development. ‘In
brief the PESTLE analysis of the various factors can provide suitable justification and decision
making of the business situation analyses (John Wiley & Sons. Sonavane, Rathi, Patil, 2018
p.25-78). As illustrated on appendix I the following is a summary of items denoted from the
template. Social and political factors were some of the factors that the project team will make
assumptions over them not to occur and affect the outcome of the process. Some of the social
and political factors that can affect the project outcomes include: life styles, leaders influence,
demographic changes. Economic factors were considered well in planning process through
contingency plans in order they do not affect the budgeting process. Some of the economic
factors that can influence the product delivery include: currency changes, market demand, and
price changes. Positively market factors were assessed to establish if whether they would provide
sufficient results. All aspects of legislative process and documentation will be considered to
avoid any conflicts and court battles. ‘Technology will never be ignored in the entire process,
modern and flexible technologies will be adopted in order to provide suitable products meeting
customer needs’ (Hidding & Nicholas, 2017 p.81-95). Proper research will be conducted on the
best technology that will be adopted for production process. The results of a suitable PESTLE
analysis will be suitable in planning process. The product to be developed will ensure that it
complies with environment sustainability best practices that will not pollute the environment.
Project organizing and scheduling
Project organizing (WBS)
‘Project organizing involves the process of dividing tasks, unifying similar tasks into units, and
creating relationships in order to achieve the desired goal’ (Bryde, Broquetas & Volm., 2013
p.971-980). The project team will be using the work breakdown down structure (WBS) as part of
the organizing tool as illustrated in appendix II. The WBS involves the process of dividing the

Project plan5
project into sub projects, the sub-projects to tasks, tasks divided into sub tasks, sub-tasks are
further divided into work packages. The development of WBS was depended on the deliverable
of the projects outlined. The various WBS was developed from the following milestones:
1. Research development-the process will involve the process of coming up with the best ideas
by gathering required information. The process will involve other processes that will be
required to analyze information’s. The other sections involved in the process include:
carryout PESTLE analysis, resigning prototype. The PESTLE analysis will involve gathering
information to explain the situation in hand. Prototype development will involve coming
suitable designs that will resemble the future productions. The new product development will
entail developing suitable prototype that will fit the market needs.
2. The project delivery and execution-it will involve stage in which the product will be
introduced to the market. The delivery of the product will depend on its reception by the
market. A suitable method need to be formulated in order to come up with a useful system
that will make the product accepted in the market. The main events during the stage as shown
in appendix II include: prototype testing and launching of the product. In project
management the stage is important because majority of the activities and efforts take place.
Majority of resources are consumed during the particular stage and that need to be controlled
fully.
3. The last stage of the project will be closure which will entail coming up with a suitable
mechanism to allow slow closure or termination of project deliverables. The process involves
closing the required items and eventually handing over to the required user. The WBS
indicated in appendix II shows the key events during closure. A project manager will use
project closure checklists that will comprehensively take consideration of the items required
to be part of the closure process.
Suitable WBS as illustrated in appendix II is important in allocation of resources, time and
reducing conflicts emanating from overlap of tasks and inefficiencies in operations. The WBS if
developed well is a critical tool that if developed well can contribute significantly to the final
outcome of the project. The project organizing will take place during the planning phase of the
project. It is then important for project managers to adopt suitable WBS structure suitable for the

Project plan6
organization needs and operations (Burke, 2013). In the project the WBS was developed using
the top down structure which follows project being divided into a lower parts. The divided units
will form sections in which it will make it easier to allocate resources and assign responsibilities
to them. That will be illustrated in development of Gantt charts and responsibility matrix in the
plan development.
The several of the components of how the project is divided as indicated in appendix II. The
components of the project divided include: generation of the idea, researching on the product,
development of a prototype, testing the prototype, trainings and communications, launching of
the products, and review of progress/performance. ‘These mentioned components represent
project main deliverables. The researching the idea will be further divided to sections like
situational analysis and secondary gathering’ (Cleland, 2013 p.34). The development of a
prototype will involve design, testing of the product. The trainings and communications will be
further divided into: workshops, on trainings, developing communication frameworks.
Launching of the product as illustrated in the appendix II will be divided into selling, distribution
and feedback gathering in the market. The review of progress and performance will involve:
final evaluation, corrective measures and handing off the project to the rightful owners. The
WBS for the project will form an important components that will ensure work flows with
efficiency and effectiveness.
Project scheduling (Gantt chart)
‘Project scheduling involves the process of structuring activities, building relationships by
establishing dependencies or independencies, and allocating resources over them’ (Fink, 2016
p.24). There are other scheduling tools like the network analysis but the current project will be
utilizing the Gantt chart. Gantt chart is an example of a project scheduling tool that provides
relationship between project activities and time allocated for them. It is a diagrammatic
illustration shown in appendix III showing how activities in sequence are allocated starting and
ending times. ‘The development of the Gantt chart depended highly on the milestones of the
projects developed taking consideration of the starting and ending times of the project activities’
(Gido & Clements, 2014 p.56). The milestones shows the activities with the scheduled times the
activities are part of those that were divided during the development of WBS in appendix II. As
shown in appendix III the milestones for the project were: researching on the product starting on

Project plan7
May 23rd to June 5th, development of a prototype began in 8th June to 16 June, testing the
prototype began 23rd to 30th June 2019, trainings and communications will begin in 1st July to 20th
July, launching of the products will begin in 23rd July to 30th June, and review of
progress/performance begin 2nd August to 15th August 2019.
The scheduling of time for the three months new development product of premium soups was
based on a number of factors. A shorter time was required to avoid competition that was present
in the market any delay would have dissolved the entire process negatively. As illustrated in
appendix III the calculation of the times were based on most likely time that took consideration
of optimistic and pessimistic times to come up with an average time. ‘Proper scheduling is
important in projects in creating activities dependencies and independencies that can facilitate
easy allocation of resources and time’ (Heagney, 2016 p.45). There are other benefits that can be
derived from the Gantt chart development by ensuring efficiency of activities, avoiding lagging
behind of certain activities, reducing prolonging in certain tasks, assigning resources, easy
allocation of duties and responsibilities. The project scheduling will take place during the
planning stage or phase of the project life cycle which will further be executed during the project
implementation process. The diagram shown in appendix III clearly shows the various activities
that will take place in delivering the project outcomes and ensuring an efficient project
execution.
Project risk management (risk register)
Management and planning of risks in projects is a very critical component that cannot be ignored
or assumed (Hedman, 2013). The risk management and planning in certain books is also known
as risk management system. ‘Risk management system involves the process of identifying,
analyzing, evaluating, mitigation through planning and risk reporting’ (Hedman, 2013 p.345).
The most suitable tool that will document how the project risks will be managed is shown in
appendix IV known as risk register. The definition of a risk register is a written document that
shows the risks, effects and mitigation of risks in a project. As shown in appendix IV there are
several risks that the project identified that would affect the project they included: changes in
tastes and preferences, high competition in the market, changes in legislations and policies, and
changes in technology. The identification process was through brain storming and expert
reviews. Through analysis and evaluation through impact/probability occurrence matrix which

Project plan8
helped in the ranking it showed that some of the risks as shown in appendix IV had high
occurrence and impact levels. The ones with high probability occurrence and impact will be
ranked higher and given more considerations during the mitigation process. ‘Those with low
occurrence or occurrence levels are not ignored but suitable measures are placed over them to
manage their influence and effects’ (Joslin & Müller, 2015 p.68).
The risk register in appendix IV shows that some of the risks will be monitored, transferred and
shared as a means of mitigating them. ‘The register shows the suitable measures that can be in
place in case they occur in projects’ (Kendrick, 2013 p.84). The register will provide a main key
role of communicating various assumptions and a certainties that would occur in projects. The
register will be presented to the relevant stakeholders involved in the project as a means of
creating awareness. Risk management systems in projects are important in projects because it
can eliminate wastages, avoid stopping of project operations, and facilitate project contingency
planning. This can take place earlier during the planning phase of the project but need to factor in
each of all project stages. As shown in appendix IV every person in charge of an activity or
responsibility will be in charge of the risk if it occurs. Proper risk management is one of the main
method in project management that will enable the product to be delivered according to the
acceptance criteria of the users.
Project responsibility
Part of human resource management activity is allocation of duties and responsibilities to project
teams (Larson, 2011). In projects responsibility management is an important aspect in projects
that ensures responsibilities are given high accountability and integrity in delivery of the
operations. Responsibility, accountability, communicate, involve (RACI) matrix as shown in
appendix v form a very important tool for allocation of duties and responsibilities to project team
members and making them participate in general delivery of the project (Turner, 2014 p.56).
RACI is developed in projects depending on a number of factors in projects which include: level
of education, competency, experience and availability of the project employees. There are certain
tasks that will be divided and given as shown appendix IV and given to certain individuals to be
responsible over them. Those given responsibilities are expected to be leaders in the areas
allocated to them and would represent the others in case of any clarification or query. Those who

Project plan9
are accountable as per appendix v are expected to be fully in charge of any formal processes
inputs and resources are directly answerable in case of loss of inputs or integrity issues.
There are others as indicated in appendix v are expected to be communicated too in every project
activity delivery. Those who will be communicated are expected to be aware of things going on
in the projects. It is a way of increasing the level of involvement among all the project teams. But
there are also others as per appendix v that will require to be involved in the process. The
involvement is important because they would provide expert advice role or it is related with
some of the activities they are performing which can be having a relationship with the scheduled
tasks. Overall development of RACI in project delivery is important in ensuring that the project
is achieved as per set targets. The benefits that can accrue by having a RACI matrix include:
increasing participation among project team members, increasing efficiency, enhancing project
commitments, and increasing desired results. RACI is developed during the planning phase of
the project but will become effective across other stages of the project. It is then important that
project managers formulate the RACI at earlier stages to enhance their co-ordination and
direction functions in projects. RACI in the new development of the premium soups will be
important in ensuring that the project will be delivered within budget and time (Scholes, 2013
p.67).
Stakeholder management strategy
Stakeholder management is a critical component delivery of any projects. Stakeholders involve
individuals that are directly or indirectly affected by the project. In the new development of
premium soup project some of the stakeholders as illustrated in appendix VI using the
stakeholder communication strategy include: project team members, senior management teams,
other departmental staff, customers, and suppliers. Stakeholder analysis was conducted to
identify, analyze and provide means of communicating to them relevant data related to the
project (Meredith & Mantel, 2017 pp. 521-550). The stakeholder communication strategy
illustrated in appendix VI shows the stakeholders, their interest in the project, there effect to the
project, methods to communicate to them, and timing for communication. Based on their
influence they can be classified as primary, secondary or tertiary stakeholders (Van Horne, 2017
p.87). The primary are those with greater influence and directly affected by the project,
secondary are those affected indirectly by the project, and tertiary are those that are part of any

Project plan10
project delivery. Both form part of the project delivery and they need to form part of the project
delivery strategy.
As shown in the appendix VI the senior management teams are the primary secondary type of
stakeholders that need to be informed on the progress of the project on occasional times. They
are primary in providing resources and making critical decisions in projects. Others like the
customers are important they represent secondary stakeholders they will be successful in
acceptance of the product they need to be involved or informed of the project outcome as shown
in appendix VI. The tertiary stakeholders can involve relevant authorities and members of other
department within the organization affected by the project activities. But need to be informed
and be part of the project execution and delivery. There reasons why stakeholder management
strategy is important in projects. They help in reducing conflicts, increasing ownership, and
enhances sustainability of the projects. The stakeholder analysis strategy need to be conducted at
earlier stages during the planning phases (Milosevic & Martinelli, 2016 p.89). But it will need to
be managed in other stages of the project to ensure smooth delivery of the outputs and provide a
desirable tool for communicating project aspects to the stakeholders. If the stakeholder
management is not done the project can face several risks which can affect its execution causing
delay in delivery of the intended results. Appendix VI directly shows the stakeholder strategy
communication matrix for the new development of premium soups.
Conclusion
The conclusion will involve closing out of the project or reviewing the extent to which the
project was able to achieve the intended objectives. Project closure which can resemble
conclusion of a project involves the process in which the project reaches the entire end. The
project goal was measured on the basis of three constraints of quality, budget, and time. This
means that the evaluation of the success of the new development of premium soup will be based
on the mentioned criteria. The project will be successful if the results are done within the quality,
and if the budget is not overrun or underrun or it is accomplished within the three month period.
A post evaluation will be conducted to enable understand the key learning experiences of the
project and identifying any other limitations or weaknesses that did affect the project outcomes.
During the closure period the project will be handed over to the rightful owners after certain
factors have been considered. The items to be addressed include: if the project was accepted by

Project plan11
the owners, resources, and contract closure and termination meetings. Each of the items will be
evaluated and proper mechanisms formulated in order to ensure they are completed effectively
and within the required time to avoid any form of spillovers of conflicts and complains.
The employment of the project management techniques and methods will enable the project to be
achieved according to the desirable results. The project of new production of premium soups can
be successful if all the planned activities are followed to the latter. The use of the project tools
like stakeholder matrix, risk registers, WBS, Gantt chart and RACI will be helpful for the
management team to deliver the project. The tools will ease the project management functions
and will provide suitable reference points in making valuable decisions. They have been useful
in management of resources, stakeholders, risks management, and work organizations and
scheduling. In every project the closure time will provide the conclusion of the project and
should be done effectively because it is the last stage of the project. It also important in any type
of projects that tools and methods relating to projects can be useful in planning project outcomes
successfully. In conclusion there are several project but its success stories are depended on the
techniques and methods that have been used to design, develop and implement the various
deliverables.

Project plan12
Reference lists
Bryde, Broquetas & Volm., 2013. The project benefits of building information modelling.
International Journal of project management, 31(7), 971-980.
Burke, R. 2013., Project management: planning and control tecniques. New Jersey: Wiley
publishers.
Cleland, D., 2013. Project management handbook. New York, United States: Van Nostrand
Reinhold.
Fink, A. 2016., How to Conduct Surveys: A Step-by-step Guide. Beverly Hills. CA: Sage.
Gido & Clements., 2014. Successful project management. Chicago: Nelson Education.
Harrison, and Lock, D., 2017. Advanced project management: a structured approach. New
York: Routledge.
Heagney, J., (2016). Fundamentals of project management. AMACOM: American management
association .
Heagney, J., 2016. The project manager leader. In fundamentals of project Management. New
York: Adventure works press.
Hedman, K., 2013. Project management professional exam study guide. Indianapolis: Wiley.
Hidding, G.J. and Nicholas, J.M., 2017. A new way of thinking about IT project management
practices: Early empirical results. Journal of Organizational Computing and Electronic
Commerce, 27(1), 81-95.
John Wiley & Sons. Sonavane, S., Rathi, M. and Patil, S., 2018. Practice Based Closure Quality
Loop Optimization in Teaching Learning Process: A Case Study in Software Engineering
Design. International Journal of Education and Learning Systems, 4(1), 25-78.
Jones, T.A., Lewis, T.A., Groomes, D.A. and Adams, L.A., 2015. Casework Management Using
Double Loop Learning. Journal of Rehabilitation Administration, 39 (2), 23-56.

Project plan13
Joslin, R. and Müller, R., 2015. Relationships between a project management methodology and
project success in different project governance contexts. International Journal of Project
Management, 33(6), 1377-1392.
Kendrick, T., 2013. The project management tool kit: 100 tips and techniques for getting the job
done right. . AMACOM Div: American management Assn.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling . New York: John Wiley & Sons.
Kloppenborg, T., 2014. Contemporary project management. London: Nelson Education.
Larson, E., 2011. Project management: the managerial process. New York: Mc Graw Hill.
Lowe, D., 2016. Commercial management of projects;defining the dicipline. Chicago:
Blackwell.
McClory, S., Read, M. and Labib, A., 2017. Theorizing the lessons-learned procedure in project
management: Concerning a triple-loop knowledge framework. International Journal of Project
Management, 35(7), 1322-1335.
Meredith, J.R. & Mantel, S.J., 2017. Project management: a managerial approach. Hoboken:
Wiley.
Milosevic, D.Z. and Martinelli, R.J., 2016. Project management toolbox: tools and techniques
for the practicing project manager. . Chicago: Wiley.
Phillips, J., 2013. PMP, project management professional (certification study guides). New
York: Mc Graw Hill.
PMI., 2013. A guide to project management body of knowledge . Newtown Square: PA: PMI.
Scholes, G., 2013. Project consultancy and contracting. New Delhi: New Age.
Simpson, F., 2013. Performance reporting in projects. Adventure works monthly, 12-78.
Turner, R. 2014. Contracting for project management. New York: Gower publishing.

Project plan14
Van Horne, G., 2017. Financial managements: cases and applications. London: Mc Graw Hill
publishers.
Von Zedtwitz, M., 2014. Organizational education through post project appraisals in R&D. R&D
Management, 32 (3), 255-268.

Project plan15
Appendices I PESTLE analysis
Factor Explanation of the analysis
Political The political environment is conducive to conducting of the
business. The leaders will not affect the operations of the business.
Economic There are certain factors that will be assumed to be constant and will
not affect the operations of the business e.g. prices, currency levels.
The demand of the products is conducive to enable sale and
distribution of the product. There is also availability of inputs for the
production process.
Social The business environment in terms of beliefs, cultures, and lifestyles
have no impact on the project delivery. Analysis shows that they are
not a threat but an opportunity.
Technology The project will adopt suitable technologies that is modern they will
include use of suitable tools, equipment’s and systems.
Legal The legal environment is very conducive it encourages the
operations of the project.
Environment The project is conducive to the environment and will not pollute it.
They will remain sustainable in the long run.

Project plan16
Appendices II: WBS
New premium soup product development
1.0
Research &
development
1.1
Pestle analysis
1.1.1
Designing prototype
1.1.1.1
Pilot and execution
1.2
Prototype testing
1.2.1
Launching of product
1.2.1.1
Closure
1.3
Closing of items
1.3.1
Handing over
1.3.1.1

Project plan17
Appendices III: Gantt chart
May
2019
MAY
2019
JUNE
2019
JUNE
2019
JULY
2019
JULY
2019
AUGUST
2019
Project plan
development
Situation
analysis
Designing
product
prototype
Testing the
prototype
Launching of
the product
Training,
monitoring
Evaluation and
project
closure

Project plan18
Appendices IV: Risk analysis
Prepared by:
project manager Date:18/5/18
Rank Risk Description Root Cause Potential
Responses
Risk Owner Probability Impact
1 Changes in
legislations
Poor planning Contingency
plans
Project
manager
high High
2 Changes in
technology
Changes in
technology
used in
productions
Lack of
environmental
scanning
Plan
contingency
plan
Project
team
High High
3 None
responsive
markets
Customers
refuse to
adopt
products
Lack of market
surveys
Awareness
creation
Project
team
High Low
4 Competition Unhealthy
competition
Poor competitors
analysis
Need to
conduct
operation
early
Project
team
Low High

Project plan19
Appendices V: RACI
RACI CHART PERSONS/TEAMS
ACTIVITY Project
manager
A
Employee
B
Project
sponsor
User
departments
Development of plan R A C I
Pestle analysis R C A I
Prototype development 1 A R C
Project delivery C R A 1
Updating documents I C A R
Launching of project C I R A
Tests & delivery I A R C
Communications I A C R
Technical human resource R A C I

Project plan20
Appendices VI: STAKEHOLDER STRATEGY REGSITER
Prepared by: project manager Date: 18/05/2019
Name Project Position Contact
Information
Project Management
Deliverables.
Due Date
Distribution
Potential Management Strategies
Senior management teams Sponsors xxxx Project report and project
plan, progress report
Periodically Have consultative meetings
Project team members Employees yyyy Project plan Often Project team members/participation
strategies
Other departmental
representatives
Users nnnnn Progress report Occasionally Consultative meetings
Customers Customers vvvvv Progress report Often Periodic meetings