sub-tasks are not visible on backlog

Question

Have spent some time trying to figure out this with no success....

Here is the case :

* board filter/query shows sub-tasks
* canban board shows sub-tasks
* sub -task belongs to story
* for all sub-tasks and parent story :* assigned to the sprint
* assigned to a team member
* having same component
* having same project

And yes, I have tried the following with no success:

* changing swimlanes grouping
* adding sub-tasks to card layout
* changing board query to filter on only sprint id or one project
* changing query to include only component

Any idea that can help me solve this?

Fernando Trindade_9u4wxc · Answer

Even though people say "Sub-tasks have no place in Scrum backlog", they do.

For example, when you are assigning sub-tasks to developers and you are planning future sprints, it is nice to get a view on who is taking the subtasks. For example I wanna know IN THE BACKLOG, what is the "load" for a certain developer. Having that available in the backlog is nice because we can IMMEDIATELY see and have an idea on the workload that person will have.

User Stories will be with the PO, Subtasks will be done and owned by Devs and Testers.... So this makes sense.

Nic Brough -Adaptavist- · Answer

Yes, Scrum does not have anything to say about sub-tasks.

That's why they are not sprint items - they're a part of a story, not sprint items in their own right.

Scrum works fine for large companies (certainly better than waterfall) with large stories - remember a part of Scrum is backlog refinement which that includes breaking up stories into smaller parts so they can be completed by the team in a sprint.

Константин Михайлов_z9xv6t · Answer

"Atlassian view of agile" is a correct description. I have no idia on why other community leaders say that Scrum have no place for sub-tasks.

Scrum DO NOT say how you should work with your task and should you or not dismantle a story into several sub-task.

Limiting scrum board to Story only making it useless for companys with big products where you simply can't do a single Story in a regular 2 weeks sprint or if you have to distribute work among team members.