Granularity: Epics, Stories and sub-tasks?

I'm kicking off a new project, it's my first real agile project. Right now we have 4 epics. One of them is "Account System". Under that, I have a few stories like "As a user I need to be able to login". Each of the stories has sub-tasks like "Design login page", "Create Account Database", etc.

One of my problems is that I'm using JIRA and sub-tasks do not show up on the backlog. In general, I just don't know how granular to be. What would everyone recommend to categorize the "Account login" scenario? (Here is a breakdown of some example tasks)

└ Account System
   └ "As a user I need to Login"
      ├ Design login screen
      │ └ Add "save password" checkbox
      └ Design account tables

I'm starting to think the story needs to be the epic and the two design tasks need to be "tasks" with the checkbox as a sub-task. This would mean a lot more epics. I assume that's okay?

Any input would be GREATLY appreciated.

1 comment

Thomas Schlegel Community Champion Jun 27, 2017

Hi Scott,

my opinion of this is:

an epic is defined as something that lasts longer than one sprint. It is a container for stories.

Stories should be ready within one sprint. You plan your sprint with stories, they have storypoints for estimation.

A task is part of a story. In my opinion, a task should be done in a very short time (one day), they are not estimated as stories are. The storypoints of a story should contain the efforts of all the subtasks.

That's why I think, tasks don't have to be in the backlog. There you plan your stories for the next sprint. Adding every task would result in a big, confusing backlog.

So, I would design your issues like that

  • Account System (Epic)
    • Design Login Screen (Story)
      • Add checkbox (task)
    • Design Account tables

OR

  • Account System (Epic)
    • As a User I need to login
      • Design login screen
      • Design account table

I think, "Add checkbox" is a little bit too small for a task.

 

Comment

Log in or Join to comment
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,305 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot