When should I create a subtask ?

Baijia Chen

Hi everyone, our team is applying Epic -> Story/Task -> Subtask workflow

Recently I got requirements from our Program Team to create the sub-task (even just a blank sub-task) for each story even the story is a small story point ticket (i.e. a UI bug fix). They said it is a good way for task tracking?

Based on my understanding, the sub-task usually is applied to a complex task (high story points) or a task that needs to be worked on by multi teammates.

It makes me confused about the definition of the sub-task function. 

Jack Brickey

I don’t believe there are any rules. Personally I only create sub tasks if I feel the task story isn’t clear or the sub tasks will be done by different folks. Another example might be: document the story, implement the story, test the story. Keep in mind that if using scrum/sprints the story should be completed within a single sprint, otherwise the story should be broken into multiple stories not sub-tasks.