Student name

1
 Contents
Introduction.................................................................................................................... 3

Literature review............................................................................................................ 4

Project selection............................................................................................................ 5

Methodology...................................................................................................................7

Analysis.......................................................................................................................... 8

Critical Evaluation..........................................................................................................9

Synthesis of Original Recommendations..................................................................10

Conclusion....................................................................................................................10

References.................................................................................................................... 11

2
Introduction
In the analysis of new product development projects, developing beyond superficial
observations to a deeper understanding that transcends traditional case study
summaries is therefore critical(Takeuchi & Nonaka, 1986). This research is underpinned
by the need for innovation and depth with a desire to offer new perspectives on project
planning. As an alternative, this approach uses a deep analysis of two newly selected
NPD projects and internal sources. The criteria used in this selection process will be
specific to ensure that the selected materials are relevant and applicable for the stated
scope. The following analysis will not just narrate historical events but critically analyse
the methods, procedures and techniques used in these projects. The focus will be
directed at either personal involvement or access to primary sources, adding
experiential aspects that go beyond the limitations of formal literature. This introduction
paves the way for a broad study that aims to reveal unique and profound insights into
new product development project management(Wind & Mahajan, 1997).

The focus of this analysis on new product development projects is to get beyond the
ordinary and undertake an experiential journey that possesses both creativity and
depth. This need to evaluate the new product development projects goes beyond simple
re-telling of previous historical cases and necessitates a critical analysis that should
bring some fresh insights into project planning and management debates. This analysis
is not just limited to the superficial summaries that have been mentioned in previous
literature. However, it is a conscious attempt to understand the complexities of project
management methodologies, processes and techniques. For this study, the chosen
reference class is that of innovative product development which encompasses
innovation, market dynamics and strategic planning to institute a process through which
new ideas are created with desirable scope. This analysis seeks to compare, contrast,
and critically evaluate two projects by focusing on a pair of relevant cases. These
projects will act as a background where the concepts learned in BUS9041M Project
Planning and Management will be implemented and evaluated(Bhuiyan, 2011).

Under this chosen analysis, a few essential elements are included to reflect various
aspects of the selected projects. In the first instance, well-defined criteria that guide the

3
selection of projects will be established to ensure their compliance with specific scope
and objectives set for this assignments. This step is vital for informing about the
relevance and applicability of scrutinized projects to a broader theme that involves new
product development. This deliberate process can be made effective by establishing
clear criteria and the selection is directed toward projects that are not only informative
but could also represent contexts of key challenges, issues or opportunities in a sector.

After that, the analysis will go beyond traditional case study summaries by adopting a
methodology emphasizing depth and intrinsic value. But the aim is to come beyond
mere reiteration of project histories and recorded outputs. Alternatively, the attention will
be drawn to a critical analysis of used methodologies approaches, procedures and
techniques in each chosen project. This also includes an analysis of the decision
making, risk management and stakeholder engagement approaches used during each
project cycle. The objective is to identify the underlying factors that facilitated or
inhibited project success and failure, with a specific focus on how applicable these
methodologies are in relation to BUS9041M module lessons(Sethi, 2000).

In addition, the selected method puts more emphasis on a personal touch in analyzing.
This is through borrowing from personal stories and perceptions, if possible, to add
context that helps increase the level of comprehension. Through incorporation of
personal viewpoints within the analysis, it seeks to go beyond simple criticism and
supply a more refined approach which considers realities achieved in practice by
managing new product development projects. This personal touch breaks away from
academic standards but also makes the evaluation deeper and more contextual.

Essentially, this introductory approach formulates a methodology that involves more

than the surface level and leads to gaining deeper insights into new product
development projects. The selected reference class helps to create a specific prism
through which the principles learnt in BUS9041M module will be used, analyzed and
evaluated. The following sections of this report will reveal the underlying complexities
associated with project management methodologies, procedures, and techniques used
in such projects analyzed herein as a refined analysis based on personal insights and
scholarly literature alongside the overall objectives that govern this assignment. By

4
applying this method, the analysis seeks to significantly enhance project planning and
management as a field of knowledge(Ogawa & Piller, 2006).

Literature review
All the literature on NPD methodologies, procedures and techniques is a resource of
theoretical frameworks empirical studies as well as practical perspectives. In the world
of project planning and management, especially relating to BUS9041M, a well-rounded
literature review is vital for contextualizing and critiquing “NPD methodologies
commonly utilized.”

