I would like to formalize some of the implicit ground rules we have on my team of developers.
To summarize, I have thought about the following sections :
-----------------
"performance report"
sending the weekly performance report each monday
"leave management"
sending an email to the team when booking leaves
and scheduling a handing over meeting
"quality of code"
following the code standards
using the provided code templates when creating a new sql table
using the provided control checklist when applying a script on production
-----------------
What are your thought about it ? Is this the correct document for this kind of information ?
Do you have any examples or template to complete it ?
What is your experience about using such a document ?
How did you introduce it to your team (so that it gets buy-in) ?
As these are ground rules most people on your team would already be aware of them and are probably already following these rules without realising it. Performance Report and leave management would fall under HR and are probably already contained in team members signed contracts so check first that contradictions do not exist between what the HR department is looking for and what you expect from them. Any deviations between this could lead to complications further down the line. One suggestion about performance report is to have team members send them to you on a Thursday evening so that you can use the Friday to assess work from the previous week and plan any issues that need to be addressed for the following week. Also it makes Mondays easy to deal with so you don't spend the morning dealing with reports. Make sure more than two people are in a handover meeting so that nothing is lost as some projects have a lot of local knowledge or 'ways of doing things' that have not been formalised. A strict and consistent quality of code should exist as this is were bugs creep into code and can slow down production of code. A expert programming principle of code writing could exist were code is produced in pairs and debugged and tested while its being written. Saving Changes...
