...
As a conclusion and to cover both needs, you need to set top-down time budgets on a certain level, and at the same time, you want to use bottom-up time budgets that are derived from a more detailed planning on lower levels. How this can be reached is described in the following paragraph.
When doing the planning and when showing plan time planning values, we distinguish two kinds of values:
...
| Tip |
|---|
Even though it might be difficult to understand in the beginning, it is very simple. It's basically all about the component time planning value. By setting a generic plan value on component level, you decide that this value should be used for calculating the results for the project (top-down approach, not very detailed). By not setting it, you decide that the calculated result for the component (= work estimates for all task/sub-tasks of the component) should be used for calculating the project time budget (bottom-up approach, detailed). |
...
| Info |
|---|
If you don't use components and/or if you have tasks without component assignment, such tasks will be automatically summed up into a "virtual" component provided by ictime in order not to break the logic that all calculated values always need to come from the next-lower level("No Component"). You can't set a generic plan value for this "component" of course, but the calculated value will be considered for the project like it were a real component. This way, work estimates on task level are made available to calculate the planning value for the project without having a real component. |
Setting Plan Values
...