How to Elicit (Gather) Requirements

February 2, 2013 Foundation 2 Comments

Techniques for Getting Business and Stakeholder Requirements from Subject Matter Experts

Course Duration:
Traditional Classroom: 2 days
Virtual Workshop: 14 hours total, flexible scheduling

Contact Us
to get this course tailored to your needs

list of upcoming eventsView currently scheduled online and face-to-face classes
Please send me a personal e-mentoring offer for this class
View other scheduling options


IIBA® Endorsed Education Provider - Endorsed Course

Earn 14 PD/CDUs toward IIBA® and PMI certification
Contact us to schedule this class or tailor it to your needs (included in our price).

The International Institute of Business Analysis (IIBA®) in their Business Analysis Body of Knowledge® (BABOK® v2.0) defines four major categories of requirements that are common to information technology projects:

  • Business requirements define the goals and objectives that any IT solution has to support.
  • Stakeholder requirements specify the needs of individuals or groups.
  • Solution requirements describe functions, information, and specific qualities that the delivered technology has to enable.
  • Finally, transition requirements define behaviors that facilitate moving from the as-is state of the enterprise to the to-be state.

This course gives you a proven set of core techniques, methods, and tricks to elicit (gather or capture) business, stakeholder, solution, and transition requirements. Requirements elicitation is more than simply asking stakeholders what they want. The course offers a variety of techniques that force stakeholders to consider different dimensions of the solution, which helps them recognize and express requirements they did not know they had.

NOTE: The techniques taught in this course are methodology-neutral, meaning they are relevant to traditional, UML or Agile development environments. This instructor-led course can be delivered in a series of virtual sessions via the Internet or live your site.

IIBA®, the IIBA® logo, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. These trademarks are used with the express permission of International Institute of Business Analysis.

Learning Objectives

  • Classify the 5 types of requirements described in the BABOK®
  • Identify the value of good requirements
  • Evaluate a management vision statement
  • Write business requirements that solve business problems
  • Creates requirements during "analysis by walking around"
  • Prepare, perform and follow up requirements interviews
  • Develop and process surveys
  • Use 10 critical requirements questions to guide the requirements capture process
  • Contrast the pros and cons of prototyping for requirements
  • List the components of a user story
  • Explain the strengths and weaknesses of user stories
  • Identify the appropriate time to use user stories
  • Explain the pros and cons of alternative ways to manage user stories
  • List techniques for gathering user stories
  • Describe how user stories support testing
  • Describe what makes a "good" user story
  • Create business event/response tables
  • Develop requirements based on business events and responses
Detailed View

1 Introduction to Business Analysis

Requirements Defined

2 Requirements Elicitation (Capture)

Who Do You Talk to about What?

Document Analysis

Business Problem Definition and Analysis

Effective Interviewing Techniques

Requirements Workshops

Using Surveys to Elicit Requirements

Analysis by Walking Around (Site Visits)

Requirements Elicitation Critical Questions

Considering Prototyping

3 Introduction to User Stories

What Are User Stories

What Are Roles in User Stories

5 Techniques for Gathering User Stories

How Do You Get to User Stories

6 User Stories Focus on the Business

What Makes a User Story Good

7 User Stories and Acceptance Testing

From User Stories to Test Scenarios

8 User Stories Summary

User Story Qualities

9 Event-based Requirements Elicitation

Business Event/Response Analysis

Anyone involved in defining or deciphering business system requirements, including:
  • Product Owners
  • Subject Matter Experts
  • Project Leaders
  • Process Managers
  • Requirement Analysts
  • Requirement Managers
  • Project Managers
Contact Us
to get this course tailored to your needs
About author:

Tom has been in business analysis since long before it was called business analysis. He has over 30 years experience in the fields of information technology, methodologies, and business analysis. In his writings and lectures he strives for enlightening while entertaining. As a facilitator, he achieves results through inclusion and synergistic group-building. He has taught thousands of students business and systems analysis skills since the '80's and has facilitated hundreds of requirements discovery sessions under a variety of acronyms (JAD, ASAP, JADr, JRP, etc.).

2 Responses to “How to Elicit (Gather) Requirements”

  1. claire says:

    hi, how much is this course and is it elearning? thanks

Leave a Reply

Sorry, you can not to browse this website.

Because you are using an outdated version of MS Internet Explorer. For a better experience using websites, please upgrade to a modern web browser.

Mozilla Firefox Microsoft Internet Explorer Apple Safari Google Chrome