Configuration Item Record

From PRINCE2 Agile wiki
Jump to: navigation, search


The state of the Configuration Item Records are somehow different in Agile environment for two main reasons:

  1. Adaptation
    • The whole configuration is not clear at the beginning, and the product is supposed to evolve during the project. Therefore, the Configuration Management Items also evolve during the project, instead of being composed upfront and updated later.
    • The existing items are subject to change. So, it might be a good idea to keep the items high-level to allow for a certain level of change without frequent changes in the database.
  2. Dependencies
    • One of the uses of a configuration management system is to store the dependencies between items, so that we can check how changes in one item might influence the rest, and understand the consequences of change requests. In a perfect Agile environment with well-defined items, the dependencies are minimal or totally removed, and therefore, there won't be a need for this application of the configuration management.

On the other hand, since Agile is mostly used with IT development and this kind of projects always need a proper versioning, it's a good idea to implement a simple configuration management system along with the versioning system.

Process Model

PRINCE2 Agile Process Model state13.png



  • The above image assumes that Scrum is used in the delivery level, which is not necessary.
  • The number of stages, releases, and Sprints are just examples, as well as the exception in the third stage.
  • The diagram is schematic and many details are not shown.

See Also

External Links