|Objective||Define procedures for tracking changes in internal and external artifacts|
This practice spans across entire project.
This practice applies to all projects.
|Addressed elements in SMM||2.5. Software and configuration changes|
|Prerequisites to apply||none|
- Identify relevant artifacts, processes, decisions and dependencies that need to be tracked
- Use (or adapt) commonly used approaches (e.g., git flow or trunk-based developement); creating a new approach is not recommended
- Consider different procedures for various processes/artifacts (depending on their relevance and the change-frequency of the items)
- Assign responsibilities and inform the team. Provide necessary trainings.
- Balance simplicity and rigor (ensure that the relevant changes are traceable without an excessive effort overhead).
- Monitor if the chosen approaches for tracking changes are consistently used.
- Use appropriate tools to support tracking the changes
- Give priority to the tools that are already available (and supported) in the organization
- The level of rigor does not correspond to the level of relevancy of artifacts
- Relevant dependencies cannot be identified and analyzed.
- Effort spent on tracking is partially wasted.
- Responsibility for tracking changes is not assigned
- The changes are not tracked or tracked in a chaotic way.
|Current use in teams|
This practice has been defined based on the survey.