How do you apply (or not?) an iterative approach to development?

Question

Work organization

A lot has been said and written about iterative development. Maybe even too much. And this is all, of course, good, but no matter how much I read and dug in the direction of this topic, I was not able to put this approach into practice with the desired result.
For example, there is a real project. A resource for automating the work of a certain department.
DB - MySQL
Beck - PHP (Yii)
Front - JS + JQuery + Backbone
Human resource is not limited. The company has everything. (to simplify)
Can you use this or a similar example to explain how to plan iterative development? Let's say we have already received both the technical specification and the design and everything that is needed. How to form a team for a project? How to break everything into stages? (and who should do it?) How to evaluate the stages by stacking tasks? How then to lead the project according to the iterative model?

Answer 1

1) Beat TK on puzzles.
2) Evaluate each problem in hours / hares / story points.
3) Pull out as many tasks for the sprint as you think you can.
4) After 3, 4 sprints, you start counting the velocity of the team and get the project completion date. For example, like this: mnogosdelal.ru/slidecasts/project-estimation
5) You are horrified, look for methods to increase velocity.
Of course, the answer is not to all questions, but still.