DOCSLIB.ORG

Agile Processes in Software Engineering and Extreme Programming LNBIP 383

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Agile Processes in Software Engineering and Extreme Programming LNBIP 383 Viktoria Stray Rashina Hoda Maria Paasivaara Philippe Kruchten (Eds.) Agile Processes in Software Engineering and Extreme Programming LNBIP 383 21st International Conference on Agile Software Development, XP 2020 Copenhagen, Denmark, June 8–12, 2020, Proceedings 123 Lecture Notes in Business Information Processing 383 Series Editors Wil van der Aalst RWTH Aachen University, Aachen, Germany John Mylopoulos University of Trento, Trento, Italy Michael Rosemann Queensland University of Technology, Brisbane, QLD, Australia Michael J. Shaw University of Illinois, Urbana-Champaign, IL, USA Clemens Szyperski Microsoft Research, Redmond, WA, USA More information about this series at http://www.springer.com/series/7911 Viktoria Stray • Rashina Hoda • Maria Paasivaara • Philippe Kruchten (Eds.) Agile Processes in Software Engineering and Extreme Programming 21st International Conference on Agile Software Development, XP 2020 Copenhagen, Denmark, June 8–12, 2020 Proceedings 123 Editors Viktoria Stray Rashina Hoda University of Oslo Monash University Oslo, Norway Clayton, VIC, Australia Maria Paasivaara Philippe Kruchten IT University of Copenhagen University of British Columbia Copenhagen, Denmark Vancouver, BC, Canada ISSN 1865-1348 ISSN 1865-1356 (electronic) Lecture Notes in Business Information Processing ISBN 978-3-030-49391-2 ISBN 978-3-030-49392-9 (eBook) https://doi.org/10.1007/978-3-030-49392-9 © The Editor(s) (if applicable) and The Author(s) 2020. This book is an open access publication. Open Access This book is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made. The images or other third party material in this book are included in the book’s Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the book’s Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. The publisher, the authors and the editors are safe to assume that the advice and information in this book are believed to be true and accurate at the date of publication. Neither the publisher nor the authors or the editors give a warranty, express or implied, with respect to the material contained herein or for any errors or omissions that may have been made. The publisher remains neutral with regard to jurisdictional claims in published maps and institutional affiliations. This Springer imprint is published by the registered company Springer Nature Switzerland AG The registered company address is: Gewerbestrasse 11, 6330 Cham, Switzerland Preface This volume contains the research papers of the 21st International Conference on Agile Software Development (XP 2020), planned to be held June 8–12 at the IT University of Copenhagen, Denmark. However, due to the COVID-19 pandemic, the conference was held online. XP is the premier agile software development conference combining research and practice. It is a unique forum where agile researchers, practitioners, thought leaders, coaches, and trainers get together to present and discuss their most recent innovations, research results, experiences, concerns, challenges, and trends. XP conferences provide an informal environment to learn and trigger discussions and welcome both people new to agile and seasoned agile practitioners. XP 2020 marked the 21st edition of the “First Conference in Agile.” Agile continues to advance, and the focus of the XP conference program has expanded over the years. While the first XP conference focused on eXtreme Programming and predated the “Agile Manifesto,” XP 2020 solicited contributions that address all modern agile approaches, as well as the application of agile to areas including but not limited to FinTech, AI/ML, IoT, and other mission-critical systems with global reach. The XP 2020 conference invited submissions on 12 tracks, including research papers, research workshops, experience reports, industry and practice, doctoral sym- posium, education and training, on-site research, journal first, diversity and inclusion, leadership, agile games, and lightning talks. In total, across all submission types, we received over 300 proposals, which demonstrates that the XP community is growing and active. The research paper track invited submissions of unpublished high-quality research papers, full and short, related to agile and lean software development. Submissions addressing topics across the full spectrum of agile software development, broadly on agile, on issues of concern to researchers or practitioners or both were welcomed. The XP 2020 research paper track received 46 submissions. After the first screening by the track chairs, 37 submissions were sent for peer review. Each paper was reviewed by three members of the Program Committee. Based on the reviewer comments, 12 full and 4 short papers were accepted for publication in these proceedings. The papers contribute to the literature on agile research and experience, addressing a wide range of topics, including distributed development, large-scale transformation, ethics, leader- ship, user-centered design, and test-driven development. We would like to extend our sincere thanks to all the people who contributed to XP 2020: the authors, reviewers, sponsors, chairs, and volunteers. Finally, we would like to express our gratitude to the XP Conference Steering Committee and the Agile Alliance for their ongoing support. April 2020 Viktoria Stray Rashina Hoda Maria Paasivaara Organization Conference Chair Maria Paasivaara Technical University of Denmark, Denmark Program Co-chairs Viktoria Stray University of Oslo, SINTEF, Norway Rashina Hoda Monash University, Australia Publication Chair Philippe Kruchten The University of British Columbia, Canada Program Committee Noura Abbas Colorado Technical University, USA Scott Ambler SA+A, Canada Craig Anslow Victoria University of Wellington, New Zealand Hubert Baumeister Technical University of Denmark, Denmark Marthe Berntzen University of Oslo, Norway Jan Bosch Chalmers University of Technology, Sweden Frank Buschmann Siemens AG, Germany Fabio Calefato University of Bari, Italy Daniela S. Cruzes SINTEF, Norway Torgeir Dingsøyr Norwegian University of Science and Technology, Norway Yael Dubinsky StepAhead, Israel Jutta Eckstein IT Communication, Germany Neil Ernst University of Victoria, Canada Steven Fraser Innoxec, USA Juan Garbajosa Universidad Politécnica de Madrid, Spain Eduardo Guerra National Institute of Space Research, Brazil Orit Hazzan Technion – Israel Institute of Technology, Israel Helena H. Olsson University of Malmö, Sweden Philippe Kruchten The University of British Columbia, Canada Kati Kuusinen Technical University of Denmark, Denmark Casper Lassenius Aalto University, Finland Ville Leppänen University of Turku, Finland Lech Madeyski Wroclaw University of Science and Technology, Poland Michele Marchesi Cagliari University, Italy viii Organization Sabrina Marczak PUCRS, Brazil Tommi Mikkonen University of Helsinki, Finland Alok Mishra Atilim University, Turkey Nils Brede Moe SINTEF, Norway Jürgen Münch Reutlingen University, Germany Ipek Ozkaya Carnegie Mellon University, USA Ken Power Cisco Systems, Ireland Pilar Rodríguez University of Oulu, Finland Darja Šmite Blekinge Institute of Technology, Sweden Simone V. Spiegler University of Stuttgart, Germany Stefan Wagner University of Stuttgart, Germany Xiaofeng Wang Free University of Bozen-Bolzano, Italy Hironori Washizaki Waseda University, Japan Contents Agile Adoption Agile Implementation and Expansive Learning: Identifying Contradictions and Their Resolution Using an Activity Theory Perspective . 3 Pritam Chita, Peter Cruickshank, Colin Smith, and Kendall Richards Onboarding: How Newcomers Integrate into an Agile Project Team . 20 Peggy Gregory, Diane E. Strode, Raid AlQaisi, Helen Sharp, and Leonor Barroca Agile Practices Combining User-Centered Design and Lean Startup with Agile Software Development: A Case Study of Two Agile Teams. 39 Ingrid Signoretti, Larissa Salerno, Sabrina Marczak, and Ricardo Bastos Agile Software Development Practices and Success in Outsourced Projects: The Moderating Role of Requirements Risk . 56 Oliver Krancher On the Use of Design Thinking: A Survey of the Brazilian Agile Software Development Community. 73 Matheus Prestes, Rafael Parizi, Sabrina Marczak, and Tayana Conte Characterising the Quality of Behaviour Driven Development Specifications . 87 Leonard Peter Binamungu, Suzanne M. Embury, and Nikolaos Konstantinou “I Don’t Understand!”: Toward a Model to Evaluate the Role of User Story Quality . 103 Daniel Hallmann Large-Scale Agile Large-Scale Agile Transformation: A Case Study of Transforming Business, Development and Operations . 115 Nils Brede Moe and Marius Mikalsen Improving Risk Management in a Scaled Agile Environment . 132 Eva-Maria Schön, Dirk Radtke, and Christian Jordan x Contents The Business
Load more

