Target-oriented prototyping in highly iterative product development
|
|
- Jeffrey McBride
- 6 years ago
- Views:
Transcription
1 Target-oriented prototyping in highly iterative product development T. Gartzen Laboratory for Machine Tools and Production Engineering (WZL) of RWTH Aachen University, Steinbachstraße 19, Aachen, Germany C. Reuter Laboratory for Machine Tools and Production Engineering (WZL) of RWTH Aachen University, Steinbachstraße 19, Aachen, Germany F. Brambring Laboratory for Machine Tools and Production Engineering (WZL) of RWTH Aachen University, Steinbachstraße 19, Aachen, Germany F. Basse Laboratory for Machine Tools and Production Engineering (WZL) of RWTH Aachen University, Steinbachstraße 19, Aachen, Germany Abstract For the development of radical product innovations agile processes are essential. These are characterized by a highly iterative production of prototypes. The paper presents a systematic method of physical prototyping in order to gradually reduce the high degree of market and technological uncertainty associated with radical innovations. Keywords: Physical Product Development, Agile Product Development, Highly Iterative Prototyping INTRODUCTION Short product life cycles and continually increasing customer requirements characterize today s markets. The majority of established manufacturing companies have difficulties to launch radically innovative hardware products at high speed - an essential ability to succeed in this dynamic environment (McDermott and O'conner, 2002; O'Conner and Rice, 2001). The dominant approach in physical product development, the sequential Stage-Gate process model, is overstrained with the realization of radical product innovation (Schuh et al. 2015). Companies must rethink and restructure their processes to meet the requirements for a successful development of radical products (Meyer 2012). Based on these thoughts, in this paper, we present a prototyping approach suitable for a highly iterative product development processes. 1
2 The Characteristics of Radical Innovations Radical innovations are characterized by a high degree of both market and technological uncertainty (Lynn and Akgün, 1998). This fact makes it harder to control them compared to evolutionary and incremental innovations with their medium and low degree of uncertainties, respectively. The high degree of market uncertainty of radical innovations results from a lack of clarity about the target market and the market potential. Customer requirements are unknown and the willingness to pay cannot be easily estimated (Lynn and Akgün, 1998; Walcher 2007). Technological uncertainty can be classified in terms of product and process. Concerning the product, a lack of information regarding technical specifications and technical feasibility exists for radical innovations. Furthermore, technical challenges are often unclear and the cost of development is difficult to predict. Regarding the process, a variety of alternative production processes and unknown production costs are characteristic for radical innovations (Lang 2013; Lynn and Akgün, 1998). In Figure 1 a) the three types of innovation mentioned above are positioned in a graph according to their specific level of uncertainty in the dimensions market, technology (product) and technology (process). Development Processes as a Function of Uncertainty In his article What s Next?: After Stage Gate Cooper (2014) states that one size should not fit all : The product development process should be adjusted to the specific degree of uncertainty. In the case of incremental innovations which are based on existing market knowledge and technological know-how, it is appropriate to make use of approaches which systemize the process of innovation. Therefore, Cooper developed the Stage-Gate model, which structures the innovation process into separate phases (Cooper 1990). A further reduction of the time to market and the development costs could achieved by a parallelization and forward displacement of activities, as with Concurrent Engineering (Shina 1993) and Front-Loading (Fujimoto and Thomke, 2000). In the case of radical innovations, however, a learning-oriented approach is recommended (Herstatt and Verworn, 2007). Contrary to the clear hierarchical structures that are commonly used to manage daily operations, a high degree of agility and flexibility is necessary to give development teams more creative freedom (Meyer 2012). Being open to new ideas, as well as working target-oriented rather than process-oriented, are the basic enablers for successful market innovations (Meyer 2012). Concerning evolutionary innovations a mixture of agile and sequential processes is suggested. Figure 1 b) visualizes the suggested types of development processes for the specific types of innovation. 2
3 Produkt Inkremen t Technological uncertainty (Product) Radical Produkt Inkrement Evolutionary Incremental Market Uncertainty Technological Uncertainty (Process) Figure 1 a) Position of radical, evolutionary and incremental innovations according to their level of uncertainty (left); b) Visualization of the suggested development processes for the three types of innovation (right) Prototyping in Agile Process Structures (Scrum) In the development of software, sequential approaches have been identified as too bureaucratic and heavyweight due to an extensive documentation and strict project role divisions (Gao and Rusu, 2015). For this reason, the popularity of agile development processes has increased significantly: A comprehensive assessment of industrial surveys of agile software development shows that the usage of agile methods worldwide is reported at about 55% (Stavru 2014). Among various agile frameworks, Scrum is the most commonly used one (Stavru 2014). It structures the work in a development project along so called Sprints. These Sprints are of fixed duration and take place one after the other. Every Sprint starts with a Sprint Planning in which a cross-functional team selects the top-prioritizes items of the Product Backlog. The Product Backlog is a list of items containing short descriptions of all functionalities desired in the final product. The items can range from specifications and requirements, to use cases, epics, user stories, or even bugs and chores. The team commits to complete a specific amount of items by the end of the Sprint. During the Sprint, the chosen items and the overall aim do not change. At the end of it, the Product Increment, the sum of all the Product Backlog items completed, is reviewed with all stakeholder interested in the Sprint Review. The feedback obtained can be incorporated into the next Sprint, again in the form of items. (Sutherland 2013) Scrum emphasizes a functional product at the end of the Sprint that meets a predefined Definition of Done. Within the context of software, this means a code that is integrated, fully tested and potentially shippable (Sutherland 2013). Physical product development, however, is different from software development. As software consists of lines of code which can be arbitrarily broken down into software increments, it is almost infinitely divisible. The development of a physical product cannot be incrementalized this way, and thus the notion of short time-boxed Sprints has to be adjusted to the characteristics of physical developments (Cooper 2014). In physical development with Scrum the deliverable of each Sprint should be something physical that can be demonstrated (Cooper 2014): A prototype. Corresponding to the 3
4 development of functional code in software development, the rapid implementation and testing of prototypes enables an agile development of physical products. With the help of prototypes the development team can learn and incorporate obtained information into the next development cycles. The potential customers and stakeholders can be integrated already in the early stages into the development process, in order to provide important information about their needs and requirements. Furthermore, prototypes represent milestones and act as a channel of communication between the various stakeholders in the development process. (Ulrich and Eppinger, 2012). Figure 2 shows the Scrum framework in the context of the development of radically innovative products of physical nature. The high uncertainties in all dimensions can be reduced in steps by the realization of prototypes (blue dots) in various Sprints (arrows from dots to dots) in order to arrive at a point of minimum uncertainty (green dot) where the series production should begin. Technological uncertainty (Product) Product Backlog Sprint Planning Daily Scrum Sprint Market Uncertainty Product Increment (Prototype) CHALLENGE Inspect and adapt! Sprint Review Technological Uncertainty (Process) Figure 2 The Scrum framework in the context of physical product development As shown in Figure 2 by the stepwise approach of a point of minimum market and technological uncertainty, the development process is a process of reducing uncertainty (Burmeister and Rüggeberg, 2008). The construction and testing of prototypes within the Sprints is a key enabler in continuously reducing the high degree of uncertainty of radical innovations in a process of learning. However, approaches of selecting the most suitable prototype in the complex environment of physical products are mostly unsystematic. Prototyping has always been an established part of the product development cycle, but the underlying motivation is rarely explicitly formulated and therefore not taken into account when selecting prototypes (Kohler et al. 2013). With the prototype being at the center of the agile development process as a means of interaction with the customer, this can be seen as a major obstacle to the implementation of this approach. 4
5 In the Scrum framework, the motivation for a specific prototype results from the top items to be implemented within the next Sprint as derived from the prioritized Product Backlog. The prioritization of the Product Backlog items and the selection of the top items should thus control the development and the prototyping strategy. In this context, the question of how to prioritize the items of the Product Backlog emerges. Different prioritizations of items lead to a different design of prototypes. The potential differences of the design of the second prototype (framed) based on a different prioritization and selection of items is portrayed in Figure 3. The effect is a difference in the remaining degree of uncertainty in the three dimensions. The result of the varying prototyping strategies are numerous possible paths along which prototypes are supposed to lead to the final target of a minimum amount of uncertainty remaining. Technological uncertainty (Product) Sprint Planning Product Backlog Prioritization and selection of top items???? Market Uncertainty Figure 3 Numerous possible prioritizations and selections of the top items to be implemented within the Sprints give rise to various development paths With the following methodical approach, we would like to propose a model of prioritizing the items of the Product Backlog in order to follow the most efficient development path in the development of radical products. Furthermore, a model describing the characteristics of prototypes is presented. Together, these models are supposed to define the most suitable prototypes within the Sprints of an agile product development process. This forms the foundation of a methodology aiming at a gradual reduction the high degree of market and technological uncertainty associated with radical physical innovations. METHODICAL APPROACH Prioritization of the Product Backlog We propose that the comparably high degree of complexity in the development of physical products caused by the high degree of uncertainty in the three dimensions makes a more analytical approach necessary to prioritize and select the top items compared to the experiencebased approaches in the software industry (in software, technological uncertainty concerning the process is basically absent). For a methodical and uncertainty-reducing prioritization the basis is 5 Technological Uncertainty (Process)
6 a comparison between the systematically derived benefit (maximum output in terms of reduction of uncertainty) and effort (minimum input in terms of invest resources) connected to the potential implementation of each item. At the beginning of the development, in the case of radical innovations there is a high degree of uncertainty in all three dimensions mentioned above. A systematic prioritization of the Product Backlog items at a given point in time is suggested to be based on their specific ratio between potential benefit and effort. The items that show the highest ratio are top priority and will thus be implemented in the upcoming Sprint. In our approach, the benefit of an item at a certain point depends on the one hand on the specific amount of uncertainty reduction in the three dimensions through the item s realization. On the other hand, the reduction of uncertainty in a specific dimension can be currently of more interest than the reduction of uncertainty in the other two: For each dimension there is an estimation of the benefit generated by the reduction of its uncertainty. In this context, we suggest a target-oriented prioritization approach that addresses the three dimensions of uncertainties in specific sequences: Intuitively, as a first step, the development team should focus on the market to analyze its potential and needs to ensure that the product meets the market requirements. At this stage the principle of "Fail early and cheaply" applies the aim should be the generation of the highest possible output information in form of the reduction of market uncertainty with the least possible resources. Often, cost-efficient prototypes can be used to integrate the customer in the development process to uncover their latent needs. The market information obtained serves as a framework for the further prototype development, which should focus on the reduction of the technological uncertainty in terms of the product. The customer needs must be systematically translated into technical specifications and be technically realized. Furthermore, the functionality of the product technology needs to be understood. In this step, the development and testing of prototypes can provide the development team with important information about the final product. Late prototypes should focus on reducing the technological uncertainty in terms designing the most efficient and economic manufacturing process for the series product. Figure 4 shows the sequential reduction of uncertainties suggested in our approach. Technological uncertainty (Product) Benefit Market Uncertainty Technological Uncertainty Product Technological Uncertainty Process 1. Uncertainty 100% Technological Uncertainty (Process) Market Uncertainty Figure 4 The sequential reduction of uncertainties in the three dimensions helps to assess the benefit of the items of the Product Backlog The effort of the implementation of an item has to be considered for a target-oriented prioritization, as well. Depending on the company s capabilities, the implementation of an item needs a specific amount of effort which needs to be assessed individually. The analysis of benefit t
7 and effort for every item is the basis for a systematic prioritization of the Product Backlog. For each Sprint the information on the potential amount of reduction of uncertainty in the three dimensions, the importance of the three dimensions according to their sequence as proposed above and the required effort has to be updated. Characterization and Design of Valid Prototypes As mentioned above, the prioritization and selection of the items of the Sprint Backlog forms the motivation for the prototype to be developed in the upcoming Sprint. There is a need for a generic descriptive model of prototypes, in order to ensure the selection of a prototype design compatible with the prioritized items. There are different characterizations of prototypes in literature. While Gebhardt (1996) makes a simple distinction of six different physical model types, Lim et al. (2008) suggests a multidimensional approach in order to characterize software prototypes in a generic way. Arising from the multidimensional approach, Kohler et al. (2013) present a filter-fidelity-model based on the context of human computer interaction products. With the target of adequately characterizing prototypes used in physical product development, we have adjusted this filter-fidelity-model. We propose to characterize a prototype along the dimensions appearance, functionality, interactivity and topology. With each dimension, productspecific attributes needs to be defined. Prototypes can be described by evaluating the degree of fidelity in each attribute. In order to select a valid prototype design for a Sprint, the motivation based on the selected items and the filter-fidelity-profile has to match (Kohler et al. 2013). Table 1 contrasts a full production model and a physical design prototype. While the full production model shows a high fidelity in all attributes, the prototype shows only a high fidelity in the attributes which are relevant according to its underlying motivation. The motivation for the prototype characterized in this example is to test and validate the appearance of the product to be developed. For this motivation, a valid prototype must have a high fidelity in the attributes that are connected to the dimension appearance. The prototype does not fulfill every function of the final product and the necessity to interact with the prototype is limited. The topological attributes have a high fidelity, since it is a fully physical prototype and not a virtual one. Hence, the presented filter-fidelity-profile is a reflection of the prototype s characteristics. 7
8 Table 1 - A possible prototype profile according to items aiming at the testing and validation the product s appearance Degree of Fidelity Appearance Dimension ο ο ο ο ο X X Color ο ο ο ο ο X X Shape ο ο ο ο ο X X Weight X ο ο ο ο X Hardness X ο ο ο ο X Haptics X ο ο ο ο X Sound X ο ο ο ο X Functionality Functional Depth ο X ο ο ο X Functional Width ο X ο ο ο X Interactivity CONCLUSION Action ο ο X ο ο X Reaction X ο ο ο ο X Topology Physical ο ο ο ο ο X X Tangible ο ο ο ο ο X X X Prototype X Full Production Model Incremental innovations have been successfully developed for many decades with the help of traditional sequential process structures. However, agile approaches that literature suggests for the realization of radical physical innovations still deserve thorough study. The approach presented in this paper is a contribution to existing research in this field. It serves as a basic framework for an efficient Sprint Planning within an adapted Scrum process. In Scrum, experiencable prototypes possess a crucial role. So far, however, prototyping often lacks a specific prototyping strategy in practice. Addressing this shortcoming, our approach follows a sequential reduction of the high uncertainties associated with radical innovations as a basis for a target-oriented prototyping strategy. This way, the most suitable prototypes for the various Sprints can be derived. In the Sprint Planning, the items of the Product Backlog with the highest priority are implemented in the upcoming Sprint. The prioritization follows the assignment a specific benefit/effort ratio to each item of the Product Backlog. The sequential addressing of the uncertainties in the dimensions of market and technological uncertainty guarantees that the prototyping strategy focusses on the most beneficial items. At the same time, the effort for the implementation of the items is estimated on the basis of the team s capabilities. The motivation formed by the prioritized items is systematically translated into a filterfidelity-profile. The derived profile provides a structure for the design of the most suitable prototype for the upcoming Sprint. The generic character of the profile leaves enough degrees of 8
9 freedom to prevent a limitation of the team s creativity in the search for solution.future work must address various aspects of the models presented in this paper to permit their use in practice. For example, research is necessary in the context of the assessment of benefits connected to the items of the Product Backlog. On the one hand, an operationalization of the degree of uncertainty in the dimensions market and technology is necessary. The development of key performance indicators on the basis of aspects affecting the corresponding uncertainties is seen as suitable here. On the other hand, a method of assessing the amount of uncertainty reduction in the three dimensions through the implementation of an item remains to be investigated. Also, the number of items from the prioritized list selected for the upcoming Sprint must be determined based on the specific amount of time at disposal for the realization of the prototype. Further research remains in the identification of the correlation of the nature of items and the dimensions of the filter-fidelity-model in order to derive a valid fidelity-profile for the prototype. ACKNOWLEDGEMENT The new approach of Target-oriented Prototyping in Highly Iterative Product Development is being examined by the Laboratory of Machine Tools and Production Engineering (WZL) within the publicly funded (German Research Foundation, DFG) University graduate training program Interdisciplinary Ramp-Up (Graduiertenkolleg Anlaufmanagement). 9
10 Bibliography Burmeister, K., H. Rüggeberg Innovationsprozesse in kleinen und mittleren Unternehmen. Working Papers 41: 35. Cooper, R. G Stage-Gate Systems A New Tool for Managing New Products. Business Horizons 33(3): Cooper, R. G What s Next?: After Stage Gate. Research Technology Management 57: Fujimoto, T., S. Thomke The Effect of "Front-Loading" Problem-Solving on Product Development Performance. Journal of Product Innovation Management 2: Gao, S., L. Rusu Modern techniques for successful IT project management. Business Science Reference An Imprint of IGI Global, Hershey. Gebhardt, A Rapid Prototyping. Hanser, München. Herstatt, C., B. Verworn Management der frühen Innovationsphase. Gabler, Wiesbaden. Kohler, K., T. Hochreuter, S. Diefenbach, E. Lenz, M. Hassenzahl Durch schnelles Scheitern zum Erfolg: Eine Frage des passenden Prototypen?. Usability Professionals : Lang, H Forschungskooperationen zwischen Universitäten und Industrie: Kooperationsentscheidung und Performance Management. Gabler Verlag, Wiesbaden. Lim, Y.-K., E. Stolterman, J. Tenenberg The anatomy of prototypes: Prototypes as filters, prototypes as manifestations of design ideas. ACM Transactions on Computer-Human Interaction 15(7): Lynn, G. S., A. E. Akgün Innovation Strategies Under Uncertainty: A Contingency Approach for New Product Development. Engineering Management Journal 10(3): McDermott, C. M., G. C. O'Connor Managing radical innovation: an overview of emergent strategy issues. Journal of product innovation management, 19(6): Meyer, J.-U Radikale Innovation. BusinessVillage, Göttingen. O'Connor, G. C., M. P. Rice Opportunity Recognition and Breakthrough Innovation in Large Established Firms. California Management Review 43(2). Schuh, G., T. Gartzen, F. Basse, E. Schrey Enabling radical innovation through highly iterative product expedition in ramp up and demonstration factories. Procedia CIRP. Shina, S. G Successful Implementation of Concurrent Engineering Products and Processes. Van Nostrand Rheinhold, New York. Stavru, S A critical examination of recent industrial surveys on agile method usage. Journal of Systems and Software 94: Sutherland, J The Scrum Handbook. Scrum, Inc., Cambridge. Ulrich, K. T., S. D. Eppinger Product Design and Development. McGraw Hill Higher Education, Boston. Walcher, D Der Ideenwettbewerb als Methode der aktiven Kundenintegration. Deutscher Universitätsverlag, Wiesbaden. 10
Agile Software Development
Agile Software Development Lecturer: Raman Ramsin Lecture 3 Scrum Framework 1 Scrum Origins First mentioned as a development method in 1986, referring to a fast and flexible product development process
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 4 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationA new framework for the development of smart products
A new framework for the development of smart products 60 th EOQ Quality Congress in Helsinki, 01.06.2016 Dipl.-Ing. Dipl.-Wirt.Ing. Henning Voet Prof. Dr.-Ing. Robert H. Schmitt Chair for Production Metrology
More informationEngineering Change Management within agile Product Development A Case Study
Engineering Change Management within agile Product Development A Case Study Lucia Becerril, Veronika Heinrich, Annette Böhmer, Sebastian Schweigert, Udo Lindemann Institute of Product Development, Technical
More informationPRINCE Update. Changes to the manual. AXELOS.com. April 2017 PUBLIC
PRINCE2 2017 Update s to the manual AXELOS.com April 2017 2 PRINCE2 2017 Update Contents 1 Introduction 3 2 Summary of changes 4 PRINCE2 2017 Update 3 1 Introduction This document provides a list of the
More informationAdapt! Agile Project Management Supported by Axiomatic Design
Adapt! Agile Project Management Supported by Axiomatic Design Jakob Weber 1,*, David Förster 1, Markus Stäbler 1 and Kristin Paetzold 2 1 Daimler AG, Process Development and Materials Department, 71059
More informationScaled agile deliveries; do we still need estimates? ICEAA Workshop 2018
Scaled agile deliveries; do we still need estimates? ICEAA Workshop 2018 Eric van der Vliet Director CGI - Estimation Centre CGI Group Inc. Agile becomes more and more important across the IT Industry.
More informationAgile Essentials Track: Business Services
Agile Essentials Track: Business Services Presenter: Mark Thomas Synopsis Are you a victim of building the wrong solutions slowly? If so, you re not alone, and considering an Agile approach may be the
More informationEarned Value in Agile: The Definition of done in Agile Software development EVA 16, London, June 14th 15th Kjetil Strand, Promis AS
Earned Value in Agile: The Definition of done in Agile Software development EVA 16, London, June 14th 15th Kjetil Strand, Promis AS 20.06.2011 PROMIS AS 1 Outline of the talk Background Earned Value Analysis
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 7 Agile Methodologies: Scrum 1 Agile Methodologies: Brief History First appeared in 1995. The once-common perception that agile methodologies
More informationSCRUM - compact The agile software development methodology
Scrum in 30 seconds Scrum is an empirical way to manage software development projects. Scrum is made up of an easy set of rules and ensures that every team member feels the responsibility of a project
More informationIs Agile Project Management fit for small tech start-ups?
2017 IJSRST Volume 3 Issue 1 Print ISSN: 2395-6011 Online ISSN: 2395-602X Themed Section: Science and Technology Is Agile Project Management fit for small tech start-ups? Priti Asthana Project Manager,
More informationInstitut für gestaltorientierte Organisationsentwicklung. SCRUM Implementation. IGOR 2018 Institute for Gestalt organizational Consulting
Implementation IGOR 2018 Institute for Gestalt organizational Consulting Frankfurt/Main - 06. Dec. 2018 SUCCESS FACTORS cross functional development team development team responsibility for work feedback
More informationProcesses. Object Orientated Analysis and Design. Benjamin Kenwright
Processes Object Orientated Analysis and Design Benjamin Kenwright Outline Review What are Processes? Why are they important in Object Orientated Analysis and Design Conclusion and Discussion Summary Revision
More informationLSP METHODOLOGY GUIDE. LSP Group
LSP METHODOLOGY GUIDE LSP Group 2017 Introduction... 3 Scrum framework... 4 Why scrum?... 4 Scrum Principles... 5 Lean Canvas... 6 Why Lean Canvas?... 6 Lean canvas life cycle... 7 Knowledge lean canvas...
More informationLead User in Open Organizations How a Refined Lead User Concept can help to Integrate Workshop Results
Lead User in Open Organizations How a Refined Lead User Concept can help to Integrate Workshop Results Alexander Lang 1, Sarah Telkamp 2, Udo Lindemann 1, Thomas Münster 2 1: Institute of Product Development
More informationObject-Oriented Software Engineering Practical Software Development using UML and Java. Chapter 11: Managing the Software Process
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 11: Managing the Software Process 11.1 What is Project Management? Project management encompasses all the
More informationSprint. Innovate via rapid product/service prototyping and market testing.
Strategic Doing Google Ventures Sprint SCRUM Kanban Lean Development Guiding Themes Align networks in via a shared discipline of simple rules. Innovate via rapid prototyping and market testing. Empower
More informationDesigning the Process. A Brief Introduction to Agile Programming
Designing the Process A Brief Introduction to Agile Programming In the beginning, there was the waterfall... Analysis, Design, Implementation, Testing & Evaluation: Discrete, linear tasks Each step completed
More informationJohanna Rothman Part II Design and Manage an Agile and Lean Project Chapter 5 Start Your Agile Project Right. Copyright 2017
Johanna Rothman Part II Design and Manage an Agile and Lean Project Chapter 5 Start Your Agile Project Right Copyright 2017 Start you Agile project right Projects need direction teams need to know where
More informationThe Software Life Cycle
Inception Software Increment Communication Planning Production The Software Life Cycle Software Engineering Deployment Andreas Zeller Saarland University Modelling Elaboration Transition Construction Construction
More informationSoftware Engineering
Software Engineering Lecture 02: Processes Peter Thiemann University of Freiburg, Germany SS 2013 Peter Thiemann (Univ. Freiburg) Software Engineering SWT 1 / 41 Terms Software Component SW System Organized
More informationKeywords: Scrum framework, agile software development, change management, iterative development.
International Journals of Advanced Research in Computer Science and Software Engineering ISSN: 2277-128X (Volume-7, Issue-7) Research Article July 2017 Implementation of Change Management in Software Development
More informationEMBEDDED OPEN TOOLKITS FOR USER INNOVATION: POSTPONING NEW PRODUCT DEVELOPMENT DECISIONS INTO THE CUSTOMER DOMAIN
Association for Information Systems AIS Electronic Library (AISeL) Wirtschaftsinformatik Proceedings 2009 Wirtschaftsinformatik 2009 EMBEDDED OPEN TOOLKITS FOR USER INNOVATION: POSTPONING NEW PRODUCT DEVELOPMENT
More informationThis document is copyrighted, the distribution of this document is punishable by law.
Lecture 1 A project is a temporary endeavor undertaken to create a unique product, service or result A process is a series of actions taken in order to achieve result, a project is temporary with a clear
More informationLecture 8 Agile Software Development
Lecture 8 Agile Software Development Includes slides from the companion website for Sommerville, Software Engineering, 10/e. Pearson Higher Education, 2016. All rights reserved. Used with permission. Topics
More informationapproach to successful project
1 The NYS Forum, Inc. Using an Agile / Waterfall Hybrid approach to successful project delivery Presented by Matthew Carmichael Project Management Workgroup 2 When to use Waterfall Projects that require
More informationGETTING STARTED. Introduction to Sprint Reviews
GETTING STARTED Introduction to Sprint Reviews contents SECTION introduction to sprint SECTION conducting sprint reviews in 1 reviews what is a sprint review? 4 benefits of sprint reviews 5 anatomy of
More informationIngegneria del Software Corso di Laurea in Informatica per il Management. Scrum. Davide Rossi Dipartimento di Informatica Università di Bologna
Ingegneria del Software Corso di Laurea in Informatica per il Management Scrum Davide Rossi Dipartimento di Informatica Università di Bologna What is Scum Scrum (n): A framework within which people can
More informationBUSINESS INSIGHTS. Making the Transformational Shift to Scrum
BUSINESS INSIGHTS > Making the Transformational Shift to Scrum 1 Meeting Market Demand Transforming an organizational culture to one that embraces and succeeds with that new methodology is essential. Choosing
More informationBUSINESS INSIGHTS > Making the Transformational Shift to Scrum
BUSINESS INSIGHTS > Making the Transformational Shift to Scrum 1 Meeting Market Demand Transforming an organizational culture to one that embraces and succeeds with that new methodology is essential. Choosing
More informationAssistant Professor, Integral University, Lucknow, India. Quality Parameters. Correctness. Efficiency. Portability. Usability.
Extreme Programming: Aiming towards Quality Assurance Ayesha Saad Khan, Mohammad Suaib M.tech CSE (2 nd Year), Integral University, Lucknow, India Abstract- Agile methodologies are among the most popular
More informationThe Software Life Cycle
Production Inception The Life Cycle Engineering Modelling Andreas Zeller Saarland University Elaboration Transition A Crisis Denver International Airport (DIA) started in 1989 53 sq miles Planned: 1.7
More informationAgile Certified Professional
Certified Professional Study Guide Take the Certification Online www.scrumprofessionals.org Contents 1. AGILE PRIMER... 1 Roles in... 1 Cross-functional Team... 2 How an Team Plans its Work?... 3 What
More informationHow to Utilize Agile Project Management for GIS Projects. Lana Tylka and Jennifer Prather
How to Utilize Agile Project Management for GIS Projects Lana Tylka and Jennifer Prather How to Start Conduct kickoff meeting Discuss similar industries Assess workflows Prioritize workflows Create a plan
More informationWhite paper Pink Agile Framework
Make your organization Agile, The Pink Way. About Pink Elephant Pink Elephant is an international knowledge leader in the field of business innovation and business change. With advisory and IT services,
More informationCTC/ITC 310 Program Management California State University Dominguez Hills First Exam Answer Key November 20, 2018 Instructor: Howard Rosenthal
CTC/ITC 310 Program Management California State University Dominguez Hills First Exam Answer Key November 20, 2018 Instructor: Howard Rosenthal There are 30 questions on this exam. Each question is worth
More informationFIT2101 Software Engineering Process and Management
FIT2101 Software Engineering Process and Management Agile and Software Process Models Topics Covered Features of Agile What Agile Isn t Agile Process Models Software Process Models In 2001 leaders of lightweight
More informationProject Management. Kristian Sandahl
Project Management Kristian Sandahl 2 Maintenance Requirements Validate Requirements, Verify Specification Acceptance Test (Release testing) System Design (Architecture, High-level Design) Verify System
More information2. True or false: In Scrum all the requirements for the project are known prior to the start of development.
CTC-ITC 310 Program Management California State University Dominguez Hills Fall 2018 Instructor: Howard Rosenthal Assignment 5 A Deeper Look At Agile Methodologies Answer Sheet Each question is worth 10
More informationCS2310 Software Engineering Fall 2015 Project Report. Displanner (Distributed Scrum/Sprint Planner) By: Bhavin Modi Jose Michael Joseph Vivek Punjabi
CS2310 Software Engineering Fall 2015 Project Report Displanner (Distributed Scrum/Sprint Planner) By: Bhavin Modi Jose Michael Joseph Vivek Punjabi Introduction: The software industry has evolved dramatically
More informationAgile Management Guide
1 Agile Management Guide These days there is a strong push for Agile Management, as opposed to Waterfall. Personally at Castellan Systems we believe that the agility should be applied to the project development
More informationSWE 211 Software Processes
SWE 211 Software Processes These slides are designed and adapted from slides provided by Software Engineering 9 /e Addison Wesley 2011 by Ian Sommerville 1 Outlines Software process models Process activities
More informationAGILE LESSONS FROM THE NEW PMBOK. Presented by Eddie Merla, PMI-ACP, PMP
AGILE LESSONS FROM THE NEW PMBOK Presented by Eddie Merla, PMI-ACP, PMP 2 Agenda Summary of Changes Agile Concepts Five Mindset Shifts Agile Methods & Scrum Q&A Wrap-up 3 Summary of Changes Project managers
More informationSoftware Engineering
Software Engineering (CS550) Software Development Process Jongmoon Baik Software Development Processes (Lifecycle Models) 2 What is a S/W Life Cycle? The series of stages in form and functional activity
More informationThe Business Value of Agile Transformation
SolutionsIQ The Business Value of Agile Transformation By John Rudd Overview The potential benefits of full-scale Agile are enormous, although rarely fully realized. Many of the companies that adopt Agile
More informationWhat is Scrum: An Introduction to the Scrum Framework
What is Scrum: An Introduction to the Scrum Framework Eric Naiburg Vice President of Marketing and Operations eric.naiburg@scrum.org April 4, 2018 @ScrumDotOrg 1 Improving the Profession of Software Delivery
More informationSOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) UNIT OBJECTIVE Understand the influences on a project Understand what a software process is Understand two common models WHAT EACH PARTY CONTROLS Client Side Every
More informationSoftwaretechnik. Lecture 02: Processes. Peter Thiemann SS University of Freiburg, Germany
Softwaretechnik Lecture 02: Processes Peter Thiemann University of Freiburg, Germany SS 2012 Peter Thiemann (Univ. Freiburg) Softwaretechnik SWT 1 / 34 Terms Software Program SW System organized collections
More informationWatson Internet of Things. Agile Development Why requirements matter
Watson Internet of Things Agile Development Why requirements matter Executive summary The clear benefits of agile development better collaboration, incremental delivery, early error detection and the elimination
More informationSoftware Processes in an Agile World
Software Processes in an Agile World RWTH Aachen University, Research Group Software Construction lichter@swc.rwth-aachen.de Abstract In this paper we relate classical software process models to new agile
More informationSoftware Design COSC 4353/6353 D R. R A J S I N G H
Software Design COSC 4353/6353 D R. R A J S I N G H Outline Week 2 Software Development Process Software Development Methodologies SDLC Agile Software Development Process A structure imposed on the development
More informationAGILE FOR HARDWARE AND CROSS-DISCIPLINE TEAMS
AGILE FOR HARDWARE AND CROSS-DISCIPLINE TEAMS Applying Agile principles to hardware and products with embedded software. Agile development has taken over the software industry. Developers and leaders have
More informationSOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS. Saulius Ragaišis.
SOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS Saulius Ragaišis saulius.ragaisis@mif.vu.lt CSC2008 SE Software Processes Learning Objectives: Explain the concept of a software life cycle and
More informationSCRUM GUIDE SCRUM GUIDE 02. * Agile Software Development with Scrum, Ken Schwaber, Microsoft Press, 2004
SCRUM GUIDE SCRUM GUIDE This guide explains how to use Scrum to build products. In doing so, it will describe how the framework and its artifacts, time-boxes, roles and rules work together. Scrum does
More informationTOWARDS AN EARLY CONSIDERATION OF RAMP-UP PHASE IN THE PRODUCT DEVELOPMENT OF COMPLEX PRODUCTS
INTERNATIONAL DESIGN CONFERENCE - DESIGN 2012 Dubrovnik - Croatia, May 21-24, 2012. TOWARDS AN EARLY CONSIDERATION OF RAMP-UP PHASE IN THE PRODUCT DEVELOPMENT OF COMPLEX PRODUCTS S. Elstner and D. Krause
More informationImproving Agile Execution in the Federal Government
Improving Agile Execution in the Federal Government 1 Committed Partner. Creating Results. In December of 2010 the government introduced the 25 Point Implementation Plan to Reform Federal Information Technology
More informationAn Introduction to Scrum
What is Scrum? Even projects that have solid, well-defined project plans encounter some degree of change. Shifting market conditions, budget cuts, staff restructuring, or any number of influences will
More informationInternational Scrum Master Foundation. Study Guide Take the Certification online
International Scrum Master Foundation Study Guide Take the Certification online www.scrum.as Contents Chapter 1: WHAT IS SCRUM?... 3 Chapter 2: INTRODUCTION TO SCRUM - A REAL WORLD EXAMPLE... 5 Chapter
More informationeconstor Make Your Publications Visible.
econstor Make Your Publications Visible. A Service of Wirtschaft Centre zbwleibniz-informationszentrum Economics Verworn, Birgit; Herstatt, Cornelius Working Paper Approaches to the "fuzzy front end" of
More informationSoftware Organizations are Struggling to Prove their Value
OVERVIEW Over the last 15 years, software development organizations have been superficially described as value-generators. In fact, the increasingly common cost-cutting practice of outsourcing development
More informationChapter 3 Agile Software Development. Part 1b
Chapter 3 Agile Software Development Part 1b 1 Testing in XP Testing is central to XP and XP has developed an approach where the program is tested after every change has been made. XP testing features:
More informationA practical guide to governance of enterprise-scale Agile projects. 4 October 2011
A practical guide to governance of enterprise-scale Agile projects 4 October 2011 What are we talking about! Governance of enterprise-scale Agile projects What is Governance? What is enterprise-scale Agile?
More informationSYED AMMAL ENGINEERING COLLEGE (An ISO 9001: 2008 Certified Institution)
MG6088 SOFTWARE PROJECT MANAGEMENT 1. Define software project management. QUESTION BANK UNIT - 1 PART A 2. Point out the characteristics of software project? 3. List the activities covered by software
More informationBest Practices for Enterprise Agile Transformation
Best Practices for Enterprise Agile Transformation A White Paper for the Software Development Project Community Date: May 2017 Select Computing, Inc. 9841 Broken Land Parkway Suite 209 Columbia, MD 21046
More informationIntroduction to Agile/Extreme Programming
Introduction to Agile/Extreme Programming Matt Ganis, Senior Technical Staff Member (Certified Scrum Master) IBM Hawthorne, New York ganis@us.ibm.com August 2007 Session 8061 Current slides at: http://webpage.pace.edu/mganis
More informationAgile leadership for change initiatives
Agile leadership for change initiatives Author Melanie Franklin Director Agile Change Management Limited Contents Introduction 3 Agile principles 3 Introduction to Agile techniques 6 Working in sprints
More information[control] [data] [process] [strategy] [partners] [testing] [validation]
[control] [data] [process] A practical approach to using Agile in an FDA regulated environment environment Jim Gunning Director, Q-CSV Johnson & Johnson [strategy] [partners] [testing] [validation] Agenda
More informationCMPT 275 Software Engineering
CMPT 275 Software Engineering Software life cycle 1 Software Life Cycle Sequence of processes completed as a software project moves from inception to retirement At beginning of project development, choose
More informationSoftware Processes. With a focus on Agile/Scrum CPSC310 Software Engineering
Software Processes With a focus on Agile/Scrum CPSC310 Software Engineering Learning Goals Why do software projects fail? Unrealistic project goals Inaccurate estimates of needed resources Unmanaged risks
More informationManaging the Innovation Process. Launch and Nurture stage: Methods and principles
Managing the Innovation Process Launch and Nurture stage: Methods and principles Strategic Orientation for the Launch Stage Input: Corporate and team decisions made earlier. Often found in the PIC Guidelines.
More informationImplementing customer solutions successfully
Implementing customer solutions successfully Gerhard Gudergan, Ralf Frombach, Norbert Skala, Peter Thomassen FIR Research Institute for Operations Management, Pontdriesch 14/16, 52062 Aachen, Germany,
More informationEVIDENCE-BASED MANAGEMENT GUIDE
EBMgt EVIDENCE-BASED MANAGEMENT GUIDE Empirical management for software organizations By Ken Schwaber Patricia Kong David Starr OVERVIEW Over the last 15 years, software development organizations have
More informationHandling Product Management Across The Enterprise. copyright Net Objectives, Inc.
Handling Product Management Across The Enterprise copyright 2010. Net Objectives, Inc. Lean for Executives Product Portfolio Management Business Lean Enterprise ASSESSMENTS CONSULTING TRAINING COACHING
More informationINTEGRATION OF PROJECT MANAGEMENT IN THE HIGHER EDUCATION CURRICULUM
ENGINEERING AND PRODUCT DESIGN EDUCATION CONFERENCE 7-8 SEPTEMBER 2006, SALZBURG UNIVERSITY OF APPLIED SCIENCES, SALZBURG, AUSTRIA INTEGRATION OF PROJECT MANAGEMENT IN THE HIGHER EDUCATION CURRICULUM Malcolm
More informationTHE CONCEPT OF MISSIONS SHIFTING PERSPECTIVE TO A MORE IMPACT-DRIVEN APPROACH
FRAUNHOFER-GESELLSCHAFT ZUR FÖRDERUNG DER ANGEWANDTEN FORSCHUNG E.V. THE CONCEPT OF MISSIONS SHIFTING PERSPECTIVE TO A MORE IMPACT-DRIVEN APPROACH Brussels, 30/08/2017 Contact Fraunhofer Department for
More informationEvents. Artifacts. Roles. Product Owner Scrum Master Development Team. Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective
Scrum Lecture 2 1 Roles Product Owner Scrum Master Development Team Events Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Artifacts Project Charter Product Backlog Sprint Backlog
More informationAgile Software Development
Agile Software Development Chapter 3 Agile Software Development in the textbook 3.1 Agile methods 3.2 Plan-driven and agile development 3.3 Extreme programming (XP) - A well known agile method 3.4 Agile
More information$BILLION AGILE EXECUTING LARGE EPC/EPCM PROJECTS USING SCRUM VALUES AND PRINCIPLES
EXECUTING LARGE EPC/EPCM PROJECTS USING SCRUM VALUES AND PRINCIPLES WHAT PROBLEMS NEED SOLVING? Unclear priorities, roles Working in silos Lack of visible progress on what s important and why Lack of accountability
More informationThe Move from Traditional Change Management to Agile Methodology
The Move from Traditional Change Management to Agile Methodology Jean Davis Palazzetti, MSN, MBA, HCM, RN, Senior Director Nursing Informatics, Banner Health Implementing agile change management methodology
More informationAGILE AND SCRUM IN A SMALL SOFTWARE DEVELOPMENT PROJECT- A CASE STUDY
AGILE AND SCRUM IN A SMALL SOFTWARE DEVELOPMENT PROJECT- A CASE STUDY Shanmuganathan Vasanthapriyan Department of Computing and Information Systems, Sabaragamuwa University of Sri Lanka, Sri Lanka priyan@appsc.sab.ac.lk
More informationIntroduction to Agile and Scrum
Introduction to Agile and Scrum Matthew Renze @matthewrenze COMS 309 - Software Development Practices Purpose Intro to Agile and Scrum Prepare you for the industry Questions and answers Overview Intro
More informationPMINJ Chapter 02 May Symposium Hybrid Agile The Best of Both Worlds
PMINJ Chapter 02 May Symposium 2016 Hybrid Agile The Best of Both Worlds Robert Medary www.hcltech.com 1 Copyright 2015 HCL Technologies Limited www.hcltech.com CONTENTS Waterfall Overview High Level Agile
More informationSoftware Development Life Cycle:
Software Development Life Cycle: The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software
More informationThe analytics translator The Must-Have Role for AI-Driven Organizations. Whitepaper. Proudly part of Xebia Group
The analytics translator The Must-Have Role for AI-Driven Organizations. Whitepaper Proudly part of Xebia Group Executive Summary» Many organizations have not seen return on their investment after developing
More information3. Comparison of Above Described SDLC Models
123 3. Comparison of Above Described SDLC Models Waterfall Model is little hard to manage due to the rigidity of the model as each phase has specific deliverables and a review process. It works well for
More informationScrum. a description. V Scrum Alliance,Inc 1
Scrum a description V 2012.12.13 2012 Scrum Alliance,Inc 1 Scrum Principles Values from the Agile Manifesto Scrum is the best-known of the Agile frameworks. It is the source of much of the thinking behind
More informationTOTAL PERFORMANCE SCORECARD
Anca ȘERBAN Oana DUMITRAȘCU Department of Management, Marketing and Business Administration Faculty of Economics, "Lucian Blaga" University Sibiu, Romania TOTAL PERFORMANCE SCORECARD Keywords Balanced
More informationWhat if Scrum had no rules?
What if Scrum had no rules? Peter Stevens Attribution- ShareAlike 3.0 Unported (CC BY- SA 3.0) Transforming your Culture with Working Agreements Basic (2. Stock) 16:00 17:00 Which best describes the attitude
More informationDarshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1
Failure Rate Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1 SOFTWARE (What is Software? Explain characteristics of Software. OR How the software product is differing than
More informationCA Technologies Increases Customer Satisfaction and Repeat Business by Scaling Agile for Mainframe Development
CUSTOMER SUCCESS STORY CA Technologies Increases Customer Satisfaction and Repeat Business by Scaling Agile for Mainframe Development CLIENT PROFILE Industry: IT Organization: CA Technologies Mainframe
More informationManage Projects Effectively
White Paper Application Development, Test & Delivery Manage Projects Effectively Table of Contents page Executive Summary... 1 The Micro Focus Solution Invest in What Matters Most then Manage It... 2 Strategic
More informationNonlinear Dynamic Analysis a Step Advance
Nonlinear Dynamic Analysis a Step Advance in Assessing the Vulnerability of Buildings Editor s note: The strength of an earthquake catastrophe model in producing to Earthquake reliable loss estimates lies
More informationABHELSINKI UNIVERSITY OF TECHNOLOGY
T 76.3601 Introduction to Software Engineering Software Life-Cycle Models http://www.soberit.hut.fi/t-76.3601/ Casper.Lassenius@tkk.fi Software Engineering? 1. The application of a systematic, disciplined,
More informationSolutions for higher performance! Agile. Methodologies. Key. Principles. Series-I
Solutions for higher performance! Agile Methodologies & Key Principles Series-I Introduction Agile software development is a group of software development methods in which requirements and solutions evolve
More informationSoftware Processes 1
Software Processes 1 Topics covered Software process models Process activities Coping with change 2 The software process A structured set of activities required to develop a software system. Many different
More informationChapter 7. Project Reporting Keeping Everything Visible
Chapter 7 Project Reporting Keeping Everything Visible A Scrum project is controlled by means of frequent inspection of the project followed by necessary adaptations Daily Scrum to get a feel for the tone,
More informationBased on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems
Software Processes Based on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems Slide 1 Objectives To introduce software
More informationThis tutorial also elaborates on other related methodologies like Agile, RAD and Prototyping.
i About the Tutorial SDLC stands for Software Development Life Cycle. SDLC is a process that consists of a series of planned activities to develop or alter the Software Products. This tutorial will give
More informationAcceptance Criteria. Agile. Details that indicate the scope of a user story and help the team and product owner determine done-ness.
Acceptance Criteria Details that indicate the scope of a user story and help the team and product owner determine done-ness. Agile The name coined for the wider set of ideas that Scrum falls within. These
More information