XP - e Xtreme Programming Outline Traditional life cycle...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
e e X X treme  treme  P P rogramming rogramming    
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Outline Outline Traditional life cycle vs. XP XP motto: “embrace change” How does this attitude compare with that implicit with  traditional waterfall software life cycle? XP values XP practices Pair programming An XP development road map References
Background image of page 2
3 Extreme Programming (XP) Extreme Programming (XP) XP does  not  involve bungee cords!  It does not encourage blind hacking.  It is a systematic methodology. It predates Windows “XP”. Developed by  Kent Beck  (earlier helped create CRC cards): XP is “a light-weight methodology for small to medium-sized teams  developing software in the face of vague or rapidly changing  requirements.” Alternative to “heavy-weight” software development models  (which tend to avoid change and customers) " Extreme Programming turns the conventional software process sideways. Rather than planning, analyzing, and designing for the far-flung future, XP programmers do all of these activities a little at a time throughout development.” -- IEEE Computer , October 1999   XP Introduction
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Successes in industry Successes in industry  Chrysler Comprehensive Compensation system After finding significant, initial development problems, Beck and  Jeffries restarted this development using XP principles The payroll system pays some 10,000 monthly-paid employees  and has 2,000 classes and 30,000 methods, went into  production almost on schedule, and is still operational today  (Anderson 1998) Ford Motor Company VCAPS system Spent four unsuccessful years trying to build the Vehicle Cost  and Profit System using traditional waterfall methodology XP developers successfully implemented that system in less  than a year using Extreme Programming (Beck 2000). XP Introduction
Background image of page 4
5 Embrace change Embrace change In traditional software life cycle models, the cost of  changing a program rises exponentially over time Why would it cost more to make large changes during  testing than during requirements specification? A key assumption of XP is that the cost of changing a  program can be hold mostly constant over time Hence XP is a lightweight (agile) process: Instead of lots of documentation nailing down what customer  wants up front, XP emphasizes plenty of feedback Embrace change: iterate often, design and redesign, code  and test frequently, keep the customer involved Deliver software to the customer in short (2 week) iterations Eliminate defects early, thus reducing costs
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 Four Core Values of XP Four Core Values of XP Communication Simplicity Feedback Courage XP values
Background image of page 6
7 Communication Communication What does lack of communication do to projects? XP emphasizes value of communication in many of 
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/06/2008 for the course CSE 432 taught by Professor Blank during the Fall '08 term at Lehigh University .

Page1 / 27

XP - e Xtreme Programming Outline Traditional life cycle...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online