Vadim Tsapok:” Seven requirements elicitation techniques: real-life examples, strengths and limitations”

1. Seven Requirements
Elicitation Techniques
Real-life examples, strengths and limitations

2. CONTENTS
1. Disclaimer:
 Why 7?
 What is requirement? Just in case 
 What is elicitation and why not gathering?
 What is technique?
2. Techniques:
 (1) Benchmarking and market analysis
 (2) Concept modelling and mind mapping
 (3) Document analysis
 (4) Interface analysis
 (5) Process analysis
 (6) Prototyping
 (7) Survey or questionnaire
3. Q&A.

3. Disclaimer
 Why 7?
Magic 7 +/- 2 rule, most spread and commonly used techniques, and time limit of course.
 What is requirement? Just in case 
(BABOK definition) Requirement is a usable representation of a need.
 What is elicitation and how it differs from gathering?
Elicitation - iterative extraction of information from stakeholders or other sources. Why not
gathering:
o more proactive, less reactive
o “requirement” is not something that exists by default
o requires close collaboration with stakeholders
 What is technique?
Technique is a method (conceptually similar approaches) business analysts use to perform
business analysis tasks.

4. Requirements gathering vs elicitation

5. (1) Benchmarking and market analysis (description)
1. Benchmarking includes:
 identifying competitors
 analyze selected enterprises (survey, RFI, meetings or visits)
 determine gap between current and best practices
2. Market analysis contains:
 identifying customers and understanding their needs
 gathering market data and analyzing trends
Strengths Limitations
 New ideas, methods, tools to improve
existing functionality
 New features
 Targeting specific customer groups
− Cannot produce innovative solutions
− Time-consuming
− Requires expertise and experience

6. (1) Benchmarking and market analysis (example)

7. (2) Concept modelling and mind mapping (description)
Concept modelling together with mind mapping organize business vocabulary in a visual way.
1. Provide noun and verb (connections between noun) concepts.
2. Add categorizations, roles, if needed.
3. Organize mind-map with topics and sub-topics, branches, colors and images.
Strengths Limitations
 Business-friendly way to communicate with
stakeholders
 Summarizes thoughts, ideas (helpful for
presentations)
 Independent of data models
− Requires abstract thinking
− Can be difficult to communicate a shared
understanding of mind map

8. (2) Concept modelling and mind mapping (example)

9. (3) Document analysis (description)
1. Prepare: define materials, access content relevancy and credibility.
2. Review and analysis: conduct detailed review, add and sort notes (no conflicts or duplicates).
3. Record findings: topic, type, source, details, follow-up actions.
Strengths Limitations
 No need to create content
 Point of reference (current vs changed)
 Easy to review the findings
− Documentation should exist
− Outdated documentation
− Authors availability

10. Source: Display Ad Requirement Spec 2017-07-16.docx
(3) Document analysis (example)
# Topic Type Details Next steps
01 Definitions Question Products breakdown by
categories to be defined
Revise and approve the list
02 Supported ad units Constraint Only standard ad formats will
be supported
Update specification with a
note that custom ad formats
are not supported
03 Products visibility Assumption The only rule is to show /
hide products from other
marketplaces
Confirm assumption
04 Revenues reports Question Both DFP and back-end
system can serve as
revenues data source
Define the data source
05 Currencies Constraint Product price is set and
shown only in one currency.
Find a workaround for multi-
currency products

11. (4) Interface analysis (description)
Where, what, why, when, how, and for whom information is exchanged between solution components
(user interfaces, data integrations, APIs, etc.).
1. Prepare: understand which interfaces need to be identified (use other techniques, such as
document analysis, for instance).
2. Define: interface name and function, frequency of the usage, initial details, exchange method,
message format, etc.
Strengths Limitations
 Functional coverage increase on early stages
 Specifies business rules and constraints of
the solution
− No insights into other solution components
− 3rd parties dependency

12. (4) Interface analysis (example)

13. (5) Process analysis (description)
Assessment of the process efficiency and effectiveness, as well as opportunities of change.
1. Identify gaps: current vs desired future state.
2. Identify root cause: there might be multiple, inputs leading to the gap.
3. Generate options to improve or alternative solutions.
Strengths Limitations
 Ensures that solution addresses right issues
 Minimizing waste
− Time-consuming, requires SMEs
involvement
− High-level analysis might not reveal
problems in process

14. (5) Process analysis (example)
SIPOC model
Suppliers Inputs Process Outputs Customers
Google DFP
(Double Click for
Publishers)
DFP revenue
data
Revenue sharing
percentages
Revenue
distribution
calculation
Revenue report
Invoice
statements
Influencers
(inventory
owners)
Administrator
Export data
from DFP
Paste inputs
to Excel
Refresh
pivot tables
Reconcile
calculations
Distribute
reports

15. (6) Prototyping (description)
Defines stakeholder needs through iterative feedback process that creates design options or even
basis for development of the final solution.
1. Define approach: throw-away or evolutionary (functional) prototype.
2. Select method:
 Throw-away – paper, storyboarding, usability/visual prototyping.
 Functional – proof of concept, simulation, etc.
Strengths Limitations
 Visual representation of the future state
 Feedback provided early in the design
process
− Detailed prototypes may develop unrealistic
stakeholders expectations
− Focus on the design instead of
requirements

16. (6) Prototyping (example)

17. (7) Survey or questionnaire (description)
1. Prepare: define objective, target group, questionnaire type (close-ended or open-ended),
distribution and collection method, timeline for response, prepare questions, test survey.
2. Distribute: engage the audience.
3. Process results: summarize results and share with audience (if possible).
Strengths Limitations
 Quick
 Close-ended questions easy to quantify
 Open-ended questions provide insights and
ideas
− Response rate might be too low
− Open-ended questions processing requires
time
− Ambiguous questions may be left
unanswered or answered randomly

18. (7) Survey or questionnaire (example)
bit.ly/2CMqhhM

19. Thank you! Any questions?