: Tuesday
A Simple Model of Agile Software Processes - or - Extreme Programming Annealed
Sunrise
Tuesday, 10:30, 1 hour 30 minutes
| 7 | · | 8 | · | 9 | · | 10 | · | 11 | · | 12 | · | 13 | · | 14 | · | 15 | · | 16 | · | 17 | · | 18 | · | 19 | · | 20 | · | 21 |
Glenn Vanderburg, Countrywide Financial
The essay begins:
"If you built a piece of software that was as tightly coupled as Extreme Programming, you'd be fired." It was late 1999, and I was sitting at lunch with Pragmatic Dave Thomas and the rest of the North Texas XP interest group. It's not unusual for Dave to make provocative statements like that, but this time I was dumbstruck [...] He was right. The same characteristic that I appreciated in XP, I would decry in a software design.
In his essay, Glenn tackles various questions: Are the interdependencies between Extreme Programming's various practices bad? If not, what makes coupling in a process different from coupling in a product? And can understanding the nature of XP's coupling help us tailor software processes?
