E> I need to break tasks of this project into stages (substeps, iterations) to select operation of the first stage and to launch them in operation. E> who has an experience how it is more convenient for implementing in MS Project? Hardly it turns out to give specific advice about so description abstraction. What is "project tasks"? How much in details they are described? In what type? E> this project it is made in Microsoft Project under the classical approach: on products and its components. The product and components already have a prototype, or this circuit is made "from "? Experience shows that until real operation under the project begins, 80 % of volume remain invisible (for, as an iceberg, under water). However, if you have understanding and desire to go the iterative approach, it makes sense to go here what way: 1. To identify key crucial functionality. Only such without which generally there is no sense to begin. It can be generally 1 screen (or at all command line with 1 command). 2. To make a visual prototype (sketches, sketches, pictures, screenshots - everything if only to understand how it will look), covering __ the functionality described above. 3. To create internal model and architecture sketches. 4. On the basis of points (2) and (3) to create the first iteration. 5. To declare it iteration and to launch in operation.... : to repeat points 1-5, for each subsequent iteration adding the next piece of the most crucial functionality.