1 / 35

Agile Software Development (How Flexible Are Your Fingers?)

Explore the principles and practices of Agile software development, such as Extreme Programming (XP), pair programming, continuous integration, and more. Gain insights into the values and methodologies that promote efficient and adaptable software development.

virginiaholton
Download Presentation

Agile Software Development (How Flexible Are Your Fingers?)

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. Agile Software Development(How Flexible Are Your Fingers?) CSEMS Seminar Dr. Jay Fenwick

  2. Consider… • Debugging is not planned for. • Debugging is not enjoyable. • Debugging is worn proudly like a badge! • ????????????????????????????????

  3. What is XP? • eXtreme Programming • “XP is a lightweight methodology for small to medium sized teams developing software in face of vague and changing requirements.” – Kent Beck • XP is a specific (one of many) methodology of a set of methodologies referred to as “agile.”

  4. XP Values • Why values? • Methodologies impose certain ways of doing things. • The reason for doing something should be valued. • Communication • Simplicity • XP makes a bet: “better to do a simple thing today and pay a little more tomorrow to change it if it needs to be, than to do a complicated thing today that may never be used anyway.” (YAGNI) • Feedback • Courage

  5. Pair Programming (unit)Tests first Planning Game Small Releases Metaphor Simple Design Sustainable Pace Collective Ownership Continuous Integration Coding Standards On-Site Customer Refactoring XP Practices The practices support and reinforce each other.

  6. XP Values and Practices • Practices bring accountability to the Values • Values give purpose to the Practices-- Kent Beck (XP/AU 2003) accountability Values Practices purpose

  7. XP Values and Practices(Lowell Lindstrom XPAU03) D E L I V E R Communication Simplicity Courage Feedback

  8. XP Values and Practices (Lowell Lindstrom XPAU03) D E L I V E R Communication Simplicity Whole Team AcceptanceTests PlanningGame Small Releases Courage Feedback

  9. XP Values and Practices(Lowell Lindstrom XPAU03) D E L I V E R Communication Simplicity Whole Team Test DrivenDevelopment AcceptanceTests PlanningGame PairProgramming Refactoring SimpleDesign Small Releases Courage Feedback

  10. XP Values and Practices(Lowell Lindstrom XPAU03) D E L I V E R Communication Simplicity Whole Team Retrospectives CodingStandards CollectiveOwnership Test DrivenDevelopment AcceptanceTests PlanningGame PairProgramming Refactoring Continuous Integration SimpleDesign SustainablePace Metaphor Small Releases Courage Feedback

  11. XP Metaphor • Controlling software development is like driving a car. • We need to make many small adjustments, not a few large adjustments • We need feedback to know if we are a little off

  12. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  13. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  14. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  15. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  16. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  17. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  18. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  19. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  20. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  21. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  22. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  23. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  24. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  25. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  26. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  27. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  28. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  29. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  30. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  31. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  32. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  33. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  34. Wait, can this really work?(Beck 2000) On-site Customer Planning Game Sustainable Pace Metaphor Simple Design Refactoring Short releases Testing Pair Programming Coding Standards Collective Ownership Continuous Integration

  35. Clues of design flaws Speed Visual people Values Communication Simplicity No concrete feedback Will test case pass? Is this simple? Values Feedback Courage Wait, what about those pictures?<good> <bad> • Draw only a few at time; find out quickly if on target • Don’t use out of fear; leverage people skills • Don’t save when they’ve had effect on the code

More Related