• NotesForXpQaPresentation

I've been asked to present XP to the Utah Quality Assurance group, they want to "keep up with what's current." Here is where I'm (attempting to) organize my thoughts for the presentation, which will be in either January 2003 or March 2003 (TBD). I have roughly 45 minutes, an audience of 20 to 40.

Outline:

• Intro (5 min)
  • (show of hands) How many have done XP?
  • What will you get from this presentation?
  • Be thinking of questions
• Presentation (15 min)
  • Impact of XP (impact on INDUSTRY)
  • Experiential Learning
  • Photo documentary of team using XP
  • Interviews with QA staff on XP team
• Demo (5 min)
  • Pair programming
  • Test first programming
  • Running acceptance tests
  • 3x5 cards
• Wrap up (5 min)
  • Implementing XP (impact on ME)
  • Where to find out more

• Question & Answer (15 min)

Things I'd like to fit in but are lower priority:

• Pass out cards for writing down questions
• Combination of technical roles, separation of business roles
• The testing practices of XP
• Cost of change
• Mentality of scarcity/Mentality of sufficiency
• Interviews are short video clips
• White board session in demo

• Implementing XP - common pitfalls (WatchOutForThat)

• "Selling" XP
• Spiffs

Unit tests vs Acceptance Tests

• (Automated) Unit tests point to the exact location in the code where the bug is
• (Automated) Unit Tests test everything that could possibly break
• (Automated) Acceptance tests point to the exact feature where the bug is
• (Automated) Acceptance tests test what you care about working