Abstract
This is a report on an effort to bring the practices of the Extreme Programming methodology into a Software Design course. Two teams of 11 members followed many of those practices in developing their semester projects. We described the practices required of the development teams, those encouraged, and those that were not easily simulated. Near the end of the semester the students were asked to answer questions about how well each practice had served the process. Summaries and examples of their responses along with the instructor's observations are presented as an evaluation of this approach. The main conclusions are that pair programming is generally powerful and popular, and that it is difficult to make upper level students write tests prior to writing code. Suggestions for what might be done differently to better simulate the Extreme Programming methodology are included. The foremost suggestion is to teach a “test first” approach in all programming courses.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
