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
@Amelica12349 ай бұрын
Thank you so much. 😊 My team was having a hard time writing Jira, and your video helped me a lot!
@defineagile9 ай бұрын
Glad I could help!
@nadimsl3 жыл бұрын
bro.. .you are amazing ,, u explained Jira in 10 minutes !!!!! kudos
@defineagile3 жыл бұрын
Thanks!
@doit4luv13 жыл бұрын
I appreciate your beautiful way of explaining it all. I am glad to be an agile project manager with scrum master certification.
@defineagile3 жыл бұрын
Thank you for the complement, means a lot!
@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!
@PillarFitness5 жыл бұрын
Anatoly, that's was really helpful. I like the way you are producing these videos. well done!
@defineagile5 жыл бұрын
Thank you for your feedback!
@tupuranisrinivasa86083 жыл бұрын
Thank you, you explained the concepts (EPIC/ Story/ Task and Subtask) very well easy to follow and put in practice..
@defineagile3 жыл бұрын
Thank you for kind words!
@drawmaster774 жыл бұрын
I finally understand... been an sde for a decade could never clearly get this, thanks
@defineagile4 жыл бұрын
I am glad it helped!
@rafaelmacedo22103 жыл бұрын
Excellent! Tks so much for sharing.
@defineagile3 жыл бұрын
Thank you for taking time and writing a comment!
@stevencrays89304 жыл бұрын
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.
@defineagile4 жыл бұрын
I am glad it helped! Good luck with your screening!
@dominped233 жыл бұрын
Thank you so much, I followed along your video and was doing as I was in jira!
@defineagile3 жыл бұрын
Thank you for the feedback!
@simonanuvoli37413 жыл бұрын
Thanks for sharing this content! You were very clear :)
@defineagile3 жыл бұрын
Thank you I appreciate it!
@shivanishetye13893 жыл бұрын
Thank you so much. This really helped me out to revise before my interview.
@defineagile3 жыл бұрын
Thank you for kind words !
@igordzhenkov58602 жыл бұрын
Great! Thank You👍
@defineagile2 жыл бұрын
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
@nandinishukla125 ай бұрын
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
@hamedriyahyzadeh84143 жыл бұрын
that was fantastic
@defineagile2 жыл бұрын
Thank you!
@zhitnick924 жыл бұрын
I know English bad, but I understood most of your explanations. Thank you for nice speaking and useful info!
@defineagile4 жыл бұрын
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!
@Middollo6 ай бұрын
Thank you.
@defineagile4 ай бұрын
You are welcome
@yichenshen50023 жыл бұрын
Thanks!
@defineagile3 жыл бұрын
You are welcome!
@santiagovgb4 жыл бұрын
Thank you! This was very helpful. I really like how easily you explained it.
@defineagile4 жыл бұрын
Thank you
@carmiabramowitz36214 жыл бұрын
Thank you! This was a great explanation - very clear.
@defineagile4 жыл бұрын
Glad it was helpful!
@KostiaVasylenko4 жыл бұрын
Thank you for the great content!
@defineagile4 жыл бұрын
Thank you for taking time and commenting - means a lot!
@sharadchandraadepu61783 жыл бұрын
Good explanation...
@defineagile3 жыл бұрын
Thank you!
@carolinerichardson17434 жыл бұрын
Thank you! This was helpful
@defineagile4 жыл бұрын
You are welcome!
@LoungeInTown3 жыл бұрын
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?
@defineagile3 жыл бұрын
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.
@adonisme2k2843 жыл бұрын
Thanks for sharing - indonesian guy
@defineagile3 жыл бұрын
Thanks
@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
@ianchong74224 жыл бұрын
thank you for sharing. it is useful for me.
@defineagile4 жыл бұрын
Thank you for watching and taking time to write feedback
@martinbobak6222 жыл бұрын
Does your team move stories or tasks or both across the 'In progress' ,' Test', 'Done' pipelines?
@defineagile2 жыл бұрын
Storied and Tasks. Sorry for late reply Martin.
@malikasalikhova53424 жыл бұрын
Thanks a lot!
@defineagile4 жыл бұрын
You're welcome!
@derfvergara4 жыл бұрын
Should I add tasks to Epic or should it only contain Stories?
@defineagile4 жыл бұрын
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.
@drawmaster774 жыл бұрын
@@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?
@defineagile4 жыл бұрын
@@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.
@drawmaster774 жыл бұрын
@@defineagile so then tasks and stories would have point value, but not subtasks?
@defineagile4 жыл бұрын
@@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!
@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.
@jayashreebai5184 жыл бұрын
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 :)
@defineagile4 жыл бұрын
YES! I should make one more detailed on reports. In regards estimation, search for Burndown Chart video it talks how estimates help there.
@asindal4 жыл бұрын
@@defineagile Is it done ?? .. will you please share the video url
@defineagile4 жыл бұрын
@@asindal Not yet.
@MortyRides3 жыл бұрын
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
@defineagile3 жыл бұрын
What are you trying to achieve ?
@Christopherney3 жыл бұрын
Difference between story and task is not clear at all! Sounds like Story is purely a task, but just renamed to mimic Agile ?
@defineagile3 жыл бұрын
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 ?
@BBB-964 жыл бұрын
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 .
@defineagile4 жыл бұрын
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 defineagile.com@gmail.com and lets discuss it further. Thanks for your comment!
@vidcreatorlondon3 жыл бұрын
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?
@defineagile3 жыл бұрын
Yes, will be releasing this video in the next 7 days, stay tuned
@ryanjohnson86593 жыл бұрын
How do you define bugs vs tasks?
@defineagile3 жыл бұрын
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.
@OliverGuildford4 жыл бұрын
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)
@defineagile4 жыл бұрын
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.
@janeburo47184 жыл бұрын
I can't download the book after i paid for it
@defineagile4 жыл бұрын
can you please write to support@defineagile.com 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.
@defineagile4 жыл бұрын
This has been resolved.
@bhavanar77834 жыл бұрын
Can anyone tell me what is epic story and issue in one line
@defineagile4 жыл бұрын
Watch the video carefully and you will be able to figure it out yourself.
@ConstantinDeliu4 жыл бұрын
@@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.
@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.