An introduction to XP and Agile for SyXPAC

1. An Introduction to XP and Agile Jason Yip, [email_address] http:// www.thoughtworks.com

2. What’s the problem?

3. Software takes too long , costs too much , and requires too many people

4. The plan is fantasy… and we don’t learn this until it’s too late

5. We’re wasting our lives doing things that don’t matter

6. Why do the problems occur?

7. We only have one opportunity to decide, so we ask for everything… and we waste time building what we don’t actually need

8. How often are features used?

9. We defer concrete validation until it’s too late to respond

10. We punish raising problems

11. We have too much specialisation

12. We have a “not my problem” culture

13. What do we want instead?

14. Any feature, any order, one at a time

15. Highest productivity, highest quality, lowest cost, highest morale

16. Real visibility about what’s happening

17. Learn about problems as early as possible

18. Less administrative work; more value-adding work

19. XP and Agile as a solution

20. Philosophy, Process, People, Problem Solving Problem Solving People Process Philosophy

22. Software is too damned hard to spend time on things that don't matter. So, starting over from scratch, what are we absolutely certain matters? … Listening, Testing, Coding, Designing. That's all there is to software. Anyone who tells you different is selling something. Kent Beck, http://www.c2.com/cgi/wiki?ExtremeProgramming

23. Process: Just-in-Time

26. Timeboxed iterative-incremental development

27. Small Releases http://www.slideshare.net/cching/rocks-into-gold-by-clarke-ching-presentation

28. Process: Built-in Quality

31. Continuous Integration

32. Pair Programming

33. People: T-shaped people

34. People: Whole Team http://www.think-box.co.uk/blog/2007/11/theres-hole-in-your-side-of-boat.html

35. Authority vs Responsibility

39. Why should we believe this will work?

41. Don’t believe… think for yourself… try something… see what happens… adjust