RDM Process
requirements definition and management (RDM) process: process for deciding what
changes to make to a product and when to make the changes—where change means a set of modifications to the
functional design of the product in order to address one or more business problems or meet one or more business needs
simply put, process for ensuring having agreement on a functional design change before making the change
A Simple, Effective, and Efficient RDM Process
To make GOOD REQUIREMENTS and make a great product, it is essential to follow a simple, effective, and efficient RDM process.
Below is a reference model of such a process:
 |
|---|
)
Twelve Principles of Effective Requirements-Decision-Making – – WholeTEAM RDM Process
In WholeTEAM, the product team owns the product.
Requirements definition (RD) is the responsibility of the whole product team—and of only the product team.
Business process owners and subject matter experts are a part of the product team.
IT business analysts (IT) and product managers (Business) are responsible for facilitating requirements.
The ultimate decision–maker on requirements is the product's chief solutions architect (CSA.) (In the absence of one, requirements-decision-making becomes an ad hoc — or even worse, a consensus — activity.)
The CSA is a member of the change management core team (CMCT) and of the product functional design team—and is an IT role.
The CSA is also a member of the product change control board (CCB.)
The CCB is a part of the product team—and is a Governance role.
The CCB owns the product vision.
The CCB can demand or overrule any requirement.
The CMCT has representative from every unit of the product team.
The CMCT is the eyes of the product team.
Requirements definition (RD) is the responsibility of the whole product team—and of only the product team.
Business process owners and subject matter experts are a part of the product team.
IT business analysts (IT) and product managers (Business) are responsible for facilitating requirements.
The ultimate decision–maker on requirements is the product's chief solutions architect (CSA.) (In the absence of one, requirements-decision-making becomes an ad hoc — or even worse, a consensus — activity.)
The CSA is a member of the change management core team (CMCT) and of the product functional design team—and is an IT role.
The CSA is also a member of the product change control board (CCB.)
The CCB is a part of the product team—and is a Governance role.
The CCB owns the product vision.
The CCB can demand or overrule any requirement.
The CMCT has representative from every unit of the product team.
The CMCT is the eyes of the product team.