Adding "Code review" starting copy

[edmullen]

This language is copied from the EIS-R (DPA) repo. It serves as a good starting point that OCS can use to define the way they intend to conduct code reviews during the Dashboard procurement.

OCS can use this as their starting point and use as much as is useful and change as much as necessary. @cnelsonakgov could share insights on how it has worked for the EIS-R (DPA) project.

[edmullen]

@waldoj I'd like you to take a look at this. I'm copying the DPA code review language to the OCS repo. I want to be sure this all remains valid. Can you please review and let me know what state it's in.

• If it all applies, great.
• If small changes are needed, please make them.
• If extensive changes are needed, let me know.

[cnelsonakgov]

This process worked very well for the EIS-R (DPA) project:

• We used the checklist and pulled this document up before every sprint code review for reference.
• The process accommodates the VSTS workflow nicely.
• It's a living document -- as our code reviews evolved, we modified it to reflect that
• Enabled us to be more confident that we could build and manage the code at the end of the project

[waldoj]

Yeah, what Curtis said. :) I think this is all likely to apply, but it really is best to regard it as a living document. We freely edited it as we found that reality didn't match our intentions.