Have you been tripped up by unspoken requirements? Product owners who can't articulate or simply don't talk about their expectations for usability, reliability, understandability, and all those other "ilities"? Do you know some of your "nonfunctional" requirements, but worry that you've missed some? Or perhaps your project has gotten those expectations on the table, but you're unsure whether to handle them as a user story, or in your Definition of Done, or in some other way. This paper demonstrates how to solve these quandaries by combining traditional tools for defining quality targets with modern agile methods. We'll present a checklist of nonfunctional requirements, a set of agile tools for incorporating those attributes into your project, and some criteria for deciding which tool to use in which circumstances. As a bonus, we'll also explore how to surface hidden quality requirements by developing a defect severity chart.
展开▼
