agile approaches to achieve working product / application, at the end of each iteration, called sprint.
V-model does not contain any iteration approach.
Agile iteration - sprint, contains every phase of software development, i.e. requirement understanding, design, coding, testing
In agile, developer, tester and customer works together on piece of code for application.
V-model does not have this concept. In V-model, developer works on designing and coding and testers working on writing testcases and testing the product. THere is no concept of "working together" for V-model.
Agile is more suitable for the projects where requirements change rapidly.
V-model is suitable where requirement changes are almost none.
1) Why can't be V Modle iterative? Don't we have the concept of releases in V?
2) In agile, developer, tester and customer works together on piece of code for application.? when customer can work on code why hire developers???
3) V-model is suitable where requirement changes are almost none - this Waterfall model not V.
Coming to the reply,
1) Agile mandates customer interaction on a regular basis, V doesn't
2) Task(requirements) are never measured to their weight in V, yes in Agile, hence we see Task Break down in smaller chunks
3) In Agile we can change the direction on will, meaning back logs can be postponed or preponed, V doesn't have a look back or ahead and change direction concept.