Outsourcing process in pharmaceutical product development

The aim of this study was to create an outsourcing process for pharmaceutical product development. This study focuses on two main questions. The first question is “What is the outsourcing process model?” In the second phase key success factors of the outsourcing process are identified. As a result of the literature reviews, a general outsourcing process was created. Transaction cost economics and resource based view were used to derived a theoretical framework to the process by combining the existing processes presented in the literature. The model of process is considered used to the outsourcing broadly. The general outsourcing process was then developed further with the key factors that affect the success of pharmaceutical product development and the interviews of pharmaceutical outsourcing experts. The result of the research was the process consists of seven phases with key activities and expected outputs for each of the phases. In addition, the strategic decision-making framework for outsourcing decision in pharmaceutical product development is giving as well as the tools for selecting supplier and preparing structured contract. This study also gives some recommendations for managing the outsourcing process.

Product recall process development for exported nonfood consumer products

The purpose of this research is to examine the different opportunities that companies operating on international level has for conducting a product recall. The main subject of the research is strategic decision-making of recall and product recall process. The theoretical framework, core of the research, is based on research questions. The research is performed as qualitative case study and the material has been collected by combining results of previous studies and by observing the case company. Different opportunities for conducting a recall are examined in the empirical part of this study. As a result, different product recall models have been created, which all require deep cooperation between different entities of the supply chain.

Study of the innovation management process in the development of a discontinuous product case: Motorola RAZR V3

This study will collaborate by bringing some detailed analysis and findings on a special case study of a discontinuous product development process, trying to answer how the discontinuous product development process takes place and the main factors that influence this process. Additionally, it tried to explore some explanations for the difficulties generally faced by the companies to sustain innovation. The case is about the Motorola cell phone RAZR V3, launched in 2004. RAZR V3 was noted by industry experts as game-changing feat of design and engineering, selling more than 110 million units by end of 2008 and recognized as one of the fastest selling products in the industry. The study uses a single case methodology, which is appropriate given the access to a phenomenon that happened inside corporate dominium and it is not easily accessed for academic studies, besides being a rare case of success in the cellular phone industry. In order to magnify the understanding of the phenomenon, the exploration was extended to contrast the RAZR development process and the standard product development process in Motorola. Additionally, it was integrated a longitudinal reflection of the company product development evolution until the next breakthrough product hitting the cellular phone industry. The result of the analysis shows that discontinuous products do not fit well traditional product development process (in this case, stage-gate). This result reinforces the results obtained on previous studies of discontinuous product development conducted by other authors. Therefore, it is clear that the dynamics of discontinuous product development are different from the continuous product development, requiring different treatment to succeed. Moreover, this study highlighted the importance of the management influence in all the phases of the process as one of the most important factors, suggesting a key component to be carefully observed in future researches. Some other findings of the study that were considered very important for a discontinuous product development process: have champions (who believe and protect the project) and not only one champion; create a right atmosphere to make flow the creative process; question paradigms to create discontinuous products; simple guiding light to focus the team; company culture that accepts and knows how to deal with risks; and undoubtedly, have a company strategy that understands the different dynamics of continuous and discontinuous product development processes and treat them accordingly.

Creative process in globally distributed teams: a study of new product development in Volvo

With the business environments no longer confined to geographical borders, the new wave of digital technologies has given organizations an enormous opportunity to bring together their distributed workforce and develop the ability to work together despite being apart (Prasad & Akhilesh, 2002). resupposing creativity to be a social process, the way that this phenomenon occurs when the configuration of the team is substantially modified will be questioned. Very little is known about the impact of interpersonal relationships in the creativity (Kurtzberg & Amabile, 2001). In order to analyse the ways in which the creative process may be developed, we ought to be taken into consideration the fact that participants are dealing with a quite an atypical situation. Firstly, in these cases socialization takes place amongst individuals belonging to a geographically dispersed workplace, where interpersonal relationships are mediated by the computer, and where trust must be developed among persons who have never met one another. Participants not only have multiple addresses and locations, but above all different nationalities, and different cultures, attitudes, thoughts, and working patterns, and languages. Therefore, the central research question of this thesis is as follows: “How does the creative process unfold in globally distributed teams?” With a qualitative approach, we used the case study of the Business Unit of Volvo 3P, an arm of Volvo Group. Throughout this research, we interviewed seven teams engaged in the development of a new product in the chassis and cab areas, for the brands Volvo and Renault Trucks, teams that were geographically distributed in Brazil, Sweden, France and India. Our research suggests that corporate values, alongside with intrinsic motivation and task which lay down the necessary foundations for the development of the creative process in GDT.

Tailoring the Scrum Development Process to Address Agile Product Line Engineering

Software Product Line Engineering (SPLE) is becoming widely used due to the improvement it means when developing software products of the same family. However, SPLE demands long-term investment on a product-line platform that might not be profitable due to rapid changing business settings. Since Agile Software Development (ASD) approaches are being successfully applied in volatile markets, several companies have suggested the idea of integrating SPLE and ASD when a family product has to be developed. Agile Product Line Engineering (APLE) advocates the integration of SPLE and ASD to address their lacks when they are individually applied to software development. A previous literature re-view of experiences and practices on APLE revealed important challenges about how to fully put APLE into practice. Our contribution address several of these challenges by tailoring the agile method Scrum by means of three concepts that we have defined: plastic partial components, working PL-architectures, and reactive reuse.

