0
<ul><li>Agile development </li></ul><ul><li>Extreme Programming (XP) </li></ul><ul><li>Abder-Rahman Ali </li></ul><ul><li>...
Just before we begin… <ul><li>Agile development is a: </li></ul><ul><li>Software development  process model . </li></ul>.
Software development  Process Task (1) Task (2) Task (3) . . . Task (n) Goal HIGH QUALITY SOFTWARE Action
<ul><li>In other words… </li></ul>
THE ROADMAP THAT YOU FOLLOW
Software development Process   Models
Nature of Software Change
Change in what? <ul><li>Software being built (i.e. requirements). </li></ul><ul><li>Team members. </li></ul><ul><li>New te...
Implications … <ul><li>Change is the  HEART  of software. </li></ul><ul><li>Support for changes should be built in  everyt...
So, what is Agility? <ul><li>A  rapid  and  effective   response  to  change . </li></ul>
So, what is Agility? <ul><li>Effective  communication  among stakeholders. </li></ul>
So, what is Agility? Drawing the  customer into the team .
This yields to…
Rapid  &  incremental  delivery of software.
An Agile team… <ul><li>A team that is able to appropriately  to changes. </li></ul>
Extreme Programming (XP) Planning Design Test Coding Release The XP Process The most widely used Agile process, and it is ...
Planning
Design <ul><li>KIS Principle </li></ul>We  just  want the design to provide an  implementation guidance  for the story  as...
Design <ul><li>CRC Cards </li></ul>
Design <ul><li>Spike Solutions </li></ul>1- A design problem occurs. 2- Create a  PROTOTYPE  of that portion of the design...
Design <ul><li>Refactoring </li></ul>Changing  a software system in such a way that: 1- The internal structure is improved...
Testing TEST FIRST
Testing Unit tests are written  before  the code. Tests are run to ensure that our software  fails . A  good  test case is...
Testing <ul><li>All unit tests are executed  daily . </li></ul>This can raise warning flags  early  if things are going wr...
Testing <ul><li>Acceptance tests (customer tests): </li></ul>They are specified by the customer. They focus on the overall...
Testing Fixing small problems every few hours takes  less time  than fixing huge problems just before the deadline. Fact:
Coding Pair Programming
Coding Two people work together at one computer to create code for a story. This provides a mechanism for  real-time  prob...
Coding ROI
Coding ROI
Release Project Velocity The  number of stories  that we performed in this release.
When to use XP? Dynamically changing requirements. Risky projects. Small development groups (up to 100). Non-fixed price c...
XP Rules… <ul><li>Planning </li></ul><ul><li>User Stories </li></ul><ul><li>Release Planning </li></ul><ul><li>Small Relea...
XP Rules… <ul><li>Coding </li></ul><ul><li>Customer available </li></ul><ul><li>Code standards </li></ul><ul><li>Test-Driv...
We Must Ask Ourselves… Do we need Agile or any other  Software Development Process models  in our lab?
Questions?
Upcoming SlideShare
Loading in...5
×

Agile Development Ultimate Slides

