Epic vs Story vs Task - Jira Tutorial

Epic vs Story vs Task - Jira Tutorial
Hey Guys, Anatoly here! ✌
Are you stuck with your JIRA ? Lets sit down for an hour or two, so I can unblock you!!!
Book Here: 329ew4w8zo3.typeform.com/to/f...
❤ Anatoly
In this tutorial, we will learn the difference between epic, story and task in JIRA.
--- What will be covered
00:00 What this is all about
00:43 Defining "Epics" and its function
01:15 Showing a "Scrum Project"
01:46 Creating an epic
01:56 Filling in the details
02:45 Choosing a sample story
02:53 Clicking the "Show More" option
03:02 Selecting "Epic Link"
03:08 Selecting the created sample epic
03:26 Showing another example
04:02 Opening the epic link view
04:22 Explaining different features and functions within an epic
06:00 Creating a "Sub Task" of a story
06:35 Creating another task
06:57 Showing "Backlog" view
07:20 Explaining the difference between Tasks and Stories
09:13 Schedule a meeting with Anatoly 1 on 1
Want to learn JIRA in 1 day? Join my JIRA FOR BEGINNERS COURSE! It is worth it! drive.google.com/drive/folder...
--- Related Videos to check out:
Bulk Create Jira Tickets from CSV: • Bulk Create Jira Ticke...
Epic vs Story vs Task in JIRA: • Epic vs Story vs Task ...
How to Move Issues between Projects: • Move Issue between pro...
How to Log a Bug in JIRA: • Jira tutorial - How to...
How to Use Labels in JIRA: • How to use Labels in Jira
How to see All Issues I am Watching: • Show All Issues You Wa...
How to Convert Subtask into a Story: • Convert Subtask into S...
How to Convert Story into a Subtask: • Convert Story Into Sub...
How to Clone an Issue: • How to Clone Issues in...
--- Stay in touch:
Want Anatoly to help your business? defineagile.com
Connect on Linkedin: / anatolyspektor
Connect on Facebook: / defineagile

[@PillarFitness]

Anatoly, that's was really helpful. I like the way you are producing these videos. well done!

[@defineagile]

Thank you for your feedback!

[@tupuranisrinivasa8608]

Thank you, you explained the concepts (EPIC/ Story/ Task and Subtask) very well easy to follow and put in practice..

[@defineagile]

Thank you for kind words!

[@doit4luv1]

I appreciate your beautiful way of explaining it all. I am glad to be an agile project manager with scrum master certification.

[@defineagile]

Thank you for the complement, means a lot!

[@drawmaster77]

I finally understand... been an sde for a decade could never clearly get this, thanks

[@defineagile]

I am glad it helped!

[@santiagovgb]

Thank you! This was very helpful. I really like how easily you explained it.

[@defineagile]

Thank you

[@FatenAbilmouna]

Wow, I seriously appreciated this video. Thank you for making these!

[@defineagile]

Thank you Faten for taking time and leaving a comment - means a lot!

[@carmiabramowitz3621]

Thank you! This was a great explanation - very clear.

[@defineagile]

Glad it was helpful!

[@stevencrays8930]

Hi, I have a Project Coordinator phone screening and needed to learn the basics of JIRA. Your videos were perfect for bringing me up to speed quickly. Thank you.

[@defineagile]

I am glad it helped! Good luck with your screening!

[@Amelica1234]

Thank you so much. 😊 My team was having a hard time writing Jira, and your video helped me a lot!

[@defineagile]

Glad I could help!

[@rafaelmacedo2210]

Excellent! Tks so much for sharing.

[@defineagile]

Thank you for taking time and writing a comment!

[@dominped23]

Thank you so much, I followed along your video and was doing as I was in jira!

[@defineagile]

Thank you for the feedback!

[@nadimsl]

bro.. .you are amazing ,, u explained Jira in 10 minutes !!!!! kudos

[@defineagile]

Thanks!

[@KostiaVasylenko]

Thank you for the great content!

[@defineagile]

Thank you for taking time and commenting - means a lot!

[@shivanishetye1389]

Thank you so much. This really helped me out to revise before my interview.

[@defineagile]

Thank you for kind words !

[@simonanuvoli3741]

Thanks for sharing this content! You were very clear :)

[@defineagile]

Thank you I appreciate it!

[@defineagile]

Hey Guys, Anatoly here! ✌ Are you stuck with your JIRA ? Lets sit down for an hour or two, so I can unblock you!!! Here is how to get yourself in my calendar: 329ew4w8zo3.typeform.com/to/f4AcheqX? ❤ Anatoly

[@carolinerichardson1743]

Thank you! This was helpful

