Integrating traditional and agile processes in the classroom

ABSTRACT

Teaching software engineering is difficult because the true benefits of a disciplined software process and the production of significant artifacts are most meaningful when programming-in-the-large, with varying levels of team experience in the context of a professional organization. Using the same techniques when programming-in-the-small can often lead to the students feeling that it is better to not use any process because the effort and tedium of producing artifacts is so great compared with the relatively simple task of writing the code for the target solution. This paper describes our solution, a curriculum that exposes the students to both lightweight traditional and lightweight agile processes. We describe two offerings of the class and conclude from the positive student feedback that we have found the correct balance.

REFERENCES

• 1: Kent Beck , Cynthia Andres, Extreme Programming Explained: Embrace Change (2nd Edition), Addison-Wesley Professional, 2004
• 2: Cockburn, A. Crystal Clear: A Human-Powered Methodology for Small Teams, Addison-Wesley Professional, 2004.
• 3: Richard Hundhausen, Working with Microsoft Visual Studio 2005 Team System, Microsoft Press, Redmond, WA, 2005
• 4: Ivar Jacobson, Object-oriented software engineering, ACM Press, New York, NY, 1991
• 5: Kessler, R. and Williams L. "If this is what it's really like, maybe I better major in English": Integrating Realism into a Sophomore Software Engineering Course. 29th Annual Frontiers in Education Conference, Vol 1, (Nov 1999), 12A4/12 - 12A4/16.
• 6: Nancy Mead , David Carter , Michael Lutz, The State of Software Engineering Education and Training, IEEE Software, v.14 n.6, p.22-25, November 1997 [doi>10.1109/MS.1997.636393]
• 7: Parker, G. Team Players and Teamwork, Jossey-Bass, 1990.
• 8: Laurie Williams , Robert Kessler, Pair Programming Illuminated, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2002

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

Additional Classification:
  K. Computing Milieux
  K.3 COMPUTERS AND EDUCATION
      K.3.2 Computer and Information Science Education

General Terms:
Human Factors

Keywords:
UML, agile, projects, software engineering education, teams