The review is based on the impact analysis work, which is performed prior to this task. A Chief Engineer may assist the Project Manager in this task, along with a more formal Change Control Board (CCB) review and approval. The actual approval process is not mandated, but it is a recommended practice to perform a review and approval at this stage, prior to new development work streams created and actual development work started. At the end of this task, the request will be approved or rejected. It is also possible that individual system components are de-scoped, and an organization may need to go through a few iterations of impact analysis and review, until a all approval decisions are reached.

Preconditions:

• Impact analysis has been performed and reported for a new product variant request

Postconditions:

• Product variant request approved or rejected
• Changes to individual components may be de-scoped, if feasible

While the review and approval process should primarily take place in your Change Management application, you may also want to mark product configuration as approved or rejected in your product definition tool.

In your product definition tool, use meta-data or attribute of a product to mark them as “Scope Approved=Yes”, or a similar property name and value. This way a Configuration Lead can recognize that a particular product configuration has been impacted and approved by the variation in the new product variant, and consequently, may need to be reconfigured to enable future development work (i.e. new development streams will need to be provided for approved components).