What method or format was used to communicate requirements within the team?

In teams working with Java, formal documents such as specifications in Markdown or Confluence format, as well as task management systems (Jira, Trello), are often used to communicate requirements. Within the team, requirements can be conveyed through User Stories, Acceptance Criteria, and UML diagrams. This approach helps to clearly structure tasks and ensure understanding between developers and clients.

Example of a User Story:

**As** a user
**I want** to be able to filter the list of products
**So that** I can quickly find the needed items

**Acceptance Criteria:**
- Filter by price
- Filter by category
- Update the list without reloading the page

Additionally, Agile practices such as daily stand-ups, sprint planning, and retrospectives are often used for discussing and clarifying requirements.