Great video in nuggets for easy understanding. I just wanted to add that the logic of prioritisation here has been subjective but the technique demands that as BA we base it on objective facts. The center of the exercise of prioritisation has be the customer and the value it brings to them. With that in mind I think login and registration should be deprioritised since customer should be able to book the ticket as a guest user just using their email address. This way the time allocated to build and deliver login and registration can be swapped to bring make payment and select seats thereby offering more value to customer and much better customer experience. Thanks
Excellent explanation, content as well as appropriate examples. Through your video we are learning much. It shows, you are really being a Perfect BA Thanks for sharing your knowledge with free of cost. Keep it up good work
Hi , this is a really good video,I just want to give my view on Rank technique you explained,I felt it is incomplete specially when you have to apply for large scale projects you need to check on Dependency and Dev efforts, summation of Business value ,Dev Effort and Dependency and averaged gives the right rank,due to space constraint I can't comment on cost of delay in the above explained ...I suppose you got my point and good to see a New video in depth related to this.. Thanks for such good videos-Neeraja
About Kano Analysis: It is represented with a graph (level of implementation on x-axis and satisfaction on y- axis) and there is Kano survey as well to gather this information. My question is how this technique is used with the survey results and graph in reality?
Great video... May be I'm missing the point but wouldn't registration be a should and not a must... One can always search for a seat and book it without being registered?
very good and nicely explained. one observation is make payment option should be Must have and Ranked same as Book tickets in previous slides as both these tasks are sequential.
Thanks for the video. These techniques make more sense while developing a new application or for a major program. Please suggest how to utilize these techniques in relation to ongoing minor enhancement or fixes, with examples. Do we any other technique focusing this area?
Thanks Karthick for watching the video and for your comment. The same techniques can be used for minor enhancements and bug fixes. the main idea is to prioritise the items which deliver the highest business benefit. I would recommend using the 'ranking' technique and asking the business stakeholders to rank on highest business benefit. That should really help.
This is extraordinary. I had the pleasure of reading something similar, and it was truly extraordinary. "The Art of Saying No: Mastering Boundaries for a Fulfilling Life" by Samuel Dawn
After reading from many sources found this channel is the most effective, easy to understand and grasp the knowledge.Thanks for the content designed so beautifully🙏😍
Quick question......... When writing Prioritise requirement documentation, can you write down only the must have requirements or you need to included all 4 ?
So in scenario where I must create a social media platform which allows people to chat with family and also ask for if they need it, what are the priorities requirements
@@tloulehlohonolo06 I think For Social Media you should be able to connect to the family / members so that will come as Must where as Chat is also equally needed but can be marked as Should based on the time as you will have workaround
If you have 100-150, then first round of classification is to use, High, Medium , Low and lets say we have 50 highs on those, we have to use the ranking method.
@@ThePrefectBA Thank you very much for your suggestion! You are the second person who mentions the amount of 50 requirements as a "magical border" for the stakeholders to understand at once!
Technique #4 can be used only when you're using agile methodology, right? In agile methodology, would anyone use other techniques such as MOSCOW and Ranking?
Yes, in Agile, Ranking technique could be used efficiently. While you have a ready product backlog and u need to plan sprints then u must have user stories prioritised or ranked by the Product Owner, as per the value to the customer, in the product backlog so that you can pull them to the sprint backlog according to your Velocity and ultimately per the agile principle, the highest value could be delivered to customer early.
![Process Mapping in [2 STEPS ]](http://i.ytimg.com/vi/4W-vLESAhoo/mqdefault.jpg)
![Process Mapping in [2 STEPS ]](/img/tr.png)
I guess this is the only youtube channel which explains in depth 👌👌❤️ thank you for putting your efforts to make it so clear 😀
Thanks a lot for the feedback 😀
200% agree. I was searching and just clicked looking at the thumbnail
Great video in nuggets for easy understanding. I just wanted to add that the logic of prioritisation here has been subjective but the technique demands that as BA we base it on objective facts. The center of the exercise of prioritisation has be the customer and the value it brings to them. With that in mind I think login and registration should be deprioritised since customer should be able to book the ticket as a guest user just using their email address. This way the time allocated to build and deliver login and registration can be swapped to bring make payment and select seats thereby offering more value to customer and much better customer experience. Thanks
I dont know how to thank u ... u people are great ... really doing great job ... thank u very much ...
Thank you so much 😀
So far all vedios are best to study BA..keep going ......keep posting.. .looking forwrd fr more !!!!!!😊😊😊😊😊😊
Was very helpful. Clear understanding presentation.
Thanks for the feedback 😀
Excellent explanation, content as well as appropriate examples.
Through your video we are learning much. It shows, you are really being a Perfect BA
Thanks for sharing your knowledge with free of cost. Keep it up good work
Thanks a lot for the feedback 😀
Please make a video on the case study of cab-booking application. This one's really helpful for me as a novice. Thanks
Great explanation.. Amazing video
Thanks for the feedback 😀
Great Video. very useful for beginners as well people trying to change the role to business analyst . thanks a lot for the video.
Thanks for the feedback 😀
Can we say that we must limit the excitement factors while using kano model as including more excitement factors can cause Scope Creep?
Hi , this is a really good video,I just want to give my view on Rank technique you explained,I felt it is incomplete specially when you have to apply for large scale projects you need to check on Dependency and Dev efforts, summation of Business value ,Dev Effort and Dependency and averaged gives the right rank,due to space constraint I can't comment on cost of delay in the above explained ...I suppose you got my point and good to see a New video in depth related to this.. Thanks for such good videos-Neeraja
Simply one word "Excellent"!!!!!!
About Kano Analysis: It is represented with a graph (level of implementation on x-axis and satisfaction on y- axis) and there is Kano survey as well to gather this information. My question is how this technique is used with the survey results and graph in reality?
Great video... May be I'm missing the point but wouldn't registration be a should and not a must... One can always search for a seat and book it without being registered?
Very well explained. Thank you soo much :) Cheers!
This is the best place to prrepare for BA interviews , it would be nice if you could add videos for FRD , BRD etc
Will upload soon
very good and nicely explained. one observation is make payment option should be Must have and Ranked same as Book tickets in previous slides as both these tasks are sequential.
Thak you so much its great work, kudos to you ...way to go ...
Thanks Kalyan
Registration can be de prioritised, as booking can be done without it as well, at the checkout counter, app can request for a PII
Thank you for uploading these videos. I did not find link for free Jira Trial. Can you please send again?
Please make vedio on healthcare BA
Thanks for the video.
These techniques make more sense while developing a new application or for a major program. Please suggest how to utilize these techniques in relation to ongoing minor enhancement or fixes, with examples. Do we any other technique focusing this area?
Thanks Karthick for watching the video and for your comment. The same techniques can be used for minor enhancements and bug fixes. the main idea is to prioritise the items which deliver the highest business benefit. I would recommend using the 'ranking' technique and asking the business stakeholders to rank on highest business benefit.
That should really help.
@@ThePrefectBA Thanks for the response. Appreciate it.
Please share a case study on Insurance process example
Really very good vides , coverings all points with scenario. Thank you.
Thanks for the feedback 😀
This is extraordinary. I had the pleasure of reading something similar, and it was truly extraordinary. "The Art of Saying No: Mastering Boundaries for a Fulfilling Life" by Samuel Dawn
Amazing content....i requested a video related o FRD creation from scratch..hoping to see it in upcoming episodes
Thanks Sahil,yes we would be posting the video on FRD shortly in one of upcomong episodes
Excellent content
Thanks for the feedback 😀
could u do business case video for real estate leasing?!
Sorry. We don't have domain experts
After reading from many sources found this channel is the most effective, easy to understand and grasp the knowledge.Thanks for the content designed so beautifully🙏😍
You are most welcome
Also please create videos on wireframing as well.
Sure , added to our list. Thanks for suggesting the topic
Thanks for clarifying so easily..can we have some your website from i can make some useful notes ?
Another great job.
Thanks again!
Thank you for this video!
Glad you liked it
Quick question.........
When writing Prioritise requirement documentation, can you write down only the must have requirements or you need to included all 4 ?
We need to have the requirements listed and then we do the prioritization process as explained in the video
So in scenario where I must create a social media platform which allows people to chat with family and also ask for if they need it, what are the priorities requirements
@@tloulehlohonolo06 I think For Social Media you should be able to connect to the family / members so that will come as Must where as Chat is also equally needed but can be marked as Should based on the time as you will have workaround
Where is Priority Groups technique is discussed?
Great video!
Thanks for the feedback
Is the ranking method suitable for non-functional requirements and an overall amount of around 100-150 requirements? What are your experiences?
If you have 100-150, then first round of classification is to use, High, Medium , Low and lets say we have 50 highs on those, we have to use the ranking method.
@@ThePrefectBA Thank you very much for your suggestion! You are the second person who mentions the amount of 50 requirements as a "magical border" for the stakeholders to understand at once!
if possible please share demo documents ... for each content ...
Just to be clear everyone. The W stands for Will Not have, not ‘Would Have’…
excellent
Thank you! Cheers!
Useful 👍
Glad you liked it
Technique #4 can be used only when you're using agile methodology, right? In agile methodology, would anyone use other techniques such as MOSCOW and Ranking?
Yes, in Agile, Ranking technique could be used efficiently. While you have a ready product backlog and u need to plan sprints then u must have user stories prioritised or ranked by the Product Owner, as per the value to the customer, in the product backlog so that you can pull them to the sprint backlog according to your Velocity and ultimately per the agile principle, the highest value could be delivered to customer early.
Take Case study for Insurance or Banking & Finance App
Agreed, request you to plz share a case study based on Insurance or banking if feasible.