New Foods, New Consumers: Innovation in Food Product Development

BACKGROUND: Today, new lifestyles, higher incomes and consumer awareness are creating consumer demand for a year-round supply of high-quality, diverse and innovative food products. However, when it comes to innovation, the food sector is less changeable when compared to other sectors, such as high technology. Still, in the past decades much and important developments have been achieved in several areas related to foods and the food industry. METHODS: A systematic review of scientific literature was conducted on Science Direct. The topics investigated were: aspects related to innovation in food development (such as the transfer of innovation, open innovation, collaborative innovation and consumer perception and its role in the developing process); the innovation in the food industry (particularly regarding the processing technologies and packaging, which are two prominent areas of innovation in this sector nowadays); the innovation in the cooking sector (particularly in regards to the molecular gastronomy and science based cooking). RESULTS: A total of 146 articles were included in the review and the aspects focused allowed confirming that innovation has been recognized as a key driver of economic growth. Within the framework of ‘open innovation’, a number of key issues related to the acquisition of external knowledge in food technology must be taken into consideration. Food product development is highly dependent on the consumer perception and acceptance, and hence it is of utmost importance to include the consumer in the development process to minimize failure probabilities. The sectors of the food industry where important developments and innovation are registered include the processing technologies and the packaging systems, where the latest progresses have produced very significant outcomes. CONCLUSION: The present work allowed verifying the latest improvements and trend towards food product development from two perspectives, the product itself and the industrial processing. This sector is undoubtedly a major key for the success and competitiveness nowadays in the food industry.

Preparation for ramp-up production process in metal manufacturin

Collaboration is essential for successful new product development. In the preparation for ramp-up production collaboration between R&D and supply chain functions is crucial. This thesis examines the meaning of collaboration and the effects of collaboration between R&D and supply chain. The aim of this thesis is to analyse and advice on how to improve the collaboration between the research and development department and supply chain within the preparation for rampup process. This thesis begins by introducing the reader to the product development methodologies and collaboration literature. The following part of the thesis describes the current situation and the results of the qualitative research. The last part of the thesis will explain the improvement suggestions. The main improvement suggestions are clarification of the processes and responsibilities and the introduction of a kick-off meeting.

Product Assurance in Agile Space Systems Development

Product assurance is an essential part of product development process if developers want to ensure that final product is safe and reliable. Product assurance can be supported withrisk management and with different failure analysis methods. Product assurance is emphasized in system development process of mission critical systems. The product assurance process in systems of this kind requires extra attention. Inthis thesis, mission critical systems are space systems and the product assurance processof these systems is presented with help of space standards. The product assurance process can be supported with agile development because agile emphasizes transparency of the process and fast response to changes. Even if the development process of space systems is highly standardized and reminds waterfall model, it is still possible to adapt agile development in space systems development. This thesisaims to support the product assurance process of space systems with agile developmentso that the final product would be as safe and reliable as possible. The main purpose of this thesis is to examine how well product assurance is performed in Finnish space organizations and how product assurance tasks and activities can besupported with agile development. The research part of this thesis is performed in survey form.

Product assurance in agile space systems development

Product assurance is an essential part of product development process if developers want to ensure that final product is safe and reliable. Product assurance can be supported with risk management and with different failure analysis methods. Product assurance is emphasized in system development process of mission critical systems. The product assurance process in systems of this kind requires extra attention. In this thesis, mission critical systems are space systems and the product assurance process of these systems is presented with help of space standards. The product assurance process can be supported with agile development because agile emphasizes transparency of the process and fast response to changes. Even if the development process of space systems is highly standardized and reminds waterfall model, it is still possible to adapt agile development in space systems development. This thesis aims to support the product assurance process of space systems with agile development so that the final product would be as safe and reliable as possible. The main purpose of this thesis is to examine how well product assurance is performed in Finnish space organizations and how product assurance tasks and activities can be supported with agile development. The research part of this thesis is performed in survey form.

Agile modeling data warehouse development

