# Requirements Gathering Interview Template

- The goal is to collect comprehensive information about stakeholders' needs, expectations, and constraints to inform project requirements accurately.   These items can be initially basic and refined over time, but they should capture all identified requirements from the interview.  How to Conduct a Requirements Gathering Interview

## How to Conduct a Requirements Gathering Interview

### Preparation

- Identify Stakeholders: Determine who needs to be interviewed, such as business users, project sponsors, managers, QA personnel, and compliance staff.
- Research: Understand the project's background and its impact on stakeholders.
- Define Objectives: Clarify what information you need from each stakeholder based on their role.
- Prepare Questions: Customize the interview questions to fit the stakeholder's role and the project's context.
- Logistics: Schedule the interview and inform the stakeholder about its purpose and expected duration.

### During the Interview

- Explain the Purpose: Start by clearly stating why you're conducting the interview and what you hope to achieve.
- Establish Rapport: Build a comfortable environment to encourage open communication.
- Ask Open-Ended Questions: Use questions that prompt detailed responses rather than simple yes/no answers.
- Active Listening: Pay attention to the stakeholder's answers and ask follow-up questions as needed.
- Document Responses: Take thorough notes or record the conversation (with permission) for accuracy.

### After the Interview

- Review Notes: Go over your notes promptly to ensure clarity and completeness.
- Create Requirement Work Items: For each requirement discussed, create a Requirement Work Item in Azure DevOps.
- Follow-Up: If necessary, reach out for clarification on any ambiguous points.
- Validation: Send a summary to the stakeholder to confirm understanding and accuracy.

## Interview Questions

### General Questions

- Role Understanding:
  Can you describe your role and responsibilities within the organization?
- Project Involvement:
  How does this project relate to your work or department?
- Objectives:
  What are the main goals you want to achieve with this project?
- End-Users:
  Who will be the primary users of this system or service?
- Current Challenges:
  What problems or challenges are you currently facing that this project should address?

### Functional Requirements

- Features and Functions:
  What specific features or functionalities do you need the system to have?
- Processes:
  Can you walk me through a typical workflow or use case?
- Tasks:
  What tasks must the system enable users to perform?
- Automation:
  Are there manual processes that could be automated through this system?

### Non-Functional Requirements

- Performance:
  What performance criteria should the system meet (e.g., speed, responsiveness)?
- Security:
  Are there any security requirements or concerns we should be aware of?
- Scalability:
  How should the system handle growth in users or data volume?
- Reliability:
  What uptime or availability is expected for the system?
- Compliance:
  Are there industry standards or regulations we need to comply with?

### User Interface and Experience

- Design Preferences:
  Do you have any preferences or standards for the user interface design?
- Accessibility:
  Are there any accessibility requirements we need to consider?
- User Training:
  What kind of training or support will users need?
- Localization:
  Will the system need to support multiple languages or regions?

### Data and Integration

- Data Requirements:
  What data needs to be captured, stored, and processed by the system?
- Existing Systems:
  Are there current systems or databases that need to integrate with this project?
- Data Migration:
  Is there existing data that needs to be migrated to the new system?
- Data Privacy:
  What data privacy and protection requirements must be followed?

### Constraints and Assumptions

- Budget and Timeline:
  Are there any budget or time constraints we need to consider?
- Technological Constraints:
  Are there specific technologies or platforms we must use or avoid?
- Assumptions:
  What assumptions are we making that need to be validated?
- Resource Availability:
  What resources (personnel, equipment) are available or limited?

### Success Criteria

- Measuring Success:
  How will you measure the success of this project?
- Key Outcomes:
  What outcomes are most important to you?
- KPIs:
  Are there specific Key Performance Indicators we should track?

### Risks and Challenges

- Potential Obstacles:
  What risks or potential challenges do you foresee?
- Risk Mitigation:
  Do you have suggestions for mitigating these risks?
- Dependencies:
  Are there dependencies on other projects or initiatives?

## Tips for Effective Interviews

- Be Prepared:
  Familiarize yourself with the stakeholder's background and the project's context.
- Build Trust:
  Be respectful and professional to encourage honest and open dialogue.
- Clarify and Summarize:
  Restate key points to confirm understanding.
- Stay Flexible:
  Be prepared to explore new topics that arise during the conversation.
- Avoid Jargon:
  Use clear language and explain any necessary technical terms.
- Manage Time:
  Keep track of time to cover all essential questions without rushing.
- Seek Permission:
  Always ask before recording the interview or sharing sensitive information.
- Follow Ethical Guidelines:
  Respect confidentiality and handle all information appropriately.
