Abstract
Adopting a new concept often proves harder than it seems at first. Adopting Agile is definitely a case in point. Although Agile is still relatively new, having been formally defined by a meeting of seventeen signatories in February 2001 in their “Manifesto for Agile Software Development,” it has gained significant adoption over the past decade.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
See Kent Beck, et al. "Manifesto for Agile Software Development," (2001), http://agilemanifesto.org .
- 2.
Actuation Consulting and Enterprise Agility, "The Study of Product Team Performance, 2012," http://www.actuationconsultingllc.com/whitepaper_request.php .
- 3.
Forrester-Dr. Dobb’s Global Developer Technographics Survey, Q3 2009.
- 4.
Joe M. Bohlen and George M. Beal, “The Diffusion Process”, Special Report No. 18, Agriculture Extension Service, Iowa State College, May 1957, 1:56–77.
- 5.
Geoffrey A. Moore, Crossing the Chasm (New York: Harper Business Essentials, 1991).
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2013 Mario E. Moreira
About this chapter
Cite this chapter
Moreira, M.E. (2013). Crossing the Agile Chasm. In: Being Agile. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-5840-7_2
Download citation
DOI: https://doi.org/10.1007/978-1-4302-5840-7_2
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-5839-1
Online ISBN: 978-1-4302-5840-7
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)