Most of the traditional software and database development approaches tend to be serial, not evolutionary and certainly not agile, especially on data-oriented aspects. Most of the more commonly used methodologies are strict, meaning they’re composed by several stages each with very specific associated tasks. A clear example is the Rational Unified Process (RUP), divided into Business Modeling, Requirements, Analysis & Design, Implementation, Testing and Deployment. But what happens when the needs of a well design and structured plan, meet the reality of a small starting company that aims to build an entire user experience solution. Here resource control and time productivity is vital, requirements are in constant change, and so is the product itself. In order to succeed in this environment a highly collaborative and evolutionary development approach is mandatory. The implications of constant changing requirements imply an iterative development process. Project focus is on Data Warehouse development and business modeling. This area is usually a tricky one. Business knowledge is part of the enterprise, how they work, their goals, what is relevant for analyses are internal business processes. Throughout this document it will be explained why Agile Modeling development was chosen. How an iterative and evolutionary methodology, allowed for reasonable planning and documentation while permitting development flexibility, from idea to product. More importantly how it was applied on the development of a Retail Focused Data Warehouse. A productized Data Warehouse built on the knowledge of not one but several client needs. One that aims not just to store usual business areas but create an innovative sets of business metrics by joining them with store environment analysis, converting Business Intelligence into Actionable Business Intelligence.

Agile Construction and Evolution of Product-Line Architectures

Software Product Line Engineering (SPLE) has proved to have significant advantages in family-based software development, but also implies the up¬front design of a product-line architecture (PLA) from which individual product applications can be engineered. The big upfront design associated with PLAs is in conflict with the current need of "being open to change". However, the turbulence of the current business climate makes change inevitable in order to stay competitive, and requires PLAs to be open to change even late in the development. The trend of "being open to change" is manifested in the Agile Software Development (ASD) paradigm, but it is spreading to the domain of SPLE. To reduce the big upfront design of PLAs as currently practiced in SPLE, new paradigms are being created, one being Agile Product Line Engineering (APLE). APLE aims to make the development of product-lines more flexible and adaptable to changes as promoted in ASD. To put APLE into practice it is necessary to make mechanisms available to assist and guide the agile construction and evolution of PLAs while complying with the "be open to change" agile principle. This thesis defines a process for "the agile construction and evolution of product-line architectures", which we refer to as Agile Product-Line Archi-tecting (APLA). The APLA process provides agile architects with a set of models for describing, documenting and tracing PLAs, as well as an algorithm to analyze change impact. Both the models and the change impact analysis offer the following capabilities: Flexibility & adaptability at the time of defining software architectures, enabling change during the incremental and iterative design of PLAs (anticipated or planned changes) and their evolution (unanticipated or unforeseen changes). Assistance in checking architectural integrity through change impact analysis in terms of architectural concerns, such as dependencies on earlier design decisions, rationale, constraints, and risks, etc.Guidance in the change decision-making process through change im¬pact analysis in terms of architectural components and connections. Therefore, APLA provides the mechanisms required to construct and evolve PLAs that can easily be refined iteration after iteration during the APLE development process. These mechanisms are provided in a modeling frame¬work called FPLA. The contributions of this thesis have been validated through the conduction of a project regarding a metering management system in electrical power networks. This case study took place in an i-smart software factory and was in collaboration with the Technical University of Madrid and Indra Software Labs. La Ingeniería de Líneas de Producto Software (Software Product Line Engi¬neering, SPLE) ha demostrado tener ventajas significativas en el desarrollo de software basado en familias de productos. SPLE es un paradigma que se basa en la reutilización sistemática de un conjunto de características comunes que comparten los productos de un mismo dominio o familia, y la personalización masiva a través de una variabilidad bien definida que diferencia unos productos de otros. Este tipo de desarrollo requiere el diseño inicial de una arquitectura de línea de productos (Product-Line Architecture, PLA) a partir de la cual los productos individuales de la familia son diseñados e implementados. La inversión inicial que hay que realizar en el diseño de PLAs entra en conflicto con la necesidad actual de estar continuamente "abierto al cam¬bio", siendo este cambio cada vez más frecuente y radical en la industria software. Para ser competitivos es inevitable adaptarse al cambio, incluso en las últimas etapas del desarrollo de productos software. Esta tendencia se manifiesta de forma especial en el paradigma de Desarrollo Ágil de Software (Agile Software Development, ASD) y se está extendiendo también al ámbito de SPLE. Con el objetivo de reducir la inversión inicial en el diseño de PLAs en la manera en que se plantea en SPLE, en los último años han surgido nuevos enfoques como la Ingeniera de Líneas de Producto Software Ágiles (Agile Product Line Engineering, APLE). APLE propone el desarrollo de líneas de producto de forma más flexible y adaptable a los cambios, iterativa e incremental. Para ello, es necesario disponer de mecanismos que ayuden y guíen a los arquitectos de líneas de producto en el diseño y evolución ágil de PLAs, mientras se cumple con el principio ágil de estar abierto al cambio. Esta tesis define un proceso para la "construcción y evolución ágil de las arquitecturas de lineas de producto software". A este proceso se le ha denominado Agile Product-Line Architecting (APLA). El proceso APLA proporciona a los arquitectos software un conjunto de modelos para de¬scribir, documentar y trazar PLAs, así como un algoritmo para analizar vel impacto del cambio. Los modelos y el análisis del impacto del cambio ofrecen: Flexibilidad y adaptabilidad a la hora de definir las arquitecturas software, facilitando el cambio durante el diseño incremental e iterativo de PLAs (cambios esperados o previstos) y su evolución (cambios no previstos). Asistencia en la verificación de la integridad arquitectónica mediante el análisis de impacto de los cambios en términos de dependencias entre decisiones de diseño, justificación de las decisiones de diseño, limitaciones, riesgos, etc. Orientación en la toma de decisiones derivadas del cambio mediante el análisis de impacto de los cambios en términos de componentes y conexiones. De esta manera, APLA se presenta como una solución para la construcción y evolución de PLAs de forma que puedan ser fácilmente refinadas iteración tras iteración de un ciclo de vida de líneas de producto ágiles. Dicha solución se ha implementado en una herramienta llamada FPLA (Flexible Product-Line Architecture) y ha sido validada mediante su aplicación en un proyecto de desarrollo de un sistema de gestión de medición en redes de energía eléctrica. Dicho proyecto ha sido desarrollado en una fábrica de software global en colaboración con la Universidad Politécnica de Madrid e Indra Software Labs.

