Agile Development

Agile Development

Fabrizio Fioravanti (Exitech, Italy)
Copyright: © 2006 |Pages: 13
DOI: 10.4018/978-1-59140-757-7.ch008
OnDemand PDF Download:
No Current Special Offers


The aim of this chapter is not to compare one Agile methodology against the other but to evidence the common factors that are behind each methodology that can be defined as an Agile one in order to give to the reader a basic understanding needed to better comprehend XP (described in Chapter X) and ADPD (described in Chapter XI and exploited in Chapters XII and XIII). Agile development and Agile methodologies have not been well considered in the past nor in the present by several people that have published papers (Briand, 2003; Rakitin, 2001) and others in different journals considering this approach too similar to hacking to be considered as a methodology for controlling and developing projects. For some project types, it is true, since safety-critical systems and real-time systems can be difficult to approach with Agile methodologies, as already stated in Chapter VII. On the other hand, several other authors and researchers have tried to consider something more — Agile development (paying particular attention to XP but considering Agile methodologies in a large sense) — and to evidence the strong points behind its approach (Beck, 1999, 2000; Boehm, 2002; Cockburn, 2001, 2001a; Paulk, 2001) and also the interaction of social issues with Agile software development (Cockburn, 1996; Highsmith, 2001).

Complete Chapter List

Search this Book: