INTRODUCTION<br />  HIRA   KHURSHID<br />   BSCS   4TH  B...
Extreme Programming<br />Agile Software Development Methodology<br />Iterative<br />Lightweight<br />Stresses customer sat...
Extreme Programming Model<br />
Planning<br />User stories<br />Written by the customers <br />The stories that will be developed in one of three ways:<br...
Release planning meeting<br />Creation of a release plan document<br />Planning of individual iterations<br />Estimation o...
Make frequent small releases<br />For valuable feedback<br />Important features are introduced early <br />
Project velocity <br />How many user stories were finished during the iteration<br />Poject velocity can then be used to h...
Designing<br />Simplicity<br />Needs no explanation<br />Use KIS  principle. <br />Design Of extra  functionality is  disc...
CRC cards<br />Class, Responsibilities and Collaboration<br />Used to represent objects<br />Class written on top<br />Org...
system metaphor <br />Allows consistent naming of classes and methods<br />
Spike solution<br />A very simple program to explore potential solutions<br />
Refactoring<br />Helps keep the design simple and keeping code clean and concise<br />
Coding<br /> Coding standards<br />Everybody chooses class names and variable names in the same style <br />
Pair programming<br />Sitting side by side in front of the monitor<br />One person types<br />The other one thinks strateg...
Sequential integration<br /> Code is integrated  together<br /> Customer is always available.<br />
On-site Customer<br />To write user stories<br />To select user stories<br />Developers need to talk with the customer to ...
Testing<br />Unit testing<br />Written by developer <br />Test only a single class are small cluster of classes.<br />
Acceptance tests<br />Created from user stories.<br />Customer verifies the correctness of the tests.<br />Test the entire...
Thanks<br />
Upcoming SlideShare
Loading in …5
×

Hira Xp

603 views
453 views

Published on

Extreme Programming

Published in: Technology, News & Politics
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
603
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
13
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Hira Xp

  1. 1. INTRODUCTION<br /> HIRA KHURSHID<br /> BSCS 4TH B <br /> EXTREME PROGRAMMING<br />
  2. 2. Extreme Programming<br />Agile Software Development Methodology<br />Iterative<br />Lightweight<br />Stresses customer satisfaction and teamwork<br />
  3. 3. Extreme Programming Model<br />
  4. 4. Planning<br />User stories<br />Written by the customers <br />The stories that will be developed in one of three ways:<br /> All stories will be implemented immediately<br />The stories with highest value will be implemented first .<br />The riskiest stories will be implemented first <br />
  5. 5. Release planning meeting<br />Creation of a release plan document<br />Planning of individual iterations<br />Estimation of user stories in terms of ideal programming weeks<br />
  6. 6. Make frequent small releases<br />For valuable feedback<br />Important features are introduced early <br />
  7. 7. Project velocity <br />How many user stories were finished during the iteration<br />Poject velocity can then be used to help estimate delivery dates and schedule and implemented first.<br />
  8. 8. Designing<br />Simplicity<br />Needs no explanation<br />Use KIS principle. <br />Design Of extra functionality is discourage.<br />
  9. 9. CRC cards<br />Class, Responsibilities and Collaboration<br />Used to represent objects<br />Class written on top<br />Organize the components<br />
  10. 10. system metaphor <br />Allows consistent naming of classes and methods<br />
  11. 11. Spike solution<br />A very simple program to explore potential solutions<br />
  12. 12. Refactoring<br />Helps keep the design simple and keeping code clean and concise<br />
  13. 13. Coding<br /> Coding standards<br />Everybody chooses class names and variable names in the same style <br />
  14. 14. Pair programming<br />Sitting side by side in front of the monitor<br />One person types<br />The other one thinks strategically<br />increases software quality <br />comes big savings later in the project. <br />
  15. 15. Sequential integration<br /> Code is integrated together<br /> Customer is always available.<br />
  16. 16. On-site Customer<br />To write user stories<br />To select user stories<br />Developers need to talk with the customer to get enough detail to complete a programming task<br />
  17. 17. Testing<br />Unit testing<br />Written by developer <br />Test only a single class are small cluster of classes.<br />
  18. 18. Acceptance tests<br />Created from user stories.<br />Customer verifies the correctness of the tests.<br />Test the entire system. <br />
  19. 19. Thanks<br />

×