An essay on agile project management practices

The main goals for the current dissertation is to research on how practices and concepts from Agile Project Management can be applied in a non-IT context and to discover which aspects should be considered when deciding if whether an Agile approach should be implemented or not. Previous studies reflect on the adoption for the identified context. However, the recognition of these practices and concepts by the Project Management field of studies still remains unresolved. The adoption of Agile Project Management emerges as a manifestation against traditional approaches, mainly due to their inability of accepting requirements’ changes. Therefore, these practices and concepts can be considered in order to reduce the risks concerning the increase of competition and innovation – which does not apply to the IT sector solely. The current study reviews the literature on Agile Project Management and its adoption across different sectors in order to assess which practices and concepts can be applied on a non-IT context. Nine different methods are reviewed, where two of these show a higher relevance – Scrum and Extreme Programming. The identified practices and concepts can be separated into four different groups: Cultural and Organizational Structures, Process, Practices, and Artefacts. A framework based on the work by Boehm & Turner in 2004 is developed in order to support the decision of adopting agile methods. A survey intended for project managers was carried in order to assess the implementation of the identified practices and concepts and to evaluate which variables have the highest importance on the developed decision support framework. It is concluded that New Product Development is the project type with the highest potential to implement an agile approach and that the Project Final Product’s Innovativeness, Competitiveness, and the Project Member’s Experience and Autonomy are the most important aspects to consider an implementation of an Agile approach.

Product Platform Development from the Product Lines' Perspective: Case of Switching Platform

