The document discusses the history and principles of Extreme Programming (XP). It traces XP back to its origins on the Chrysler Comprehensive Compensation System project in 1993. The core values of XP like communication, simplicity, feedback and courage are explained. Fundamental XP practices like pair programming, planning game, test-driven development and continuous integration are also outlined. The document then considers how technology advances since XP was first developed have changed how software teams work. It concludes by questioning how "extreme" software teams are willing to be in exposing themselves to achieve success for their customers, teams and society.

1. Is XP still
eXtreme?
Kiro Harada
Attractor Inc.
XP Day Hanoi 2015

2. Extreme Programming

3. eXtreme?

4. eXtreme Biking

6. eXtreme
Ironing

7. eXtreme
Ironing

8. eXtreme Programming?

9. Extreme Programming :)
http://commons.wikimedia.org/wiki/File:Pair_Programming.jpg

10. Where did XP come from?

11. C3 Project
Chrysler Comprehensive Compensation System
Started 1993
Kent Beck joined 1996
Working Software in 1997

12. XP Values
Communication
Simplicity
Feedback
Courage
Respect

15. XP Practices
Pair Programming
Planning Game
Test-Driven Development
Whole Team

16. Continuous Integration
Refactoring
Small Releases

17. Coding Standards
Collective Code Ownership
Simple Design
System Metaphor

18. Sustainable Pace

19. In 1996
Windows95
Pentium Processor at 200MHz
4MB or 8MB of RAM
1GB of HDD
56K Modem Connection

20. In 2015
Windows 8.1 / OS X 10.10
Core i7 Processors (4 cores / 8 Threads) at 3GHz
8GB or 16GB RAM
2TB HDD or 512GB SSD
4G Wireless

21. How these advances
changed the way we work?

22. Like This?
Minority Report (2002)

23. What we do now
http://commons.wikimedia.org/wiki/File:Pair_Programming.jpg

24. (pause)
Estimated Delivery Time - 20 Min
Actual Delivery Time - Min.

25. Christopher
Alexander

26. The Timeless Way
of
Building

27. A Pattern
Language

28. "At the core... is the idea that people should design for
themselves their own houses, streets and communities.
This idea... comes simply from the observation that most
of the wonderful places of the world were not made by
architects but by the people".
Christopher Alexander et al.,
A Pattern Language, front bookflap

29. Pattern Language

30. Pattern Language for
Software Development?

31. Wiki Wiki Web

32. Hillside Group

33. Pattern Language of
Programs

36. Let’s see if there was no XP

37. Write thousands of lines of code without tests.

38. You cannot see the problems you made until the very
end.

39. You debug your code on a printed copy.

40. Preparing a server usually takes a week at fastest.

41. You can only integrate at the end of the project.
When your real project starts :P

42. Opposite Direction

43. Mob Programming

44. (pause)
Estimated Delivery Time - 35 Min
Actual Delivery Time - Min.

45. What is XP?
Extreme Programming (XP)
is about social change.
Extreme Programming Explained: Emblace Change (2nd Edition)
Kent Beck

46. Prepare for success.
Don’t protect yourself from success by holding back.
Do your best and then deal with the consequences.
That’s extreme.
You leave yourself exposed.
Extreme Programming Explained: Emblace Change (2nd Edition)
Kent Beck

47. It is about letting go of habits and patterns that were
adaptive in the past, but now get in the way off its
doing our best work.
It is about giving up defenses that protect us but
interfere with our productivity.
It may leave us feeling exposed.
Extreme Programming Explained: Emblace Change (2nd Edition)
Kent Beck

48. Are you ready
to have yourself
exposed for success?

49. XP assumes:
you see yourself a part of a team
you want to work together
change can be made inexpensive
you want to grow to improve skills and to improve your
relationships
you are willing to make changes to meet those goals

50. Expose yourself:
How extreme can you be
to deliver success to your customer, team and
society?