Using an Interaction Room for Digitalization Strategy Development (IR:digital)

This chapter describes how an Interaction Room is used in the early phases of digitalization initiatives in order to identify an organization’s digitalization potential and to identify candidates for concrete digitalization projects that should be pursued

  • PDF / 9,342,210 Bytes
  • 333 Pages / 453.543 x 683.15 pts Page_size
  • 101 Downloads / 170 Views

DOWNLOAD

REPORT


Tamed Agility Pragmatic Contracting and Collaboration in Agile Software Projects

Tamed Agility

Matthias Book Volker Gruhn Rüdiger Striemer •

Tamed Agility Pragmatic Contracting and Collaboration in Agile Software Projects

123

Matthias Book Faculty of Industrial Engineering, Mechanical Engineering and Computer Science University of Iceland Reykjavík Iceland

Rüdiger Striemer adesso AG Berlin Germany

Volker Gruhn paluno - The Ruhr Institute for Software Technology Universität Duisburg-Essen Essen Germany

ISBN 978-3-319-41476-8 DOI 10.1007/978-3-319-41478-2

ISBN 978-3-319-41478-2

(eBook)

Library of Congress Control Number: 2016944417 © Springer International Publishing Switzerland 2016 This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. 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. Printed on acid-free paper This Springer imprint is published by Springer Nature The registered company is Springer International Publishing AG Switzerland

Preface

Industrial software development is one of the major success stories of the twentieth century. Otherwise, software would not have been able to pervade other areas of life and business, established business models of entire industries would not have been swept away by digitalization, and the global success of Apple, Amazon, Google, Facebook, and eBay would not have been possible. Software engineering, i.e., the design of larger and larger software systems based on engineering principles, enabled the development of software systems that seemed impossible just a couple of years ago. Therefore, any kind of fundamental denial of this success story is downright absurd (Osterweil et al. 2008). This fact cannot be changed, not even by numerous studies on the alleged state of the software industry, which were in some cases prepared under the flimsiest of conditions, as exposed, e.g., by Eveleens and Verhoef (2010), Glass (2006), or Jørgensen and Moløkken-Østfold (2006). Yet, time and again, evidence is provided of projects that encounter difficulties— sometimes because the established so