Recommended publications
  • Artificial Intelligence in Health Care: the Hope, the Hype, the Promise, the Peril
    Artificial Intelligence in Health Care: The Hope, the Hype, the Promise, the Peril Michael Matheny, Sonoo Thadaney Israni, Mahnoor Ahmed, and Danielle Whicher, Editors WASHINGTON, DC NAM.EDU PREPUBLICATION COPY - Uncorrected Proofs NATIONAL ACADEMY OF MEDICINE • 500 Fifth Street, NW • WASHINGTON, DC 20001 NOTICE: This publication has undergone peer review according to procedures established by the National Academy of Medicine (NAM). Publication by the NAM worthy of public attention, but does not constitute endorsement of conclusions and recommendationssignifies that it is the by productthe NAM. of The a carefully views presented considered in processthis publication and is a contributionare those of individual contributors and do not represent formal consensus positions of the authors’ organizations; the NAM; or the National Academies of Sciences, Engineering, and Medicine. Library of Congress Cataloging-in-Publication Data to Come Copyright 2019 by the National Academy of Sciences. All rights reserved. Printed in the United States of America. Suggested citation: Matheny, M., S. Thadaney Israni, M. Ahmed, and D. Whicher, Editors. 2019. Artificial Intelligence in Health Care: The Hope, the Hype, the Promise, the Peril. NAM Special Publication. Washington, DC: National Academy of Medicine. PREPUBLICATION COPY - Uncorrected Proofs “Knowing is not enough; we must apply. Willing is not enough; we must do.” --GOETHE PREPUBLICATION COPY - Uncorrected Proofs ABOUT THE NATIONAL ACADEMY OF MEDICINE The National Academy of Medicine is one of three Academies constituting the Nation- al Academies of Sciences, Engineering, and Medicine (the National Academies). The Na- tional Academies provide independent, objective analysis and advice to the nation and conduct other activities to solve complex problems and inform public policy decisions.
    [Show full text]
  • Optimization of Software Quality Using Management and Technical Review Techniques
    International Journal of Computer Trends and Technology (IJCTT) – volume 17 Number 6 Nov 2014 Optimization of Software Quality using Management and Technical Review Techniques Inibehe Emmanuel Akpannah Post Graduate Student (MSc. Information Technology), SRM University, Chennai, India Abstract compromising the security of the entire system. Optimizing the quality of software is a function of Improving the quality of our software process leads the degree of reviews made during the early life of to minimal rework, cost effectiveness and also a software development process. Reviews detect meeting up with schedules, which all lead to errors and potential errors early in the software improvement in capability measurement. Software development process. The errors detected during review is a chain process, it is dynamic and review the early life cycle of software are least expensive needs to be performed at every phase of the to correct. Efficient involvement in software development process until there is a transition to the inspections and technical reviews, help developers testing phase. improve their own skills, thereby mitigating the Software design and code review is a phase in the occurrence of errors in the later stage of software software development process in which development process. The ideas gathered on this programmers (authors of codes), quality assurance paper point that a properly implemented program of (QA) team, and peer reviewers get together to technical and management reviews drastically review design and code [9]. One way of optimizing reduces the time as well as the cost required for the quality of software is finding and correcting testing, debugging, and reworking, and dramatically errors at the early stage of a software development improves the quality of the resulting product.
    [Show full text]
  • The Timeboxing Process Model for Iterative Software Development
    The Timeboxing Process Model for Iterative Software Development Pankaj Jalote Department of Computer Science and Engineering Indian Institute of Technology Kanpur – 208016; India Aveejeet Palit, Priya Kurien Infosys Technologies Limited Electronics City Bangalore – 561 229; India Contact: [email protected] ABSTRACT In today’s business where speed is of essence, an iterative development approach that allows the functionality to be delivered in parts has become a necessity and an effective way to manage risks. In an iterative process, the development of a software system is done in increments, each increment forming of an iteration and resulting in a working system. A common iterative approach is to decide what should be developed in an iteration and then plan the iteration accordingly. A somewhat different iterative is approach is to time box different iterations. In this approach, the length of an iteration is fixed and what should be developed in an iteration is adjusted to fit the time box. Generally, the time boxed iterations are executed in sequence, with some overlap where feasible. In this paper we propose the timeboxing process model that takes the concept of time boxed iterations further by adding pipelining concepts to it for permitting overlapped execution of different iterations. In the timeboxing process model, each time boxed iteration is divided into equal length stages, each stage having a defined function and resulting in a clear work product that is handed over to the next stage. With this division into stages, pipelining concepts are employed to have multiple time boxes executing concurrently, leading to a reduction in the delivery time for product releases.
    [Show full text]
  • Software Architecture and Agility
    Agility and Architecture May 18 2010 Agility and Architecture: An Oxymoron? Philippe Kruchten Saturn May 18, 2010 Philippe Kruchten, Ph.D., P.Eng., CSDP Professor of So)ware Engineering NSERC Chair in Design Engineering Department of Electrical and Computer Engineering University of BriIsh Columbia Vancouver, BC Canada [email protected] Founder and president Kruchten Engineering Services Ltd Vancouver, BC Canada [email protected] Philippe Kruchten 1 Agility and Architecture May 18 2010 Agile & Architecture? Oil & Water? • Paradox • Oxymoron • Conflict • IncompaIbility Outline • Agility?? • SoSware architecture? • A story • Seven viewpoints on a single problem • The zipper model • A clash of two cultures • Summary Philippe Kruchten 2 Agility and Architecture May 18 2010 Agility • A definiIon – Agility is the ability to both create and respond to change in order to profit in a turbulent business environment. Jim Highsmith (2002) • CharacterisIcs – IteraIve and incremental – Small release – Collocaon – Release plan/ feature backlog – IteraIon plan/task backlog Sanjiv AugusIne (2004) Agile Values: the Agile Manifesto We have come to value: • Individuals and interacIons over process and tools, • Working soSware over comprehensive documents, • Customer collaboraIon over contract negoIaIon, • Responding to change over following a plan. That is, while there is value in the items on the right, we value the items on the leS more Source: hp://www.agilemanifesto.org/ Philippe Kruchten 3 Agility and Architecture May 18 2010 Geng at the Essence of Agility • SoSware development is a knowledge acIvity – Not producIon, manufacturing, administraIon… • The “machines” are humans • Dealing with uncertainty, unknowns, fear, distrust • Feedback loop -> – reflect on business, requirements, risks, process, people, technology • CommunicaIon and collaboraIon -> – Building trust Named Agile Methods • XP = eXtreme Programming (K.
    [Show full text]
  • Agile Software Development and Im- Plementation of Scrumban
    Joachim Grotenfelt Agile Software Development and Im- plementation of Scrumban Metropolia University of Applied Sciences Bachelor of Engineering Mobile Solutions Bachelor’s Thesis 30 May 2021 Abstrakt Författare Joachim Grotenfelt Titel Agile software utveckling och Implementation av Scrumban Antal Sidor 31 sidor Datum 30.05.2021 Grad Igenjör YH Utbildningsprogram Mobile Solutions Huvudämne Informations- och kommunikationsteknologi Instruktörer Mikael Lindblad, Projektledare Peter Hjort, Lektor Målet med avhandlingen var att studera agila metoder, hur de används i mjukvaruföretag och hur de påverkar arbetet i ett programvaruutvecklingsteam. Ett annat mål med avhandlingen var att studera bakgrunden till den agila metoden, hur den togs i bruk och hur den påverkar kundnöjdhet. I denna avhandling förklaras några existerande agila metoder, verktygen för hur agila metoder används, samt hur de påverkar programvaruutvecklingsteamet. Avhandlingen fokuserar sig på två agila metoder, Scrum och Kanban, eftersom de ofta används i olika företag. Ett av syftena med denna avhandling var att skapa förståelse för hur Scrumban metoden tas i bruk. Detta projekt granskar fördelarna med att ha ett mjukvaruutvecklingsteam som arbetar med agila processer. Projektet lyckades bra och en arbetsmiljö som använder agila metoder skapades. Fördelen blev att utvecklarteamet kunde göra förändringar när sådana behövdes. Nyckelord Agile, Scrum, Kanban, Scrumban Abstract Joachim Grotenfelt Author Basics of Agile Software Development and Implementation of Title Scrumban Number of Pages 31 pages Date 30.05.2021 Degree Bachelor of Engineering Degree Program Mobile Solutions Professional Major Information- and Communications Technology Instructors Mikael Lindblad, Project Manager Peter Hjort, Senior Lecturer The goal of the thesis is to study the Agile methods and how they affect the work of a soft- ware development team.
    [Show full text]
  • Extreme Programming Considered Harmful for Reliable Software Development
    AVOCA GmbH Extreme Programming Considered Harmful for Reliable Software Development Status: Approved Author(s): Gerold Keefer Version: 1.0 Last change: 06.02.02 21:17 Project phase: Implementation Document file name: ExtremeProgramming.doc Approval Authority: Gerold Keefer Distribution: Public Security Classification: None Number of pages: 1 Extreme Programming Considered Harmful for Reliable Software Development AVOCA GmbH 1 MOTIVATION ................................................................................................................................... 3 2BIAS................................................................................................................................................. 4 3 BENEFITS ........................................................................................................................................ 4 4 DUBIOUS VALUES AND PRACTICES........................................................................................... 5 5 C3 REVISITED ................................................................................................................................. 7 6 MISSING ANSWERS ....................................................................................................................... 7 7 ALTERNATIVES .............................................................................................................................. 8 8 CONCLUSIONS ............................................................................................................................
    [Show full text]
  • Louisiana Department of Insurance Software Development Standards
    Louisiana Department of Insurance Software Development Standards Louisiana Department of Insurance Table of Contents TABLE OF CONTENTS ....................................................................................... 2 EXECUTIVE SUMMARY ...................................................................................... 3 IMPLEMENTATION OBJECTIVES ...................................................................... 5 LDI SYSTEMS INTEGRATION ............................................................................ 6 LDI ACCEPTABLE TOOLS AND TECHNOLOGIES BY CATEGORY ................ 7 LDI PROJECT MANAGEMENT ......................................................................... 10 LDI PROJECT AND SOFTWARE DELIVERABLES ......................................... 12 SOFTWARE DELIVERABLES ................................................................................. 13 DOCUMENTATION DELIVERABLES ........................................................................ 14 User Documentation/ User Manual ................................................................................... 15 Technical Documentation .................................................................................................. 16 LDI APPLICATION LOOK AND FEEL GUIDELINES ........................................ 19 LDI EXTERNAL BROWSER COMPATIBILITY REQUIREMENTS .................... 20 NETWORK, SERVERS AND MISCELLANEOUS STANDARDS ...................... 21 LDI DEVELOPMENT, TEST AND PRODUCTION ENVIRONMENTS ............... 23 METHODS AND PROCEDURES
    [Show full text]
  • THE OA EFFECT: HOW DOES OPEN ACCESS AFFECT the USAGE of SCHOLARLY BOOKS? White Paper
    springernature.com Illustration inspired by the work of Jean-Claude Bradley Open Research THE OA EFFECT: HOW DOES OPEN ACCESS AFFECT THE USAGE OF SCHOLARLY BOOKS? White paper Open Research: Journals, books, data and tools from: 2 The OA effect: How does open access affect the usage of scholarly books? springernature.com Contents Authors Foreword . 3 Christina Emery, Mithu Lucraft, Executive summary . 4 Agata Morka, Ros Pyne Introduction . 5 November 2017 Part 1: Quantitative findings . 6 Summary . 6 Downloads . 7 Citations and mentions . 11 Part 2: Qualitative findings . 13 Summary . 13 Reasons for publishing open access . 14 Experience of publishing open access . 15 The future of open access . 16 Discussion . 18 Conclusion and recommendations . 20 Acknowledgements . 22 Contacts . 23 About Springer Nature and OA books . 24 Appendices . 26 Appendix 1: Definitions and limitations . 26 Appendix 2: Methodology . 27 Appendix 3: Top 10 downloaded books . 29 Appendix 4: Interviewed authors and funders . 30 Appendix 5: Author questionnaire . 32 Appendix 6: Funder questionnaire . 33 Appendix 7: References . 34 This work is licensed under a Creative Commons Attribution International License (CC BY 4.0) The OA effect: How does open access affect the usage of scholarly books? springernature.com 3 Foreword Springer Nature was created in 2015, but from our earliest days as Springer, Palgrave Macmillan and Nature, we have been publishing monographs and long-form research for some 175 years. The changing environment for book publishing has created both opportunities and challenges for researchers and their funders, for publishers, and for the wider community of readers and educators. As a publisher, we have championed new models of scholarship, introducing ebooks in 2006, and our first open access (OA) book in 2011.
    [Show full text]
  • Reflections on Software Architecture Linda Northrop SEI Fellow
    Reflections on Software Architecture Linda Northrop SEI Fellow Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 © 2016 Carnegie Mellon University Distribution Statement A: Approved for Public Release; Distribution is Unlimited Notices Copyright 2016 Carnegie Mellon University This material is based upon work funded and supported by the Department of Defense under Contract No. FA8721-05-C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the United States Department of Defense. NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. [Distribution Statement A] This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution. This material may be reproduced in its entirety, without modification, and freely distributed in written or electronic form without requesting formal permission. Permission is required for any other use. Requests for permission should be directed to the Software Engineering Institute at [email protected]. Carnegie Mellon® and CERT® are registered marks of Carnegie Mellon University.
    [Show full text]
  • Comparative Study on Agile Software Development Methodologies
    Global Journal of Computer Science and Technology Software & Data Engineering Volume 13 Issue 7 Version 1.0 Year 2013 Type: Double Blind Peer Reviewed International Research Journal Publisher: Global Journals Inc. (USA) Online ISSN: 0975-4172 & Print ISSN: 0975-4350 Comparative Study on Agile Software Development Method- ologies By A B M Moniruzzaman & Dr. Syed Akhter Hossain Daffodil International University, Bangladesh Abstract - Today‘s business environment is very much dynamic, and organizations are constantly changing their software requirements to adjust with new environment. They also demand for fast delivery of software products as well as for accepting changing requirements. In this aspect, traditional plan-driven developments fail to meet up these requirements. Though traditional software development methodologies, such as life cycle-based structured and object oriented approaches, continue to dominate the systems development few decades and much research has done in traditional methodologies, Agile software development brings its own set of novel challenges that must be addressed to satisfy the customer through early and continuous delivery of the valuable software. It‘s a set of software development methods based on iterative and incremental development process, where requirements and development evolve through collaboration between self-organizing, cross-functional teams that allows rapid delivery of high quality software to meet customer needs and also accommodate changes in the requirements. In this paper, we significantly indentify and describe the major factors, that Agile development approach improves software development process to meet the rapid changing business environments. We also provide a brief comparison of agile development methodologies with traditional systems development methodologies, and discuss current state of adopting agile methodologies.
    [Show full text]
  • Kruchten Frog Octopus JSS V6
    Paper submitted to the Journal of Software and Systems, July 2011, resubmitted November 2011. The frog and the octopus: a conceptual model of software development Philippe Kruchten University of British Columbia 2332 Main Mall Vancouver BC V6N2T9 Canada email: [email protected] phone: +1 (604) 827-5654 fax: +1 (604) 822-5949 Abstract We propose a conceptual model of software development that encompasses all approaches: traditional or agile, light and heavy, for large and small development efforts. The model identifies both the common aspects in all software development, i.e., elements found in some form or another in each and every software development project (Intent, Product, People, Work, Time, Quality, Risk, Cost, Value), as well as the variable part, i.e., the main factors that cause the very wide variations we can find in the software development world (Size, Age, Criticality, Architecture stability, Business model, Governance, Rate of change, Geographic distribution). We show how the model can be used as an explanatory theory of software development, as a tool for analysis of practices, techniques, processes, as the basis for curriculum design or for software process adoption and improvement, and to support empirical research on software development methods. This model is also proposed as a way to depolarize the debate on agile methods versus the rest-of-the-world: a unified model. Keywords: software development, conceptual model, ontology, method, software development process, software engineering, theory Visual abstract for JSS: !"#$%& !"#$%& '()*& '()*& Alternate visual abstract for JSS: Authorʼs bio: Philippe Kruchten is professor of software engineering at the University of British Columbia, Vancouver, Canada.
    [Show full text]
  • Disciplined Agile
    Disciplined Agile Jas Madhur and Scott Ambler Presentation for PMI Luxembourg November 22nd, 2016 - Chambre des Metiers, Kirchberg #pmiluxagile Agenda • Part 1 – Jas Madhur (Luxembourg) • Part 2 – Plan A - Scott Ambler (Toronto) • Part 2 – Plan B – Slides. No refunds. Free event. Even food! Sponsors. • agilepartner • Since 2004 architecting agile information systems • Don’t worry be AP! • Lux – Advisory • Since 2009 consulting company specialising in organisation and strategy Questions and comments use #pmiluxagile Part 1 - Jas Madhur – Who am I? • PMI Luxembourg – Director of Finance … 2017 + Sponsorship • Agile Practitioner / Methodologist • 1993 Iterative/Object Oriented Development (Canadian Air Traffic System) • 1997 Rational Unified Process (RUP) Development Team (IBM Rational Software) • 2004 Agile Vancouver – Dr.Philippe Kruchten • 2008 Agile Toronto – Scott Ambler • 2011 Luxembourg • AZUR ERP for Health Insurance Companies • SMEs • Agile RUP (Matisse) • PM / PMO • Write proposals and submit tenders EU institutions at infeurope • jasmadhur.blogspot.com - @jmadhur Who are you? Why are we here? • Audience • IT Project Managers • HR • Curious about what is all this ‘AGILE’ noise is about? • Know • Agile. Like teenage romance. Rampant and variable. Great experts. Let’s hope it’s safe. • Patterns and anti-patterns of agile and agility. • Do • How could the agile approach be useful throughout your organization? • Think • Being agile stimulates evolution and innovation. • Feel • Being agile and adaptive is engrained in our DNA. • It’s natural. The Context • Software/Systems Engineering • 1 Dimensional .. Waterfall .. DoD Mil-Spec 2167a • 2 Dimensional .. Iterative .. IBM Rational Unified Process (RUP) (1996) • Market Pressures of the “Internet Economy” • Small Teams • The Agile Movement • Rapid Delivery and Innovation • A Balanced Reliable Approach • Disciplined Agile DoD Mil-Spec 2167a (1989) Hardware (HW) Computer Software (CS) Unit (U) Component (C) Configuration Item (CI) Baselines WATERFALL 1.
    [Show full text]