Hi Thank you for the video Had a Few questions Is the As Is state is part of the BRD How do we submit the observations for validation. Is it similar to the Minutes of meetings in a word or excel format Also are the requirements gathered by the means of interview , observation , workshop need to be signed off
It would be great to support your videos with example format /templates for the Final step. Will add more knowledge for the viewers. Your doing a great job !
Thanks R R appreciate your feedback. We are putting together a portal with all reference material and templates. I will provide an update once it is ready .
14.42 you've said that this technique used only for observation and the same as-is captured requirements will be shared to all? How about To-be process? Is it captured or elicited in current session and same will be validated with all? Please help to clarify thanks a lot 🙏
Hello Shilpa Thanks for your question, the observation is commonly used for understanding the as is process. once you have the as is process you can use other techniques like workshop, interview prototyping to meet the stakeholders show them the as is state which you have captured and then elicit requirements on the changes required which will give you the to be state. hope this clarifies
1. The solution should be fully accessible in the English, French and German languages.-general requirement 2. Users should be able to retrieve holiday details by booking reference number.-functional requirement 3.Holiday providers shall be able to add the details, date and prices of their tours directly onto the system.-functional requirement 4. The solution will be able to support up to 2000 concurrent active users.-functional requirement 5.The solution will be restorable from back-up within 4 hours.-non functional requirement 6.The solution should be able to retrieve holiday details within 10 seconds.-non functional requirement Can u please let me know if this is correct.
Helllo Andrey, Thanks for the comment. When a BA starts the project , below are few steps to kick start the process. 1. Have a discussion with the project sponsor to understand what is the outcome which is expected. 2. The outcome and nature of project helps to decide the approach. waterfall , agile, process improvemeny initative etc... 3.Next is to identify the impacted stakeholders first off getting the initial list from sponsor and also using various techniques to identify all the impacted stakeholders. 4. Once you have identified the stakeholder then the next step is to schedule the requirement gathering sessions using various techniques like workshop, interview, observation etc.... 5.from then on it is an iterative process to gather , document the requirements and getting the requirements devloped, tested and deployed. Hope this helps. Cheers
One of the requirements of a new accounts management system is that it must allow users to scale the size of text on the screen. The requirement states that the text can be reduced to 10% of normal size and increased up to 500% of normal size, depending on the preference of the user. What would this requirement be classified as? general or non functional? Can you please let me know this? Thanks in advance.
Hi! Can you let us know what should we answer when the interview asks what are the challenges we have faced in project being in a BA role
Hi
Thank you for the video
Had a Few questions
Is the As Is state is part of the BRD
How do we submit the observations for validation.
Is it similar to the Minutes of meetings in a word or excel format
Also are the requirements gathered by the means of interview , observation , workshop need to be signed off
It would be great to support your videos with example format /templates for the Final step. Will add more knowledge for the viewers. Your doing a great job !
Thanks R R appreciate your feedback. We are putting together a portal with all reference material and templates. I will provide an update once it is ready .
hi, great explanation, can you please also prepare videos for RPA business analyst
thank you for making this video. god bless you.
Thank you so much for your wishes and glad you are finding our videos useful
14.42 you've said that this technique used only for observation and the same as-is captured requirements will be shared to all? How about To-be process? Is it captured or elicited in current session and same will be validated with all? Please help to clarify thanks a lot 🙏
Hello Shilpa
Thanks for your question, the observation is commonly used for understanding the as is process. once you have the as is process you can use other techniques like workshop, interview prototyping to meet the stakeholders show them the as is state which you have captured and then elicit requirements on the changes required which will give you the to be state.
hope this clarifies
great video.... so informative...... Can u plss plsss plssss make a video on BRD and FRD creation??
Eagerly waiting for that too....
As soon as possible :)
Hi, thanks for the video...are there any upcoming videos on Business process mapping tools?
Hello Pramod
It is in the plan, will create one tutorial using lucid chart
1. The solution should be fully accessible in the English, French and German languages.-general requirement
2. Users should be able to retrieve holiday details by booking reference number.-functional requirement
3.Holiday providers shall be able to add the details, date and prices of their tours directly onto the system.-functional requirement
4. The solution will be able to support up to 2000 concurrent active users.-functional requirement
5.The solution will be restorable from back-up within 4 hours.-non functional requirement
6.The solution should be able to retrieve holiday details within 10 seconds.-non functional requirement
Can u please let me know if this is correct.
Hi! Thank you!
Can you tell about what should do BA when he start to new project?
Maybe you met the description in the BABOK or anywhere?
Helllo Andrey,
Thanks for the comment. When a BA starts the project , below are few steps to kick start the process.
1. Have a discussion with the project sponsor to understand what is the outcome which is expected.
2. The outcome and nature of project helps to decide the approach. waterfall , agile, process improvemeny initative etc...
3.Next is to identify the impacted stakeholders first off getting the initial list from sponsor and also using various techniques to identify all the impacted stakeholders.
4. Once you have identified the stakeholder then the next step is to schedule the requirement gathering sessions using various techniques like workshop, interview, observation etc....
5.from then on it is an iterative process to gather , document the requirements and getting the requirements devloped, tested and deployed.
Hope this helps.
Cheers
@@ThePrefectBA thanks you!
Brilliant 👌👍
Thanks Sahil
One of the requirements of a new accounts management system is that it must allow users to scale the size of text on the screen. The requirement states that the text can be reduced to 10% of normal size and increased up to 500% of normal size, depending on the preference of the user.
What would this requirement be classified as? general or non functional? Can you please let me know this? Thanks in advance.
In my view it is a functional requirement
@@ThePrefectBA thank you so much for your answer.
Great.
Thanks for the feedback 😃
Could you please create a video on Used case Vs. User's Story.
Thanks Vikash for the comment.
We will definitely create one and post it as part of the weekly video series
Hi Vikash,
As requested , Please find the video on Use case Vs User story below
ruclips.net/video/UtV_gXkkX80/видео.html