Focus on agile methods and how they differ from ordinary. In 1980’s and early 1990s the best way to achieve better software was through project planning and case tools – complex big systems. NOW – agile methods increment development and delivery (used in small and medium- sized projects).
The best known agile methods All requirements are expressed as scenarios (planning game) which are implemented directly as a series of tasks. Have 10/12 principels/best pracctices. - test first development - test-first - unittest of each task - user involvement - use of automated test - pairprogramming
When a programmer builds the system to create a new version, he or she must run all existing automated tests as well as the test for new functionality. Only accepted if all test execute succesfully. Refactoring – look for possible improvements to the software and implements them immediately. Code should be rewitten to improve their clarity or structure.