Another 4 core software requirements practices
Do you know of any software team that wouldn’t benefit from these practices? It’s unlikely.
Two previous articles described the six most important requirements practices that every software team should perform, as well as six more important requirements practices. Here are four more core practices that, again, virtually every software or systems development project will find valuable. This article is adapted from Software Requirements Essentials: Core Practices for Successful Business Analysis by Karl Wiegers and Candase Hokanson.
Practice #13: Identify empowered decision makers
Every project faces a continuous stream of decisions large and small. There are many types of requirements-related decisions. You’ll need to resolve conflicting requirements both within a user class and across user classes. You’ll have to resolve conflicting priorities among different stakeholder groups, set requirement priorities, and adjust them as reality happens. Quality attributes often conflict, demanding trade-off choices. And someone must define the scope of each development increment and elect when and how to modify that scope in view of new requirements, evolving business needs, and other factors.
