Towards a Generic Model for Agile Processes

  • Anne Fuller
  • Peter Croll
Conference paper


The development of the information systems software typically follows standard Software Engineering (SE) practices. SE is a discipline founded on improving development methods to eliminate or mitigate the many risks associated with software projects1 and traditional SE methodologies have generally been classified as following a particular process model e.g. a Waterfall, Spiral or the V process model.2 This ability to apply a particular process model to a method has enabled researchers to theorize about methods in a generic sense and allowed the results of research centered on a particular method to be extrapolated to other methods fitting the same model.


Shared Vision Agile Method Customer Involvement Agile Development Agile Software Development 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Tom Roberts, Why Can’t We Implement This SDM? IEEE Software, Nov/Dec, 70–75 (1999)Google Scholar
  2. 2.
    Bob Hughes and Mark Cotterell, Software Project Management,3rd Edition, (McGraw Hill, 2002)Google Scholar
  3. 3.
    A. Fuller, P. Croll and O. Garcia, Why Software engineering is riskier than ever. Proceedings of the 2nd Asia, Pacific Conference on Quality Software (APAQS 2001 ). (2001)Google Scholar
  4. 4.
    S. Rakitin, Manifesto Elicits Cynicism, Computer, Dec. 2001, 4 (2001)Google Scholar
  5. 5.
    Mark C. Paulk, Extreme Programming from a CMM Perspective. IEEE Software 18 (6): 19–26 (2001)CrossRefGoogle Scholar
  6. 6.
    Martin Fowler, The New Methodology, (February, 2003) originally published as “Put Your Processes on a Diet,” Software Development,vol. 8, no. 12, Dec. 2000
  7. 7.
    S. Thomas, An Agile Comparison (December, 2002)
  8. 8.
    Eric Poinsignon, Introduction to Agile Method Movement, CERN-CNL-2002–002, Vol. XXXVII, issue no 2, (February, 2003 )
  9. 9.
    Murdoch McTaggart, RADical Software Development, Application Development Advisor, Nov-Dec 2001, (2001)
  10. 10.
    James Martin, Rapid Application Development,(Macmillan Publishing Co.,1991)Google Scholar
  11. 11.
    DSDM Consortium, History of DSDM (February, 2003)
  12. 12.
    Alan Zeichick, eXtreme Programming: Developing Agility with Intel Processors and Development Tools, (February, 2003)
  13. 13.
    CASEMaker Inc., What is RAD? (October, 2002 ) Google Scholar
  14. 14.
    Paul Beynon-Davies, Rapid Application Development (RAD), (February 2003 )
  15. 15.
    Jim Highsmith, History: The Agile Manifesto, (2001)Google Scholar
  16. 16.
    P. Abramsson, O. Salo, J. Ronkainen and J. Warsta, Agile Software Development Methods: Review and Analysis, Espoo 2002, (VTT Publications 478, 2002 )Google Scholar
  17. 17.
    Fraunhofer USA, Summary of the First workshop on Agile Methods, (2002)Google Scholar
  18. 18.
    M. Cohn and K. Schwaber The Need for Agile Project Management, Agile Times Newsletter, 1 /1, 10–12 (2003)Google Scholar
  19. 19.
    The Online Dictionary, http://dictionary.reference.comGoogle Scholar
  20. 20.
    A. Cockburn, Agile Software Development (Addison Wesley 2002 )Google Scholar
  21. 21.
    Don Wells, What is Extreme Programming? (February, 2003 )
  22. 22.
    Kent Beck and Martin Fowler, Planning Extreme Programming,(Addison Wesley, 2001)Google Scholar
  23. 23.
    M. Lippert and S. Roock, Adapting XP to Complex Applicatoin Domains. ESEC/FSE 2001, Proceedings of Joint 8th European Software Engineering Conference (ESEC) and 9th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-9) (2001)Google Scholar
  24. 24.
    J. Pelrine, Modelling infection scenarios — a fixed price eXtreme Programming success story, OOPSLA 2000, 23–24 (2000)Google Scholar
  25. 25.
    Bob Martin, Rigorous refactoring or BFUD, Agile Times Newsletter,1/1, 6 (2003)Google Scholar
  26. 26.
    B. Boehm, Get Ready for Agile Methods, with Care, IEEE Computer, Vol. 35, No. 1, 64–69 (2002)CrossRefGoogle Scholar
  27. 27.
    M. J. Carr, S. L. Konda, I. Monarch, F. C Ulrich. and C. F. Walker, Taxonomy-Based Risk Identification, Software Engineering Institute Technical Report, CMU/SEI-TR-6, ESC-TR-93–183 (1993)Google Scholar

Copyright information

© Springer Science+Business Media New York 2004

Authors and Affiliations

  • Anne Fuller
  • Peter Croll
    • 1
  1. 1.University of WollongongWollongongAustralia

Personalised recommendations