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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
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!
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