Case Study of a Mechanical Product Development Team Using Scrum Master of Science Thesis in the Master Degree Programme, Product Development
Total Page:16
File Type:pdf, Size:1020Kb
Scrum in Mechanical Product Development Case Study of a Mechanical Product Development Team using Scrum Master of Science Thesis in the Master Degree Programme, Product Development ÞÓRDÍS REYNISDÓTTIR Department of Product and Production Development Division of Product Development CHALMERS UNIVERSITY OF TECHNOLOGY Gothenburg, Sweden, 2013 1 MASTER’S THESIS Scrum in Mechanical Product Development Case Study of a Mechanical Product Development Team using Scrum Master of Science Thesis in the Master Degree Programme, Product Development ÞÓRDÍS REYNISDÓTTIR SUPERVISOR & EXAMINER: GÖRAN GUSTAFSSON Department of Product and Production Development Division of Product Development CHALMERS UNIVERSITY OF TECHNOLOGY Gothenburg, Sweden, 2013 Scrum in Mechanical Product Development Case Study of a Mechanical Product Development Team using Scrum © ÞÓRDÍS REYNISDÓTTIR Supervisor & Examiner: Göran Gustafsson, Ph.D. Chalmers University of Technology Department of Product and Production Development SE- 412 96 Gothenburg Sweden Telephone: +46(0)31-772 10 00 Gothenburg, Sweden, 2013 Abstract The purpose of this study was to investigate if it would be possible for a mechanical product development team to use Scrum, an Agile Development framework. The Agile philosophy and methods have revolutionized the software development industry in the last decade, and therefore it was of interest to see if this new way of working would be applicable in hardware development. The study focuses on if Scrum can be applied in mechanical product development, and if it needs any adaptations. Three case studies of Scrum or Agile methods used in mechanical and hardware design and development are presented. The primary case study follows a mechanical product development team through their 7-month experiment of using Scrum. The team in question co-operates with an embedded software development team in new product development. Two supplementary case studies are presented: The first on a single cross-functional hardware team using a Scrum like method, and the second, on an organization re-structuring. The methods used in order to form the case studies were observations, interviews and informal conversations. The results indicate that it is possible for a mechanical development team to use the Scrum framework, with some minor adaptions of the framework. The team in the primary case made use of all main aspects of the framework, but the deviations were that the team was not cross-functional and a working product or product increment is not produced every iteration. The results also indicate that using the framework improved the team’s work and progress, and the team decided to continue using the framework after the experiment. The conclusion is that Scrum can be used in a hardware environment, by mechanical development teams. Some adaptations might be needed, depending on each case, but this is also recommended in the literature to software development teams. Key words: Product development, Scrum, Agile, Lean Product Development, Hardware, Mechanical I Acknowledgements Firstly, I specially want to thank Mr. Ásgeir Ásgeirsson, the Innovation Community Director at Marel GRB, for believing in me and giving me the opportunity to work for Marel and getting the chance to do my Master Thesis project there. Secondly, I want to thank Ms. Rósa Björg Ólafsdóttir, Agile Center Manager at Marel GRB, for her full support, insightful discussions and mentorship throughout the project. I also want to thank her for the interest shown in my work and the input she provided. Thirdly, I want to thank IC-Fish, the development teams and its management, for giving me the chance to perform my study with them, and the time we have had working together throughout the experiment. Special thanks to the mechanical team for their patience and allowing me to observe and question them. In addition to this, I want to thank those who gave their time and provided me with further case study material on the use of Agile and Scrum in hardware product development. Firstly, I thank Mr. Martin Labecker, Line Manager at SAAB EDS, Gothenburg Sweden, for giving me the chance to visit and see the way one of their hardware teams works. I want to thank Mr. Henrik Lindsjö for giving me an insight into the new organization at Andritz Hydro AB, Service and Rehab division in Sweden, and the interesting discussions we had through our correspondence. I also want to thank Mr. Mikael Lundgren, Agile and Lean Product Development Expert, for his correspondence, his further insight into the organizational restructuring at Andritz Hydro and insight into how Scrum is used in hardware and mechanical development in the industry. I want to thank my family for their unconditional support throughout my studies and project work. Last but not least, I want to thank my supervisor Dr. Göran Gustafsson, believing in the project and me and seeing the potential of taking it to a higher level. His enthusiasm, guidance and support, and inspired me during the project work. I am also very grateful to him for introducing me to Lean Product Development. II III Table of Contents Abstract ................................................................................................................................ I Acknowledgements ........................................................................................................... II Table of Contents ............................................................................................................. IV List of Abbreviations ....................................................................................................... VII 1 Introduction ................................................................................................................ 1 1.1 Purpose .................................................................................................................................................................. 1 1.2 Delimitations ....................................................................................................................................................... 1 1.3 Outline of the Thesis ......................................................................................................................................... 2 2 Problem formulation .................................................................................................. 3 2.1 Introduction to Marel GRB .............................................................................................................................. 3 2.2 The Problem Definition ................................................................................................................................... 3 2.3 Research Questions ........................................................................................................................................... 4 3 Methodology............................................................................................................... 5 3.1 Research Approach ........................................................................................................................................... 5 3.2 Literature Review ............................................................................................................................................... 5 3.3 Observations ........................................................................................................................................................ 6 3.4 Interviews ............................................................................................................................................................. 6 3.5 Case Studies ......................................................................................................................................................... 6 3.5.1 Primary Case Study .................................................................................................................................... 7 3.5.2 Supplementary Case Studies ................................................................................................................... 7 3.6 Validity ................................................................................................................................................................... 7 4 Theoretical Framework .............................................................................................. 9 4.1 Agile Software Development ........................................................................................................................ 9 4.1.1 History and Background ........................................................................................................................... 9 4.1.2 Manifesto for Agile Software development .......................................................................................... 9 4.1.3 The Waterfall Model ................................................................................................................................ 10 4.1.4 Traditional vs. Agile ................................................................................................................................. 12 4.1.5 Agile Planning ........................................................................................................................................... 12 4.1.1 Success Factors in Deployment and Sustaining of Agile Methods ............................................... 15 4.1.2 Kanban ......................................................................................................................................................