qa-of-code-guidance
qa-of-code-guidance copied to clipboard
Emphasise documenting project development standards
In project documentation, projects should indicate which development standards they are applying (e.g. linking to the Duck Book)
We find that many teams reference the Duck Book as a general resource, but inconsistently apply the guidance from one project to another. This might be for good reason (i.e. proportionality) but appears to be because the expectation is not set clearly for developers