A very important aspect of NPD is traditional and modern techniques. Traditional course
tends to follow a linear or sequential model wherein each step of the development
process is performed as in sequence. These models exemplify stability and determinism
in the sense of project development represented by them. However, the criticism to
such approaches is their rigidness because they may not be able to respond to
unanticipated changes or market movements. On the contrary, contemporary
methodologies rely on iterative and agile approaches like Agile or Scrum where
changes are possible during development. These more recent methodologies seem to
respond better to uncertainties in NPD, promoting flexibility and stakeholder
participation(Kahn, Barczak, Nicholas, Ledwith, & Perks, 2012).

Key observations from previous studies emphasize the role of customer-oriented

practices in NPD approaches. For example, Design Thinking promotes sympathizing
with end-users to better understand their desired needs and hence producing products
that will more likely find a ready market. Likewise, the LPPD aims at eliminating waste
and optimizing value to a customer; this is in line with current trends of efficiency and
sustainability. But the critical analysis of these approaches focuses on difficulties in
reaching an equilibrium between customers-oriented innovation and operational
performance. As literature indicates, involvement of the customers is very critical
whereas exaggerated focus might result in scope creep and delays in projects if not
managed carefully(Tzokas, Hultink, & Hart, 2004).

5
The process of risk management is constantly mentioned in the literature dedicated to
NPD methodologies. The traditional PM frameworks tend to treat risk as an isolated
phase rather than a naturally occurring one of project development at large. Meanwhile,
modern approaches like Risk-Driven Model encourage a steady and dynamic risk
management procedure during the whole project lifecycle. The literature review
identifies, therefore, the benefits of these emerging practices to cope with uncertainties
in NPD project and but also questions their scalability.

Besides methodologies, the literature provides insights into process aspects of NPD.
For example, the Stage-Gate process offers a structured approach where projects
progress through gates at each development stage helping in decision making and
resource allocation. The emphasis of the Critical Chain Project Management (CCPM)
methodology is on resources’ optimization to shorten project duration. Yet, the criticism
frequently focuses on limiting rigidity of stage gates and balance between resource
optimization and project quality. Thus, tailoring of procedures based on specific NPD
project needs and complexity is strongly underscored within the literature
review(Poolton & Barclay, 1998).

Techniques like Prototyping, Simulation and Value Stream Mapping play a significant
role in the NPD landscape because of their iterative nature. These approaches allow
organizations to see pictures of, test and refine concept products before mass
implementation minimizing the risk of expensive mistakes. But literature focuses on the
importance of a careful choice in selecting techniques based on its type, size and
resource limitations. Additionally, it focuses on the need to integrate these methods in
order prevent a narrow approach for NPD.

This critical appraisal of these significant findings from the research literature makes it
clear that theory and application need to be balanced by NPD projects developing
frameworks. Although modern methodologies promote the principle of flexibility and
customer orientation, their effective implementation requires a clear understanding of
how they are applied in each particular practical situation. Therefore, the literature
review becomes a preface to further analysis of the chosen NPD projects wherein these

6
methodologies, procedures and techniques are reflected in implementations and may
become barriers or facilitators affecting project completion(Zirger & Maidique, 1990).

Project selection
In selecting the pair of NPD projects for comparison and contrast, it is necessary to
articulate certain criteria that ensure compliance with the scope defined in this
assignment while constituting a substantive base for an insightful analysis. The
requirements used in the described frame are well-thought – out to make sure that
selected projects not only fit under an umbrella of a theme but also reflect variety within
this scope and enhance depth and applicability by surrounding analysis(Bessant &
Francis, 1997).

An industry context is considered the first criterion in selection for new products
development projects. This criterion is intended to represent the depth and breadth of
the NPD environment and suggests that a range of projects from different sectors
should be selected, each with specific challenges as well as potential benefits. Given
that the analysis takes into consideration diverse industries, including technology,
healthcare; consumer goods or industry can derive insights beyond specific
idiosyncrasies. This breadth is essential for generalizing findings and recommendations
that are relevant to the wider range of new product development projects.

The second criterion is characterized by the size and magnitude of the projects.
Projects of different scales, dimensions and significance must be chosen. This variability
in size allows the subsequent analysis to analyze these project management
methodologies and techniques, showing their process of adaptation according to
different parameters. For example, a mega-project with high impact could necessitate a
different approach in management compared to an incremental project involving limited
changes. The aim is to determine whether the concepts learned in BUS9041M are
generally applicable or if they require adaptation based on project complexity(Barczak &
Kahn, 2012).

