Agile Software Development with XP

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    2 Favorites

    Agile Software Development with XP - Presentation Transcript

    1. BY Extreme Programming
      • The problem in today Software Development
      • Agile Methods
      • eXtreme Programming (XP)
      • Q&A
      • Risks:
        • Schedule Slips
        • Quality of product (Defect Rate)
        • Requirement Changes
        • Project Cancelled
    2.  
    3.  
    4.  
    5.  
    6. Customer satisfaction by rapid, continuous delivery of useful software
    7. Working software is delivered frequently
    8. Working software is the principal measure of progress
    9. Even late changes in requirements are welcomed
    10. Close, daily cooperation between business people and developers
    11. Face-to-face conversation is the best form of communication
    12. Projects are built around motivated individuals, who should be trusted
    13. Continuous attention to technical excellence and good design
    14. Simplicity
    15. Self - organizing teams
    16. Regular adaptation to changing circumstances
      • Agile UP
      • XP (eXtreme Programming)
      • FDD (Feature Driven Development)
      • Scrum
    17. >>
    18.  
    19.  
    20. An attempt to reconcile humanity and productivity
    21. A mechanism for social change
    22. A path to improvement
    23. A style of development
    24. A software development discipline
    25.  
    26. Communication
    27. Simplicity
    28. Feedback
    29. Courage
    30. Respect
    31.  
      • Planning game
      • Frequent releases
      • Metaphor
      • Simple Design
      • Testing
      • Refactoring
      • Pair Programming
      • Collective Ownership
      • Continuous Integration
      • 40 Hour Week
      • On-site customer
      • Coding Standards
      • A release cycle is usually up to 3 months
      • Each iterations is around to 3 weeks
      • Each iteration the selected user stories are implemented
      • Each user story is split in programming tasks of 1-3 days
      • small and frequent releases provide frequent feedback from the customer.
      • Do the simplest thing that could possible work
      • You aren’t going to need it
        • do not spend time implementing potential future functionality (requirements will change)
      • Put in what you need when you need it
      • Simple design ensures that there is less
        • to communicate
        • to test
        • to refactor
      • Tests play the most important and central role in XP
      • Tests are written before the code is developed
      • All tests are automated (test suites, testing framework)
      • User stories = Requirements
      • Tests = System Specification
      • 2 kinds of test:
        • Acceptance tests (functional tests)
          • clients provide test cases for their stories
          • developers transform these in automatic tests
        • Unit tests
          • developers write tests for their classes (before implementing the classes)
          • All unit tests must run 100% successfully all the time
      • Process of improving code while preserving its function
      • The aim of refactoring is to
        • make the design simpler
        • make the code more understandable
        • improve the tolerance of code to change
      • The code should not need any comments
        • There is no documentation in XP
        • The code and the user stories are the only documents
      • Refactoring is continuous design
      • Two programmers sit together in front of a workstation
        • one enters code
        • one reviews the code and thinks
      • Second most important practice after tests
      • Costs 10-15% more than stand-alone programming
      • Code is simpler (fewer LOC) with less defects (15%)
      • Ensures continuous code inspection (SE)
      • Daily integration at least
      • The whole system is built (integrated) every couple of hours
      • XP feedback cycle:
        • develop unit test
        • code
        • integrate
        • run all units tests (100%)
        • release
      • A working tested system is always available
    32.  
      • Traditional Software Lifecycle:
        • Listen - Design - Code - Test
      • XP lifecycle
        • Listen - Test - Code - Design
      • Listen to customers while gathering requirements
      • Develop test cases (functional tests and unit tests)
      • Code the objects
      • Design (refactor) as more objects are added to the system
    33. Listen to customers while gathering requirements
    34. Develop test cases (functional tests and unit tests)
    35.  
    36. Design (refactor) as more objects are added to the system
    37.  
    38.  

    + Vashira RavipanichVashira Ravipanich, 2 years ago

    custom

    884 views, 2 favs, 0 embeds more stats

    The Object Oriented Technology course assignment fr more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 884
      • 884 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 2
    • Downloads 56
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Tags