...
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.
Time Planning Method
We distinguish a top-down time budget and a bottom-up time budget.
...
When doing the planning and when showing plan values, we distinguish two kinds of values:
| Planning Values | Description | Remarks |
|---|---|---|
| generic | plan-values directly entered on this level, you set this value | possible for components and project; on task level, this is simply the JIRA work estimate |
| calculated | time is retrieved from lower levels, you see this value, but can't set it | this is a value calculated by ictime from available data on the next-lower level according to the logic explained below |
Depending on the level (project, component, task) you are working on, these values have a slightly different idea:
| Level | Value | Description |
|---|---|---|
| Sub-Task | generic | JIRA work estimate on sub-task level |
| calculated | n.a. | |
| Task | generic | JIRA work estimate on task level |
| calculated | n.a.* | |
| Component | generic | |
| calculated | ||
| Project | generic | |
| calculated |
...
| Expand | ||
|---|---|---|
| ||
In fact, JIRA calculates the work estimate for a task as sum of work estimates of all sub-tasks + the work estimate for the task itself; but from ictime planning point of view, this is not a calculated value, as in our project time planning sheet, we do not show the sub-task level, but our starting point is the JIRA work estimate result on task level. |
Have a look at the following example:
...