Extreme Programming (Xp)
Agile projects are similar to traditional projects. “You still must define and initiate the project, plan for the project, execute the plan, and monitor and control the results” ("ccspace.com," 2011). How these steps are accomplished is different and therefore, the Agile project manager must adapt his approach. One agile software engineering method is Extreme Programming or XP.
XP is a collection of values, principles and practices designed to rapidly create highquality software that provides the maximum value for the customer as quickly as possible. It is called extreme or XP because it takes commonsense principles and practices to extreme levels, changing the way programmers work. It is a lightweight methodology suitable for small-tomedium-sized teams developing software that are faced with vague or rapidly changing requirements. XP began in the late 90’s. Ward Cunningham, Kent Beck, and Ron Jeffries are considered the originators. It is based on Beck’s years of software development using objectoriented programming (Brewer, 2001). “Beck and Jeffries worked together at Chrysler Corporation on the first large-scale project to use XP” ("Software development methodologies:," n.d., para. 2). Since the publishing in 1999 of Extreme Programming Explained by Beck, more publicity has been given to XP as is evident by an increase in books, papers, conferences and web sites.
Beck (2000) gives examples of taking well-known software development practices to extremes. By using pair programming, code reviews are continual, through unit testing and functional testing, testing is continual, integration is continuous by integrating and test several times a day, and considering short iterations, XP makes the iterations very short, minutes and hours vs., weeks and months and years (Beck, 2000).
XP has with five values: communication, feedback, simplicity, courage, and respect. These values are expanded into fourteen principles and again into practices. These practices are
XP is a collection of values, principles and practices designed to rapidly create highquality software that provides the maximum value for the customer as quickly as possible. It is called extreme or XP because it takes commonsense principles and practices to extreme levels, changing the way programmers work. It is a lightweight methodology suitable for small-tomedium-sized teams developing software that are faced with vague or rapidly changing requirements. XP began in the late 90’s. Ward Cunningham, Kent Beck, and Ron Jeffries are considered the originators. It is based on Beck’s years of software development using objectoriented programming (Brewer, 2001). “Beck and Jeffries worked together at Chrysler Corporation on the first large-scale project to use XP” ("Software development methodologies:," n.d., para. 2). Since the publishing in 1999 of Extreme Programming Explained by Beck, more publicity has been given to XP as is evident by an increase in books, papers, conferences and web sites.
Beck (2000) gives examples of taking well-known software development practices to extremes. By using pair programming, code reviews are continual, through unit testing and functional testing, testing is continual, integration is continuous by integrating and test several times a day, and considering short iterations, XP makes the iterations very short, minutes and hours vs., weeks and months and years (Beck, 2000).
XP has with five values: communication, feedback, simplicity, courage, and respect. These values are expanded into fourteen principles and again into practices. These practices are
References: Beck, K. (2000). Extreme programming explained, embrace change. Addison-Wesley Professional. Brewer, J. (2001). Jera design. Retrieved from http://www.jera.com/techinfo/xpfaq.html ccspace.com. (2011). Retrieved from http://www.ccpace.com/resources/documents/agileprojectmanagement.pdf Goodpasture, J. C. (2010). Project management the agile way: Making it work in the enterprise. Fort Lauderdale, FL: J. Ross Publishing, Inc. Shore, J. (2007, DECEMBER 13). Scrum and xp practices: Cross reference. Retrieved from http://www.jamesshore.com/Blog/Scrum-XP-Practices-Cross-Reference.html Software development is a team sport!. (2007, JULY 25). Retrieved from http://blogs.msdn.com/b/aridle/archive/2007/07/25/definition-iterative-and-incrementaldevelopment.aspx Software development methodologies: extreme programming (xp). (n.d.). Retrieved from http://cs.smu.ca/~porter/csc/465/notes/sdm_xp.html