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 well
simply put, process for ensuring agreement on a functional design change
In order to have GOOD REQUIREMENTS and make a great product,
it is essential to have and to follow a simple, effective, and efficient RDM process.
Below is a reference model of one.
Below is a reference model of one.
![]() |
|---|
Reference Model Extended Notes
In this reference model, the whole product team owns the product.
The whole product team—and only the product team— is responsible for requirements definition (RD.)
Business process owners (BPOs) and subject matter experts (SMEs) are a part of the product team and define the product's business requirements and business rules.
The product's business product managers (BPMs) and IT business analysts (ITBAs) facilitate requirements.
The product's chief solutions architect (CSA) makes the final decisions on the product's functional design, i.e., on the product's systems requirements. (In the absence of one, the product's design becomes an ad hoc — or even worse, a consensus — activity.)
The CSA is a member of the product functional design team and of the change management core team (CMCT.) The product functional design team comprises both Business and IT. The CSA is the head of the product functional design team — and is an IT role.
The CSA is a member of the product change control board (PCCB) also.
The product change control board (PCCB) owns the product vision.
The PCCB is a part of the product team — and is a Governance (a self-governance) role.
The PCCB can demand or overrule any requirement.
The change management core team (CMCT) has representative from every unit of the product team and is the eyes of the product team.
The Goal is to meet business needs well!
The whole product team—and only the product team— is responsible for requirements definition (RD.)
Business process owners (BPOs) and subject matter experts (SMEs) are a part of the product team and define the product's business requirements and business rules.
The product's business product managers (BPMs) and IT business analysts (ITBAs) facilitate requirements.
The product's chief solutions architect (CSA) makes the final decisions on the product's functional design, i.e., on the product's systems requirements. (In the absence of one, the product's design becomes an ad hoc — or even worse, a consensus — activity.)
The CSA is a member of the product functional design team and of the change management core team (CMCT.) The product functional design team comprises both Business and IT. The CSA is the head of the product functional design team — and is an IT role.
The CSA is a member of the product change control board (PCCB) also.
The product change control board (PCCB) owns the product vision.
The PCCB is a part of the product team — and is a Governance (a self-governance) role.
The PCCB can demand or overrule any requirement.
The change management core team (CMCT) has representative from every unit of the product team and is the eyes of the product team.
The Goal is to meet business needs well!



)