Lightweight Software Methodologies eXtreme Programming XP

1
Lightweight Software MethodologieseXtreme
Programming (XP)

• 11/26/2002
• Shawn Cooper

2
What is XP?

• Deliberate and disciplined approach to software
  development developed by Kent Beck
• Lightweight methodology for rapid development

3
Waterfall method
4
Iterative
5
Why Another Methodology?

• Software development is relatively young
• Not an exact science
• Lightweight
• Programming Languages/Frameworks have evolved
• We are still figuring it out!

6
Enter XP!
7
XP
8
XP Process Phase 1 Planning

• Entire team sits and works together with a
  business user
• Business user writes User Stories, Developers
  estimate implementation time
• Business user prioritizes into a Release Plan
• Developers create Iteration Plan for each story
  (frequent releases)

9
XP Process Phase 2 Designing

• Choose a metaphor to describe the system
• Design for current knowledge only
• Keep things simple
• Prototype when possible
• Revise and Refactor whenever possible

10
XP Process Phase 3 Coding

• Pair Programming
• Write tests before you code
• Group ownership
• Continual integration and builds

11
XP Process Phase 4 Testing

• Unit test
• Bugs found write a test
• Acceptance tests
• All tests are automated and run continually
• Fixes should be made as soon as possible

12
Advantages/disadvantages of XP
13
Advantages of XP

• Incorporates good industry standard practices.
• Testing, Communication, Coding standards,
  Customer driven, Managed risk, etc..
• Stresses simplicity and consistency.
• Continual improvement, flexibility.
• Release cycles.

14
Disadvantages of XP

• Finding a business user with 100 time and
  adequate knowledge
• Downstream architectural flaws, risk management
  and mitigation
• Pair programming Additional Cost

15
When to Use XP

• Small projects (less than 10 developers)
• New projects, New team members
• Open minded team/clients
• Continually changing requirements

16
How to start with XP

• Find a brand new small project
• Add one practice at a time
• Requirements via user stories
• Iterative development
• Unit testing
• Collective ownership

17
Whats Next

• Agile Software Development
• Better ways of developing software
• http//www.agilealliance.org

18
Resources

• www.extremeprogramming.org
• www.xprogramming.com
• Extreme Programming Explained Embrace Change by
  Kent Black

19
QA