Project configuration management requires tracking and controlling changes to important project documents, products and assets.¿What Software do you recommend for Configuration Management? Saving Changes...
There are multiple aspects of configuration management that can use different tools to right-size the solution.
For basic project documents that only need to survive the duration of the project like working schedules, some things can be handled as simply as using a pre-defined set of file structures and file names so that the latest always has the same name and location supporting links, and each old version gets archived with key metadata like the implementation date.
The software itself can be undergoing a high degree of change activity, and managing that configuration can be very time consuming. Databases like Access can be a good tool for that because you start building a lot of records as you add functionality and resolve bugs on a variety of different bits of software developed by different sub-teams. The ability to track things like whether all the right people have reviewed the latest versions is a lot easier if you can build the right queries.
...
1 reply by Verónica Elizabeth Pozo Ruiz
May 07, 2021 12:44 PM
Verónica Elizabeth Pozo Ruiz
...
Thanks Keith, the idea of a set of file structures is useful for simple projects
Saving Changes...
Stephanie SyMarketing| Software TestedWi, United States
You should also think about how secure your configuration management tools are and whether you are giving them access to too much sensitive information.
...
1 reply by Verónica Elizabeth Pozo Ruiz
May 07, 2021 12:39 PM
Verónica Elizabeth Pozo Ruiz
...
Thanks, Stephanie, it's an important consideration
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Veronica,
configuration management deals mainly with product scope, the deliverables and the states they go thru (e.g. design-code-test). You may consider project management artefacts worthy of controlling as part of the scope and include them in the configuration mgmt.
Different industries have different types of scope which have led to different tools, e.g. construction (BIM tools), automotive (IBM Doors), SW development. Sometimes it is also called requirements engineering (RE), as all scope starts with requirements.
You should also think about how secure your configuration management tools are and whether you are giving them access to too much sensitive information.
Thanks, Stephanie, it's an important consideration Saving Changes...
There are multiple aspects of configuration management that can use different tools to right-size the solution.
For basic project documents that only need to survive the duration of the project like working schedules, some things can be handled as simply as using a pre-defined set of file structures and file names so that the latest always has the same name and location supporting links, and each old version gets archived with key metadata like the implementation date.
The software itself can be undergoing a high degree of change activity, and managing that configuration can be very time consuming. Databases like Access can be a good tool for that because you start building a lot of records as you add functionality and resolve bugs on a variety of different bits of software developed by different sub-teams. The ability to track things like whether all the right people have reviewed the latest versions is a lot easier if you can build the right queries.
Thanks Keith, the idea of a set of file structures is useful for simple projects Saving Changes...
configuration management deals mainly with product scope, the deliverables and the states they go thru (e.g. design-code-test). You may consider project management artefacts worthy of controlling as part of the scope and include them in the configuration mgmt.
Different industries have different types of scope which have led to different tools, e.g. construction (BIM tools), automotive (IBM Doors), SW development. Sometimes it is also called requirements engineering (RE), as all scope starts with requirements.
