Component Change Control

From IT frameworks

Jump to: navigation, search

Component Change Control

Everyone involved in the Project has the possibility to send in Request for Changes where a change to the Projects scope, resources, quality may be requested. A model to assess these RfCs should be implemented

The PRINCE2 framework needs to be flexible to allow Changes. All Changes must also trigger the Configuration Management component.

All RfCs should be dealt with as project issues. Changes must then be assessed for their potential impact:

Project outcome:

  • Costs
  • Benefits
  • Risks
  • Time
  • Resources
  • Priority

The Project Board must re-approve any changes to a product (BUS roles). The Product Based Planning technique may need reviewing:

  • Project Product Description
  • Product Breakdown Structure
  • Products Descriptions
  • Product Based Flow Diagram
Retrieved from "http://www.itframeworks.org/wiki/Component_Change_Control"
Personal tools