Last updated on December 16th, 2017 at 06:29 am
DuBrin define policies as “… general guidelines to follow when making decisions and taking action” [DuBrin 2016]. Some policies are written, some are unwritten. Some have names or identifiers, some don’t. For organizations seeking to gain control of technical debt, written policies are probably a good idea, for two reasons:
- Many people affected by technical debt policies are probably unfamiliar with the technical debt concept. A written policy is more likely to be communicated uniformly to everyone.
- The effort spent devising a written policy is likely to surface ambiguities, confusions, and varying needs. Resolving these issues during the policy formation process is better for the organization than resolving them during the deployment process.
A useful policy is clear. It uses terminology that is simple and well defined.