It's all about the answers!

Ask a question

planning - show workload as sum of toplevel workitems


Bernd van Oostrum (21724565) | asked Aug 10 '15, 10:33 a.m.
edited Aug 10 '15, 10:53 a.m.
Workload in a sprintplan is calculated as the sum of the estimates of all workitems assigned to an owner, including both parent- and child-tasks.

Is there a way to avoid that the sum of both parent- and child-estimates are used to calculate the load? It should be or the estimates of the children, or the estimate of the parent; not both.


 


One answer



permanent link
Gustavo Reis (13927) | answered Aug 16 '15, 12:00 a.m.
Normally, you will have diferrent levels for parent and child work itens. Parent types will be set as "planning item" and dont have any time measure linked to it. Child types will be "execution itens" and don't will have a "size" attribute as story ou function points.

What work itens types you using? task? activities? stories?

Comments
Bernd van Oostrum commented Aug 16 '15, 12:45 p.m. | edited Aug 16 '15, 12:47 p.m.

Hi @gustavoreis,

We're using 'epics', 'stories' and 'tasks' for high level planning. This planning is done by a seperate team, and the 'task'-workitems are used to be able to plan resources (and see their workload).

In a second step, developers refine the task by creating child-tasks.

The estimation of these child-tasks are added to the estimation of the parent 'task' workitem resulting in wrong loads.

Regards,
Bernd.

 


Bernd van Oostrum commented Aug 16 '15, 12:46 p.m.

Hi @gustavoreis,

We're using 'epics', 'stories' and 'tasks' for high level planning. This planning is done by a seperate team, and the 'task'-workitems are used to be able to plan resources (and see their workload).

In a second step, developers refine the task by creating child-tasks.

The estimation of these child-tasks are added to the estimation of the parent 'task' workitem resulting in wrong loads.

Regards,
Bernd.

Your answer


Register or to post your answer.