[@defineagile]

You are welcome!

[@ianchong7422]

thank you for sharing. it is useful for me.

[@defineagile]

Thank you for watching and taking time to write feedback

[@malikasalikhova5342]

Thanks a lot!

[@defineagile]

You're welcome!

[@igordzhenkov5860]

Great! Thank You👍

[@defineagile]

You are welcome Igor! Quick ask, if you have 3 minutes: I am trying to figure out how to add even more value and eventually monetize my content. If you did get value from this video it would mean a lot to me if you could spend 3 minutes filling out this survey : 329ew4w8zo3.typeform.com/to/Qyp39hQl (I really do read and reply to everyone) 🚀 Love, Anatoly

[@LoungeInTown]

Thanks for your nice video! Related to tasks, how do you know what your team can achieve in a Sprint if you don't estimate them?

[@defineagile]

Great question, should make a video on it! Estimation is not needed per se as to know what team can achieve (because estimation is not always accurate), as to know where you are moving sprint over sprint. If you team is mature, and you don't estimate, in planning you agree on Sprint goal (build feature X), then take all the issues related to Feature X and DEMO your work at the end. In this case you don't need estimation. That being said, I am a proponent of estimation, because "what gets measured gets managed". In terms of "How do you know if you can build Feature X in one Sprint ?", Estimation won't answer this question either. Your team needs to make sure to break down the feature into a small chunks and understand what needs to be done in any way.

[@hamedriyahyzadeh8414]

that was fantastic

[@defineagile]

Thank you!

[@nandinishukla12]

What if the PO is writing the requirement in the user story and then BA further refines it and add detailed business rules and more description. When it comes to the agile team, they create multiple tasks in that story because the original story is too big to be done. How to coach PO and BA in such case to write small user stories. For example. If there is a user story about requesting a mortgage increase form with various fields, their validations and at the end a submit button to move to the verification page. Then verification page is another user story. In these stories , developers team creates multiple tasks to work on parts of this user story and then after all tasks are done, QA picks the actual story to QA the entire screen.i.e the main story becomes a QA story

[@yichenshen5002]

Thanks!

[@defineagile]

You are welcome!

[@sharadchandraadepu6178]

Good explanation...

[@defineagile]

Thank you!

[@Middollo]

Thank you.

[@defineagile]

You are welcome

[@jayashreebai518]

Anatoly, can you make a clip for how these start date , end date, time estimations, time tracking will help for reports?? What is the way to follow before and after the sprint start .Thanks in advance :)

[@defineagile]

YES! I should make one more detailed on reports. In regards estimation, search for Burndown Chart video it talks how estimates help there.

[@asindal]

@@defineagile Is it done ?? .. will you please share the video url

[@defineagile]

@@asindal Not yet.

[@m-leanagile9623]

Hello Anatoly, do you still offer classes as per your website? are these recorded or live sessions? I will like to take a course to go over a couple of questions with respect to business values .

[@defineagile]

I do offer currently: 1) Pre-Recorded JIRA course + you can additionally get 1h with me when you checkout 2) Full JIRA/Agile support with packages starting with 10h Would any of this work for you ? Let me know, send an email [e-mail] and lets discuss it further. Thanks for your comment!

[@MortyRides]

Can you advise on something that is similar to Epic, with almost the same purpose or function? I need 2 epics, but as far as i understand only 1 epic can be done a default one

[@defineagile]

What are you trying to achieve ?

[@thiruvel5756]

Hi - Can you advise on the Epic closure / management for release. Instance - Epic 1 has 10 stories and 2 stories are in progress, we are planning to rolling out the EPIC for upcoming release to Prod and with the open user stories shall we rollout to Prod ?

[@defineagile]

Epic can span across multiple releases, for release management JIRA has Releases/Versions functionality, so I won't be worried about not closing up all stories of the epic if that is what yo u are asking ?

[@thiruvel5756]

@@defineagile Yes - You are on the point and thanks for clarifying However based on a few research Release readiness: The Epic must be ready for release, meaning that it has been properly tested, deployed, and is ready for production use. Release dependencies: The Epic should not have any blocking issues, dependencies with other Epics or Features that are not completed yet. Can you shed some light here

[@zhitnick92]

I know English bad, but I understood most of your explanations. Thank you for nice speaking and useful info!

[@defineagile]

Thank you, you are the first person who commented on my English! I am glad it helped! I appreciate you taking time and posting a comment! Means a lot!

[@martinbobak622]

Does your team move stories or tasks or both across the 'In progress' ,' Test', 'Done' pipelines?

[@defineagile]

Storied and Tasks. Sorry for late reply Martin.