In the era of fast product development and customized product requirements, the concept of product platform has proven its power in practice. The product platform approach has enabledcompanies to increase the speed of product introductions while simultaneously benefit from efficiency and effectiveness in the development and production activities. The product platforms are technological bases, which can be used to develop several derivative products, and hence, the differentiation can be pushed closer to the product introduction. The product platform development has some specific features, which differ somewhat from the product development of single products. The time horizon is longer, since the product platform¿slife cycle is longer than individual product's. The long time-horizon also proposes higher market risks and the use of new technologies increases the technological risks involved. The end-customer interface might be far away, but there is not a lack of needs aimed at the product platforms ¿ in fact, the product platform development is very much balancing between the varying needs set to it by thederivative products. This dissertation concentrated on product platform development from the internal product lines' perspective of a singlecase. Altogether six product platform development factors were identified: 'Strategic and business fit of product platform', 'Project communication and deliverables', 'Cooperation with product platform development', 'Innovativeness of product platform architecture and features', 'Reliability and quality of product platform', and 'Promised schedules and final product platform meeting the needs'. From the six factors, three were found to influence quite strongly the overall satisfaction, namely 'Strategic and business fit of product platform', 'Reliability and quality of product platform', and 'Promised schedules and final product platform meeting the needs'. Hence, these three factors might be the ones a new product platform development unit should concentrate first in order to satisfy their closest customers, the product lines. The 'Project communication and deliverables' and 'Innovativeness of product platform architecture and features' were weaker contributors to the overall satisfaction. Overall, the factors explained quite well the satisfaction of the product lines with product platform development. Along the research, several interesting aspects about the very basic nature of the product platform development were found. The long time horizon of the product platform development caused challenges in the area of strategic fIT - a conflict between the short-term requirements and long term needs. The fact that a product platform was used as basis of several derivative products resulted into varying needs, and hence the match with the needs and the strategies. The opinions, that the releases of the larger product lines were given higher priorities, give an interesting contribution to the strategy theory of powerand politics. The varying needs of the product lines, the strengths of them as well as large number of concurrent releases set requirements to prioritization. Hence, the research showed the complicated nature of the product platform development in the case unIT - the very basic nature of the product platform development might be its strength (gaining efficiency and effectiveness in product development and product launches) but also the biggest challenge (developing products to meet several needs). As a single case study, the results of this research are not directly generalizable to all the product platform development activities. Instead, the research serves best as a starting point for additional research as well as gives some insights about the factors and challengesof one product development unit.

The Development of an Internal Testing Process for a Bluetooth Product

BlueGiga Technologies on uusi Bluetooth -teknologiaa soveltava pk-yritys. Yrityksen tuotekehitysprosessia täydentämään tarvittiin testausprosessi. Testausprosessin luominen oli haastavaa, koska Bluetooth -teknologia on uutta ja yritys on vielä nuori. Lisäksi se integroi kovo- ja ohjelmistokomponentteja tuotteissaan. Testaus aloitettiin evaluoimalla standardinmukaista tapaa dokumentoida testit. Tämän jälkeen tutkittiin BlueGigan ohjelmistokehitysprosessin suhdetta olemassa oleviin ohjelmistokehitysprosesseihin. Samanaikaisesti perehdyttiin Bluetooth -kvalifikaation testaukselle asettamiin vaatimuksiin. Tämän seurauksena TTCN:ää kokeiltiin helppolukuisen testitapauksen määrittelyssä. Käyttötapauksiin perustuvan testauksen sopivuutta Wireless Remote Access Platform:in (WRAP) testaamiseen arvioitiin kokeilemalla sitä Man-to-Machine -käyttötapauksen testaamisessa. Yllämainittujen tehtävien aikana kerätyn tiedon ja hankittujen kokemusten pohjalta laadittiin testausprosessi, joka kattaa yksikkö-, integraatio- ja järjestelmätason testauksen. Painopiste on järjestelmätason testauksessa. Prosessi määrittelee myös vastuuhenkilön tai -henkilöt eri testaustasoille.

Development of Collaborative Product Structure Management

The purpose of this thesis is to develop an environment or network that enables effective collaborative product structure management among stakeholders in each unit, throughout the entire product lifecycle and product data management. This thesis uses framework models as an approach to the problem. Framework model methods for development of collaborative product structure management are proposed in this study, there are three unique models depicted to support collaborative product structure management: organization model, process model and product model. In the organization model, the formation of product data management system (eDSTAT) key user network is specified. In the process model, development is based on the case company’s product development matrix. In the product model framework, product model management, product knowledge management and design knowledge management are defined as development tools and collaboration is based on web-based product structure management. Collaborative management is executed using all these approaches. A case study from an actual project at the case company is presented as an implementation; this is to verify the models’ applicability. A computer assisted design tool and the web-based product structure manager, have been used as tools of this collaboration with the support of the key user. The current PDM system, eDSTAT, is used as a piloting case for key user role. The result of this development is that the role of key user as a collaboration channel is defined and established. The key user is able to provide one on one support for the elevator projects. Also the management activities are improved through the application of process workflow by following criteria for each project milestone. The development shows effectiveness of product structure management in product lifecycle, improved production process by eliminating barriers (e.g. improvement of two-way communication) during design phase and production phase. The key user role is applicable on a global scale in the company.

Customized agile development process for embedded software development

