Many problems with this: a Business Analyst is analysing product functionality instead of the User. By the time I got to 5:38 I had to stop. While you might want to capture 'Requirements' in the theme, that is where they stop. The whole point to Agile working is to focus on User Value which is an experience based thing, not a functional thing. Now the requirement could be "I want a great User Experience", so the next step is to map out the User Journey, activities or goals they want to achieve and we use Epics for that, therefore when a goal is achieved, as decided by the user's experience, the Epic is complete or Done. We break that Epic goal or activity into actual User Steps that the user wants/needs to perform in order to get to that goal, or complete the activity. Those steps turn into User stories. So far the User Journey and Steps are only giving better definition to the problem(s) to be solved, i.e. the Problem Space. Then we have Sub-tasks, or better if named developer tasks, which are where the team define what they will add, change, remove, test, document, etc. to enable the User (step) Story to be fulfilled. The Sub/Developer tasks describe the solution, i.e. the Solution Space. There are no Design sub-tasks, because design is done in refinement and/or sprint planning meetings. In other words it is a phase the User Story goes through in getting it ready for the sprint. So to the detail post 7 minutes in your video 'Cash Payment' and 'Online Payment' might be requirements but they are not the user journey. The journey might be 'Browse Tickets', 'Search for Tickets', 'Order Tickets', 'Pay for tickets', 'Receive tickets'. Each of these is a User Goal, not a System Feature or Function. When you start talking about system feature break down it detracts from User Value and Experience and sounds like you are using agile tools to mask the fact that you are working in a manner kin to waterfall Work Breakdown Structures. Business Analysts need to be User Analysts, because that defines the 'Subject' of the analyst activity, the User, not the Business.

Thank you and it was nicely explained !! appreciate it.

Hello, i appreciate the work done here. Do you have any concise study material explaining the basics and stuff in proper manner. With lot's of sample user stories.

Appreciate the simplicity of explaining the topics ❤ Would be really helpful if you could provide us real time exampls and documentation. You could make a series with a sample project.

Thanks a lot.... Understood very well.... Very practically explained.... God bless u

You are doing great work

Great, thank you

Liked examples. More examples would be great in demoing decomposition.

I appreciate your efforts. It will be great If make video specific to industries of Specific like Health care, Banking. thank you so much.

you are doing great job... I basically from Non IT background and looking to get into BA role. Appreciate all your efforts. how can we approach you for any questions??

Can you please make a video on Wireframing software Axsure & REST & SOAP API in terms of BA.....I like your videos they are up to the marks and easy to understand for non-IT & who are trying to get into BA roles.....thanks and keep up the good work buddy........

Hi ,thank you for explaining so well , would appreciate if you could share another example for "Epic vs User Story vs Task"

on scrum board, it's not easy to view the embed relationship b/w US & task as it can with US & subtask

Where does feature fit in this?

Thank you

Hai sir pls provide jira administration work plan n videos

Can you do one video on the common competency based questions

Thanks you

could please share link or make video on below points • Creating user stories for requirements • Dissecting EPICs into small user stories. • Creating flow chart with MS Visio • Creating BRD, FRS, documents.

How it is different from Theme Intiative Feature Story Task

Can we link one epic with another epic?One user story with another user story and task to other task in JIRA?

Is feature part of epic?

Nice

great explanation. be a little fast

Feature missing