Project Information
| Project: |
PROJECT-NAME |
| Interviewer(s): |
PERSON-NAME
PERSON-NAME
|
| Interviewee(s): |
PERSON-NAME in DEPARTMENT
PERSON-NAME in DEPARTMENT
PERSON-NAME at PARTNER
|
| Date of Interview: |
YYYY-MM-DD |
| Interview Location: |
LOCATION |
| Related Documents: |
|
TODO: Copy this file once for each interview. Fill in the details
below. Link to each copy of this file from the "Notes from
Interviews and Brainstorming" section of the
user needs document.
Process impact: Planning questions for interviews
with stakeholders is key to effective requirements gathering. Good
requirements are needed to build the right system. These notes
should be kept as part of the documentation on
user needs are referred to when the
software requirements specification is written
or updated.
Interview Questions and Answers
TODO: Before the interview, plan the questions you will ask.
After the interview, type up the answers you received, any additional
questions and answers, and any new follow-up questions.
- How did you learn about the need for this product? What
business problem do you want solved?
- ANSWER
- What types of users are likely to use this product?
- ANSWER
- Can you give an example of how a user might actually use the product?
- ANSWER
- Do you expect the new system to be similar to an existing
product? How would it be the same or different?
- ANSWER
- What benefits are you expecting as a result of using the product?
- ANSWER
- Which of those expected benefits are the most important to you?
- ANSWER
- What do you think the priority of each of these proposed
enhancements should be?
-
- ENHANCEMENT-1: Essential | Expected | Desired | Optional
- ENHANCEMENT-2: Essential | Expected | Desired | Optional
- ENHANCEMENT-3: Essential | Expected | Desired | Optional
- ENHANCEMENT-4: Essential | Expected | Desired | Optional
- ENHANCEMENT-5
- ENHANCEMENT-5-A: Essential | Expected | Desired | Optional
- ENHANCEMENT-5-B: Essential | Expected | Desired | Optional
- Previously you requested FEATURE-1 and FEATURE-2. Today you
know more about the product, what is their priority now?
- FEATURE-1: Essential | Expected | Desired | Optional
- FEATURE-2: Essential | Expected | Desired | Optional
- Can you explain what the term PROJECT-SPECIFIC-TERM means to you?
- ANSWER
- How will this product change your business processes?
- ANSWER
- How will this product change your interactions with OTHER-STAKEHOLDER?
- ANSWER
- Is there any risk or downside to using the product? How do you
expect those potential downsides to be controlled?
- ANSWER
- QUESTION-1
- ANSWER-1
- QUESTION-2
- ANSWER-2
- QUESTION-3
- ANSWER-3
- QUESTION-4
- ANSWER-4
New Questions and Action Items
TODO: Often early interviews will raise more questions than they
answer. Note these new questions and what you must do to find the
answer.
- Can we do X?
- Do we support Y?
- Action item: research topic Z.
- Action item: Send follow-up email as per post-interview checklist.
- Action item: prepare for next interview with PERSON(S) on DATE.
Other Interview Notes
TODO: Note anything else that came out of the interview, either
explicitly or implicitly. Remember to confirm things that you
picked up implicitly if there is any doubt. E.g., make a note if
the interviewee uses an unusual meaning for a certain term. Add
links to any documents provided to you by the interviewee.