1

Topic: Partition of the ready project on stages \iterations

Hello! The new small project got to me.  this project it is made in Microsoft Project under the classical approach: on products and its components. 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. Who has an experience how it is more convenient for implementing in MS Project? Whether It is necessary to alter structure of operations for this purpose?

2

Re: Partition of the ready project on stages \iterations

Hello, es3000, you wrote: E> who has an experience how it is more convenient for implementing in MS Project? I have no wide experience in MS Project. But proceeding from rules of compilation , the logic of new structure arises the such: Level 1: Products. Level 2: Stages Level 3: Components. First two levels can be changed in places if finishings in products have to be synchronized on stages. Whether E> it is necessary to alter structure of operations for this purpose? Yes.

3

Re: Partition of the ready project on stages \iterations

Hello, 0x7be, you wrote: 0> I have no wide experience in MS Project And in what there is an experience? In what plans do \trace? 0> but proceeding from rules of compilation , the logic of new structure arises the such: And if this plan not to change, and to make the new plan which is including operations only for the very short step? So do?

4

Re: Partition of the ready project on stages \iterations

Hello, es3000, you wrote: E> And in what there is an experience? E> in what plans do \trace? TFS + the crutches in Excel 0>> But proceeding from rules of compilation , the logic of new structure arises the such: E> And if this plan not to change and to make the new plan which is including operations only for the very short step? E> so do? Yes, so do. Earlier it named planning by a method of "a filling wave", and then decided to name a fashionable word "" If shortly the idea consists that only operations are in details planned for the very short step, and the future stages are contoured only in general. Normally or simply at level of setting of the purposes, or the purpose + a rough estimate. The question only in, whether will be inscribed it in the traditions of planning of projects accepted at you. If at you it is accepted to plan in details all beforehand the heads can and not understand

5

Re: Partition of the ready project on stages \iterations

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.

6

Re: Partition of the ready project on stages \iterations

0> Yes so do. Earlier it named planning by a method of "a filling wave", and then decided to name a fashionable word "" 0> If shortly the idea consists that only operations are in details planned for the very short step, and the future stages are contoured only in general. 0> it is normal or simple at level of setting of the purposes, or the purpose + a rough estimate. Then probably all the same it is necessary to work with two plans. Even it turns out plans there will be not two, and it is more: one plan the general which is formed from the very beginning, and with each new stage will be added one more detailed plan. Then in this connection three questions: 1) How to connect these two projects with each other? There are tools which support such communication "automatically"? Or it is necessary purely manually most attentively to trace what purpose of the general plan "is split up" for tasks in a stage detailed plan? 2) how to assign resources in the general plan? In it there are specific operations on the specific executor, only no purpose? 3) how to consider the general actual expenses under the project?

7

Re: Partition of the ready project on stages \iterations

Hello, es3000, you wrote: E> Then probably all the same it is necessary to work with two plans. E> even it turns out plans there will be not two, and it is more: one plan the general which is formed from the very beginning, E> and with each new stage will be added one more detailed plan. Physically it can be the same plan which extends therein. E> then in this connection three questions: E> 1) How to connect these two projects with each other? There are tools which support such communication "automatically"? E> Or it is necessary purely manually most attentively to trace what purpose of the general plan "is split up" for tasks in a stage detailed plan? I do not see, what for these plans to space apart generally. The plan can quite be one, is simple during each moment of time at it the part of tasks is in details broken into subtasks only. In process of approach of new iterations of their task  on more detailed. E> 2) how to assign resources in the general plan? In it there are specific operations on the specific executor, only no purpose? Purely technically the general plan from the point of view of  it is simple a dial-up  operations. On each operation it is possible to assign some resources. MS Project allows. More interesting other question - for what purpose you want to do it? E> 3) how to consider the general actual expenses under the project? Complete iteration contains all detailed tasks. If in them to fix spent time it is possible to count actual expenses.