Page tree
Skip to end of metadata
Go to start of metadata
ObjectiveInclude in the development cycle (as early as possible) activities that foster and improve maintainability of the product
Applicability

This practice spans across two phases of the project: development and maintenance.

Context

The practice applies to all projects, but in particular to the ones that are expected to be maintained in the long term.

Addressed elements in SMM

5.1. Planning and designing for maintainability

Prerequisites to applynone
Recommendation
  1. Monitor measures of maintainability for the product
    1. Consider using technical debt as the primary measure of maintainability
    2. Assign responsibility for monitoring the maintainability
    3. Provide training on writing maintainable code to the team members
    4. Report, manage and handle the issues related to maintainability
  2. Iteratively refactor the product
    1. Allocate time (preferably, in each development cycle) for managing the technical debt and code refactoring
    2. Provide training on refactoring to the team members
Risks
  1. Maintainability is not measured or the product is not refactored regularly
    1. The project becomes unmaintainable
    2. Technical debt increases
    3. Development of new features and fixing defects requires more and mode effort
Related practicesBP-B.5: Record and manage issues encountered with the product
SourceThis practice has been defined based on the literature, supported by the observation by the SwM team.
  • No labels