Who in your team was responsible for gathering non-functional requirements in the subsequent project?

In a team, the responsibility for gathering non-functional requirements usually lies with a business analyst (BA) or a systems architect. Their task is to identify requirements related to performance, security, scalability, usability, and other aspects not directly related to functionality.

In some cases, this role may be performed by a team lead or a quality assurance (QA) engineer, especially if the team is small. It is important that the person responsible for non-functional requirements works closely with the customer and the technical team to understand and document these requirements correctly.