Implementing nonfunctional requirements is essential to build the right product. Yet teams often struggle with when and how to discover, specify, and test these requirements. Many teams neglect nonfunctional requirements up front, considering them less important or unrelated to user requirements; other teams specify them incompletely or with untestable and non-measurable attributes. EBG's Paul Reed introduces three types of nonfunctional requirements: interfaces; attributes including performance, usability, security, and robustness; and the environment for the product’s design and implementation. Paul helps you explore ways to visualize interfaces and value their options, examine techniques to specify quality attributes and their acceptance criteria, and consider environmental requirements. Leave with a better understanding of how these dimensions intertwine with functional requirements, and the challenges of incorporating nonfunctional requirements in your product backlog. Ellen shared a fast-paced survey of key practices and an exercise designed to help you discover and define holistic nonfunctional requirements for your agile project.