Requirements Are Simply Requirements—or Maybe Not Prior Year Content
When talking about requirements, people 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 yet another has a different approach. These “experts” seem unaware of the critical inconsistencies of their positions. No wonder getting requirements right remains a major challenge on many projects. Robin Goldsmith analyzes several often conflicting and 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. With this structure you can more easily see where user stories do—or do not—fit, identify pitfalls of the “as a <role>” format, and reconcile some of the conflicts between user stories, features, use cases, and requirements.