
|
Contents |
Extreme Programming
is the mostly widely used Agile methodology to date. Originally formulated by
Kent Beck with collaborators such as Ron Jefferies and Martin Fowler, XP
consists of approximately twelve interconnected practices, making it the most
well-defined agile process. It has been adopted by development groups around
the world in a variety of different companies, inspired as series of books
published by Addison Wesley, and is the subject of various conferences around
the world. The
twelve practices of XP are:
XP is founded
around small releases (approximately six months) with iteratations of two
weeks during which developers implement User Stories -- program features
specified jointly by customer and developer. Customer collaboration and tight
feedback loops are paramount to XP, where the customer is involved in
planning and is also on hand to answer developer questions in order to
produce a piece of software closely tailored to the users' needs.The emphasis
on testing, such as customer acceptance tests, pair programming, and
test-driven development, result in production code of higher quality and more
reliability. The robustness of XP combined with its lightweight approach to
the software process and substantial knowledge base has made it the most
popular Agile methodology with practitioners in every domain of software
engineering.
Books: Ambler, Scott and Ron Jeffries, Agile Modeling: Effective Practices for Extreme Programming and the
Unified Process, John Wiley & Sons, 2002. Aslets, D., G. Miller, and M.
Novak, a Practical Guide to eXtreme
Programming, Prentice Hall, 2002. Auer, K. and R. Miller, Extreme Programming Applied, Addison Wesley, 2002. Baird, S., Sams
Teach Yourself Extreme Programming in 24 Hours, Sams, 2002. Beck, K., Extreme Programming
Explained: Embrace Change, Addison Wesley, 2000. Beck, K. and M. Fowler, Planning eXtreme Programming, Addison Wesley, 2001. Crispin, L. and T. House, Testing Extreme Programming, Addison Wesley, 2002. Jeffries, R., A. Anderson, and C. Hendrickson Extreme Programming Installed, Addison
Wesley, 2001. McBreen, P. Questioning
Extreme Programming, Addison Wesley, 2002. Newkirk, J. and R. Martin, Extreme Programming in
Practice, Addison Wesley, 2001. Succi, Giancarlo and M. Marchesi, Extreme Programming Examined, Addison Wesley, 2001. Succi, G., J.D. Wells, L. Williams, and M. Marchesi, Extreme Programming Persepctives,
Addison Wesley, 2002. Wake, W. Extreme
Programming Explored, Addison Wesley, 2001. Wallace, D., Web
Sites/Web Pages: Wiki
Extreme Programming Roadmap The XP
Exchange (in English and German) Papers: Beck, K., “Embracing change with
Extreme Programming”, IEEE Computer, Vol. 32, Issue 10, October 1999 pages
70-77. Glass, R.L., “Extreme programming:
the good, the bad, and the bottom line”, IEEE Softawre, Vol. 18, Issue 6,
Nov/Dec 2001, pages 112, 111. Grenning, J., “Launching Extreme
Programming at a Process-Intensive Company”, IEEE Software, Nov/Dec 2001. Maurer, F. and S. Martel, “Extreme
programming. Rapid development for Web-based applications”, IEEE Internet
Computer, Jan/Feb 2002, pages 86-90. Murru, O., R. Deias and G.
Mugheddu, “Assessing XP at a European Internet Company”, IEEE Software, Vol.
20, No. 3, May/June 2003, pages 37-43. Paulk, M., “Extreme Programming
from a CMM Perspective”, IEEE Software, Nov/Dec 2001. Rasmusson, J., “Introducing XP
into greenfield Projects: Lessons Learned”, IEEE Software, Vol. 20, No. 3,
May/June 2003, pages 21-28. Schuh, Peter, Recovery,
“Redemption and Extreme Programming”, IEEE Software, Nov/Dec 2001. Strigel, W. “Reports from the
field – using extreme programmingand other experiences”, IEEE Software,
Nov/Dec 2001, pages 17-18. Images on this page taken from extremeprogramming.org for
educational and informational purposes only. |