Advertisement

An Ideal Process Model for Agile Methods

  • Marcello Visconti
  • Curtis R. Cook
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3009)

Abstract

We present a software process model that can be effectively applied to the agile software development context. Our approach builds an ideal agile software process model starting from the principles established by the agile community in what is known as the Agile Manifesto. The practices defined by the ideal model can be used to assess the various agile methods to determine any missing or under-emphasized practices or practices needing improvement. We compared the practices defined for two of the most popular agile methods (XP and Scrum) with the ideal model and found that these two methods do not explicitly address in an organized way all the principles in the Manifesto. While these approaches do include practices to regularly review the effectiveness of the particular method and tune the method’s behavior accordingly for a particular product being developed, they lack explicit practices to perform a retrospective focusing on the process, with the goal of adapting and improving the method itself and its future application. We propose a simple practice that could be added to these methods that would address this apparent oversight. This practice would also provide the ability to leverage what was learned from previous projects to the future projects,. We believe the proposed ideal model is complete, flexible, and can be used to assess and propose simple process improvement actions for agile methods. We also point out some open questions about the best way to share the knowledge gained from retrospectives and to do end of project reviews.

Keywords

Agile methods process models assessment XP Scrum 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Alliance, A.: Manifesto for agile software development (2001), http://agilemanifesto.org/
  2. 2.
    Alliance, A. (2001), http://www.agilealliance.com/
  3. 3.
    Beck, K.: Extreme Programming Explained: Embrace Change. Longman Higher Education (2000)Google Scholar
  4. 4.
    Boehm, B.: Get ready for agile methods, with care. IEEE Computer 35(1), 64–69 (2002)Google Scholar
  5. 5.
    Cockburn, A.: Agile Software Development. Addison-Wesley, Reading (2002)Google Scholar
  6. 6.
    Highsmith, J.: What is agile software development? CrossTalk 15(10), 4–9 (2002)Google Scholar
  7. 7.
    What is Extreme Programming (2002), http://www.xprogramming.com/xpmag/whatisxp.htm/
  8. 8.
    Kane, D., Ornburn, S.: Agile development: weed or wildflower? CrossTalk 15(10), 30 (2002)Google Scholar
  9. 9.
    Paulk, M.: Extreme Programming from a CMM perspective. IEEE Software 18(6), 19–26 (2001)CrossRefGoogle Scholar
  10. 10.
    Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice-Hall, Englewood Cliffs (2002)Google Scholar
  11. 11.
    Turner, R.: Agile development: good process or bad attitude? In: Oivo, M., Komi-Sirviö, S. (eds.) PROFES 2002. LNCS, vol. 2559, pp. 134–144. Springer, Heidelberg (2002)CrossRefGoogle Scholar
  12. 12.
    Visconti, M., Cook, C.: A meta-model framework for software process modeling. In: Oivo, M., Komi-Sirviö, S. (eds.) PROFES 2002. LNCS, vol. 2559, pp. 532–545. Springer, Heidelberg (2002)CrossRefGoogle Scholar
  13. 13.
    Wendorff, P.: Organisational culture in agile software development. In: Oivo, M., Komi-Sirviö, S. (eds.) PROFES 2002. LNCS, vol. 2559, pp. 145–157. Springer, Heidelberg (2002)CrossRefGoogle Scholar
  14. 14.
  15. 15.
    Miller, R.: Demystifying Extreme Programming: “XP distilled” revisited, Part 1 (2002), http://www-106.ibm.com/developerworks/java/library/j-xp0813/
  16. 16.
    Fowler, M.: The new methodology (2003), http://www.martinfowler.com/articles/newMethodology.html
  17. 17.
    Kerth, N.: Project retrospectives: a handbook for team reviews. Dorset House, New York (2001)Google Scholar
  18. 18.
    Rising, L.: Using patterns to improve process improvement: the argument for a resident minstrel. In: JAOO 2002 Java Technology and Object-Oriented Software Engineering, Aarhus, Denmark (2002)Google Scholar
  19. 19.
    Collins, C., Miller, R.: Adaptation: XP Style. In: Extreme Programming XP 2001, Cagliari, Sardinia, Italy (2001)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Marcello Visconti
    • 1
  • Curtis R. Cook
    • 2
  1. 1.Departamento de InformáticaUniversidad Técnica Federico Santa MaríaValparaísoChile
  2. 2.Computer Science DepartmentOregon State UniversityCorvallisUSA

Personalised recommendations