2,847

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,847
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
122
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Agile Development Ultimate Slides"

  1. 1. <ul><li>Agile development </li></ul><ul><li>Extreme Programming (XP) </li></ul><ul><li>Abder-Rahman Ali </li></ul><ul><li>M.S.Software Engineering </li></ul><ul><li>DePaul CTI </li></ul><ul><li>[email_address] </li></ul>
  2. 2. Just before we begin… <ul><li>Agile development is a: </li></ul><ul><li>Software development process model . </li></ul>.
  3. 3. Software development Process Task (1) Task (2) Task (3) . . . Task (n) Goal HIGH QUALITY SOFTWARE Action
  4. 4. <ul><li>In other words… </li></ul>
  5. 5. THE ROADMAP THAT YOU FOLLOW
  6. 6. Software development Process Models
  7. 7. Nature of Software Change
  8. 8. Change in what? <ul><li>Software being built (i.e. requirements). </li></ul><ul><li>Team members. </li></ul><ul><li>New technology appearing. </li></ul>
  9. 9. Implications … <ul><li>Change is the HEART of software. </li></ul><ul><li>Support for changes should be built in everything we do in software </li></ul>
  10. 10. So, what is Agility? <ul><li>A rapid and effective response to change . </li></ul>
  11. 11. So, what is Agility? <ul><li>Effective communication among stakeholders. </li></ul>
  12. 12. So, what is Agility? Drawing the customer into the team .
  13. 13. This yields to…
  14. 14. Rapid & incremental delivery of software.
  15. 15. An Agile team… <ul><li>A team that is able to appropriately to changes. </li></ul>
  16. 16. Extreme Programming (XP) Planning Design Test Coding Release The XP Process The most widely used Agile process, and it is originally proposed by Kent Benck.
  17. 17. Planning
  18. 18. Design <ul><li>KIS Principle </li></ul>We just want the design to provide an implementation guidance for the story as it is written ---nothing less, nothing more. Don’t try to design extra functionality because you assume it will be required later.
  19. 19. Design <ul><li>CRC Cards </li></ul>
  20. 20. Design <ul><li>Spike Solutions </li></ul>1- A design problem occurs. 2- Create a PROTOTYPE of that portion of the design. 3- Implement and evaluate the prototype. Intent: To lower risk when true implementation starts.
  21. 21. Design <ul><li>Refactoring </li></ul>Changing a software system in such a way that: 1- The internal structure is improved. 2- The external behavior is not altered (not changed). Design occurs CONTINUOUSLY as the system is constructed. Also means:
  22. 22. Testing TEST FIRST
  23. 23. Testing Unit tests are written before the code. Tests are run to ensure that our software fails . A good test case is one that ensures that the software fails. Test is rerun until it passes .
  24. 24. Testing <ul><li>All unit tests are executed daily . </li></ul>This can raise warning flags early if things are going wrong.
  25. 25. Testing <ul><li>Acceptance tests (customer tests): </li></ul>They are specified by the customer. They focus on the overall system features and functionality that are visible and reviewable by the customer. They are derived from user stories.
  26. 26. Testing Fixing small problems every few hours takes less time than fixing huge problems just before the deadline. Fact:
  27. 27. Coding Pair Programming
  28. 28. Coding Two people work together at one computer to create code for a story. This provides a mechanism for real-time problem solving and real-time quality assurance . Keeps the developers focused on the problem at hand. As pair programmers complete their work, the code they develop is integrated with the work of others.
  29. 29. Coding ROI
  30. 30. Coding ROI
  31. 31. Release Project Velocity The number of stories that we performed in this release.
  32. 32. When to use XP? Dynamically changing requirements. Risky projects. Small development groups (up to 100). Non-fixed price contract.
  33. 33. XP Rules… <ul><li>Planning </li></ul><ul><li>User Stories </li></ul><ul><li>Release Planning </li></ul><ul><li>Small Releases </li></ul><ul><li>Measure Project Velocity </li></ul><ul><li>Divide project to iterations </li></ul><ul><li>Iterations Planning </li></ul><ul><li>Move People around </li></ul><ul><li>Stand up meeting </li></ul><ul><li>Designing </li></ul><ul><li>Simplicity </li></ul><ul><li>CRC cards </li></ul><ul><li>Spike solutions </li></ul><ul><li>Refactor </li></ul>
  34. 34. XP Rules… <ul><li>Coding </li></ul><ul><li>Customer available </li></ul><ul><li>Code standards </li></ul><ul><li>Test-Driven </li></ul><ul><li>Pair Programming </li></ul><ul><li>Sequential change integration </li></ul><ul><li>Integrate often </li></ul><ul><li>Collective code ownership </li></ul><ul><li>Don’t optimize early </li></ul><ul><li>No overtime </li></ul><ul><li>Testing </li></ul><ul><li>Unit test everything </li></ul><ul><li>All tests pass before release </li></ul><ul><li>Bug == new test </li></ul><ul><li>Acceptance tests </li></ul>
  35. 35. We Must Ask Ourselves… Do we need Agile or any other Software Development Process models in our lab?
  36. 36. Questions?
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×