The other important criteria involve the geographical boundaries of the selected
projects. This stems out of the understanding that cultural, regulatory and market

7
influences may be substantially different from one region to another. In order to
understand the impact of geographic diversity on selecting and using project
management methodologies, this analysis seeks projects that operate in different
spatial settings. This criterion matches with the modules approach to get knowledge of
organizational and environmental forces for planning and management of project

The fourth criterion relates to the innovation quotient of selected projects. As a pillar of
new product development, innovation offers projects that demonstrate different levels of
innovativeness fertile soil for measuring the adjustability to project management
methodologies. By focusing on project types that vary from evolutionary enhancements
to revolutionary breakthroughs, the analysis strives to identify the subtle differences in
approaches toward project management needed for navigating uncertainty associated
with emerging products(Kahn, Castellion, & Griffin, 2013).

The last condition concerns the availability of full and trustworthy data for each chosen
project. Since the task focuses on evidence-based analysis, it is crucial to select
projects for which enough information can be found. This principle prevents the
subsequent evaluation from being hindered by a lack of data and allows for an in-depth
analysis of project management methodologies, processes, and techniques(Cooper,
2019).

These criteria defined, the set of NPD projects to be analyzed in this paper includes a
technology-driven project from software business and another healthcare-related
initiative targeted on medical devices development. This selection is based on the need
to summarize the extent of new product development, as it encompasses projects both
large and small in nature, from varying geographical locations and different levels of
innovation.

Innovation in the software industry occurs rapidly and with excitement, as demonstrated
by this technology-based project located amidst a competitive environment. Conversely,
the healthcare-centric project where we see medical devices development involves a
very strict regulatory environment and relevance of accuracy and reliability as inherent
to innovations in medicine. Through this contrast, the analysis can reveal broader
implications that are industry-specific yet beyond such nuances within new product
8
development as these projects allow capturing an integrated assessment of how project
management methodologies may adjust to various challenges in a diverse
environment(Schilling & Hill, 1998).

These projects are relevant to the scope of this assignment because they can act as
microcosms for that broader NPD environment. The agility and iterative nature of the
technology-led innovation is reflected in Software industry project while healthcare
innovations are demonstrated by elaborate planning process with a great adhesion to
regulatory compliance which both projects have highlighted. Having looked at these
varied dimensions anew product development, the analysis can provide more detailed
perspectives on adaptability and efficacy of project management methodologies,
procedures, techniques introduced by BUS9041M module.

Methodology
The methodology used in gathering information on the NPD projects that were chosen
is diverse and multidimensional fundamentally involving both primary sources as well as
secondary. This methodological decision is motivated by the need to achieve a
sophisticated and detailed comprehension of projects that goes beyond the limits of
existing literature(Barclay, Dann, & Holroyd, 2010).

First, a comprehensive analysis of secondary sources was carried out to begin the
process of data collection. This included scholarly articles, academic journals, industry
reports and related literature about project management methodology and NPD in both
software as well as healthcare sectors. Thus, this literature review can be perceived as
a preliminary step which gave knowledge about theoretical frameworks application, best
practices and barriers related to NPD projects in those fields. Through the integration of
knowledge from reputable sources, this phase provided a foundation upon which key
areas of interest were defined and guided the study on particular aspects in chosen
projects.

Secondary data was supplemented by primary research to ensure subjective

perspectives and unpublished information. To this end, project stakeholders were
engaged directly. All project members, and anyone managing projects, executives as

9
well as all staff working with any of these people were interviewed. The aim of the
interviews was to provide new knowledge about different perceptions behind choice
processes, barriers encountered and why a specific approach had been selected. What
happens in interviews has greatly helped people gain a better understanding of what is
happening, some other fine details that may be missed out sometimes from documents
or reports(Loch & Kavadias, 2007).

However, the method also used document analysis as a source of primary data. This
also involved a highly detailed review of project documentation including but not limited
to the plans, status reports, meeting minutes and all artifacts created during the entire
life cycle. This analysis enabled a specific historical account of the evolution for each
project allowing to identify significant markers and dissimilarities in initial intentions,
triggers. This methodology was triangulated, meaning cross-validated through the use
of both interviews and document analysis.