[@vidcreatorlondon]

Is it possible to convert an Epic to a Story? And is it possible to create a higher level hierarchy above epic. Like a Grandepic?

[@defineagile]

Yes, will be releasing this video in the next 7 days, stay tuned

[@patricioibarrag]

Hi Anatoly, if user stories and tasks are at the same hierarchy level when you create sub-tasks for both types of workload, how can you track the progress of each sub-tasks to see how team members are performing? It seems Jira don¿t allow you to monitor sub-tasks in reports, which is something super bad because you can't understand how each team member is performing individually.

[@defineagile]

When you say tracks, what metrics do you mean ? If you are talking about where exactly in the process it is - it is visible on the swim-lane, if you are talking about reporting - yes sub-task are pretty bad with that. My recommendation is to avoid using subtasks, and use more granular stories, one story picked up by one team member, estimated separately, and if they are linked, I would rather use "link to" option.

[@defineagile]

I want to also mention that in this video I refer to TASK as issue type not a subtask.

[@patricioibarrag]

@@defineagile I mean time tracking for example

[@defineagile]

@@patricioibarrag Yep time is calculated based on main story not the subtasks. So I do recommend use smaller stories instead of subtasks.

[@adonisme2k284]

Thanks for sharing - indonesian guy

[@defineagile]

Thanks

[@derfvergara]

Should I add tasks to Epic or should it only contain Stories?

[@defineagile]

There is no right or wrong answer here. You can add tasks to epic if you want to track all the extra non-business-value related work. I personally usually have stories and bugs in the epics.

[@drawmaster77]

@@defineagile it would make sense that every task should belong to a story then? Since if it's not part of any story what value does it add?

[@defineagile]

@@drawmaster77 Great question! There are Tasks and there are Subtasks. Task does not bring business value, but it is something that just has to be done. Example - have a process meeting - it might not belong to any story and does not bring direct business value, but you want to capture it. Subtask - is the way to break down story functionality into smaller pieces, in that was subtask belongs to a story. In the case of Subtasks, you still estimate the main Story. so Story brings business value not Subtasks. Hope that make sense.

[@drawmaster77]

​@@defineagile so then tasks and stories would have point value, but not subtasks?

[@defineagile]

@@drawmaster77 I would not put story points to either Tasks or Subtasks - because they do not bring the business value. I would still have them on the board so that you can track your non-business value activities. Some teams DO estimate Tasks because they want to include those tasks in the velocity. It is a preference. I prefer for all the story points represents only business value for stakeholders. Hope that helps!

[@ryanjohnson8659]

How do you define bugs vs tasks?

[@defineagile]

Need a video on this !!! Thanks for reminding! Bug is a regression - we built something and this something has an issue. Task is just a unit work that does not bring business value.

[@bhavanar7783]

Can anyone tell me what is epic story and issue in one line

[@defineagile]

Watch the video carefully and you will be able to figure it out yourself.

[@ConstantinDeliu]

@@kaspergyselinck4846 Tasks also can have sub-tasks. There is only a difference is on how you agree to use to use them on your team. Frequently stories are used for business value tasks. Tasks are used for behind the scenes tasks, like analysis or setting up a java project etc.

[@Christopherney]

Difference between story and task is not clear at all! Sounds like Story is purely a task, but just renamed to mimic Agile ?

[@defineagile]

Main difference as i pointed out Business value vs no business value. You estimate stories, not tasks. Not sure what you mean by renamed - renamed from what ?

[@janeburo4718]

I can't download the book after i paid for it

[@defineagile]

can you please write to [e-mail] we will resolve it immediately, it seems like there is an issue with our book provider today, I got message from 2 people already, we use Clickfunnnels and their service for this does to work today. Just send an email I will send you all info. It should be fixed in the next 12 hours as per our provider.

[@defineagile]

This has been resolved.

[@OliverGuildford]

Great video, apart from @8m20s ... story points != Business Value (www.scrum.org/forum/scrum-forum/30955/story-points-and-business-value-are-related-or-not)

[@defineagile]

Thank you for your comment, and for including link to a Scrum.org forum where people are debating this. In many of my teams (and not all of them following Scrum either), we are treating Story Points as Business value and it works great for us.

[@cuybueno]

You are confusing tasks with sub-tasks.

[@defineagile]

Am I ? :) Why?

[@cuybueno]

@@defineagile Because you use the terms task and sub-task interchangeably. In Jira, they are two different things. Sub-tasks can be created under a User Story, but tasks are created at the same level as the Story.

[@defineagile]

@@cuybueno In this video I have shown both how to create and what are Tasks and Subtasks, but thanks for your feedback.