nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to know the workload of team members during a sprint when using sub-task?

Christophe Fruytier

We are starting using sub-task and we noticed that the original estimate time per team members is not right. It doesn't take into account sub-task assigned to the team members.

It seems that the estimate time at sub-task level is not added to the workload of the team member who is assignee of the sub-task but well to the assignee of the task.

Are we using the sub-task in a wrong way?

We are a dev team working on multiple projets per sprint.

Thank you

Capture d’écran 2018-02-06 à 09.43.32.png

Accepted answers

All comments

Thomas Deiler_db00h3

Dear @Christophe Fruytier,

this question was asked in similar way. Please read following posts:

Points per story (accumulated from sub-tasks)

Burndown charts in Jira ?

Analysis for Epic workload?

Was your question answered? If not how can I help you further?

So long

Thomas

Christophe Fruytier

Wow! Thanks @Thomas Deiler for these related posts. I see that we are still far to be a full scrum "compliant" team :-) but we work on it.

I understand that we have to work with SP and avoid as much as possible to work with time. Ok. But let's say that we have a sprint of two weeks. We have 10 tasks to do and the team agree to do it. It's easier than expected and everything is done in 8 days. How do you advice to complete the two days? Do we have to alterate the sprint scope?

Another question to be sure, if I understand well, it's impossible in Jira, based on original estimate time at task and sub task level to know the workload in time per team member per sprint (at least if we used subtask)?

Thomas Deiler_db00h3

Dear @Christophe Fruytier,

I understand that we have to work with SP and avoid as much as possible to work with time. Ok. But let's say that we have a sprint of two weeks. We have 10 tasks to do and the team agree to do it. It's easier than expected and everything is done in 8 days. How do you advice to complete the two days? Do we have to alterate the sprint scope?

When you backlog is well prepared, the team can pull from the top the next story (or task, that' just naming) to complete. But they will not commit to the changed scope. What is really finished in 2 days will count to the velocity. This means that the product owner has to agree that the additional stories are really done. Half ready stories are not counted.

Retrospective: Next step is to clarify the reason, why the team overestimated the stories. Was there some information missing? Was this a stomach estimation? Let them learn and improve to be next time better.

Another question to be sure, if I understand well, it's impossible in Jira, based on original estimate time at task and sub task level to know the workload in time per team member per sprint (at least if we used subtask)?

Sure you can do. If you are using the built-in work log mechanism, you can track the workload. But for agile teams, this doesn't make sense.

So long

Thomas

Thomas Deiler_db00h3

Dear @Christophe Fruytier,

your didn't answer yet - are there still questions?

So long

Thomas

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira