| Full title | Track the changes in relevant artifacts |
|---|
| Objective | Define procedures for tracking changes in internal and external artifacts |
|---|
| Applicability | This practice spans across entire project. |
|---|
| Context | This practice applies to all projects. |
|---|
| Addressed elements in SMM | 2.5. Software and configuration changes
|
|---|
| Actions | - 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 development); 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 training.
- Balance simplicity and rigour (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
|
|---|
| Risks | - The level of rigour 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.
|
|---|
| Related practices | |
|---|
