Empirical Findings in Agile Methods

  • Mikael Lindvall
  • Vic Basili
  • Barry Boehm
  • Patricia Costa
  • Kathleen Dangle
  • Forrest Shull
  • Roseanne Tesoriero
  • Laurie Williams
  • Marvin Zelkowitz
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2418)


In recent years, the use of, interest in, and controversy about Agile methodologies have realized dramatic growth. Anecdotal evidence is rising regarding the effectiveness of agile methodologies in certain environments and for specified projects. However, collection and analysis of empirical evidence of this effectiveness and classification of appropriate environments for Agile projects has not been conducted. Researchers from four institutions organized an eWorkshop to synchronously and virtually discuss and gather experiences and knowledge from eighteen Agile experts spread across the globe. These experts characterized Agile Methods and communicated experiences using these methods on small to very large teams. They discussed the importance of staffing Agile teams with highly skilled developers. They shared common success factors and identified warning signs of problems in Agile projects. These and other findings and heuristics gathered through this valuable exchange can be useful to researchers and to practitioners as they establish an experience base for better decision making.


Success Factor Large Team Agile Method Agile Software Development Daily Meeting 
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.
    Humphrey, W.S., A Discipline for Software Engineering. SEI Series in Software Engineering, ed. P. Freeman, Musa, John. 1995, Reading, Massachusetts: Addison Wesley Longman, Inc.Google Scholar
  2. 2.
    Highsmith, J., Agile Software Development Ecosystems. The Agile Software Development Series, ed. A. Cockburn and J. Highsmith. 2002, Boston, MA: Addison-Wesley.Google Scholar
  3. 3.
    Boehm, B., Get Ready for Agile Methods, with Care. IEEE Computer, 2002. 35(1): p. 64–69.Google Scholar
  4. 4.
    Basili, V.R. and A.J. Turner, Iterative Enhancement: A Practical Technique for Software Development. IEEE Transactions on Software Engineering, 1975. 1(4).Google Scholar
  5. 5.
    Cockburn, A., Agile Software Development. The Agile Software Development Series, ed. A. Cockburn and J. Highsmith. 2001, Reading, Massachusetts: Addison Wesley Longman.Google Scholar
  6. 6.
    Marchesi, M., et al., eds. Extreme Programming Perspectives. XP Series, ed. K. Beck. 2002, Addison Wesley: Boston.Google Scholar
  7. 7.
    Marchesi, M. and G. Succi, eds. Extreme Programming Examined. XP Series, ed. K. Beck. 2001, Addison Wesley: Boston.Google Scholar
  8. 8.
    Highsmith, J., Does Agility Work? Software Development, 2002. 10(6): p. 30–37.Google Scholar
  9. 9.
    Shull, F., et al. What We Have Learned about Fighting Defects. in International Software Metrics Symposium. 2002. Ottawa, Canada.Google Scholar
  10. 10.
    Basili, V.R., et al. Building an Experience Base for Software Engineering: A Report on the first CeBASE eWorkshop. in Profes (Product Focused Software Process Improvement). 2001.Google Scholar
  11. 11.
    Highsmith, J. and A. Cockburn, Gile Software Development: The Business of Innovation. IEEE Computer, 2001. 34(12).Google Scholar
  12. 12.
    Cockburn, A. and J. Highsmith, Agile Software Development: The People Factor. IEEE Computer, 2001. 34(11).Google Scholar
  13. 13.
    Beck, K., et al., The Agile Manifesto. 2001: p.
  14. 14.
    Rakitin, S., Manifesto Elicits Cynicism. IEEE Computer, 2001. 34(12).Google Scholar
  15. 15.
    Beck, K., Extreme Programming Explained: Embrace Change. 2000, Reading, Massachusetts: Addison-Wesley.Google Scholar
  16. 16.
    Auer, K. and R. Miller, XP Applied. 2001, Reading, Massachusetts: Addison Wesley.Google Scholar
  17. 17.
    Jeffries, R., A. Anderson, and C. Hendrickson, Extreme Programming Installed. The XP Series, ed. K. Beck. 2001, Upper Saddle River, NJ: Addison Wesley.Google Scholar
  18. 18.
    Schwaber, K. and M. Beedle, Agile Software Development with SCRUM. 2002: Prentice-Hall.Google Scholar
  19. 19.
    Coad, P., J. deLuca, and E. Lefebvre, Java Modeling in Color with UML. 1999: Prentice Hall.Google Scholar
  20. 20.
    Stapleton, J., DSDM: The Method in Practice. 1997: Addison Wesley Longman.Google Scholar
  21. 21.
    Ambler, S.W., Agile Modeling. 2002: John Wiley and Sons.Google Scholar
  22. 22.
    Pfleeger, S.L., Software Engineering: Theory and Practice. 1998, Upper Saddle River, NJ: Prentice Hall. 1–44.Google Scholar
  23. 23.
    Williams, L., et al., Strengthening the Case for Pair-Programming, in IEEE Software. 2000. p. 19–25.Google Scholar
  24. 24.
    Palmieri, D., Knowledge Management through Pair Programming, in Computer Science. 2002, North Carolina State University: Raleigh, NC.Google Scholar
  25. 25.
    Fowler, M., et al., Refactoring: Improving the Design of Existing Code. 1999, Reading, Massachusetts: Addison Wesley.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2002

Authors and Affiliations

  • Mikael Lindvall
    • 1
  • Vic Basili
    • 1
    • 4
  • Barry Boehm
    • 3
  • Patricia Costa
    • 1
  • Kathleen Dangle
    • 1
  • Forrest Shull
    • 1
  • Roseanne Tesoriero
    • 1
  • Laurie Williams
    • 2
  • Marvin Zelkowitz
    • 1
    • 4
  1. 1.Fraunhofer Center for Experimental Software EngineeringMaryland
  2. 2.North Carolina State UniversityUSA
  3. 3.Center for Software EngineeringUniversity of Southern CaliforniaUSA
  4. 4.Empirical Software Engineering GroupUniversity of MarylandUSA

Personalised recommendations