[thelist] setting team standards and guidelines

Martin Burns martin at easyweb.co.uk
Wed Apr 25 00:44:04 CDT 2012

On 24 Apr 2012, at 23:25, Matt Warden  wrote:

>  if the reason for the
> report is more than "I'm telling on you" (i.e., there is a legitimate
> reason to run it to make sure unchecked-in code isn't lost or
> something), it can be effective in getting the team to self-police.

I can't agree enough with this. Once the team (overall - doesn't have to be absolutely unanimous and wholehearted) has adopted a standard, pretty much the best way to get self policing is to make the reports and variances from standards visible to the team.

You may not even need much commentary - simply putting up: our standard is code should be checked in every day. Current average time between checkins: 2.5d. The team members meeting the standard will start asking why and working on the delinquents :-)


More information about the thelist mailing list