Requirements Gathering | Workshop - Gather Requirements in 12 Steps [EP2]

Рет қаралды 87,802

Күн бұрын

Make Requirements Discovery Easy With the below Checklists Which Cover Every Important Question to Ask
bit.ly/BARequirementsChecklist
Download the Requirement Elicitation Cheat sheet (For Workshop, Interview, Observation)
prefectba.getresponsepages.com/
Save time writing professional emails with simple copy paste templates
bridgingthegap.samcart.com/re...
In 10 Minutes you will learn how to plan and run a successful requirement gathering/elicitation workshop.
Workshop is considered as one of the best requirement gathering technique.
You will learn the 3 Phases and 12 Steps with an example to help you plan your next requirement gathering/elicitation workshop.
FREE Business Analyst Training Course : 25+ Video Lessons split across 9 Modules (ranging from requirement gathering, requirement documentation & diagrams to IT Skills and Testing)
• Business Analyst Train...
Commonly asked Business Analyst Questions and answers:
• Business Analyst Inter...
JIRA tutorial for brginners:
• JIRA Tutorial For Begi...
I. Also, learn to gather requirements using Interview Requirement Gathering Technique
kzfaq.info?o=U&ar=2...
Top 10 Elicitation techniques every BA should know :
prefectba.com/blog/top-10-eli...
Icons made by Plainicon from www.flaticon.com

Пікірлер: 34

@morganbryan8045 Жыл бұрын

Really nice overview. All stuff we know we should be doing but it really helps to lay it out clearly and refresh our workshop techniques. Thanks!

@ThePrefectBA Жыл бұрын

Thanks for watching!

@matthewwitter8757 5 жыл бұрын

Very clear video detailing the steps. Thank you!

@ThePrefectBA 5 жыл бұрын

Thanks Matthew for your feedback, we are glad you found this video useful

@silky2204 3 жыл бұрын

Great way to organize the requirements gathering.

@ThePrefectBA 3 жыл бұрын

Yes indeed!

@jagmanak 4 жыл бұрын

can you plz explain JAD sessions. you didn't mention them in elicitation techniques

@sameersiddiqui291 2 жыл бұрын

The content was great, thanks for your upload!

@ThePrefectBA 2 жыл бұрын

Thanks for the feedback 😀

@ameetpatra3260 4 жыл бұрын

Team please make videos on BRD,SRS,Use Case Document with sample examples.

@poojakadakia1763 3 жыл бұрын

I second this

@bhavya3008 2 жыл бұрын

Hello team, Just wanted to know if there are docs which we can refer to later on rather than watching the videos everytime. Also would like to see a video on BRD FRD ,SRS AND their differences with examples.

@hakeemremila1688 2 жыл бұрын

Thanks for this very good explanation.

@ThePrefectBA 2 жыл бұрын

Thanks a lot for the feedback

@preeti4684 3 жыл бұрын

Nicely explained!

@ThePrefectBA 3 жыл бұрын

Glad you liked it 😊

@ferman8397 2 жыл бұрын

yes sound is so low..how long have you been doing BA job ? How long does it take to be a senior BA ? what is companies expectations from BA in the first couple weeks/months ?

@imly9863 3 жыл бұрын

your voice is so low, but very good explanation , i always watch and follow your videos they are quite interesting and helpful thank you so much, a small request can you please do the case study on the healthcare domain i mean taking the healthcare domain examples...please it will be very helpful .

@ThePrefectBA 3 жыл бұрын

Thanks for your feedback, much appreciated. Apologies, we don't have anyone on the team with health care domain expertise and hence we won't be able to make videos related to that domain

@ameradam4605 9 ай бұрын

Bro is there any guidance on a real example of how to facilitate the workshop? For example, if I use a board or post its, what do I tell the attendants to fill in them?..etc

@shuchisharma3994 2 жыл бұрын

As per my understanding, interview sessions, questionnaires, workshops are different type of req gathering. Am I correct? If it is so…. How a BA decides to opt which req gathering technique for which project?

@ThePrefectBA 2 жыл бұрын

It depends on the project and situation. For example, if the assigned time is less then workshop works the best. If all the stakeholders are not available for discussion together then interview works well. You will get to know which one to select with experience..

@greeppl 2 жыл бұрын

@@ThePrefectBA Would you use say... questionnaire in the first place & then a workshop (for a more in-depth) req. gathering session? (assuming you had enough time - or there is too much overlap so it's either or? Thanks

@happyhero1093 10 ай бұрын

@@greeppl It depends again as Questionnaire would be ideal for trying to elicit requirement from a large number of client/customers. If you have time then Interview works pretty well as you tend to build rapport & relationship with the stakeholder on a one to one basis. The stakeholder is more relaxed and able to express themselves properly. Workshop I find to be the most effective when there is no time as you can get an approval on the spot and if its a situation where stakeholders arent available in person, then you can gather everyone virtually and elicit requirements there and not only that, you get thier validation and approval.

@deepakdkrishna1854 2 жыл бұрын

This is EP2, can you share the EP1 of this topic - Requirements Gathering | Workshop - Gather Requirements in 12 Steps

@ThePrefectBA 2 жыл бұрын

Hello Deepak, Check this below video link kzfaq.info/get/bejne/q9dhZ8tpurDbko0.html We have merged all the 3 episodes to the single video

@MrLemonhaze20 5 жыл бұрын

A part of a BAs job is running workshops. How does this fit into scrum? Im slightly confused. I have learned about scrum, workshops, ux, user stories. In what order does all this come together?

@ThePrefectBA 5 жыл бұрын

Hello, Let me try to simplify and answer your question. 1.First off for any change initiative you would have a workshop with all the relevant stakeholders and get their requirements. This will be recorded by the scribe in the workshop. 2.Next step is if the scrum methodology is used then the requirements captured from the workshop will be translated to Epics & user stories.This will form your product backlog 3.Then, once your product backlog is created then the highest value User stories are prioritised and then delivered across multiple sprints. Hope this helps

@RR-tf8ic 4 жыл бұрын

@@ThePrefectBA your an asset to the aspiring BA community ! Keep up the great work.

@ThePrefectBA 4 жыл бұрын

Thanks a lot for your kind words. Much appreciated and helps us to keep going

@OldManOnTrak 2 жыл бұрын

Interesting. This format seems to be ignoring a few things: 1) That you can gather all the stakeholders in the same place for a full day in order to gather ALL of the requirements. 2) That stakeholders know what they want at the time of the workshop. Requirements have a habit of changing as the project proceeds. 2) Getting someone to 'sign off' requirements creates a contractual relationship between users/customers and the solution developers that leads to a blame culture whenever something is misunderstood or mistakes happen... which is almost inevitable. It is also used by developers as an excuse to ignore any user need identified after the workshop because "it's not in the requirements document" and creates a mess of change management that isn't really necessary. Want to know more? Let me know

@sandyboy388 2 жыл бұрын

Please do share.

@funkywarrior3906 Жыл бұрын

yes post more

@OldManOnTrak Жыл бұрын

@@testforzeta2757 In my experience, “change control” is effectively change avoidance. And ignoring a business need to change a requirement is like knowing your Sat nav is sending you down the wrong road, but following it anyway. It’s stupid.