Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams
Agile methods break tasks into small increments with minimal planning, and do not directly involve long-term planning. Iterations are short time frames (“timeboxes”) that typically last from one to four weeks.
Specific tools and techniques such as continuous integration, automated or xUnit test, pair programming, test driven development, design patterns, domain-driven design, code refactoring and other techniques are often used to improve quality and enhance project agility.
– Maintain a code repository
– Automate the build
– Make the build self-testing
– Everyone commits every day
– Every commit (to mainline) should be built
– Keep the build fast
– Test in a clone of the production environment
– Make it easy to get the latest deliverables
– Everyone can see the results of the latest build
– Automate deployment
Various code-driven testing frameworks have come to be known collectively as xUnit. These frameworks allow testing of different elements (units) of software, such as functions and classes. The main advantage of xUnit frameworks is that they provide an automated solution with no need to write the same tests many times, and no need to remember what should be the result of each test. Such frameworks are based on a design by Kent Beck, originally implemented for Smalltalk as SUnit. Erich Gamma, ported SUnit to Java, creating JUnit. Out of that the SUnit framework was also ported to other languages, e.g., CppUnit (for C++), NUnit (for .NET). They are all refered as xUnit and are free, open source software. They are now available for many programming languages and development platforms.
Pair programming is an agile software development technique in which two programmers work together at one work station. One types in code while the other reviews each line of code as it is typed in. The person typing is called the driver. The person reviewing the code is called the observer (or navigator). The two programmers switch roles frequently (possibly every 30 minutes or less).
Test-driven development (TDD) is a software development technique that relies on the repetition of a very short development cycle: first the developer writes a failing automated test case that defines a desired improvement or new function, then produces code to pass that test and finally refactors the new code to acceptable standards. Kent Beck, who is credited with having developed or ‘rediscovered’ the technique, stated in 2003 that TDD encourages simple designs and inspires confidence.
* Add a test
* Run all tests and see if the new one fails
* Write some code
* Run the automated tests and see them succeed
* Refactor code