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
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.
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
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
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.
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 ?
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 ?
@@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
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 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 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!
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 .
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!
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 :)
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.
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.
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
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 ?
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)
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.
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.
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.
@@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.
@@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.
