...
| Level | Generic | Calculated | Remarks |
|---|---|---|---|
| Task A1-01 | 5h | We have made a work estimate of 5h. | |
| Task A1-02 | 10h | We have made a work estimate of 10h. | |
| Task A1-03 | 10h | We have added this task and have made a work estimate of 10h. | |
| Component A1 | = 25h | We have deleted the generic value for component A1, as we have decided that the detailed planning for tasks of this component is ready now. So we only have a calculated plan value for this component of 25h from task level (doing the detailed plan on task level, we also realised that 30h was to much). | |
| Task A2-01 | 10h | ||
| Task A2-02 | 25h | ||
| Component A2 | =35h | We have deleted the generic value for component A2, as we have decided that the detailed planning for tasks of this component is ready now. So we only have a calculated plan value for this component of 25h from task level (doing the detailed plan on task level, we also realised that 20h was not enough). | |
| Component A3 | 10h | We have planned 10h for component A3. No work estimates for tasks yet, so still no calculated value. | |
| Projekt A | = 70h | We have deleted the generic value on project level, as we think that planning for components is now okay and reflects the overall time budget we will need. So we have a calculated value of 70h from component level, and big parts of that planning value is a result of work estimates on task level. |
...
| 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. |
Setting Plan Values
Work Estimates
Component
Project
Target/Actual Comparison
SS XXX