Collaborative Quality Assurance in Information Systems Development T
This book examines how and why collaborative quality assurance techniques, particularly pair programming and peer code review, affect group cognition and software quality in agile software development teams. Prior research on these extremely popular but a
- PDF / 3,118,164 Bytes
- 258 Pages / 439.43 x 683.15 pts Page_size
- 43 Downloads / 273 Views
Kai Spohrer
Collaborative Quality Assurance in Information Systems Development The Interaction of Software Development Techniques and Team Cognition
Progress in IS
More information about this series at http://www.springer.com/series/10440
Kai Spohrer
Collaborative Quality Assurance in Information Systems Development The Interaction of Software Development Techniques and Team Cognition
123
Kai Spohrer University of Mannheim Mannheim, Germany
This book is based on a doctoral thesis successfully defended at the Business School of the University of Mannheim. ISSN 2196-8705 Progress in IS ISBN 978-3-319-25161-5 DOI 10.1007/978-3-319-25163-9
ISSN 2196-8713 (electronic) ISBN 978-3-319-25163-9 (eBook)
Library of Congress Control Number: 2015956833 Springer Cham Heidelberg New York Dordrecht London © 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 Springer International Publishing AG Switzerland is part of Springer Science+Business Media (www.springer.com)
Foreword
For more than a decade, agile software development with its principles, methods, and techniques has been challenging the traditional, plan-driven, and mechanistic ways of developing software. In fact, it has led to an enormous change in the way how software is developed in industry today, and nearly all software companies are cherry-picking one or the other agile element in order to improve in their daily routines. In the scholarly literature, however, this important trend is heavily underrepresented and only little understood, leaving us with open questions. In particular, there is little evidence whether and how agile practices actually result in beneficial development outcomes. This lack of research may well be rooted in the heterogeneity, fuzziness, and variability of aspects that are subsumed under the label “agile software development” in industry. Therefore, it appears reasonable to unveil the drivers of agile software dev
Data Loading...
