For deeper implementation, you may want to look into the or explore the authors' Atlantic Systems Guild for training resources.
This guide is based on the industry-standard established by Suzanne and James Robertson in their book, Mastering the Requirements Process: Getting Requirements Right . This framework is designed to help teams discover the true business problem and build the right solution, whether using Agile or traditional methodologies. 1. Project Blastoff: Defining the Foundation Mastering the Requirements Process: Getting - P...
Before a requirement is passed to developers, it must pass through a "Quality Gateway" to ensure it is: : It has only one interpretation. For deeper implementation, you may want to look
: Focus on external events that trigger a response from the business (e.g., "Patient books appointment"). : Move beyond "perceived" solutions to identify the
: Move beyond "perceived" solutions to identify the actual business need or opportunity.
: Use low-fidelity "sacrificial" prototypes (sketches, wireframes) to explore the problem space and test assumptions quickly. 3. Categorizing and Writing Requirements