1 / 10

Contents

eXtreme Programming experiences with a new approach to software development SPIN UK - 13 February 2001. Contents. 1. Introduction 2. XP values 3. XP practices 4. Reactions. Introduction. origins originated by Kent Beck in Chrysler payroll project (C3) take up very rapid

terris
Download Presentation

Contents

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. eXtreme Programmingexperiences with a new approach to software developmentSPIN UK - 13 February 2001

  2. Contents 1. Introduction 2. XP values 3. XP practices 4. Reactions

  3. Introduction • origins • originated by Kent Beck in Chrysler payroll project (C3) • take up • very rapid • by developers (not managers) • characteristics • strong OO orientation - OOO? • growing useful software • design a little…. • small teams • communication • verification • speed (velocity) • good humoured (fun)

  4. XP Values • humane • rational • small is beautiful • adaptable(in use) • embraces quality • expects excellence, prefers the ‘insanely excellent’ • expects change • encourages competence • supports learning • challenges s/w development status quo • estimation • cost • front loading • courage • ‘play to win’ not ‘play not to lose’ • allocate priorities to business • s/w development fundamentals

  5. XP Practices • planning game • user stories • metaphor • simple design • tests • acceptance • unit • on site user • pair programming • frequent releases • continuous integration • refactoring • collective code ownership • coding standards • 40 hour week

  6. Introducing XP • step by step • incremental - of course • introduce one practice at a time • selected by your business priorities • tailor practices to fit • up to a point - there are some ‘musts’

  7. Reactions to XP... • understands how software is produced • cf organizational models for software management • clear focus • communication, quality, delivery • supported by many (traditional) good practices • reflects its origins • large organization infrastructure • reduces distinction between development and maintenance • raises some issues of control • perhaps addressed by good tools? • professional, disciplined approach is assumed • still new with little specific advice on adapting to different situations and environments • must understand environment • apply with understanding and common sense

  8. ...Reactions to XP • initially mixed - superficially looks like hacking • actually a considered, disciplined, ‘methodology’ backed up with a useful set of tools • recognizes and addresses many of the weaknesses of conventional software management and SPI An attractive and workable approach to software development and maintenance

  9. References: http://c2.com/wiki?ExtremeProgrammingRoadmap computer.org/seweb/ www.xprogramming.com extremeprogramming.org www.sys.uea.ac.uk/Research/researchareas/spi/rapid.ppt

  10. O X F O R D S O F T W A R E E N G I N E E R I N G L I M I T E D 9 Spinners Court, 53 West End, Witney, Oxfordshire OX8 6 NS tel. +44 (0) 1993 700878 email enquiries@osel.co.uk

More Related