Skip to main content
Wednesday, November 12, 2014 - 2:45pm - 3:45pm
Business Analysis & Requirements

Non-Functional Requirements: Forgotten, Neglected, and Misunderstood

Implementing non-functional 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 non-functional requirements up front, considering them less important or unrelated to user requirements; other teams specify them incompletely or with untestable and non-measurable attributes. Paul Reed introduces three types of non-functional 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 non-functional requirements in your product backlog. Join Paul in a fast-paced survey of key practices designed to help you discover and define holistic non-functional requirements for your agile project.

Paul Reed, EBG Consulting

Paul Reed, senior associate with EBG Consulting, has led agile teams working on complex products in companies of all sizes. Paul excels at helping companies transition to agile by leveraging an adaptive rollout strategy. He is a frequent conference speaker and author of Developing Applications with Java and UML and Developing Applications with Visual Basic and UML. A practicing Certified ScrumMaster, Paul offers hands-on experience in bringing real-world, sound architecture into the product lifecycle.

read more