Integrating technology roadmapping and portfolio management at the front-end of new product development

Many authors point out that the front-end of new product development (NPD) is a critical success factor in the NPD process and that numerous companies face difficulties in carrying it out appropriately. Therefore, it is important to develop new theories and proposals that support the effective implementation of this earliest phase of NPD. This paper presents a new method to support the development of front-end activities based on integrating technology roadmapping (TRM) and project portfolio management (PPM). This new method, called the ITP Method, was implemented at a small Brazilian high-tech company in the nanotechnology industry to explore the integration proposal. The case study demonstrated that the ITP Method provides a systematic procedure for the fuzzy front-end and integrates innovation perspectives into a single roadmap, which allows for a better alignment of business efforts and communication of product innovation goals. Furthermore, the results indicated that the method may also improve quality, functional integration and strategy alignment. (C) 2010 Elsevier Inc. All rights reserved.

Warranty and optimal reliability improvement through product development

For products sold with warranty, the warranty servicing cost can be reduced by improving product reliability through a development process. However, this increases the unit manufacturing cost. Optimal development must achieve a trade-off between these two costs. The outcome of the development process is uncertain and needs to be taken into account in the determination of the optimal development effort. The paper develops a model where this uncertainty is taken into account. (C) 2003 Elsevier Ltd. All rights reserved.

New Product Development (NPD) Success Factors: A Review of the Literature

This paper reviews the literature on managerially actionable new product development success factors and summarises the field in a classic managerial framework. Because of the varying quality, breadth and scope of the field, the review only contains post-1980 studies of tangible product development that are of a rigorous scientific standard. Success is interpreted as a commercial success. The field has gained insight into a broad set of factors that vary in scope, abstraction and context. Main areas that contribute to NPD success are top management support exhibited through resource allocation and communicating the strategic importance of NPD in the organisation. The right projects need to be selected for investment at the beginning of the process and should be aligned to the organisation's internal competencies and the external environment. The NPD process should use cross-functional teams and a competent project champions. Marketing research competency is crucial, as an understanding of the market, customers and competitors is repeatedly highlighted. Product launch competency was also consistently shown to be important. In terms of controlling the NPD process, strict project gates are required to maintain control.

Requirements Management in the Software Development Process

Ohjelmistokehitys on monimutkainen prosessi. Yksi keskeisistä tekijöistä siinä on ohjelmistolle asetettavat vaatimukset. Näitä vaatimuksia on hyvin monenlaisia, ja eri tasoisia; toivotusta toiminnallisuudesta hyvinkin yksityiskohtaisiin vaatimuksiin. Näiden vaatimusten hallinta on myöskin hyvin monitahoista, vaikkakin se on kirjallisuudessa esitetty selkeänä prosessissa, joka on sarja toisistaan erottuviavaiheita. Työn painopiste oli näiden vaatimusten muutoksen ja valmiiseen ohjelmistoon kohdistuvan palautteen hallinnassa, ja kuinka vaatimustenhallintaohjelmisto voisi olla avuksi näissä prosesseissa. Vaatimustenhallintatyökalun käyttö ei sinällään ratkaise mitään ongelmia, mutta se suo puitteet parantaa vaatimusten hallitsemista. Työkalun käytöstä on muun muassa seuraavia etuja: vaatimusten keskitetty varastointi, käyttäjäoikeuksien määrittely koskien eri käyttäjiä ja heidän pääsyään näkemään tai muuttamaan tietoa, muutoksenhallintaprosessin hallinta, muutosten vaikutuksen analysointi ja jäljitettävyys ja pääsy tietoihin web-selaimella.

Product Definition Process for Mobile Radio System Product

Työn tarkoituksena oli tutkia tuotteen määrittelyyn liittyvää kirjallisuutta ja perehtyä tuotteen määrittelytyön nykytilaan kohdeyrityksessä. Näihin molempiin perustuen muodostetaan prosessimalli tuotteen määrittelytyölle kohdeyrityksessä. Työssä käsitellään prosessijohtamisen pääperiaatteet sekä tuotteen määrittelyä koskevaa kirjallisuutta ja tutkimuksia. Koska kysessä oleva tuote on suurelta osalta ohjelmistotuote, ohjelmistojen suunnittelua, erityisesti ohjelmistovaatimusten hallintaa ja ohjelmistojen määrittelyä, on myös tarkasteltu työssä. Tuotteen määrittelyn haasteita on käsitelty yksityiskohtaisemmin, esimerkiksi dokumentointia, prosessin kulkua, vaatimusten epävakaisuutta sekä muutoksia. Kohdeyritys ja sen ongelmakohdat esitellään ja luodaan prosessimalli. Tämä malli esittelee seuraavat prosessit: raakavaatimusten hallinta -prosessin, roadmapping -prosessin, esisuunnittelu- ja spesifikaatioprosessin ja julkaisun suunnittelu -prosessin. Kaikki nämä ovat vaiheita ennen varsinaisen tuotekehitysprojektin aloittamista. Työssä esitellään myös kolmetasoinen dokumentaatiomalli.