eXtreme Lessons Learned from eXtreme Programming 
Trevor Paradis
Project Manager
Stelligent Incorporated

Introduction:

As Agile development is gaining momentum and becoming the standard approach for developing software, teams are finding they have to adapt the XP approach for the specific needs of their development cycle. We have now come to a point where it is essential to share lessons learned in order to capture the best Agile practices.

Learning Objectives:

  • Hurdles and pitfalls to avoid when trying to implement XP
  • The essential nature of early feedback to the XP process
  • How to use code complexity, test coverage and other code metrics to assist the XP process
  • Useful tools that compliment the XP process
  • Parallel programming ~ when to use it and when its okay not to use it
  • How to fill the gap of developer tests in a mature code base

Outline:

  • Introduction of Agile and XP
    • Define Agile – Discussion of the Agile Manifesto and its real world application
    • Define XP - Introduction to and explanation of the methodology behind this disciplined approach to software development.
      • Customer satisfaction
      • Team Focus
      • Communication
      • Simplicity
      • Feedback
    • Clarify misconceptions about Agile and XP
  • Early feedback in the Agile process
    • Test coverage – Discussion around why testing is important and what are the different types of testing
    • Code complexity – Discussion of the role of identifying and reducing the complexity of code methods
    • Parallel programming – What is the reason for parallel programming
    • Test analysis tools – Ant, Maven, CVS, Subversion, JUnit/NUnit, TestNG, Selenium, Fit, CruiseControl, Cobertura, PMD, CheckStyle, FxCop
  • Filling the developer test gap
    • Attacking the complex areas of the code
    • New development
    • Defect fixes
  • Putting it all together
  • Conclusion
  • Question and Answer session

Biography:

Trevor Paradis is responsible for working with Stelligent 's clients during implementation engagements to develop and define goals, objectives, tasks and associating budgets and timelines. This work also includes implementing project plans, along with careful controls to ensure the plan is being managed according to plan. He has over 15 years of software development experience in Quality Assurance, Process Improvement and Project Management.