1. eXtreme Programming and Open Source engineering paradigm A comparison sankarshan@softhome.net

2. Slides and paper to be available at the iLUG-Calcutta website www.ilug-cal.org

3. Introduction Cross organisational and geographical collaboration and co-operative effort Need to implement an “agile” distributed methodology Comparison of the 2 paradigms with respect to common grounds and conflicts

4. eXtreme Programming an “agile” software engineering methodology defined by Kent Beck in the early ’90s software “best practices” taken to the eXtreme rapid response to requirement changes small to medium sized developer teams

5. eXtreme Programming Four basic values Communication Feedback Simplicity Courage

6. eXtreme “Best Practices” the planning game small iterative releases metaphor testing simple design refactoring

7. eXtreme “Best Practices” Pair Programming Collective ownership Continuous integration On-site customer Coding standards 40-hour week

8. OpenSource paradigm original roots in the hacker culture of the early 1960s considerable success in projects incl the Linux Kernel, Apache webserver, Mozilla browser etc Source code is shared

9. OpenSource paradigm provides source code that is allowed to be studied, modified and redistributed enforced by software licensing policy not a defined ‘standard’ methodology possesses unique character and values

10. OpenSource Practices distributed development model shared code small releases continuous integration code reuse coding standards

11. Areas of overlap

12. Areas of Conflict

13. Reflections Common values: Communication Feedback Simplicity “The way programmers like to work” Strong XP and OS communities

14. References Kent Beck: ‘eXtreme Programming explained - Embrace change’ ISBN: 0201616416 K Beck, M Fowler: ‘Planning Extreme Programming’ ISBN: 0201710919 E S. Raymond, B Young: ‘The Cathedral and the Bazaar’ ISBN: 0596001088 ‘Open Sources: Voices from the Open Source Revolution’ ISBN: 1565925823

15. XP practices