Who is responsible for identifying and establishing non-functional requirements?

The responsibility for identifying and establishing non-functional requirements typically lies with system and solution architects. These professionals have a comprehensive understanding of the overall system architecture, technical constraints, and performance needs that help to define non-functional requirements such as scalability, reliability, security, and maintainability.

Non-functional requirements are essential for ensuring that a system operates effectively and meets the expectations of both users and stakeholders. Since system and solution architects focus on the technical aspects and integration of various components, they are best positioned to define these requirements upfront in the development process. Their expertise allows them to establish a clear understanding of what is necessary for the system to perform well in real-world scenarios, ensuring that the sustained quality and performance standards are maintained.

While product owners and product managers play a crucial role in defining the product vision and user requirements, and development teams implement these requirements in a practical manner, the technical aspect of non-functional requirements is distinctly aligned with the role of architects. Agile coaches, on the other hand, support teams by facilitating the agile process and fostering a culture of continuous improvement but are not directly involved in setting specific requirements like non-functional aspects.