I have been working as a software consultant for more than 11 years. Because of that I am an eager supporter of lean principles and agile methods.
Agile methodologies is considered to embrace change, but it’s also about getting quick and frequent feedback from all kinds of sources, in a way to cope with changes.
- Short iterations with incremental deliveries – gives the team and the product owner frequent feedback on the progress of the product, enabling change of direction of the project.
- The daily scrum meeting - is designed to get feedback on the progress and to raise any issues.
- Continuous Integration – gives the team instant feedback on the status of the code when delivering changes to the code.
- Test Driven Development – gives even more feedback when delivering code changes. Makes it possible to get a test report from unit tests to acceptance tests immediately after a code change.
- Retrospective – at the end of an iteration gives the team feedback about the methods and processes of the project.
- Pair programming – gives the programmer instant feedback. This corresponds doing a code review simultaneously as the coding, thus providing instant feedback.
Did I miss any? Let me know in a comment!
I count the Hallway feedback also, i.e. getting out of the office to the hall, grabbing somebody and showing him your code, ui, feature, design or whatever else.
Left by Artem Marchenko on November 29th, 2006