Agile software development has grown in popularity starting from the agile manifesto declared in 2001. However there is a strong belief that the agile methods are not suitable for embedded, critical or real-time software development, even though multiple studies and cases show differently. This thesis will present a custom agile process that can be used in embedded software development. The reasons for presumed unfitness of agile methods in embedded software development have mainly based on the feeling of these methods providing no real control, no strict discipline and less rigor engineering practices. One starting point is to provide a light process with disciplined approach to the embedded software development. Agile software development has gained popularity due to the fact that there are still big issues in software development as a whole. Projects fail due to schedule slips, budget surpassing or failing to meet the business needs. This does not change when talking about embedded software development. These issues are still valid, with multiple new ones rising from the quite complex and hard domain the embedded software developers work in. These issues are another starting point for this thesis. The thesis is based heavily on Feature Driven Development, a software development methodology that can be seen as a runner up to the most popular agile methodologies. The FDD as such is quite process oriented and is lacking few practices considered commonly as extremely important in agile development methodologies. In order for FDD to gain acceptance in the software development community it needs to be modified and enhanced. This thesis presents an improved custom agile process that can be used in embedded software development projects with size varying from 10 to 500 persons. This process is based on Feature Driven Development and by suitable parts to Extreme Programming, Scrum and Agile Modeling. Finally this thesis will present how the new process responds to the common issues in the embedded software development. The process of creating the new process is evaluated at the retrospective and guidelines for such process creation work are introduced. These emphasize the agility also in the process development through early and frequent deliveries and the team work needed to create suitable process.

Project Management Tools in Agile Embedded Systems Development

Agile methods have become increasingly popular in the field of software engineering. While agile methods are now generally considered applicable to software projects of many different kinds, they have not been widely adopted in embedded systems development. This is partly due to the natural constraints that are present in embedded systems development (e.g. hardware–software interdependencies) that challenge the utilization of agile values, principles and practices. The research in agile embedded systems development has been very limited, and this thesis tackles an even less researched theme related to it: the suitability of different project management tools in agile embedded systems development. The thesis covers the basic aspects of many different agile tool types from physical tools, such as task boards and cards, to web-based agile tools that offer all-round solutions for application lifecycle management. In addition to these two extremities, there is also a wide range of lighter agile tools that focus on the core agile practices, such as backlog management. Also other non-agile tools, such as bug trackers, can be used to support agile development, for instance, with plug-ins. To investigate the special tool requirements in agile embedded development, the author observed tool related issues and solutions in a case study involving three different companies operating in the field of embedded systems development. All three companies had a distinct situation in the beginning of the case and thus the tool solutions varied from a backlog spreadsheet built from scratch to plug-in development for an already existing agile software tool. Detailed reports are presented of all three tool cases. Based on the knowledge gathered from agile tools and the case study experiences, it is concluded that there are tool related issues in the pilot phase, such as backlog management and user motivation. These can be overcome in various ways epending on the type of a team in question. Finally, five principles are formed to give guidelines for tool selection and usage in agile embedded systems development.

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.

Customer stimulation in lean software development

The process of developing software is a complex undertaking involving multiple stakeholders. While the intentions of these parties might vary to some extent, the ultimate goal can be seen as a satisfactory product. Lean and agile software development practices strive toward this and they place customer contentment as one of the highest aims of the process. An important aspect of any development process is the act of innovation. Without it, nothing progresses and the whole process is unnecessary. As a target domain expert, the customer is an important part of effective innovation. Problems arise, however, when the customer is not actively taking part in the activities. Lack of familiarity with software development can easily cause such issues. Unfortunately, the amount of research conducted on product innovation is unimpressive. This makes it difficult to formulate a recommended approach on stimulating the customer and encouraging a more active participation. Ultimately, a small set of high-level guidelines were identified from the available literary resources for inducing innovation. To conclude, this thesis presents the findings made during the development of a small web application and compares them to the aforementioned literature findings. While the guidelines seem to provide promising results, further empirical research is needed to attain more significant conclusions.

Shedding light on technological development in Brazil

We try to shed some light oil the question of wily technology-intensive businesses often fail in less-developed countries and under what circumstances they are likely to be a Success from the perspective of both domestic and export markets. The answers were drawn from a set of empirical evidences from Brazilian firms applying photonics technologies. Sonic of the issues faced by them are related to the question of state versus private initiative, entering traditional versus niche market, and technology transfer versus product development management. In overall, we concluded that weakness of the institutions and inadequacy of social and organizational demography play a key role in explaining to a large extent wily countries differ in technological development and diffusion. In this context, we point out obstacles, which must be removed in order to make public policies and firm`s achievements more efficient. (C) 2008 Elsevier Ltd. All rights reserved.