Download
1 / 10
100 likes | 179 Views
This seminar explores a new approach to software development known as eXtreme Programming (XP), focusing on its values, practices, and reactions. Originated by Kent Beck, XP emphasizes humane, adaptable, and quality-driven software development practices. Participants will learn about XP's incremental, disciplined, and user-centric methodologies. Reactions to XP have been mixed, with some seeing it as a disciplined approach, while others find it lacking specific advice for adapting to varying environments. Overall, XP offers a promising solution for modern software development challenges.
E N D
eXtreme Programmingexperiences with a new approach to software developmentSPIN 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 • by developers (not managers) • characteristics • strong OO orientation - OOO? • growing useful software • design a little…. • small teams • communication • verification • speed (velocity) • good humoured (fun)
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
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
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’
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
...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
References: http://c2.com/wiki?ExtremeProgrammingRoadmap computer.org/seweb/ www.xprogramming.com extremeprogramming.org www.sys.uea.ac.uk/Research/researchareas/spi/rapid.ppt
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
