5 Powerful Requirement Gathering Techniques Every Business Analyst Should Know

Laura Brandenburg discusses five powerful requirements elicitation techniques for discovering requirements as a business analyst.

Simply put, elicitation is the process of discovering requirements. Elicitation often refers to engaging with stakeholders and understanding stakeholders needs and expectations when it comes to the scope and detailed requirements for a project. As a business analyst, it's important to have a variety of techniques in your toolkit for effectively gathering requirements. In this video, we'll cover 5 powerful techniques that every business analyst should know, which include:

1. Observation to gather requirements.
2. Diagram review as a business analyst.
3. Structured interviews with stakeholders.
4. In-depth documentation review.
5. Using a business analysis questionnaire.

By using these powerful requirement gathering techniques, you'll be able to effectively gather and document the requirements for any project as a business analyst. Have other requirements elicitation tips for business analysts that we didn’t cover? Let us know in the comments below!

Get a free copy of the requirements checklist mentioned in this video here:

Sign up for a free workshop to kickstart your success as a BA:

Connect with us on:

Bridging the Gap is an online business analyst training and certification provider helping you become a confident business analyst. On this business analysis channel, we provide consistent business analyst videos to keep you on track to success in your business analyst career. You’ll find videos on entity relationship diagrams, mistakes to avoid as a business analyst, business analyst techniques and strategies for your next project, and other business analysis tips and tricks.

Want to know what the business analyst experience is like, and what makes a good business analyst? Success starts with you, so subscribe to our channel today!

0:00 5 Powerful Requirement Gathering Techniques Every Business Analyst Should Know
0:50 What is Requirements Elicitation?
1:30 Technique 1: Observation as a Business Analyst
2:50 Technique 2: Diagram Review to Gather Requirements
4:00 Technique 3: Structured Interviews to Gather Requirements
5:20 Technique 4: Documentation Review as a Business Analyst
6:35 Technique 5: Using a Business Analysis Survey

#BusinessAnalysis #RequirementsElicitation #Business

[BridgingtheGapBA]

Get a free copy of the requirements checklist mentioned in this video here:

[GodsChildrenOnEarth]

Smaller sessions with a few stakeholders
1. Observation - ex. wathcing a user watching them do their work. BA asks questions such as ask the user to articculate what they are doing, share the business logic, ask about alternative scenarios
2. Diagram review or walthrough - also called prototyping. You can use a workflow diagram, use case, wireframe or an entity relationship diagram

3. Structured interview - the most commonly used technique. The interview is either on-on-one or with a small group of stakeholders. Virtual or in-person meeting, You want to be prepared with a meeting agenda. You want a requrements checklist.
4. Documentation review - analyze existing documentation. Helps you come up with questions for your structured interview. Don't overuse as it might not be updated or reflect actual stakeholder perspective.
5. Survey or Quiestionaire -

[gracebrown]

I got an awesome opportunity and this really helps. This is my first BA job. Thanks Laura

[cansucoskuner]

Wonderfully summarized the whole process. I can not put it into words like you! Now i can give examples in my star interviews❤🎉thanks a lot!

[moneeraarabic]

Your videos are amazing sincerely thank you!