Configuration Item Record
Configuration Item Records are somehow different in Agile environments for two main reasons:
- 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 more 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.
- 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 configuration management.
On the other hand, since Agile is mostly used with IT development and this kind of projects always needs a proper versioning system, it’s a good idea to implement a simple configuration management system along with the versioning system and the asset management system.
- Change theme
- Configuration Item Record in PRINCE2 wiki
Written by Nader K. Rad
This is (and will be) a work in progress: More details will be added in the future, depending on the feedback.
This wiki is developed and managed by an accredited trainer, independent of AXELOS. While aligned with their guidelines, it’s not an official resource.