Better Software East 2016 - Business Analysis & Requirements
Thursday, November 17
Requirements Are Simply Requirements—or Maybe Not
Many people talk about requirements. They 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 for many projects. Robin Goldsmith analyzes often conflicting, not-so-shared-as-presumed interpretations of what requirements are, reveals likely implications, and...
Identify Business Value before Business Requirements
According to the 2015 Standish report, a mere 29 percent of software development projects are successful. Is it because developers are choosing the wrong tools and processes? Is it due to a lack of communication between business leaders and developer teams? Although these issues may contribute to the failure of a project, they do not accurately address why these projects fail time and again. Lisa Calkins says the main reason projects are unsuccessful is a lack of planning between the initial application idea and the rush to set feature requirements. Instead,...