Hira Xp
2 likes634 views
This document provides an overview of Extreme Programming (XP), an agile software development methodology. It discusses XP practices like planning with user stories, making frequent small releases, designing for simplicity, pair programming, testing with unit and acceptance tests, and having an on-site customer. The goal of XP is to satisfy customers through iterative development, lightweight processes, and team collaboration.
Hira Xp
- 2. Extreme ProgrammingAgile Software Development MethodologyIterativeLightweightStresses customer satisfaction and teamwork
- 4. PlanningUser storiesWritten by the customers The stories that will be developed in one of three ways: All stories will be implemented immediatelyThe stories with highest value will be implemented first .The riskiest stories will be implemented first
- 5. Release planning meetingCreation of a release plan documentPlanning of individual iterationsEstimation of user stories in terms of ideal programming weeks
- 6. Make frequent small releasesFor valuable feedbackImportant features are introduced early
- 7. Project velocity How many user stories were finished during the iterationPoject velocity can then be used to help estimate delivery dates and schedule and implemented first.
- 8. DesigningSimplicityNeeds no explanationUse KIS principle. Design Of extra functionality is discourage.
- 9. CRC cardsClass, Responsibilities and CollaborationUsed to represent objectsClass written on topOrganize the components
- 10. system metaphor Allows consistent naming of classes and methods
- 11. Spike solutionA very simple program to explore potential solutions
- 12. RefactoringHelps keep the design simple and keeping code clean and concise
- 13. Coding Coding standardsEverybody chooses class names and variable names in the same style
- 14. Pair programmingSitting side by side in front of the monitorOne person typesThe other one thinks strategicallyincreases software quality comes big savings later in the project.
- 15. Sequential integration Code is integrated together Customer is always available.
- 16. On-site CustomerTo write user storiesTo select user storiesDevelopers need to talk with the customer to get enough detail to complete a programming task
- 17. TestingUnit testingWritten by developer Test only a single class are small cluster of classes.
- 18. Acceptance testsCreated from user stories.Customer verifies the correctness of the tests.Test the entire system.
- 19. Thanks