Abstract
Looking back at the origins of agile software development we provide an overview of its unique blend of supple practices and vivid cultural facets that contrast so sharply with the plan-driven world of Waterfall methodologies. We discuss the iterative and incremental nature of agility and introduce a tool, agile charting, that can be used to facilitate communication within agile teams. Against this backdrop we introduce and compare the three methodologies (i.e., XP, Scrum and DSDM) used throughout this book to illustrate our application of agile risk management. We conclude with a glimpse at the state of affairs of agility today and at the management perspective on agile project management thereby setting the tone for the remainder of the book.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
Throughout this work when mentioning DSDM we will invariably be also referring to its project management cousin, AgilePM®, developed by the DSDM Consortium and accredited by the APMG International™.
- 2.
Throughout this book when we mention “Kanban” we usually mean just the board based technique. Kanban in the wider sense is, however, a methodology in its own right.
- 3.
Our timeline omits many significant events to which we refer the interested reader to (Agile Alliance 2013).
- 4.
The term Systems Development Lifecycle is also in widespread use.
- 5.
We remind the reader to refer to Appendix A for a definition of this and other agile techniques.
- 6.
Team sizes are consistently recommended to be in the range 7 \(\pm \) 2 (Miller 1956).
- 7.
Collaborative, Representative, Authorized, Committed and Knowledgeable.
- 8.
In the case of Evo a formal language, planguage, is even used to describe requirements and functional specifications!
- 9.
Though this term is often applied derogatorily by purists, it accurately reflects the reality that Scrum is often adapted to the circumstances of an enterprise.
- 10.
A further subdivision at the programme level may also apply for related projects that might benefit from such an organization.
- 11.
Designated as “project context” in Fig. 6 for reasons of simplicity.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2014 The Author(s)
About this chapter
Cite this chapter
Moran, A. (2014). Agile Software Development. In: Agile Risk Management. SpringerBriefs in Computer Science. Springer, Cham. https://doi.org/10.1007/978-3-319-05008-9_1
Download citation
DOI: https://doi.org/10.1007/978-3-319-05008-9_1
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-05007-2
Online ISBN: 978-3-319-05008-9
eBook Packages: Computer ScienceComputer Science (R0)