Documenting, analyzing & eliciting requirements is a core skill every Product Manager should possess.

1. LET'S TALK ABOUT
PREPARED BY TUNDE ADENIRAN
REQUIREMENT
ELICITATION,
ANALYSIS &
DOCUMENTATION
THE IMPORTANCE OF

2. OVERVIEW
A QUICK
Requirements Elicitation
Gathering Techniques
Requirement Types
Interviewing Stakeholders
INTRODUCTION

3. SOME REQUIREMENT ELICITATION TECHNIQUES
INTERVIEWS
DOCUMENT
ANALYSIS
FOCUS GROUPS
OBSERVATION BRAINSTORMING INTERVIEWS

4. INTRODUCTION
REQUIREMENT
SPOTTING A GOOD
UNDERSTANABLE
CORRECT
CLEAR
VERIFIABLE
FEASIBLE
NECESSARY
UNAMBIGIOUS

5. INTRODUCTION TO THE COURSE
REQUIREMENT?
WHAT'S A FUNCTIONAL
defines the function of a
system.
NON-FUNCTIONAL
specifies criteria that can be
used to judge the operation
of a system, rather than
specific behaviors.
A singular documented physical and
functional need that a particular
design, product or process must be
able to perform.

6. REQUIREMENTS
BEFORE YOU START GATHERING
WHO YOU ARE
as the interviewer, describe
your role in the organisation
and your role on the project.
WHY YOU ARE
THERE TODAY?
What the purpose of your visit
is with this stakeholder and
what you would like to
achieve (high level).
Example: Would it be OK with you if we ask you some
questions about your role in the organisation and
how you would like the new system to provide?
REQUEST
PERMISSION TO
ASK SOME
QUESTIONS

9. SOME INTERVIEW TIPS
First aim to get the basic facts about the stakeholder and his or her organization
(whether that’s just one department or the entire company).
Ask one or two colleagues to review the interview questions you’re planning to ask.
By all means use this article as a starting point for developing a customized script to
use during the interview, but remember that it’s not important to slavishly follow that
script.
To keep your interview script from becoming a hindrance rather than a help,
remember that the goal is to get thorough and consistent input for the design of the
system.

10. SOME INTERVIEW TIPS - 2
Plan for follow-up questions and don’t be afraid to ask them if they occur to you
during the interview.
Design the interview form in a way that makes it easy for you to write down the
answers or enter them into a computer, or use recording equipment.
Remember that these techniques help you focus on the content of the discussion
and not the act of documenting it.

11. TIP: THIS IS A VERY EFFICIENT TECHNIQUE TO DIG DEEPER AND FIND OUT THE ROOT CAUSE.
INTRODUCTION TO THE COURSE
PROBLEMS
IDENTIFY
What problems do you run into in your day-to-day work?
Is there a standard way of solving it, or do you have a workaround?
Why is this a problem?
How do you solve the problem today?
How would you ideally like to solve the problem?
Keep asking follow-up questions (“What else is a problem for you?”,
“Are there other things that give you trouble?”) for as long as the
interviewee has more problems to describe.

12. INTRODUCTION TO THE COURSE
MAKE SURE YOUR
UNDERSTANDING
OF THE
STAKEHOLDER’S
PROBLEM IS
COMPLETE

13. INTRODUCTION TO THE COURSE
UNDERSTANDING
IS KEY
ASK SOME FOLLOWUP QUESTIONS
Why is it a problem?
How do you solve the problem today?
How would you ideally like to solve the problem?
How big is this problem compared to the
problems you have mentioned earlier?

14. INTRODUCTION TO THE COURSE
CLOSING
WHAT TO DO WHEN
Are there any other questions you think I
should be asking, or anything else you want
to tell me?
Can I contact you again if I need to ask some
follow-up questions?
Would you want to participate in a review of
the requirements later on?

15. INTRODUCTION TO THE COURSE
THANK
YOU!