Abstract
This paper will contrast two software development projects – both addressing exactly the same problem – in the Boeing Commercial Airplane Company Electrical design organization. The first project used a traditional ’heavy-weight’ software development methodology, invested 60 man-years, and failed. The second project used a agile development approach, invested four man-years, and continues to be dramatically successful. Both projects addressed a paradigm-shift in the business process used to design and integrate electrical wiring in Boeing airplanes. This paper presents a recipe for success for an agile project in a non-agile world. It covers specific real-world lessons learned, and discusses the circumstances under which agile methods can be exceptionally effective and successful. It also points out where agile is not effective, or where the agile advantage can become a disadvantage.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2003 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Bedoll, R. (2003). A Tail of Two Projects: How ‘Agile’ Methods Succeeded After ‘Traditional’ Methods Had Failed in a Critical System-Development Project. In: Maurer, F., Wells, D. (eds) Extreme Programming and Agile Methods - XP/Agile Universe 2003. XP/Agile Universe 2003. Lecture Notes in Computer Science, vol 2753. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-45122-8_4
Download citation
DOI: https://doi.org/10.1007/978-3-540-45122-8_4
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-40662-4
Online ISBN: 978-3-540-45122-8
eBook Packages: Springer Book Archive