How did you interact with stakeholders during requirements gathering and how did you document it?

Interaction with stakeholders during requirements gathering is usually based on regular meetings, interviews, and workshops. It is important to ask open-ended questions to understand the real needs and expectations of users and the business. Techniques such as user stories, use cases, and prototyping are used to clarify requirements.

Requirements are documented in the form of specifications, which may include:

• Text descriptions of functionality
• Diagrams (e.g., UML, BPMN)
• Tables with requirements and their priorities
• User stories with acceptance criteria

For convenience and transparency, specialized tools (Jira, Confluence, Trello) are often used, where requirements can be tracked, commented on, and linked to development tasks.