I'm curious. When people ask you about the differences between Epic, Story / Tasks, and Subtasks, how do you answer them?
Are you talking about time tracking? t-shirt size? Story points vs work logs? Feedback loop with users? Roles and responsibilities?
Interesting. I like your feedback,
In many situations, I often use the following criteria to explain what's a "larger chunk of work": Epic = Related to a specific budget account (we can define in Tempo). Used at the management level
Then, the use of Epics makes sense also for traditional projects :-)
What do you think about that?
I talk about how Epics are a container/grouping that can be reported on and typically spans multiple sprints. Epics could track project phases, specific product functionality or any other way of categorising work.
Stories/tasks is the standard issue type representing work that needs to be done typically sized to be able to be completed in a single sprint (for development or internal work). The assignee may change while the issue is being worked on.
I have rarely used sub-tasks, but when I have they have been for a task that needs to be repeated in multiple environments or for multiple customers so the workload can be shared.
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.