eXtreme Programming basics

Sort of a talk I did at the first Bonn Agile Meetup (then known as the Bonn XP-meetup): http://bonnagile.blogspot.de/2011/01/announcing-bonn-xp-meetup.html

Transcript

1. Bonn XP-Meetup 21/2 – 2011 For more info, see http://twitter.com/bonnxp http://sites.google.com/site/bonnxp/
2. Why XP? After all... It's a one-man thing (Kent Beck) You have to swallow the whole pill It's called extreme (but it isn't) It “failed” at Chrysler (reference case) It's old, and it never *really* took off.
3. On the other hand.. @unclebobmartin: Agile is meaningless. [...] And XP is alive and well. Scrum is discolored by certification Lean is corrupted by the service sector Craftsmanship not business-oriented enough? @jasongorman: After 10 years of Agile, maybe we've come full circle back to the only complete Agile Software Development method - XP
4. For me.. XP crystallizes Agile From a feeling of common sense.. into a convincement toolkit • Why should we not worked with a full set scope? • Why should we not leave this testing to QA? • Why should we try pair programming? I know the reasons, but often they are hard to articulate.
5. The History of XP and KB • KB was mainly Smalltalk consultant/author • 1996: Chrysler – --> 2000 (decommissioned) • 1999: XP Explained • KB then focused on JUnit, TDD • 2005: XP Explained 2nd edt • JUnitMax, more consulting, startup
6. Contents of the book Pretty small book: 160 pages But a big reference list! 14 p. of annotated references (with why you should read them). Some philosophy, attitude. Open to ambiguity Focuses on people and business Not ignorant or isolated: Relates (indirectly) to systems thinking and Lean
7. Exploring XP Values Principles Practices • Sit Together • Whole Team • Informative Workspace • Energized Work • Pair Programming • Stories • Weekly Cycle • Quarterly Cycle • Slack • Ten-Minute Build • Continuous Integration • Test-First Programming • Incremental Design • Humanity • Economics • Mutual Benefit • Self Similarity • Improvement • Diversity • Reflection • Flow • Opportunity • Redundancy • Failure • Quality • Baby Steps • Accepted Responsibility • Communication • Simplicity • Feedback • Courage • Respect • Others
8. Exploring XP Corollary Practices • Real Customer Involvement • Incremental Deployment • Team Continuity • Shrinking Teams • Root-Cause Analysis • Shared Code • Code and Tests • Single Code Base • Daily Deployment • Negotiated Scope Contract • Pay-Per-Use The Whole XP Team • Testers • Interaction Designers • Architects • Project Managers • Product Managers • Executives • Technical Writers • Users • Programmers • Human Resources • Roles (not fixed)
9. Additional Chapters • Theory of Constraints • Planning: Managing Scope • Testing: Early, Often and Automated • Interview with an XP adopter • Scaling XP • Design: The Value of Time
10. Additional Chapters cont. • Creation Story (where XP came from) • Taylorism and Software • Toyota Production System • Offshore Development Multi-siting • Purity • Applying XP
11. Additional Chapters cont. • The Timeless Way of Programming Meta future hopes. • Community and XP You are here! • Conclusion
12. Slides/handouts prepared by @tfnico www.tfnico.com