Part III Extreme programming, or XP, is a very valuable programming process for teamwork programming. It focuses on simplicity while achieving the goals of the customers. One of the best things about XP is the fact that the customer is part of the team so that the customers expectations are met every step of the way. While this is a good in the way that there is no hold time waiting to hear back from the customer when one more step is made, this is one of the things I see as being wrong with XP, as well. I think, even though it makes the job quicker (most of the time), it can hold things up and slow down the process because customers are constantly changing ideas. As they see the project coming together, they might see one feature that they like and then ask the programmer if they can implement something along those lines to complete a different task in the software. I think it is a great idea to constantly be testing software and getting customer feedback because it ensures
This is the end of the preview. Sign up
access the rest of the document.
This essay was uploaded on 04/17/2008 for the course CSC 402 taught by Professor Epstein during the Spring '08 term at West Chester.