Requirements Are Simply Requirements—or Maybe Not Prior Year Content
People talk about requirements, use identical terms, and think they have a common understanding. Yet, one says user stories are requirements; another claims user stories must be combined with requirements; and another has a still different approach. These “experts” seem unaware of the critical inconsistencies of their positions. No wonder getting requirements right remains a major challenge for many projects. Robin Goldsmith analyzes often conflicting, not-so-shared-as-presumed interpretations of what requirements are, reveals likely implications, and challenges not-so-wise conventional wisdom. Robin describes a more appropriate model of REAL business requirements—whats that provide value when combined with product/system/software hows. He introduces the powerful Problem Pyramid™ systematic disciplined guide to help you more reliably get requirements right. The structure makes it easier to see where user stories do or do not fit, identifies pitfalls of the “as a <role>” format, and reconciles some of the conflicts between user stories, features, use cases, and requirements.