update: Requirements Engineering Prozess dokumentiert und Beispiel-Fragebogen angepasst.

requirements-gathering-interview.md

@@ -1,63 +1,137 @@
-# Requirements Gathering Interview
+# Requirements Gathering Interview Template
 
-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.
+- 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
 
-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?
+## How to Conduct a Requirements 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.
+- 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.
 
-### Conducting the Interview
+### During 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.
+- 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
 
-- 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?
+- 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
 
-- 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?
+- 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
 
-- 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?
+- 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
 
-- 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?
+- 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
 
-- 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?
+- 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
 
-- 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?
+- 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
 
-- 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?
+- 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.