Create the Code Analysis Guidelines early in the project. See Coding Standard for tips on creating good coding guidelines.
Review the coding guidelines at regular intervals, such as during iteration assessments or after baselines have been
created. This can be done as a quick agenda item asking of it would be useful to change or add any coding guidelines.
Some guidelines may be useless and can be dropped. There may be new guidelines that would be helpful that can be
adopted. Or existing guidelines may need to be better enforced.
When adopting new guidelines or changing guidelines, the team will need to consider if they want to apply those
guidelines to existing code. The benefit of doing so may not outweigh the cost and inconvenience of changing existing
code. It may be worth using the guidelines on new code (and fixes to existing code), and asking later if the new
guidelines provide enough value to change existing code.
|