new: Requirements gathering beginners guide added.

requirements-gathering-interview.md

@@ -0,0 +1,63 @@
+# Requirements Gathering Interview
+
+This guide should help anyone in our team to conduct a requirements gathering interview and collect information about the needs, desires, and constraints of stakeholders.
+
+As an outcome we want to have Requirement work items in Azure DevOps. They can rather raw and empty but should be created for each requirement we gather. They can be refined later on.
+
+## How to Conduct a Requirement Gathering Interview?
+
+### Preparation
+
+- **Identify Stakeholders:** Determine who needs to be interviewed. This could include business-users, project sponsors and managers, and qa as well as csv staff.
+- **Research:** Understand the background of the project and the implication and impact of the project on the stakeholders.
+- **Define Objectives:** Know what you need to find out from the specific interview and stakeholder. Have clear focus and goals in mind. E.g. a business person will have different needs than a qa person.
+- **Prepare Questions:** Use this list of questions as a basis, adjust it to the stakeholder’s roles and the project’s context.
+
+### Conducting the Interview
+
+- **Explain the Purpose:** Clearly explain why you are conducting the interview and what you hope to achieve.
+- **Ask Open-Ended Questions:** Encourage detailed responses by asking questions that cannot be answered with a simple “yes” or “no”.
+- **Take Notes:** Document the key points of the conversation as Requirements in Azure DevOps.
+
+### General Questions
+
+- Can you describe your role and how it relates to this project?
+- What are the main goals you want to achieve with this project?
+- Who are the end-users of this product/service?
+- What problems or challenges are you currently facing that this project should address?
+
+### Functional Requirements
+
+- What specific features or functions do you need the system to have?
+- Can you walk me through a typical use case or workflow?
+- Are there any specific tasks that the system must perform?
+
+### Non-Functional Requirements
+
+- What performance criteria should the system meet (e.g. speed, reliability)?
+- Are there any security requirements or concerns we should be aware of?
+- What are the scalability requirements for the system?
+
+### User Interface and Experience
+
+- Do you have any preferences or standards for the user interface design?
+- Are there any accessibility requirements we need to consider?
+- What kind of user training or support will be necessary?
+
+### Data and Integration
+
+- What data needs to be captured, stored, and processed by the system?
+- Are there existing systems or databases that this project needs to integrate with?
+- What data privacy and compliance requirements must be followed?
+
+### Constraints and Assumptions
+
+- Are there any budget or time constraints we need to consider?
+- What assumptions are we making about this project that need to be validated?
+- Are there any risks or potential obstacles you foresee?
+
+### Success Criteria
+
+- How will you measure the success of this project?
+- What outcomes are most important to you?
+- Are there any key performance indicators (KPIs) that we should track?