@article {1334,
	title = {Enabling Rapid Product Development through Improved Verification and Validation Processes},
	journal = {Technology Innovation Management Review},
	volume = {10},
	year = {2020},
	month = {03/2020},
	pages = {25-36},
	publisher = {Talent First Network},
	chapter = {25},
	address = {Ottawa},
	abstract = {Fierce competition in consumer electronics market has raised a lot of challenges for product development. Products now must enter to the market as fast as possible. The verification and validation (V\&V) process is normally the most resource-demanding activity in product development (PD), and thus also has huge potential for improvement. The V\&V process is traditionally executed near the end of the development process, and is one of the most critical activities because it identifies design errors. Error correction for a nearly complete product is often difficult and therefore can cause unexpected delays in product delivery. Performing V\&V activities in early phases of the PD process and utilising V\&V methods other than testing has proven to be a good approach to reduce risks associated with taking a long time to reach the market. However, V\&V can only be carried out when verifiable requirements exist. This paper focuses on the importance of moving V\&V activities to each phase of PD by defining the requirements for components and modules. In addition, we explore how some of product-level requirements can be verified before a product has been integrated, and explain the difference between definitions of verification and validation requirements. Finally, we present the idea of changing the focus of verification activities from being set-based in the early phase of development, to being point-based when the product is close to completion.},
	keywords = {agile, requirements, set-based design, validation, Verification},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/1334},
	url = {timreview.ca/article/1334},
	author = {Antti Perttula and Joni Kukkam{\"a}ki}
}
@article {1048,
	title = {Heading for a FALL: A Framework for Agile Living Lab Projects},
	journal = {Technology Innovation Management Review},
	volume = {7},
	year = {2017},
	month = {01/2017},
	pages = {37-43},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Living lab methodologies need to enhance reactivity to changing requirements as these appear in a project. Agile methods allow for quick reactivity, but have been critiqued for not sufficiently taking into account the end-user perspective. In this article, we describe how to blend living lab methodologies with agile methods and, to this end, we present a Framework for Agile Living Lab projects (FALL). To make the framework actionable, we propose a number of actor roles. With concrete examples from living lab practice and a discussion of the theoretical basis, this article is relevant to both academics and practitioners. },
	keywords = {agile, design science research, lean UX, living labs, methodology, SCRUM},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/1048},
	url = {http://timreview.ca/article/1048},
	author = {Tanguy Coenen and Sarie Robijt}
}
@article {872,
	title = {Agile New Service Development in an Interdisciplinary Context},
	journal = {Technology Innovation Management Review},
	volume = {5},
	year = {2015},
	month = {02/2015},
	pages = {33-45},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {This article it shows the role of services in a highly interdisciplinary context: promoting cooperation between organizations in the life sciences industry and in the engineering and automation industry. It provides insights on how required offerings of knowledge-intensive business services (KIBS) are developed systematically based on a simple service engineering process model. In addition to the content-related view of new service development, findings from a meta-view are presented. Cooperating researchers and practitioners in the new-service development process observed their own collaboration and how the applied service engineering model had to be modified dynamically to the requirements of the use case. The results show that an easy-to-use service engineering model in a highly interdisciplinary context has benefits, but success is dependent on the joint efforts of an accordingly interdisciplinary team of engineers and natural scientists; a close communication with the customers both from the life sciences industry and the engineering and automation industry; and a more agile approach. },
	keywords = {agile, engineering and automation, interdisciplinarity, KIBS, knowledge-intensive business services, life sciences, new service development, service engineering},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/872},
	url = {http://timreview.ca/article/872},
	author = {Sabrina Cocca and Ann-Mareen Franke and Simone Schell}
}
