To understand how we must manage requirements, we must first understand the definition of requirements management.
Requirements management focuses on two critical aspects:
1、Understanding the goals of the organization and its customers.
2、Transforming these goals into potential functions and constraints applicable to the development and evolution of products and services.
Based on this definition, one can allude that we need “a systematic approach to eliciting, organizing and documenting the requirements of the system, and establishing and maintaining agreement between the customer and the project team on the changing of requirements of the system.” How can we achieve this?
To demonstrate, let’s look at Step 1, a simple high level process flow for requirements management:
An approach that Online Business Systems’ (OBS) Alberta Region Business Analysis practice is attempting to distill amongst its Business Analysts is the OBS Overarching Model (OOM). In Step 2, we embody this model in our psyche every time we engage stakeholders. If we constantly have this model in mind when collecting requirements, it will help to convert many ambiguous requirements to unambiguous requirements.
1、Understand Requirement Management Process Flow
2、Adopt the OBS Overarching Model
3、Use PMBOK’s Collect Requirements Tools & Techniques
4、Communicate to stakeholders
As a result, managing requirements can be a breeze.