What did the process of working with requirements look like? What was input and what was output? Did you have a product owner?

The process of working with requirements usually begins with receiving initial data from the customer or product owner — these can be business goals, user stories, technical specifications, or simply a set of wishes.

Input:

• Business requirements
• Description of problems and goals
• User scenarios
• Constraints and assumptions

Then, analysis, clarification, and formalization of requirements take place. As a result, the output includes:

• A document with functional and non-functional requirements
• Models (e.g., UML diagrams, ER diagrams)
• Technical specifications

In our team, there was a product owner who acted as a link between the business and the development team. He was responsible for prioritizing requirements, clarifying details, and making decisions on functionality.

This approach helps ensure transparency, consistency, and quality control of requirements at all stages of development.