First of all, site visits were included in the methodology because it helped to achieve
immersion into real working environment. These site visits, allowed for contextualizing
the studied phenomena through direct observation of organizational culture, team
dynamics and physical social settings in which these projects occurred. Field site visits
resolved the vacuum between theoretical understanding and real messiness of NPD
project management practice(Schmidt, Sarangee, & Montoya, 2009).

The chosen methodology combined primary and secondary data collection techniques
in order to remedy the shortcomings of using documented information only. It aimed to
capturing silent knowledge that was held in each individual’s memories and thoughts
about those working with such hands-on projects on the ground. By adopting an
interdisciplinary approach, a more holistic and context-based interpretation of selected
NPD projects is facilitated that enables to analyse these in great depths beyond what
can be found in current literature.

Finally, the methodological approach used in this study is a synthesis between primary
and secondary sources with their relative strengths for framing an integrated story
around some chosen NPD initiatives. The methodology is to identify the project, which
has challenges and successes written in it through literature review as well site visits.
10
Analysis
In analyzing the various new product development (NPD) projects that have been
chosen, it is also necessary to investigate the employed project management
methodologies, procedures and techniques focusing on personal involvement and
information access beyond what one can find in public sources. This analysis seeks to
solve the mysteries of project planning and control in real-world situations, providing
information that goes beyond surface-level details presently available.

The project driven by the software industry shows a strong tendency toward Agile
methodologies, especially Scrum as such an industry tends to be adaptive and favor
iterative development. However, the project has been segmented into time-boxed
iterations known as sprints geared towards a potentially shippable product increment
piecing. The highlighted features regarding the importance of frequent collaboration with
stakeholders, reassessments and a willingness to change when necessary follow
principles promoted in BUS9041M module. Personal involvement with this project
enabled me to develop a deep insight into Agile ceremonies, such as daily stand-ups,
sprint planning and retrospective meetings. This practice reflects the practical specifics
and issues of Agile adoption, which is much more than those described in
textbooks(Millson, Raj, & Wilemon, 1992).

In addition, the software project incorporates Lean methods to increase efficacy. The
processes of continuous integration and automated testing reduce the process cost
significantly while increasing product’s quality. Involvement in the process was a
significant advantage as it provided an onsite view of real practice, where Lean and
Agile notions were intertwined. This dual-methodology approach, in which Agile and
Lean coexist, emphasizes the project's desire to achieve a balance between flexibility
on the one hand and efficiency on Inversely, the healthcare-related project centred on
medical device development follows a more sequential and process based approach.
Because patient safety and regulatory compliance are so much of focus for this
particular sector, the project follows a Stage-Gate process that obliges each stage to be
carefully reviewed before moving on to the next phase. The personal involvement in the
project allowed insight into how meticulous registration and documentation was at each

11
gate, which also helped to see that quality assurance measures were followed along
with requirements of any regulations. This differs markedly from the software project to
Agile methodology, focused on sector-specific customization for NPD methods(Hoyer,
Chandy, Dorotic, Krafft, & Singh, 2010).

Critical Evaluation
Positive and negative aspects in the set of management techniques utilized for software
industry-led healthcare category NPD projects are unveiled to be peculiar. Agile and
lean in the project of software create feasibility, which means that development iteration
occurs through reduction of waste. Reality, however, is rooted in the sustained
disciplined planning and documentation. The Stage Gate approach used in the project
of healthcare is detailed planning and control, but at the same time it restricts flexibility
to accommodate rapidly changing market needs. The strengths of this software project
are its flexibility and responses, although weaknesses can be identified in possible
documentation errors(Tidd & Bodley, 2002).

Positive and negative attributes significantly influence the project delivery followed by
performance. Agility in the software project enables a timely response to market
modifications; thereby product fit and customer satisfaction Secondly, such gaps
between documents may lead to violations or other omissions. The rigorous planning in
the healthcare project ensures compliance, but it may cause tardy response to changes
in market. Having identified these strengths and weaknesses, the next step is to figure
out how they can influence project delivery or performance.

Synthesis of Original Recommendations

The new proposal is then synthesized, supported by the critical analysis, using original
recommendations for improvement of management methods in NPD projects.
Concerning the software project, it is recommended to make documentation more
effective without affecting agility. While some lapses can be made in such a fast-paced
project, an effective documentation process implemented with regular reviews that
should minimize incidences of oversights. Secondly, establishing a culture of continual
innovation in planning and communication will guarantee sustainability(Kahn et al.,
2013).
12
Managing regulatory compliance and adaptive planning is critical in the healthcare
project. By incorporating the iterative factors to stage-gate, it is possible to improve on
responsiveness without sacrificing quality. Second, developing the risk assessment
process and the stakeholders’ feedback on an ongoing basis throughout various stages
of project life cycle will ensure adaptability. Further, implementing technology solutions
compliant with regulatory requirements streamlines project management processes.

