Agile Software Development Best Practices for Large Software Develop

Software Development is moving towards a more agile and more flexible approach. It turns out that the traditional "waterfall" model is not supportive in an environment where technical, financial and strategic constraints are changing almost every day. But

  • PDF / 4,642,058 Bytes
  • 193 Pages / 461.242 x 679.135 pts Page_size
  • 95 Downloads / 233 Views

DOWNLOAD

REPORT


Best Practices for Large Software Development Projects

Agile Software Development

Thomas Stober

l

Uwe Hansmann

Agile Software Development Best Practices for Large Software Development Projects

Dr. Thomas Stober IBM Deutschland Research & Development GmbH Scho¨naicher Str. 220 71032 Bo¨blingen Germany [email protected]

Uwe Hansmann IBM Deutschland Research & Development GmbH Schönaicher Str. 220 71032 Böblingen Germany [email protected]

ISBN 978-3-540-70830-8 e-ISBN 978-3-540-70832-2 DOI 10.1007/978-3-540-70832-2 Springer Heidelberg Dordrecht London New York Library of Congress Control Number: 2009931706 # Springer-Verlag Berlin Heidelberg 2010 This work is subject to copyright. All rights are reserved, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilm or in any other way, and storage in data banks. Duplication of this publication or parts thereof is permitted only under the provisions of the German Copyright Law of September 9, 1965, in its current version, and permission for use must always be obtained from Springer. Violations are liable to prosecution under the German Copyright Law. The use of general descriptive names, registered names, trademarks, 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. Cover design: WMXDesign GmbH, Heidelberg, Germany Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com)

‘‘Life is what happens, when you are busy making other plans’’ (John Lennon)

Foreword

Live with Heart and Soul‐ or Plan your Life? Should you develop software in an agile manner or should you follow a detailed plan? Is your affection for the final result the primary motivation? Or is it rather the accurate processing of given steps listed in a project plan? I can assure you that dealing with these questions is almost like having two ideologies confronting each other. This makes it so difficult to establish agile software development within an organization as a principle, despite its remarkable successes. Most of my time, I am dealing with innovation of all kinds. The confrontation between structure and flexibility exists in this context as well. Big enterprises want to manage their innovation in a precisely structured way. Innovation should emerge in a predictable way and based on an omniscient master plan. However, enterprises are surprised to realize that innovation happens spontaneously. It emerges in most cases directly from the lifeblood that the innovators put into their endeavor. Google and Amazon are big and profitable companies, while still preserving the agile spirit of their early days. Nevertheless, other enterprises only rarely attempt to copy this mentality. There is no plan for this. It is quite depressing to know that the agile principle works better than traditional planni