Page tree
Skip to end of metadata
Go to start of metadata
ObjectiveDefine 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 SMM2.5. Software and configuration changes
Prerequisites to applynone
Recommendation
  1. Identify relevant artifacts, processes, decisions and dependencies that need to be tracked
    1. Use (or adapt) commonly used approaches (e.g., git flow or trunk-based developement); creating a new approach is not recommended
    2. Consider different procedures for various processes/artifacts (depending on their relevance and the change-frequency of the items)
    3. Assign responsibilities and inform the team. Provide necessary trainings.
    4. Balance simplicity and rigor (ensure that the relevant changes are traceable without an excessive effort overhead).
    5. Monitor if the chosen approaches for tracking changes are consistently used.
  2. Use appropriate tools to support tracking the changes
    1. Give priority to the tools that are already available (and supported) in the organization
Risks
  1. The level of rigor does not correspond to the level of relevancy of artifacts
    1. Relevant dependencies cannot be identified and analyzed.
    2. Effort spent on tracking is partially wasted.
  2. Responsibility for tracking changes is not assigned
    1. The changes are not tracked or tracked in a chaotic way.
Related practices
Current use in teams

This practice has been defined based on the survey.

  • No labels