Conclusion
The NPD case studies reveal complex insights in the analysis of management
practices. The adaptability of the software project focuses on detail-orientated planning
in healthcare that can be learned for broader use. The generalized recommendations
provide the importance of applying both methodologies, which are to use their strengths
and complement them with some weaknesses.

This analysis has produced original insights which have contributed to the ongoing
discussion about project planning and management that show that grounds contextual
approaches are needed. By linking the theoretical frameworks with practical
pragmatism, this study offers an insightful understanding of barriers and opportunities in
NPD programs. The anticipated benefit of this complete analysis is that it might
contribute to the development and innovation in a rapidly changing environment
associated with new product launching, as future project manager improvement can be
facilitated by these findings.

The detailed analysis of the software and healthcare NPD projects, combined with
synthesized advice enables one to give a more profound insight into project planning
and management processes. Through analyzing the dynamics of agility, documentation;
regulatory compliance, and adaptability this analysis aspires to spark a comprehensive
grasp. In essence, this study seeks to catalyze changes in practices of project
management and so promote greater resilience with innovativeness being applied for
new product development.

References
Barclay, I., Dann, Z., & Holroyd, P. (2010). New product development: Routledge.

13
Barczak, G., & Kahn, K. B. (2012). Identifying new product development best practice.
Business horizons, 55(3), 293-305.
Bessant, J., & Francis, D. (1997). Implementing the new product development process.
Technovation, 17(4), 189-222.
Bhuiyan, N. (2011). A framework for successful new product development. Journal of
Industrial Engineering and Management (JIEM), 4(4), 746-770.
Cooper, R. G. (2019). The drivers of success in new-product development. Industrial
marketing management, 76, 36-47.
Hoyer, W. D., Chandy, R., Dorotic, M., Krafft, M., & Singh, S. S. (2010). Consumer
cocreation in new product development. Journal of service research, 13(3), 283-
296.
Kahn, K. B., Barczak, G., Nicholas, J., Ledwith, A., & Perks, H. (2012). An examination
of new product development best practice. Journal of Product Innovation
Management, 29(2), 180-192.
Kahn, K. B., Castellion, G., & Griffin, A. (2013). The PDMA handbook of new product
development: Wiley Online Library.
Loch, C., & Kavadias, S. (2007). Handbook of new product development management:
Routledge.
Millson, M. R., Raj, S., & Wilemon, D. (1992). A survey of major approaches for
accelerating new product development. Journal of Product Innovation
Management: AN INTERNATIONAL PUBLICATION OF THE PRODUCT
DEVELOPMENT & MANAGEMENT ASSOCIATION, 9(1), 53-69.
Ogawa, S., & Piller, F. T. (2006). Reducing the risks of new product development. MIT
Sloan management review.
Poolton, J., & Barclay, I. (1998). New product development from past research to future
applications. Industrial marketing management, 27(3), 197-212.
Schilling, M. A., & Hill, C. W. (1998). Managing the new product development process:
Strategic imperatives. Academy of Management Perspectives, 12(3), 67-81.
Schmidt, J. B., Sarangee, K. R., & Montoya, M. M. (2009). Exploring new product
development project review practices. Journal of Product Innovation
Management, 26(5), 520-535.

14
Sethi, R. (2000). New product quality and product development teams. Journal of
marketing, 64(2), 1-14.
Takeuchi, H., & Nonaka, I. (1986). The new new product development game. Harvard
business review, 64(1), 137-146.
Tidd, J., & Bodley, K. (2002). The influence of project novelty on the new product
development process. R&d Management, 32(2), 127-138.
Tzokas, N., Hultink, E. J., & Hart, S. (2004). Navigating the new product development
process. Industrial marketing management, 33(7), 619-626.
Wind, J., & Mahajan, V. (1997). Issues and opportunities in new product development:
An introduction to the special issue (Vol. 34, pp. 1-12): SAGE Publications Sage
CA: Los Angeles, CA.
Zirger, B. J., & Maidique, M. A. (1990). A model of new product development: An
empirical test. Management science, 36(7), 867-883.

15