1. eXtreme Programming Development Adrian Williamson People, Technology and People and Technology Consultant

2. Why? What? Who? When? So what … Summary Real eXtreme Programming

3. GT-X7 started in 1999 500,000 lines of Java by 2005 Modular but not re- factored Tested but not TDD Why? (1 of 2)

4. Neil decided to do something about it … Why? (2 of 2) Support 2004 Support 2005

5. Transformation required! Stop the world I want to get off! What? (1 of 9)

6. Read the books, browse the web What? (2 of 9)

7. XP Practices What? (3 of 9) The Planning Process (Planning Game) XP "customer” defines business value of features, cost estimates from programmers. Metaphor A common "system of names" and description that guides development. Simple Design The simplest program for current requirements. Little building "for the future”. Testing Constant Software Validation: Test Driven development; Customer acceptance tests. Refactoring Keep software clean: without duplication, high communication, simple, yet complete. Pair Programming Two programmers working together at one machine.

8. XP Practices What? (4 of 9) Collective Ownership All the code belongs to all the programmers. Changes without delay. Continuous Integration XP teams integrate and build the software system multiple times per day. 40-hour Week Tired programmers make more mistakes. Stay fresh, healthy, and effective. On-site Customer The dedicated individual empowered to set requirements, priorities, and answer questions. Coding Standard All the programmers need to write the code in the same way.

9. XP Principles - Fundamental What? (5 of 9) Rapid Feedback Assume Simplicity Incremental Change Embracing Change Quality Work

10. XP Principles - Further What? (6 of 9) Teach Learning Small Initial Investment Play to Win Concrete Experiments Open, honest Communication Work with people's instincts Accepted Responsibility Local Adaptation Travel Light Honest Measurement

11. Phone the consultants What? (7 of 9)

12. Support costs Lost development opportunity Product Quality Company and Product image Staff Predictability Method Build a business case What? (8 of 9)

13. Pilot.NET ciboodle Mobile Client Prepare Train team leads Workshops for team leads Choose a date Train developers Start! Implementation Plan What? (9 of 9)

14. Business Quiet Projects Quiet and Within Envelope Team Building Complete Team Stable Test Team Established Support team LEAN Kaizen September 2005! Happenstance When

15. eXtreme Programming So What? (1 of 5)

16. September 2005! So What? (2 of 5)

17. Planning 6 week cycles Teams Support, Core, Point, New Features, Strategic, Test, Docs Reporting Velocities, test coverage, defect rates Balanced Scorecard Waiting … Operation So What? (3 of 5)

18. BCS Awards 2006 Best young developer medal– Mobile team Project medal – BASCO mobile livestock tracking Prizes !! So What? (4 of 5)

19. eXtreme Ironing! So What? (5 of 5)

20. Thank You! - Any Questions? Adrian Williamson