By Manfred Pürro
Extreme Programming XP Whats that? project Metholodgy ~ Scrum Iteration ~ Sprint Goals? how? technical social test first development test, test, test pair programming (1-3 weeks) "actually it's more a toolset...." (continous integration) All Code is Pair Programmed does not work in reality Alwin, tegonal a Communication, Simplicity, Feedback, Courage and Respect tegonal core architecture by hand, paper, uml -> scan wiki directly test, code analyze design test code per task ! organizational agile manifesto Planning Game Goals be honest decrease pressure on programmer plan cost transparency No Overtime! time team > 12 all on one table Client User Stories (Cards) priorisiert Developer Risk time per iteration Sort Prio Risk a User Story task task task Project Leader Task dev dev dev 1 day 2d 3d best gets task specialists factory? pair programming know how transfer no! all tasks distributed? White Board Simplicity Always the easyiest possible solution; straightforward refactoring, refactoring, refactoring not realistic <-> Scope a open iteration done , Martin Fowler build often client on every planning meeting goal full functional build after iteration ...for that iteration without them, xp does not work distribute tasks Fear developers hate clients requirements too boring complicated clients hate developers never finish not what i wanted don't understand openess fairness trust Thanks for Listening i i hope it wasn't too boring... Communication, Simplicity, Feedback, Courage and Respect refs... Links http://de.wikipedia.org/wiki/Extreme_programming http://chaosradio.ccc.de/cre028.html http://www.martinfowler.com/ http://www.frankwestphal.de/ExtremeProgramming.html http://www.extremeprogramming.org/
A quick overview of eXtreme Programming, assumes that you already know agile project methods like Scrum...