1 / 19

XP – Extreme Programming

XP – Extreme Programming. XP in general. XP is an agile discipline of software develop -ment. It emphasis high customer satisfaction and customer involvement . When working with XP everybody works as a hole team, but the customers and the manager as well .

vaughn
Download Presentation

XP – Extreme Programming

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. XP – Extreme Programming

  2. XP in general XP is an agile discipline of software develop-ment. It emphasishighcustomersatisfaction and customerinvolvement. Whenworking with XP everybodyworks as a hole team, but the customers and the manager as well. XP aims at short iterations, and to provide workingcode, at the end of eachiteration.

  3. XP Values • Communication (communicationamong team members and between the team and the customer must bemaximized). • Simplicity (do the simplest thingthatcouldpossiblywork). Simplicityfavorscommunication, reduces the amount of code and improves the quality. • Feedback • Courage (communication, simplicity and feedback allow to tackle with courage evenbigchanges in requirements……) • Respect(ifmembers of a team don’tcareabouteachother and theirwork, nomethodologycanwork).

  4. Extreme Programming Practices • Fine scale feedback - Pair Programming - Planning game - Test Driven development - Whole team • Continousprocess - Continuous integration - design involvement - small releases

  5. Shared understanding - coding standard - collectivecodeownweship - Simple design - System Metaphor • Programmer welfare - Sustainable Pace

  6. Coding standard • An agreed upon set of rulesthat the entiredevelopment team agree to adhere to throughout the project • A consistentstyle and format for source code

  7. Collectivecodeownership • Everybody is responsible for all the code • Every programmer has the right to change the code

  8. Continous Integration • The development team shouldalwaysbeworking on the latest version of the software • Upload current version to the coderepositoryeveryfewhours

  9. Design improvement • Implement as simple as possible • Refactor the codewhenneeded - refactoring is the process of rewritinga computer program or othermaterial to improveitsstructure or readability, whileexplicitlypreservingitsmeaning or behavior.

  10. Simple designa sharedunderstandingpractice • Programmers shouldtake a ”simple is best” approach to software design

  11. Small Releasesa continousrocesspractice • The delivery of the software is done in predeterminedreleases (sometimescalled ”Builds”) • Ther small releases provides the customer to gainconfidence over the progress of the project.

  12. Sustainable Pacea programmer welfarepractice • Programmers or software developers should not work more than 40 hoursweeks. • People perform best and most creativelyiftheyarerested.

  13. System Methaphor • A namingconcept for classes and methodsthatshouldmake it easy for a team member to guess the functionality of a particularclass/method, from itsnameonly. For example a library system mat createloan_records(class) for borrowers (class), and if the item were to become overdue it may perform a make_overdue operation on a catalogue (class). For eachclass or operation the functionality is transparent to the entire team

  14. Pair Programminga fine scale feedback practice • All code is produced by twopeopleprogramming on onetask on oneworkstation. • One programmer has control over the workstation and is thinkingmostlyabout the code in detail. • The other programmer is more focused on the bigpicture, ans is continuallyreviewing the codethat is beingproduced by the first programmer. • Programmers traderolesregularly

  15. Planning gamea fine scale feedback practice • Release Planning - focused on determiningwharrequirementsareincluded in which release and whenit’sgoing to bedelivered. - the customers and developers areboth part of this. • Iterationplanning - plans the activities and task of the developers. In thisprocess the customer is not involved.

  16. Planning gameRelease planning • 3 phases: - Exploration Phase: in thisphase the custo- merwill give all his requirements for the system. Thesebwillbewrittendown on user story cards- - Commitmentphase: within the commitmentphase business and developmentwillcommit themselves to the functionalitythatwillbeincluded and the date of the nextrelease. - SteeringPhase: in the steeringphase the plan canbeajusted, new requirementscanbeadded and or existingrequirementscanbe changed or removed.

  17. Planning gameIterationplanning • 3 phases: • Exploration phase: withinthisphase the requirementwillbetranslated to differenttasks. The taskarerecorded on taskcards. • Commitmentphase: the taskswillbeassigned to the programmers and the time it takes to completewillbeestimated. • Steeringphase: the tasksareperformed and the end result is matched with the original user story.

  18. Test driven developmenta fine scale feedback practice • Unit test arewrittenbefore the eventualcode is coded. • Intended to stimulate the programmer to thinkaboutconditions in which his or her codecouldfail

  19. Whole teama fine scale feedback practice • The ”customer” is not the onewhopays the bill, but onewhowillreallyuses the system • The customershouldbe at hand at all times and available for questions.

More Related