2-1-2 Agile

[The Values of Agile Software Development]

• • Individuals and interactions are valued over processes and tools
• • Working software is valued over comprehensive documentation
• • Customer collaboration is valued over contract negotiation
• • Responding to change is valued over following a plan
  Note: With recognition of value in the compared items, the Manifesto declares the stated items to be of higher value.

[Agile-related methods/technologies]

• • XP (eXtreme Programming)
  This is a typical agile software development technique that simplifies the design phase and enhances programming and testing. It is a relatively new technique that emphasizes communication, and places importance on constant feedback, changes, and redesign rather than on setting up and proceeding processes in order. XP development practices include test driven development, pair programming, and refactoring. · 3 questions
• • Test driven development
  This is a method that creates testing before programming (i.e., “test first”), and then creates programs which pass the testing. By performing the testing first, the required functions are made clear and simple design is possible.
• • Pair programming
  This is a method in which programming is performed by a pair of persons. One person creates a program and the other person gives instruction while checking the program. The pair proceeds by switching each role, and thus it is always possible to perform code review. The technique is also expected to aid in maintaining concentration. · 2 questions
• • Refactoring
  This is a technique that improves the finished code without changing its action (i.e., behavior) that is seen from the outside. It reworks code that is difficult to understand, because of bug fixes or adaption to requirements changes, into easily understood code with high maintainability. · 3 questions